{"id":"CVE-2025-68780","aliases":["AZL-74495","BELL-CVE-2025-68780","DEBIAN-CVE-2025-68780","DLA-4476-1","DSA-6126-1","DSA-6127-1","EUVD-2026-2336","GHSA-386q-4477-2c5h","MGASA-2026-0017","MGASA-2026-0018","OESA-2026-1759","OESA-2026-1760","OESA-2026-1761","ROOT-OS-DEBIAN-11-CVE-2025-68780","ROOT-OS-UBUNTU-2204-CVE-2025-68780","ROOT-OS-UBUNTU-2404-CVE-2025-68780","SUSE-SU-2026:23881-1","SUSE-SU-2026:23887-1","SUSE-SU-2026:23897-1","SUSE-SU-2026:23902-1","UBUNTU-CVE-2025-68780","USN-8096-1","USN-8096-2","USN-8096-3","USN-8096-4","USN-8096-5","USN-8116-1","USN-8141-1","USN-8163-1","USN-8163-2","USN-8177-1","USN-8177-2","USN-8179-1","USN-8179-2","USN-8179-3","USN-8179-4","USN-8183-1","USN-8183-2","USN-8184-1","USN-8185-1","USN-8185-2","USN-8203-1","USN-8204-1","USN-8243-1","USN-8245-1","USN-8258-1","USN-8261-1","USN-8265-1","USN-8440-1","openSUSE-SU-2026:21910-1"],"status":"published","title":"sched/deadline: only set free_cpus for online runqueues","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\"sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u003eonline\") introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\"sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\") removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com\n\nAnother occurs when the last deadline task is migrated from a\nCPU that has an offlined runqueue. The dequeue_task member of\nthe deadline scheduler class will eventually call cpudl_clear\nand set the free_cpus bit for the CPU.\n\nThis commit modifies the cpudl_clear function to be aware of the\nonline state of the deadline runqueue so that the free_cpus mask\ncan be updated appropriately.\n\nIt is no longer necessary to manage the mask outside of the\ncpudl_set/clear functions so the cpudl_set/clear_freecpu\nfunctions are removed. In addition, since the free_cpus mask is\nnow only updated under the cpudl lock the code was changed to\nuse the non-atomic __cpumask functions.","severity":{"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","from":"osv"},"epss":{"day":"2026-11-10","score":0.00207,"percentile":0.10926,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2026-01-13T15:28:55Z","modified":"2026-11-11T09:39:20Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.121.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.161-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.65-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["5.15.198","6.1.160","6.6.120","6.12.64","6.18.3"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.162-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.69-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.18.3-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:Ubuntu:22.04","package":"linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","fixed_in":["5.15.0-203.213.aikido.119"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","fixed_in":["6.8.0-149.149.aikido.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","fixed_in":["5.15.0-1103.110~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","fixed_in":["5.15.0-1110.119~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","fixed_in":["5.15.0-1103.112~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-173.183~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1097.100~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1098.104~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-173.183~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1055.55~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1100.106~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1097.101~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-173.183"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1103.110"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1052.55~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","fixed_in":["5.15.0-1109.118"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1059.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","fixed_in":["5.15.0-1109.118.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1058.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","fixed_in":["5.15.0-1103.112"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1054.57~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","fixed_in":["5.15.0-1099.105"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1086.94"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-110.110~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","fixed_in":["5.15.0-1097.100"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1051.51~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","fixed_in":["5.15.0-1098.104"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1095.100"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-173.183"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-110.110.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","fixed_in":["5.15.0-1098.99"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1051.54~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","fixed_in":["5.15.0-1055.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1044.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1100.106"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1049.50~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","fixed_in":["5.15.0-1097.100"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-110.110~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1067.71"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1086.88"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1094.96"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1102.111"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1047.48~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1103.110+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1109.118+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-173.183+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1103.112+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-110.110"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1052.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","fixed_in":["6.17.0-1012.12~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1054.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","fixed_in":["6.17.0-1013.13~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","fixed_in":["6.8.0-1058.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","fixed_in":["6.8.0-1039.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1054.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","fixed_in":["6.17.0-1012.12~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1050.56"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1037.40"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","fixed_in":["6.17.0-22.22~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1051.51"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-110.110.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1051.54"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","fixed_in":["6.17.0-1018.18"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1051.54.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1022.22"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","fixed_in":["6.17.0-1020.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1049.50"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","fixed_in":["6.17.0-1011.11~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1052.56"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.17","fixed_in":["6.17.0-22.22.1~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1028.29"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1017.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2042.43"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1047.48"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","fixed_in":["6.17.0-1010.11~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1052.55+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1053.59+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-110.110+fips2"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1054.57+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux","fixed_in":["6.17.0-22.22"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-aws","fixed_in":["6.17.0-1012.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-azure","fixed_in":["6.17.0-1013.13"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-gcp","fixed_in":["6.17.0-1012.12"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-oracle","fixed_in":["6.17.0-1011.11"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-raspi","fixed_in":["6.17.0-1013.13"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-realtime","fixed_in":["6.17.0-1010.11"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-riscv","fixed_in":["6.17.0-22.22.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.121.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.159-r0"},{"fixed":"6.1.161-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.61-r0"},{"fixed":"6.12.65-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.0.0"},{"fixed":"5.15.198"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.160"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.120"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.64"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.3"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.162-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.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.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.69-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.18.3-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+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.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.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.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.2-1~exp1","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"]},{"source":"osv","ecosystem":"Debian:11","package":"linux-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.162-1~deb11u1"}]}],"versions":["6.1.106-3~deb11u1","6.1.106-3~deb11u2","6.1.106-3~deb11u3","6.1.112-1~deb11u1","6.1.119-1~deb11u1","6.1.128-1~deb11u1","6.1.129-1~deb11u1","6.1.137-1~deb11u1","6.1.140-1~deb11u1","6.1.147-1~deb11u1","6.1.148-1~deb11u1","6.1.153-1~deb11u1","6.1.158-1~deb11u1","6.1.159-1~deb11u1"],"bundled":252},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.69-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1~bpo12+1"],"bundled":251},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.162-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.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.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"],"bundled":252},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.120-1.mga9"}]}],"bundled":236},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.14-14.mga9"}]}],"bundled":236},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-88.mga9"}]}],"bundled":236},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.120-1.mga9"}]}],"bundled":236},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.127.oe2403"}]}],"bundled":85},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.139.oe2403sp1"}]}],"bundled":122},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.140.oe2403sp2"}]}],"bundled":85},{"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:Ubuntu:22.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:22.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-203.213.aikido.119"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"Root:Ubuntu:24.04","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-149.149.aikido.91"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1.160000.2.23"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1.160000.2.23"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1.160000.2.23"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1002.2","4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1009.9","4.4.0-1010.10","4.4.0-1011.11","4.4.0-1012.12","4.4.0-1014.14","4.4.0-1016.16","4.4.0-1017.17","4.4.0-1019.19","4.4.0-1022.22","4.4.0-1023.23","4.4.0-1024.25","4.4.0-1025.26","4.4.0-1027.30","4.4.0-1028.31","4.4.0-1029.32","4.4.0-1031.34","4.4.0-1032.35","4.4.0-1034.37","4.4.0-1036.39","4.4.0-1037.40","4.4.0-1038.41","4.4.0-1039.42","4.4.0-1040.43","4.4.0-1042.45","4.4.0-1044.47","4.4.0-1045.48","4.4.0-1046.50","4.4.0-1048.52","4.4.0-1050.54","4.4.0-1052.56","4.4.0-1054.58","4.4.0-1055.59","4.4.0-1056.60","4.4.0-1058.62","4.4.0-1059.63","4.4.0-1060.64","4.4.0-1061.65","4.4.0-1062.66","4.4.0-1064.68","4.4.0-1065.69","4.4.0-1066.70","4.4.0-1067.71","4.4.0-1073.77","4.4.0-1074.78","4.4.0-1075.79","4.4.0-1076.80","4.4.0-1077.81","4.4.0-1078.82","4.4.0-1081.85","4.4.0-1082.86","4.4.0-1083.87","4.4.0-1085.89","4.4.0-1086.90","4.4.0-1087.91","4.4.0-1088.92","4.4.0-1090.94","4.4.0-1091.95","4.4.0-1092.96","4.4.0-1093.97","4.4.0-1094.99","4.4.0-1095.100","4.4.0-1096.101","4.4.0-1097.102","4.4.0-1098.103","4.4.0-1099.104","4.4.0-1101.106","4.4.0-1102.107","4.4.0-1103.108","4.4.0-1104.109","4.4.0-1107.113","4.4.0-1109.115","4.4.0-1110.116","4.4.0-1111.117","4.4.0-1112.118","4.4.0-1113.119","4.4.0-1114.120","4.4.0-1115.121","4.4.0-1116.122","4.4.0-1117.123","4.4.0-1118.124","4.4.0-1119.125","4.4.0-1120.126","4.4.0-1121.127","4.4.0-1122.128","4.4.0-1123.129","4.4.0-1124.130","4.4.0-1125.131","4.4.0-1127.133","4.4.0-1128.134","4.4.0-1129.135","4.4.0-1130.136","4.4.0-1131.137","4.4.0-1133.139","4.4.0-1134.140","4.4.0-1135.141","4.4.0-1136.142","4.4.0-1137.143","4.4.0-1138.144","4.4.0-1139.145","4.4.0-1140.146","4.4.0-1141.147","4.4.0-1142.148","4.4.0-1143.149","4.4.0-1144.150","4.4.0-1145.151","4.4.0-1146.152","4.4.0-1147.153","4.4.0-1148.154","4.4.0-1149.155","4.4.0-1150.156","4.4.0-1151.157","4.4.0-1152.158","4.4.0-1153.159","4.4.0-1154.160","4.4.0-1155.161","4.4.0-1156.162","4.4.0-1157.163","4.4.0-1158.164","4.4.0-1159.165","4.4.0-1160.166","4.4.0-1161.167","4.4.0-1162.168"]},{"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","4.15.0-1209.224~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux-lts-xenial","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-13.29~14.04.1","4.4.0-14.30~14.04.2","4.4.0-15.31~14.04.1","4.4.0-18.34~14.04.1","4.4.0-21.37~14.04.1","4.4.0-22.39~14.04.1","4.4.0-22.40~14.04.1","4.4.0-24.43~14.04.1","4.4.0-28.47~14.04.1","4.4.0-31.50~14.04.1","4.4.0-34.53~14.04.1","4.4.0-36.55~14.04.1","4.4.0-38.57~14.04.1","4.4.0-42.62~14.04.1","4.4.0-45.66~14.04.1","4.4.0-47.68~14.04.1","4.4.0-51.72~14.04.1","4.4.0-53.74~14.04.1","4.4.0-57.78~14.04.1","4.4.0-59.80~14.04.1","4.4.0-62.83~14.04.1","4.4.0-63.84~14.04.2","4.4.0-64.85~14.04.1","4.4.0-66.87~14.04.1","4.4.0-67.88~14.04.1","4.4.0-70.91~14.04.1","4.4.0-71.92~14.04.1","4.4.0-72.93~14.04.1","4.4.0-75.96~14.04.1","4.4.0-78.99~14.04.2","4.4.0-79.100~14.04.1","4.4.0-81.104~14.04.1","4.4.0-83.106~14.04.1","4.4.0-87.110~14.04.1","4.4.0-89.112~14.04.1","4.4.0-91.114~14.04.1","4.4.0-92.115~14.04.1","4.4.0-93.116~14.04.1","4.4.0-96.119~14.04.1","4.4.0-97.120~14.04.1","4.4.0-98.121~14.04.1","4.4.0-101.124~14.04.1","4.4.0-103.126~14.04.1","4.4.0-104.127~14.04.1","4.4.0-108.131~14.04.1","4.4.0-109.132~14.04.1","4.4.0-111.134~14.04.1","4.4.0-112.135~14.04.1","4.4.0-116.140~14.04.1","4.4.0-119.143~14.04.1","4.4.0-121.145~14.04.1","4.4.0-124.148~14.04.1","4.4.0-127.153~14.04.1","4.4.0-128.154~14.04.1","4.4.0-130.156~14.04.1","4.4.0-131.157~14.04.1","4.4.0-133.159~14.04.1","4.4.0-134.160~14.04.1","4.4.0-135.161~14.04.1","4.4.0-137.163~14.04.1","4.4.0-138.164~14.04.1","4.4.0-139.165~14.04.1","4.4.0-140.166~14.04.1","4.4.0-141.167~14.04.1","4.4.0-142.168~14.04.1","4.4.0-143.169~14.04.2","4.4.0-144.170~14.04.1","4.4.0-146.172~14.04.1","4.4.0-148.174~14.04.1","4.4.0-150.176~14.04.1","4.4.0-151.178~14.04.1","4.4.0-154.181~14.04.1","4.4.0-157.185~14.04.1","4.4.0-159.187~14.04.1","4.4.0-161.189~14.04.1","4.4.0-164.192~14.04.1","4.4.0-165.193~14.04.1","4.4.0-166.195~14.04.1","4.4.0-168.197~14.04.1","4.4.0-169.198~14.04.1","4.4.0-170.199~14.04.1","4.4.0-171.200~14.04.1","4.4.0-173.203~14.04.1","4.4.0-174.204~14.04.1","4.4.0-176.206~14.04.1","4.4.0-177.207~14.04.1","4.4.0-178.208~14.04.1","4.4.0-179.209~14.04.1","4.4.0-184.214~14.04.1","4.4.0-185.215~14.04.1","4.4.0-186.216~14.04.1","4.4.0-187.217~14.04.1","4.4.0-189.219~14.04.1","4.4.0-190.220~14.04.1","4.4.0-193.224~14.04.1","4.4.0-194.226~14.04.1","4.4.0-197.229~14.04.1","4.4.0-198.230~14.04.1","4.4.0-200.232~14.04.1","4.4.0-201.233~14.04.1","4.4.0-203.235~14.04.1","4.4.0-204.236~14.04.1","4.4.0-206.238~14.04.1","4.4.0-208.240~14.04.1","4.4.0-209.241~14.04.1","4.4.0-210.242~14.04.1","4.4.0-211.243~14.04.1","4.4.0-212.244~14.04.1","4.4.0-213.245~14.04.1","4.4.0-214.246~14.04.1","4.4.0-215.247~14.04.1","4.4.0-218.251~14.04.1","4.4.0-219.252~14.04.1","4.4.0-221.254~14.04.1","4.4.0-222.255~14.04.1","4.4.0-223.256~14.04.1","4.4.0-224.257~14.04.1","4.4.0-227.261~14.04.1","4.4.0-229.263~14.04.1","4.4.0-230.264~14.04.1","4.4.0-231.265~14.04.1","4.4.0-233.267~14.04.1","4.4.0-234.268~14.04.1","4.4.0-235.269~14.04.1","4.4.0-236.270~14.04.1","4.4.0-237.271~14.04.1","4.4.0-239.273~14.04.1","4.4.0-240.274~14.04.1","4.4.0-241.275~14.04.1","4.4.0-242.276~14.04.1","4.4.0-243.277~14.04.1","4.4.0-244.278~14.04.1","4.4.0-245.279~14.04.1","4.4.0-246.280~14.04.1","4.4.0-248.282~14.04.1","4.4.0-250.284~14.04.1","4.4.0-251.285~14.04.1","4.4.0-252.286~14.04.1","4.4.0-253.287~14.04.1","4.4.0-254.288~14.04.1","4.4.0-256.290~14.04.1","4.4.0-257.291~14.04.1","4.4.0-258.292~14.04.2","4.4.0-259.293~14.04.1","4.4.0-260.294~14.04.1","4.4.0-261.295~14.04.1","4.4.0-262.296~14.04.1","4.4.0-263.297~14.04.1","4.4.0-264.298~14.04.1","4.4.0-266.300~14.04.1","4.4.0-267.301~14.04.1","4.4.0-268.302~14.04.1","4.4.0-269.303~14.04.1","4.4.0-270.304~14.04.1","4.4.0-271.305~14.04.1","4.4.0-272.306~14.04.1","4.4.0-273.307~14.04.1","4.4.0-274.308~14.04.1","4.4.0-276.310~14.04.1","4.4.0-277.311~14.04.1","4.4.0-278.312~14.04.1","4.4.0-279.313~14.04.1","4.4.0-280.314~14.04.1","4.4.0-281.315~14.04.1","4.4.0-283.317~14.04.1","4.4.0-284.318~14.04.1","4.4.0-287.321~14.04.1","4.4.0-288.322~14.04.1","4.4.0-289.323~14.04.1","4.4.0-290.324~14.04.1","4.4.0-291.325~14.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.2.0-16.19","4.2.0-17.21","4.2.0-19.23","4.3.0-1.10","4.3.0-2.11","4.3.0-5.16","4.3.0-6.17","4.3.0-7.18","4.4.0-2.16","4.4.0-4.19","4.4.0-6.21","4.4.0-7.22","4.4.0-8.23","4.4.0-9.24","4.4.0-10.25","4.4.0-11.26","4.4.0-12.28","4.4.0-13.29","4.4.0-14.30","4.4.0-15.31","4.4.0-16.32","4.4.0-17.33","4.4.0-18.34","4.4.0-21.37","4.4.0-22.39","4.4.0-22.40","4.4.0-24.43","4.4.0-28.47","4.4.0-31.50","4.4.0-34.53","4.4.0-36.55","4.4.0-38.57","4.4.0-42.62","4.4.0-43.63","4.4.0-45.66","4.4.0-47.68","4.4.0-51.72","4.4.0-53.74","4.4.0-57.78","4.4.0-59.80","4.4.0-62.83","4.4.0-63.84","4.4.0-64.85","4.4.0-65.86","4.4.0-66.87","4.4.0-67.88","4.4.0-70.91","4.4.0-71.92","4.4.0-72.93","4.4.0-75.96","4.4.0-77.98","4.4.0-78.99","4.4.0-79.100","4.4.0-81.104","4.4.0-83.106","4.4.0-87.110","4.4.0-89.112","4.4.0-91.114","4.4.0-92.115","4.4.0-93.116","4.4.0-96.119","4.4.0-97.120","4.4.0-98.121","4.4.0-101.124","4.4.0-103.126","4.4.0-104.127","4.4.0-108.131","4.4.0-109.132","4.4.0-112.135","4.4.0-116.140","4.4.0-119.143","4.4.0-121.145","4.4.0-122.146","4.4.0-124.148","4.4.0-127.153","4.4.0-128.154","4.4.0-130.156","4.4.0-131.157","4.4.0-133.159","4.4.0-134.160","4.4.0-135.161","4.4.0-137.163","4.4.0-138.164","4.4.0-139.165","4.4.0-140.166","4.4.0-141.167","4.4.0-142.168","4.4.0-143.169","4.4.0-145.171","4.4.0-146.172","4.4.0-148.174","4.4.0-150.176","4.4.0-151.178","4.4.0-154.181","4.4.0-157.185","4.4.0-159.187","4.4.0-161.189","4.4.0-164.192","4.4.0-165.193","4.4.0-166.195","4.4.0-168.197","4.4.0-169.198","4.4.0-170.199","4.4.0-171.200","4.4.0-173.203","4.4.0-174.204","4.4.0-176.206","4.4.0-177.207","4.4.0-178.208","4.4.0-179.209","4.4.0-184.214","4.4.0-185.215","4.4.0-186.216","4.4.0-187.217","4.4.0-189.219","4.4.0-190.220","4.4.0-193.224","4.4.0-194.226","4.4.0-197.229","4.4.0-198.230","4.4.0-200.232","4.4.0-201.233","4.4.0-203.235","4.4.0-204.236","4.4.0-206.238","4.4.0-208.240","4.4.0-209.241","4.4.0-210.242","4.4.0-211.243","4.4.0-212.244","4.4.0-213.245","4.4.0-214.246","4.4.0-216.249","4.4.0-217.250","4.4.0-218.251","4.4.0-219.252","4.4.0-221.254","4.4.0-222.255","4.4.0-223.256","4.4.0-224.257","4.4.0-227.261","4.4.0-229.263","4.4.0-230.264","4.4.0-231.265","4.4.0-233.267","4.4.0-234.268","4.4.0-235.269","4.4.0-236.270","4.4.0-237.271","4.4.0-239.273","4.4.0-240.274","4.4.0-241.275","4.4.0-242.276","4.4.0-243.277","4.4.0-244.278","4.4.0-245.279","4.4.0-246.280","4.4.0-248.282","4.4.0-250.284","4.4.0-251.285","4.4.0-252.286","4.4.0-253.287","4.4.0-254.288","4.4.0-256.290","4.4.0-257.291","4.4.0-258.292","4.4.0-259.293","4.4.0-260.294","4.4.0-261.295","4.4.0-262.296","4.4.0-263.297","4.4.0-264.298","4.4.0-266.300","4.4.0-267.301","4.4.0-268.302","4.4.0-269.303","4.4.0-270.304","4.4.0-271.305","4.4.0-272.306","4.4.0-273.307","4.4.0-274.308","4.4.0-276.310","4.4.0-277.311","4.4.0-278.312","4.4.0-279.313","4.4.0-280.314","4.4.0-281.315","4.4.0-283.317","4.4.0-284.318","4.4.0-287.321","4.4.0-288.322","4.4.0-289.323","4.4.0-290.324","4.4.0-291.325"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1001.10","4.4.0-1003.12","4.4.0-1004.13","4.4.0-1007.16","4.4.0-1009.18","4.4.0-1011.20","4.4.0-1012.21","4.4.0-1013.22","4.4.0-1016.25","4.4.0-1017.26","4.4.0-1018.27","4.4.0-1020.29","4.4.0-1022.31","4.4.0-1026.35","4.4.0-1028.37","4.4.0-1030.39","4.4.0-1031.40","4.4.0-1032.41","4.4.0-1035.44","4.4.0-1037.46","4.4.0-1038.47","4.4.0-1039.48","4.4.0-1041.50","4.4.0-1043.52","4.4.0-1044.53","4.4.0-1047.56","4.4.0-1048.57","4.4.0-1049.58","4.4.0-1050.59","4.4.0-1052.61","4.4.0-1054.63","4.4.0-1055.64","4.4.0-1057.66","4.4.0-1060.69","4.4.0-1061.70","4.4.0-1062.71","4.4.0-1063.72","4.4.0-1065.75","4.4.0-1066.76","4.4.0-1067.77","4.4.0-1069.79","4.4.0-1070.80","4.4.0-1072.82","4.4.0-1073.83","4.4.0-1074.84","4.4.0-1075.85","4.4.0-1077.87","4.4.0-1079.89","4.4.0-1081.91","4.4.0-1083.93","4.4.0-1084.94","4.4.0-1085.96","4.4.0-1087.98","4.4.0-1088.99","4.4.0-1090.101","4.4.0-1092.103","4.4.0-1094.105","4.4.0-1095.106","4.4.0-1096.107","4.4.0-1098.109","4.4.0-1099.110","4.4.0-1100.111","4.4.0-1101.112","4.4.0-1102.113","4.4.0-1104.115","4.4.0-1105.116","4.4.0-1106.117","4.4.0-1107.118","4.4.0-1109.120","4.4.0-1110.121","4.4.0-1111.123","4.4.0-1112.124","4.4.0-1113.126","4.4.0-1114.127","4.4.0-1117.131","4.4.0-1118.132","4.4.0-1119.133","4.4.0-1121.135","4.4.0-1122.136","4.4.0-1123.137","4.4.0-1124.138","4.4.0-1126.140","4.4.0-1127.141","4.4.0-1128.142","4.4.0-1129.143","4.4.0-1130.144","4.4.0-1131.145","4.4.0-1132.146","4.4.0-1133.147","4.4.0-1134.148","4.4.0-1135.149","4.4.0-1137.151","4.4.0-1138.152","4.4.0-1139.153","4.4.0-1140.154","4.4.0-1143.158","4.4.0-1145.160","4.4.0-1146.161","4.4.0-1147.162","4.4.0-1148.163","4.4.0-1150.165","4.4.0-1151.166","4.4.0-1152.167","4.4.0-1153.168","4.4.0-1154.169","4.4.0-1155.170","4.4.0-1156.171","4.4.0-1157.172","4.4.0-1158.173","4.4.0-1159.174","4.4.0-1160.175","4.4.0-1161.176","4.4.0-1162.177","4.4.0-1163.178","4.4.0-1164.179","4.4.0-1165.180","4.4.0-1166.181","4.4.0-1167.182","4.4.0-1168.183","4.4.0-1169.184","4.4.0-1171.186","4.4.0-1172.187","4.4.0-1173.188","4.4.0-1174.189","4.4.0-1175.190","4.4.0-1176.191","4.4.0-1177.192","4.4.0-1178.193","4.4.0-1179.194","4.4.0-1180.195","4.4.0-1181.196","4.4.0-1182.197","4.4.0-1183.198","4.4.0-1184.199","4.4.0-1185.200","4.4.0-1186.201","4.4.0-1187.202","4.4.0-1188.203","4.4.0-1189.204","4.4.0-1190.205","4.4.0-1191.206","4.4.0-1192.207","4.4.0-1193.208","4.4.0-1194.209","4.4.0-1195.210","4.4.0-1196.211","4.4.0-1197.212","4.4.0-1198.213","4.4.0-1199.214","4.4.0-1200.215"]},{"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-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1004.9","4.4.0-1007.12","4.4.0-1008.13","4.4.0-1009.14","4.4.0-1010.15","4.4.0-1012.17","4.4.0-1013.18","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24","4.4.0-1020.25","4.4.0-1021.26","4.4.0-1023.28","4.4.0-1026.31","4.4.0-1027.32","4.4.0-1029.34","4.4.0-1031.37","4.4.0-1032.38","4.4.0-1033.39","4.4.0-1035.41","4.4.0-1036.42","4.4.0-1037.43","4.4.0-1038.44","4.4.0-1039.45","4.4.0-1040.46","4.4.0-1041.47","4.4.0-1043.49","4.4.0-1044.50","4.4.0-1046.52","4.4.0-1047.53","4.4.0-1048.55","4.4.0-1051.58","4.4.0-1052.59","4.4.0-1054.61","4.4.0-1056.63","4.4.0-1058.65","4.4.0-1059.66","4.4.0-1060.67","4.4.0-1062.69","4.4.0-1063.70","4.4.0-1064.71","4.4.0-1065.72","4.4.0-1066.73","4.4.0-1068.75","4.4.0-1069.76","4.4.0-1070.77","4.4.0-1071.78","4.4.0-1075.82","4.4.0-1076.83","4.4.0-1077.84","4.4.0-1078.85","4.4.0-1079.86","4.4.0-1080.87","4.4.0-1082.91","4.4.0-1084.93","4.4.0-1085.94","4.4.0-1087.96","4.4.0-1088.97","4.4.0-1089.98","4.4.0-1090.99","4.4.0-1091.100","4.4.0-1092.101","4.4.0-1093.102","4.4.0-1094.103","4.4.0-1095.104","4.4.0-1096.105","4.4.0-1097.106","4.4.0-1098.107","4.4.0-1099.108","4.4.0-1100.109","4.4.0-1102.111","4.4.0-1103.112","4.4.0-1104.113","4.4.0-1105.114","4.4.0-1108.118","4.4.0-1110.120","4.4.0-1111.121","4.4.0-1112.122","4.4.0-1113.123","4.4.0-1114.124","4.4.0-1115.125","4.4.0-1116.126","4.4.0-1117.127","4.4.0-1118.128","4.4.0-1119.129","4.4.0-1120.130","4.4.0-1121.131","4.4.0-1122.132","4.4.0-1123.133","4.4.0-1124.134","4.4.0-1125.135","4.4.0-1126.136","4.4.0-1128.138","4.4.0-1129.139","4.4.0-1130.140","4.4.0-1131.141","4.4.0-1132.142","4.4.0-1134.144","4.4.0-1135.145","4.4.0-1136.146","4.4.0-1137.147","4.4.0-1138.148","4.4.0-1139.149","4.4.0-1140.151","4.4.0-1141.152","4.4.0-1142.153","4.4.0-1143.154","4.4.0-1144.155","4.4.0-1145.156","4.4.0-1146.157","4.4.0-1147.158","4.4.0-1148.159","4.4.0-1149.160","4.4.0-1150.161","4.4.0-1151.162","4.4.0-1152.163","4.4.0-1153.164","4.4.0-1154.165","4.4.0-1155.166","4.4.0-1156.167","4.4.0-1157.168","4.4.0-1158.169","4.4.0-1159.170","4.4.0-1160.171","4.4.0-1161.172","4.4.0-1162.173","4.4.0-1163.174"]},{"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:FIPS-updates:16.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1003.3","4.4.0-1005.5","4.4.0-1006.6","4.4.0-1008.10","4.4.0-1010.13","4.4.0-1011.14","4.4.0-1012.16","4.4.0-1013.17","4.4.0-1015.20","4.4.0-1017.22","4.4.0-1019.24","4.4.0-1021.26","4.4.0-1022.27","4.4.0-1023.28","4.4.0-1025.30","4.4.0-1026.31","4.4.0-1027.32","4.4.0-1028.33","4.4.0-1029.34","4.4.0-1031.36","4.4.0-1032.37","4.4.0-1033.38","4.4.0-1034.39","4.4.0-1041.46","4.4.0-1042.47","4.4.0-1043.48","4.4.0-1044.49","4.4.0-1045.50","4.4.0-1046.51","4.4.0-1048.53","4.4.0-1049.55","4.4.0-1051.57","4.4.0-1052.58","4.4.0-1054.60","4.4.0-1055.61","4.4.0-1056.62","4.4.0-1057.63","4.4.0-1058.64","4.4.0-1060.66","4.4.0-1061.67","4.4.0-1062.68","4.4.0-1063.69","4.4.0-1064.70","4.4.0-1065.71","4.4.0-1066.72","4.4.0-1067.73","4.4.0-1068.74","4.4.0-1069.75","4.4.0-1071.77","4.4.0-1072.78","4.4.0-1073.79","4.4.0-1074.80","4.4.0-1077.84","4.4.0-1079.86","4.4.0-1080.87","4.4.0-1081.88","4.4.0-1082.89","4.4.0-1083.90","4.4.0-1084.91","4.4.0-1085.92","4.4.0-1086.93","4.4.0-1088.95","4.4.0-1089.96","4.4.0-1090.97","4.4.0-1091.98","4.4.0-1092.99","4.4.0-1093.100","4.4.0-1094.101","4.4.0-1095.102","4.4.0-1097.104","4.4.0-1099.106","4.4.0-1100.107","4.4.0-1101.108","4.4.0-1102.109","4.4.0-1103.110","4.4.0-1104.111","4.4.0-1105.112","4.4.0-1106.113","4.4.0-1107.114","4.4.0-1108.115","4.4.0-1109.116","4.4.0-1110.117","4.4.0-1111.118","4.4.0-1112.119","4.4.0-1113.120","4.4.0-1114.121","4.4.0-1115.122","4.4.0-1116.123","4.4.0-1117.124","4.4.0-1119.126","4.4.0-1120.127","4.4.0-1121.128","4.4.0-1122.129","4.4.0-1123.130","4.4.0-1124.131","4.4.0-1125.132","4.4.0-1126.133","4.4.0-1127.134","4.4.0-1128.135","4.4.0-1129.136","4.4.0-1130.137","4.4.0-1131.138"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS:16.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.4.0-1001.1","4.4.0-1002.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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"}]}],"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","5.4.0-1142.152~18.04.1","5.4.0-1144.154~18.04.1","5.4.0-1145.155~18.04.1","5.4.0-1146.156~18.04.1","5.4.0-1147.157~18.04.1","5.4.0-1148.158~18.04.1","5.4.0-1149.159~18.04.1","5.4.0-1150.160~18.04.1","5.4.0-1151.161~18.04.1","5.4.0-1152.162~18.04.1","5.4.0-1153.163~18.04.1","5.4.0-1154.164~18.04.1","5.4.0-1156.166~18.04.1","5.4.0-1157.167~18.04.1","5.4.0-1158.168~18.04.1","5.4.0-1160.170~18.04.1","5.4.0-1161.172~18.04.1","5.4.0-1162.173~18.04.1","5.4.0-1163.174~18.04.1","5.4.0-1165.176~18.04.1","5.4.0-1167.178~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"}]}],"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","5.4.0-1145.152~18.04.1","5.4.0-1147.154~18.04.1","5.4.0-1148.155~18.04.1","5.4.0-1149.156~18.04.1","5.4.0-1150.157~18.04.1","5.4.0-1151.158~18.04.1","5.4.0-1152.159~18.04.1","5.4.0-1153.160~18.04.1","5.4.0-1154.161~18.04.1","5.4.0-1156.163~18.04.1","5.4.0-1157.164~18.04.1","5.4.0-1161.167~18.04.1","5.4.0-1162.168~18.04.1","5.4.0-1163.169~18.04.1","5.4.0-1164.170~18.04.1","5.4.0-1166.172~18.04.1","5.4.0-1167.173~18.04.1","5.4.0-1168.174~18.04.1","5.4.0-1169.175~18.04.1","5.4.0-1170.176~18.04.1","5.4.0-1171.177~18.04.1","5.4.0-1172.178~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"}]}],"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","5.4.0-1143.152~18.04.1","5.4.0-1145.154~18.04.1","5.4.0-1147.156~18.04.1","5.4.0-1148.157~18.04.1","5.4.0-1149.158~18.04.1","5.4.0-1150.159~18.04.1","5.4.0-1151.160~18.04.1","5.4.0-1152.161~18.04.1","5.4.0-1153.162~18.04.1","5.4.0-1154.163~18.04.1","5.4.0-1155.164~18.04.1","5.4.0-1156.165~18.04.1","5.4.0-1157.166~18.04.1","5.4.0-1159.168~18.04.1","5.4.0-1160.169~18.04.1","5.4.0-1161.170~18.04.1","5.4.0-1162.171~18.04.1","5.4.0-1163.172~18.04.1","5.4.0-1164.173~18.04.1","5.4.0-1165.174~18.04.1","5.4.0-1166.175~18.04.1","5.4.0-1167.176~18.04.1","5.4.0-1168.178~18.04.1","5.4.0-1169.179~18.04.1","5.4.0-1170.180~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"}]}],"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","5.4.0-208.228~18.04.1","5.4.0-211.231~18.04.1","5.4.0-212.232~18.04.1","5.4.0-214.234~18.04.1","5.4.0-215.235~18.04.1","5.4.0-216.236~18.04.1","5.4.0-218.238~18.04.1","5.4.0-219.239~18.04.1","5.4.0-220.240~18.04.1","5.4.0-221.241~18.04.1","5.4.0-222.242~18.04.1","5.4.0-223.243~18.04.1","5.4.0-224.244~18.04.1","5.4.0-225.245~18.04.1","5.4.0-227.247~18.04.1","5.4.0-228.248~18.04.1","5.4.0-229.249~18.04.1","5.4.0-231.251~18.04.1","5.4.0-233.253~18.04.1","5.4.0-234.254~18.04.1","5.4.0-238.258~18.04.1","5.4.0-241.261~18.04.1","5.4.0-242.262~18.04.1","5.4.0-244.264~18.04.1","5.4.0-245.265~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"}]}],"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","5.4.0-1086.91~18.04.1","5.4.0-1090.95~18.04.1","5.4.0-1092.97~18.04.1","5.4.0-1093.98~18.04.1","5.4.0-1094.99~18.04.1","5.4.0-1095.100~18.04.1","5.4.0-1096.101~18.04.1","5.4.0-1097.102~18.04.1","5.4.0-1098.103~18.04.1","5.4.0-1099.104~18.04.1","5.4.0-1100.105~18.04.1","5.4.0-1102.107~18.04.1","5.4.0-1103.108~18.04.1","5.4.0-1104.109~18.04.1","5.4.0-1105.110~18.04.1","5.4.0-1107.112~18.04.1","5.4.0-1108.113~18.04.1","5.4.0-1109.114~18.04.1","5.4.0-1111.116~18.04.1","5.4.0-1112.117~18.04.1","5.4.0-1113.118~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"}]}],"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","5.4.0-1138.147~18.04.1","5.4.0-1140.149~18.04.1","5.4.0-1141.151~18.04.1","5.4.0-1142.152~18.04.1","5.4.0-1143.153~18.04.1","5.4.0-1144.154~18.04.1","5.4.0-1145.155~18.04.1","5.4.0-1146.156~18.04.1","5.4.0-1148.158~18.04.1","5.4.0-1149.159~18.04.1","5.4.0-1150.160~18.04.1","5.4.0-1151.161~18.04.1","5.4.0-1152.162~18.04.1","5.4.0-1154.164~18.04.1","5.4.0-1155.165~18.04.1","5.4.0-1156.166~18.04.2","5.4.0-1157.167~18.04.1","5.4.0-1158.168~18.04.1","5.4.0-1159.169~18.04.1","5.4.0-1161.171~18.04.1","5.4.0-1162.172~18.04.1","5.4.0-1163.173~18.04.1","5.4.0-1164.174~18.04.1","5.4.0-1165.175~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-raspi-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1129.142~18.04.1","5.4.0-1130.143~18.04.1","5.4.0-1131.144~18.04.1","5.4.0-1132.145~18.04.1","5.4.0-1133.146~18.04.1","5.4.0-1134.147~18.04.1","5.4.0-1135.148~18.04.1","5.4.0-1136.149~18.04.1","5.4.0-1137.150~18.04.1","5.4.0-1139.152~18.04.1","5.4.0-1140.153~18.04.1","5.4.0-1143.156~18.04.1","5.4.0-1144.157~18.04.1","5.4.0-1145.158~18.04.1","5.4.0-1146.159~18.04.1","5.4.0-1147.160~18.04.1","5.4.0-1148.161~18.04.1","5.4.0-1149.162~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:Pro:20.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-208.228","5.4.0-211.231","5.4.0-212.232","5.4.0-214.234","5.4.0-215.235","5.4.0-216.236","5.4.0-218.238","5.4.0-219.239","5.4.0-220.240","5.4.0-221.241","5.4.0-222.242","5.4.0-223.243","5.4.0-224.244","5.4.0-225.245","5.4.0-227.247","5.4.0-228.248","5.4.0-229.249","5.4.0-230.250","5.4.0-231.251","5.4.0-233.253","5.4.0-234.254","5.4.0-238.258","5.4.0-241.261","5.4.0-242.262","5.4.0-244.264","5.4.0-245.265"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1140.150","5.4.0-1142.152","5.4.0-1144.154","5.4.0-1145.155","5.4.0-1146.156","5.4.0-1147.157","5.4.0-1148.158","5.4.0-1149.159","5.4.0-1150.160","5.4.0-1151.161","5.4.0-1152.162","5.4.0-1153.163","5.4.0-1154.164","5.4.0-1156.166","5.4.0-1157.167","5.4.0-1158.168","5.4.0-1159.169","5.4.0-1160.170","5.4.0-1161.172","5.4.0-1162.173","5.4.0-1163.174","5.4.0-1164.175","5.4.0-1165.176","5.4.0-1166.177","5.4.0-1167.178"]},{"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:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110~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","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","5.15.0-1097.104~20.04.1","5.15.0-1098.105~20.04.1","5.15.0-1099.106~20.04.1","5.15.0-1100.107~20.04.2","5.15.0-1101.108~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:Pro:20.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1145.152","5.4.0-1147.154","5.4.0-1148.155","5.4.0-1149.156","5.4.0-1150.157","5.4.0-1151.158","5.4.0-1152.159","5.4.0-1153.160","5.4.0-1154.161","5.4.0-1156.163","5.4.0-1157.164","5.4.0-1160.166","5.4.0-1161.167","5.4.0-1162.168","5.4.0-1163.169","5.4.0-1164.170","5.4.0-1166.172","5.4.0-1167.173","5.4.0-1168.174","5.4.0-1169.175","5.4.0-1170.176","5.4.0-1171.177","5.4.0-1172.178"]},{"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:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1110.119~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","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~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:Pro:20.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1099.106","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","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-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-1123.130","5.4.0-1125.132","5.4.0-1126.133"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1143.152","5.4.0-1145.154","5.4.0-1146.155","5.4.0-1147.156","5.4.0-1148.157","5.4.0-1149.158","5.4.0-1150.159","5.4.0-1151.160","5.4.0-1152.161","5.4.0-1153.162","5.4.0-1154.163","5.4.0-1155.164","5.4.0-1156.165","5.4.0-1157.166","5.4.0-1159.168","5.4.0-1160.169","5.4.0-1161.170","5.4.0-1162.171","5.4.0-1163.172","5.4.0-1164.173","5.4.0-1165.174","5.4.0-1166.175","5.4.0-1167.177","5.4.0-1168.178","5.4.0-1169.179","5.4.0-1170.180"]},{"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:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112~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","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1","5.15.0-1100.109~20.04.1","5.15.0-1101.110~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:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183~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","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.3","5.15.0-171.181~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:Pro:20.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1086.91","5.4.0-1088.93","5.4.0-1089.94","5.4.0-1090.95","5.4.0-1091.96","5.4.0-1092.97","5.4.0-1093.98","5.4.0-1094.99","5.4.0-1095.100","5.4.0-1096.101","5.4.0-1097.102","5.4.0-1098.103","5.4.0-1099.104","5.4.0-1100.105","5.4.0-1102.107","5.4.0-1103.108","5.4.0-1104.109","5.4.0-1105.110","5.4.0-1107.112","5.4.0-1108.113","5.4.0-1109.114","5.4.0-1111.116","5.4.0-1112.117","5.4.0-1113.118"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100~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","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1","5.15.0-1094.97~20.04.1","5.15.0-1095.98~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-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.104~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~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.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-iot","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","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-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1058.61","5.4.0-1060.63","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-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1069.72","5.4.0-1070.73","5.4.0-1071.74"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","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","5.4.0-1138.147","5.4.0-1139.148","5.4.0-1140.149","5.4.0-1141.150","5.4.0-1143.152","5.4.0-1144.153","5.4.0-1145.154","5.4.0-1146.155","5.4.0-1147.156","5.4.0-1148.157","5.4.0-1149.158","5.4.0-1150.159","5.4.0-1151.160","5.4.0-1152.161","5.4.0-1153.162","5.4.0-1154.163"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183~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","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.1","5.15.0-171.181~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.55~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","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","5.15.0-1049.49~20.04.1","5.15.0-1050.50~20.04.1","5.15.0-1051.51~20.04.1","5.15.0-1052.52~20.04.2","5.15.0-1053.53~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:Pro:20.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1138.147","5.4.0-1140.150","5.4.0-1141.151","5.4.0-1142.152","5.4.0-1143.153","5.4.0-1144.154","5.4.0-1145.155","5.4.0-1146.156","5.4.0-1147.157","5.4.0-1149.159","5.4.0-1150.160","5.4.0-1151.161","5.4.0-1152.162","5.4.0-1154.164","5.4.0-1155.165","5.4.0-1156.166","5.4.0-1157.167","5.4.0-1158.168","5.4.0-1159.169","5.4.0-1160.170","5.4.0-1161.171","5.4.0-1162.172","5.4.0-1163.173","5.4.0-1164.174","5.4.0-1165.175"]},{"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:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.106~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","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1097.103~20.04.1","5.15.0-1098.104~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:Pro:20.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1129.142","5.4.0-1130.143","5.4.0-1131.144","5.4.0-1132.145","5.4.0-1133.146","5.4.0-1134.147","5.4.0-1135.148","5.4.0-1136.149","5.4.0-1137.150","5.4.0-1139.152","5.4.0-1140.153","5.4.0-1143.156","5.4.0-1144.157","5.4.0-1145.158","5.4.0-1146.159","5.4.0-1147.160","5.4.0-1148.161","5.4.0-1149.162"]},{"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:Pro:20.04:LTS","package":"linux-riscv-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.101~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","5.15.0-1073.77~20.04.1","5.15.0-1074.78~20.04.1","5.15.0-1075.79~20.04.1","5.15.0-1076.80~20.04.1","5.15.0-1077.81~20.04.1","5.15.0-1078.82~20.04.1","5.15.0-1079.83~20.04.1","5.15.0-1081.85~20.04.1","5.15.0-1082.86~20.04.1","5.15.0-1083.87~20.04.1","5.15.0-1084.88~20.04.1","5.15.0-1085.89~20.04.1","5.15.0-1086.90~20.04.1","5.15.0-1087.91~20.04.1","5.15.0-1088.92~20.04.1","5.15.0-1090.94~20.04.1","5.15.0-1091.95~20.04.1","5.15.0-1092.96~20.04.1","5.15.0-1093.97~20.04.2","5.15.0-1094.98~20.04.1","5.15.0-1095.99~20.04.1","5.15.0-1096.100~20.04.1"]},{"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:20.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1058.62","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-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-1082.86","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1140.151+fips1","5.4.0-1142.153+fips1","5.4.0-1144.155+fips1","5.4.0-1145.156+fips1","5.4.0-1146.156+fips1","5.4.0-1147.157+fips1","5.4.0-1148.158+fips1","5.4.0-1149.159+fips1","5.4.0-1150.160+fips1","5.4.0-1151.161+fips1","5.4.0-1152.162+fips1","5.4.0-1153.163+fips1","5.4.0-1154.164+fips1","5.4.0-1155.165+fips1","5.4.0-1156.166+fips1","5.4.0-1157.167+fips1","5.4.0-1158.168+fips1","5.4.0-1159.169+fips1","5.4.0-1160.170+fips1","5.4.0-1161.172+fips1","5.4.0-1163.174+fips1","5.4.0-1165.176+fips1","5.4.0-1166.177+fips1","5.4.0-1167.178+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1145.152+fips1","5.4.0-1147.154+fips1","5.4.0-1148.156+fips1","5.4.0-1149.157+fips1","5.4.0-1151.158+fips1","5.4.0-1152.159+fips1","5.4.0-1153.160+fips1","5.4.0-1154.161+fips1","5.4.0-1155.162+fips1","5.4.0-1157.164+fips1","5.4.0-1158.165+fips1","5.4.0-1160.166+fips1","5.4.0-1161.167+fips1","5.4.0-1162.168+fips1","5.4.0-1163.169+fips1","5.4.0-1164.170+fips1","5.4.0-1166.172+fips1","5.4.0-1167.173+fips1","5.4.0-1168.174+fips1","5.4.0-1170.176+fips1","5.4.0-1171.177+fips1","5.4.0-1172.178+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","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-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-1138.148","5.4.0-1139.149","5.4.0-1140.150","5.4.0-1141.151"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:20.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.4.0-1143.152+fips1","5.4.0-1145.154+fips1","5.4.0-1146.155+fips1","5.4.0-1147.156+fips1","5.4.0-1148.157+fips1","5.4.0-1149.158+fips1","5.4.0-1150.159+fips1","5.4.0-1151.160+fips1","5.4.0-1152.161+fips1","5.4.0-1153.162+fips1","5.4.0-1154.163+fips1","5.4.0-1155.164+fips1","5.4.0-1156.165+fips1","5.4.0-1157.166+fips1","5.4.0-1159.168+fips1","5.4.0-1160.169+fips1","5.4.0-1161.170+fips1","5.4.0-1162.171+fips1","5.4.0-1163.172+fips1","5.4.0-1164.173+fips1","5.4.0-1165.174+fips1","5.4.0-1166.175+fips1","5.4.0-1167.176+fips1","5.4.0-1168.178+fips1","5.4.0-1169.179+fips1","5.4.0-1170.180+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-173.183"}]}],"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","5.15.0-133.144","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-151.161","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181"]},{"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-1103.110"}]}],"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","5.15.0-1078.85","5.15.0-1079.86","5.15.0-1080.87","5.15.0-1081.88","5.15.0-1082.89","5.15.0-1083.90","5.15.0-1084.91","5.15.0-1085.92","5.15.0-1086.93","5.15.0-1087.94","5.15.0-1088.95","5.15.0-1089.96","5.15.0-1090.97","5.15.0-1091.98","5.15.0-1092.99","5.15.0-1093.100","5.15.0-1095.102","5.15.0-1096.103","5.15.0-1097.104","5.15.0-1098.105","5.15.0-1099.106","5.15.0-1100.107","5.15.0-1101.108"]},{"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-1052.55~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118"}]}],"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","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112"]},{"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-1059.65~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118.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","5.15.0-1081.90.1","5.15.0-1082.91.1","5.15.0-1084.93.1","5.15.0-1086.95.1","5.15.0-1087.96.1","5.15.0-1088.97.1","5.15.0-1089.98.1","5.15.0-1090.99.1","5.15.0-1091.100.1","5.15.0-1092.101.1","5.15.0-1094.103.1","5.15.0-1095.104.1","5.15.0-1096.105.1","5.15.0-1097.106.1","5.15.0-1098.107.1","5.15.0-1102.111.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-azure-fde-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.65~22.04.1"}]}],"versions":["6.8.0-1041.48~22.04.1","6.8.0-1042.49~22.04.1","6.8.0-1044.51~22.04.1","6.8.0-1046.53~22.04.1","6.8.0-1053.60~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112"}]}],"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","5.15.0-1077.86","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1080.89","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1101.110"]},{"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-1054.57~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.105"}]}],"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","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1086.94"}]}],"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","5.15.0-1060.68","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-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.90","5.15.0-1083.91","5.15.0-1084.92"]},{"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-110.110~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"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","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1081.84","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1094.97","5.15.0-1095.98"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.51~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.104"}]}],"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","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.100"}]}],"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","5.15.0-1076.81","5.15.0-1077.82","5.15.0-1078.83","5.15.0-1079.84","5.15.0-1080.85","5.15.0-1081.86","5.15.0-1082.87","5.15.0-1083.88","5.15.0-1084.89","5.15.0-1085.90","5.15.0-1086.91","5.15.0-1087.92","5.15.0-1088.93","5.15.0-1089.94","5.15.0-1090.95","5.15.0-1091.96","5.15.0-1092.97","5.15.0-1093.98"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183"}]}],"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","5.15.0-133.143","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-145.158","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181"]},{"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-110.110.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.99"}]}],"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","5.15.0-1072.73","5.15.0-1073.74","5.15.0-1074.75","5.15.0-1075.76","5.15.0-1076.77","5.15.0-1077.78","5.15.0-1078.79","5.15.0-1079.80","5.15.0-1080.81","5.15.0-1081.82","5.15.0-1082.83","5.15.0-1083.84","5.15.0-1085.86","5.15.0-1086.87","5.15.0-1087.88","5.15.0-1088.89","5.15.0-1090.91","5.15.0-1091.92","5.15.0-1092.93","5.15.0-1093.94","5.15.0-1094.95","5.15.0-1095.96","5.15.0-1096.97"]},{"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-1051.54~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.55"}]}],"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","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","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-1049.49","5.15.0-1050.50","5.15.0-1051.51","5.15.0-1052.52","5.15.0-1053.53"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1044.44"}]}],"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","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1023.23","5.15.0-1024.24","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-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42"]},{"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-1100.106"}]}],"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","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1098.104"]},{"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-1049.50~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1","6.8.0-1047.48~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"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","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96"]},{"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-110.110~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.1","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~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-1067.71"}]}],"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","5.15.0-1044.48","5.15.0-1046.50","5.15.0-1050.54","5.15.0-1051.55","5.15.0-1052.56","5.15.0-1053.57","5.15.0-1054.58","5.15.0-1055.59","5.15.0-1056.60","5.15.0-1057.61","5.15.0-1059.63","5.15.0-1060.64","5.15.0-1061.65","5.15.0-1062.66","5.15.0-1063.67","5.15.0-1064.68","5.15.0-1065.69"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1086.88"}]}],"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","5.15.0-1060.62","5.15.0-1061.63","5.15.0-1062.64","5.15.0-1063.65","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1069.71","5.15.0-1070.72","5.15.0-1072.74","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.96"}]}],"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","5.15.0-1071.73","5.15.0-1072.74","5.15.0-1073.75","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1078.80","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1088.90","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1091.93","5.15.0-1092.94","5.15.0-1093.95"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1102.111"}]}],"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","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1047.48~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2"]},{"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-1103.110+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","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1","5.15.0-1100.107+fips1","5.15.0-1101.108+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-1109.118+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","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183+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","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1","5.15.0-170.180+fips1","5.15.0-171.181+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-1103.112+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","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1","5.15.0-1100.109+fips1","5.15.0-1101.110+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-110.110"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1012.12~24.04.1"}]}],"versions":["6.17.0-1005.5~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.2","6.17.0-1010.10~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1008.8~24.04.1","6.11.0-1012.12~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1017.17~24.04.1","6.11.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1010.10~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1013.13~24.04.1"}]}],"versions":["6.17.0-1008.8~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1011.11~24.04.2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.65"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.42"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15","6.8.0-1016.17","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1022.23","6.8.0-1025.27","6.8.0-1027.30","6.8.0-1029.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3","6.14.0-1006.6","6.14.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1006.6~24.04.2","6.11.0-1011.11~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1016.16~24.04.1","6.11.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1014.15~24.04.1","6.14.0-1015.16~24.04.1","6.14.0-1016.17~24.04.1","6.14.0-1017.18~24.04.1","6.14.0-1018.19~24.04.1","6.14.0-1019.20~24.04.1","6.14.0-1020.21~24.04.1","6.14.0-1021.22~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1012.12~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.3","6.17.0-1008.8~24.04.1","6.17.0-1009.9~24.04.3","6.17.0-1010.10~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.56"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.40"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1","6.11.0-21.21~24.04.1","6.11.0-24.24~24.04.1","6.11.0-25.25~24.04.1","6.11.0-26.26~24.04.1","6.11.0-28.28~24.04.1","6.11.0-29.29~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-24.24~24.04.3","6.14.0-27.27~24.04.1","6.14.0-28.28~24.04.1","6.14.0-29.29~24.04.1","6.14.0-32.32~24.04.1","6.14.0-33.33~24.04.1","6.14.0-34.34~24.04.1","6.14.0-35.35~24.04.1","6.14.0-36.36~24.04.1","6.14.0-37.37~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-22.22~24.04.1"}]}],"versions":["6.17.0-14.14~24.04.1","6.17.0-19.19~24.04.2","6.17.0-20.20~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.51"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-110.110.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1","6.11.0-1015.16~24.04.2","6.11.0-1016.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.54"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1002.2","6.11.0-1003.3","6.11.0-1007.7","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.18"}]}],"versions":["6.17.0-1004.4","6.17.0-1008.8","6.17.0-1014.14"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.54.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.22"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23","6.11.0-1024.24","6.11.0-1025.25","6.11.0-1027.27"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1005.5","6.14.0-1006.6","6.14.0-1007.7","6.14.0-1008.8","6.14.0-1010.10","6.14.0-1011.11","6.14.0-1012.12","6.14.0-1013.13","6.14.0-1014.14","6.14.0-1015.15","6.14.0-1016.16","6.14.0-1017.17","6.14.0-1018.18","6.14.0-1019.19","6.14.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1020.20"}]}],"versions":["6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1031.31","6.8.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.50"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45","6.8.0-1047.48"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1011.11~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.1","6.17.0-1010.10~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.56"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.1-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1","6.8.0-48.48.1","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-22.22.1~24.04.1","6.14.0-23.23.1~24.04.1","6.14.0-24.24.1~24.04.1","6.14.0-27.27.1~24.04.1","6.14.0-28.28.1~24.04.1","6.14.0-29.29.1~24.04.1","6.14.0-32.32.1~24.04.1","6.14.0-33.33.1~24.04.1","6.14.0-34.34.1~24.04.1","6.14.0-35.35.1~24.04.1","6.14.0-36.36.1~24.04.1","6.14.0-37.37.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-22.22.1~24.04.1"}]}],"versions":["6.17.0-14.14.1~24.04.1","6.17.0-19.19.1~24.04.1","6.17.0-20.20.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.29"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.21"}]}],"versions":["6.8.0-1011.15","6.8.0-1012.16","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1016.20"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2042.43"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1047.48"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3~24.04.3","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1010.11~24.04.1"}]}],"versions":["6.17.0-1004.5~24.04.2","6.17.0-1006.7~24.04.1","6.17.0-1008.9~24.04.1","6.17.0-1009.10~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1053.59+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-110.110+fips2"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-22.22"}]}],"versions":["6.14.0-15.15","6.15.0-3.3","6.15.0-4.4","6.16.0-13.13","6.16.0-16.16","6.17.0-3.3","6.17.0-4.4","6.17.0-5.5","6.17.0-6.6","6.17.0-7.7","6.17.0-8.8","6.17.0-12.12","6.17.0-14.14","6.17.0-19.19","6.17.0-20.20"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1012.12"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.2","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1013.13"}]}],"versions":["6.14.0-1004.4","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1015.15","6.17.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1012.12"}]}],"versions":["6.14.0-1006.6","6.14.0-1009.9+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1011.11"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1013.13"}]}],"versions":["6.14.0-1005.5","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1010.11"}]}],"versions":["6.14.0-1002.2","6.17.0-1001.2","6.17.0-1002.3","6.17.0-1003.4","6.17.0-1004.5","6.17.0-1005.6","6.17.0-1006.7","6.17.0-1008.9","6.17.0-1009.10"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-22.22.1"}]}],"versions":["6.14.0-13.13.2","6.17.0-4.4.1","6.17.0-5.5.1","6.17.0-6.6.1","6.17.0-7.7.1","6.17.0-8.8.1","6.17.0-12.12.1","6.17.0-14.14.1","6.17.0-19.19.1","6.17.0-20.20.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100~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","5.15.0-1074.77~20.04.1","5.15.0-1075.78~20.04.1","5.15.0-1076.79~20.04.1","5.15.0-1078.81~20.04.1","5.15.0-1079.82~20.04.1","5.15.0-1080.83~20.04.1","5.15.0-1081.84~20.04.1","5.15.0-1083.86~20.04.1","5.15.0-1085.88~20.04.1","5.15.0-1086.89~20.04.1","5.15.0-1087.90~20.04.1","5.15.0-1089.92~20.04.1","5.15.0-1090.93~20.04.1","5.15.0-1091.94~20.04.1","5.15.0-1092.95~20.04.1","5.15.0-1093.96~20.04.1","5.15.0-1094.97~20.04.1","5.15.0-1095.98~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.55~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","5.15.0-1039.39~20.04.1","5.15.0-1040.40~20.04.1","5.15.0-1041.41~20.04.1","5.15.0-1042.42~20.04.1","5.15.0-1043.43~20.04.1","5.15.0-1044.44~20.04.1","5.15.0-1045.45~20.04.1","5.15.0-1046.46~20.04.1","5.15.0-1047.47~20.04.1","5.15.0-1048.48~20.04.1","5.15.0-1049.49~20.04.1","5.15.0-1050.50~20.04.1","5.15.0-1051.51~20.04.1","5.15.0-1052.52~20.04.2","5.15.0-1053.53~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183"}]}],"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","5.15.0-133.144","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-151.161","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110"}]}],"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","5.15.0-1078.85","5.15.0-1079.86","5.15.0-1080.87","5.15.0-1081.88","5.15.0-1082.89","5.15.0-1083.90","5.15.0-1084.91","5.15.0-1085.92","5.15.0-1086.93","5.15.0-1087.94","5.15.0-1088.95","5.15.0-1089.96","5.15.0-1090.97","5.15.0-1091.98","5.15.0-1092.99","5.15.0-1093.100","5.15.0-1095.102","5.15.0-1096.103","5.15.0-1097.104","5.15.0-1098.105","5.15.0-1099.106","5.15.0-1100.107","5.15.0-1101.108"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112"}]}],"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","5.15.0-1077.86","5.15.0-1078.87","5.15.0-1079.88","5.15.0-1080.89","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109","5.15.0-1101.110"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1086.94"}]}],"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","5.15.0-1060.68","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-1073.81","5.15.0-1074.82","5.15.0-1075.83","5.15.0-1076.84","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.90","5.15.0-1083.91","5.15.0-1084.92"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"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","5.15.0-1070.73","5.15.0-1071.74","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1081.84","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96","5.15.0-1094.97","5.15.0-1095.98"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.104"}]}],"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","5.15.0-1073.79","5.15.0-1074.80","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1095.100"}]}],"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","5.15.0-1076.81","5.15.0-1077.82","5.15.0-1078.83","5.15.0-1079.84","5.15.0-1080.85","5.15.0-1081.86","5.15.0-1082.87","5.15.0-1083.88","5.15.0-1084.89","5.15.0-1085.90","5.15.0-1086.91","5.15.0-1087.92","5.15.0-1088.93","5.15.0-1089.94","5.15.0-1090.95","5.15.0-1091.96","5.15.0-1092.97","5.15.0-1093.98"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183"}]}],"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","5.15.0-133.143","5.15.0-134.145","5.15.0-135.146","5.15.0-136.147","5.15.0-138.148","5.15.0-139.149","5.15.0-140.150","5.15.0-141.151","5.15.0-142.152","5.15.0-143.153","5.15.0-144.157","5.15.0-145.158","5.15.0-152.162","5.15.0-153.163","5.15.0-156.166","5.15.0-157.167","5.15.0-160.170","5.15.0-161.171","5.15.0-163.173","5.15.0-164.174","5.15.0-168.178","5.15.0-170.180","5.15.0-171.181"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.99"}]}],"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","5.15.0-1072.73","5.15.0-1073.74","5.15.0-1074.75","5.15.0-1075.76","5.15.0-1076.77","5.15.0-1077.78","5.15.0-1078.79","5.15.0-1079.80","5.15.0-1080.81","5.15.0-1081.82","5.15.0-1082.83","5.15.0-1083.84","5.15.0-1085.86","5.15.0-1086.87","5.15.0-1087.88","5.15.0-1088.89","5.15.0-1090.91","5.15.0-1091.92","5.15.0-1092.93","5.15.0-1093.94","5.15.0-1094.95","5.15.0-1095.96","5.15.0-1096.97"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1055.55"}]}],"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","5.15.0-1033.33","5.15.0-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","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-1049.49","5.15.0-1050.50","5.15.0-1051.51","5.15.0-1052.52","5.15.0-1053.53"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.106"}]}],"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","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103","5.15.0-1098.104"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1067.71"}]}],"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","5.15.0-1044.48","5.15.0-1046.50","5.15.0-1050.54","5.15.0-1051.55","5.15.0-1052.56","5.15.0-1053.57","5.15.0-1054.58","5.15.0-1055.59","5.15.0-1056.60","5.15.0-1057.61","5.15.0-1059.63","5.15.0-1060.64","5.15.0-1061.65","5.15.0-1062.66","5.15.0-1063.67","5.15.0-1064.68","5.15.0-1065.69"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110+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","5.15.0-1078.85+fips1","5.15.0-1079.86+fips1","5.15.0-1080.87+fips1","5.15.0-1081.88+fips1","5.15.0-1082.89+fips1","5.15.0-1083.90+fips1","5.15.0-1084.91+fips1","5.15.0-1085.92+fips1","5.15.0-1086.93+fips1","5.15.0-1087.94+fips1","5.15.0-1088.95+fips1","5.15.0-1089.96+fips1","5.15.0-1090.97+fips1","5.15.0-1091.98+fips1","5.15.0-1092.99+fips1","5.15.0-1093.100+fips1","5.15.0-1095.102+fips1","5.15.0-1096.103+fips1","5.15.0-1097.104+fips1","5.15.0-1098.105+fips1","5.15.0-1099.106+fips1","5.15.0-1100.107+fips1","5.15.0-1101.108+fips1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183+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","5.15.0-133.144+fips1","5.15.0-134.145+fips1","5.15.0-135.146+fips1","5.15.0-136.147+fips1","5.15.0-138.148+fips1","5.15.0-139.149+fips1","5.15.0-140.150+fips1","5.15.0-141.151+fips1","5.15.0-142.152+fips1","5.15.0-143.153+fips1","5.15.0-144.157+fips1","5.15.0-145.158+fips1","5.15.0-152.162+fips1","5.15.0-153.163+fips1","5.15.0-156.166+fips1","5.15.0-157.167+fips1","5.15.0-160.170+fips1","5.15.0-161.171+fips1","5.15.0-163.173+fips1","5.15.0-164.174+fips1","5.15.0-168.178+fips1","5.15.0-170.180+fips1","5.15.0-171.181+fips1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112+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","5.15.0-1077.86+fips1","5.15.0-1078.87+fips1","5.15.0-1079.88+fips1","5.15.0-1080.89+fips1","5.15.0-1081.90+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1084.93+fips1","5.15.0-1085.94+fips1","5.15.0-1086.95+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1092.101+fips1","5.15.0-1093.102+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1099.108+fips1","5.15.0-1100.109+fips1","5.15.0-1101.110+fips1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.110~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","5.15.0-1080.87~20.04.1","5.15.0-1081.88~20.04.1","5.15.0-1082.89~20.04.1","5.15.0-1083.90~20.04.1","5.15.0-1084.91~20.04.1","5.15.0-1086.93~20.04.1","5.15.0-1087.94~20.04.1","5.15.0-1088.95~20.04.1","5.15.0-1089.96~20.04.1","5.15.0-1090.97~20.04.1","5.15.0-1091.98~20.04.1","5.15.0-1092.99~20.04.1","5.15.0-1093.100~20.04.1","5.15.0-1095.102~20.04.1","5.15.0-1096.103~20.04.1","5.15.0-1097.104~20.04.1","5.15.0-1098.105~20.04.1","5.15.0-1099.106~20.04.1","5.15.0-1100.107~20.04.2","5.15.0-1101.108~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1103.112~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","5.15.0-1077.86~20.04.1","5.15.0-1078.87~20.04.1","5.15.0-1081.90~20.04.1","5.15.0-1083.92~20.04.1","5.15.0-1085.94~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.2","5.15.0-1088.97~20.04.1","5.15.0-1090.99~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1092.101~20.04.1","5.15.0-1093.102~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1099.108~20.04.1","5.15.0-1100.109~20.04.1","5.15.0-1101.110~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183~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","5.15.0-134.145~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-151.161~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.3","5.15.0-171.181~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1098.104~20.04.1"}]}],"versions":["5.15.0-1003.5~20.04.1","5.15.0-1008.11~20.04.1","5.15.0-1010.14~20.04.1","5.15.0-1015.20~20.04.2","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.49~20.04.1","5.15.0-1045.51~20.04.1","5.15.0-1046.52~20.04.1","5.15.0-1048.54~20.04.1","5.15.0-1049.55~20.04.1","5.15.0-1050.56~20.04.1","5.15.0-1051.57~20.04.1","5.15.0-1052.58~20.04.1","5.15.0-1055.61~20.04.1","5.15.0-1058.64~20.04.1","5.15.0-1059.65~20.04.1","5.15.0-1060.66~20.04.1","5.15.0-1061.67~20.04.1","5.15.0-1062.68~20.04.1","5.15.0-1063.69~20.04.1","5.15.0-1064.70~20.04.1","5.15.0-1065.71~20.04.1","5.15.0-1066.72~20.04.1","5.15.0-1067.73~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.2","5.15.0-1074.80~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.1","5.15.0-1086.92~20.04.1","5.15.0-1087.93~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-173.183~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","5.15.0-133.143~20.04.1","5.15.0-134.145~20.04.1","5.15.0-135.146~20.04.1","5.15.0-136.147~20.04.1","5.15.0-138.148~20.04.1","5.15.0-139.149~20.04.1","5.15.0-140.150~20.04.1","5.15.0-142.152~20.04.1","5.15.0-143.153~20.04.1","5.15.0-144.157~20.04.1","5.15.0-145.158~20.04.1","5.15.0-152.162~20.04.1","5.15.0-153.163~20.04.1","5.15.0-156.166~20.04.1","5.15.0-157.167~20.04.1","5.15.0-160.170~20.04.1","5.15.0-161.171~20.04.1","5.15.0-163.173~20.04.1","5.15.0-164.174~20.04.1","5.15.0-168.178~20.04.1","5.15.0-170.180~20.04.1","5.15.0-171.181~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.106~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","5.15.0-1075.81~20.04.1","5.15.0-1076.82~20.04.1","5.15.0-1077.83~20.04.1","5.15.0-1078.84~20.04.1","5.15.0-1079.85~20.04.1","5.15.0-1080.86~20.04.1","5.15.0-1081.87~20.04.1","5.15.0-1083.89~20.04.1","5.15.0-1084.90~20.04.1","5.15.0-1085.91~20.04.3","5.15.0-1086.92~20.04.1","5.15.0-1088.94~20.04.1","5.15.0-1090.96~20.04.1","5.15.0-1091.97~20.04.1","5.15.0-1092.98~20.04.1","5.15.0-1093.99~20.04.1","5.15.0-1094.100~20.04.1","5.15.0-1095.101~20.04.1","5.15.0-1096.102~20.04.1","5.15.0-1097.103~20.04.1","5.15.0-1098.104~20.04.1"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.105"}]}],"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","5.15.0-1075.81","5.15.0-1076.82","5.15.0-1077.83","5.15.0-1078.84","5.15.0-1079.85","5.15.0-1080.86","5.15.0-1081.87","5.15.0-1082.88","5.15.0-1083.89","5.15.0-1084.90","5.15.0-1085.91","5.15.0-1086.92","5.15.0-1087.93","5.15.0-1088.94","5.15.0-1089.95","5.15.0-1090.96","5.15.0-1091.97","5.15.0-1092.98","5.15.0-1093.99","5.15.0-1094.100","5.15.0-1095.101","5.15.0-1096.102","5.15.0-1097.103"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1102.111"}]}],"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","5.15.0-1078.86","5.15.0-1079.87","5.15.0-1080.88","5.15.0-1081.89","5.15.0-1082.91","5.15.0-1083.92","5.15.0-1084.93","5.15.0-1085.94","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1093.102","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1100.109"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1044.44"}]}],"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","5.15.0-1021.21","5.15.0-1022.22","5.15.0-1023.23","5.15.0-1024.24","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-1034.34","5.15.0-1035.35","5.15.0-1036.36","5.15.0-1037.37","5.15.0-1038.38","5.15.0-1039.39","5.15.0-1040.40","5.15.0-1041.41","5.15.0-1042.42"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1094.96"}]}],"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","5.15.0-1071.73","5.15.0-1072.74","5.15.0-1073.75","5.15.0-1074.76","5.15.0-1075.77","5.15.0-1076.78","5.15.0-1077.79","5.15.0-1078.80","5.15.0-1079.81","5.15.0-1080.82","5.15.0-1081.83","5.15.0-1082.84","5.15.0-1083.85","5.15.0-1084.86","5.15.0-1085.87","5.15.0-1086.88","5.15.0-1087.89","5.15.0-1088.90","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1091.93","5.15.0-1092.94","5.15.0-1093.95"],"bundled":217},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.100"}]}],"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","5.15.0-1072.75","5.15.0-1073.76","5.15.0-1074.77","5.15.0-1075.78","5.15.0-1076.79","5.15.0-1077.80","5.15.0-1078.81","5.15.0-1079.82","5.15.0-1080.83","5.15.0-1083.86","5.15.0-1084.87","5.15.0-1085.88","5.15.0-1086.89","5.15.0-1087.90","5.15.0-1089.92","5.15.0-1090.93","5.15.0-1091.94","5.15.0-1092.95","5.15.0-1093.96"],"bundled":334},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118+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","5.15.0-1080.89+fips1","5.15.0-1082.91+fips1","5.15.0-1083.92+fips1","5.15.0-1085.94+fips1","5.15.0-1087.96+fips1","5.15.0-1088.97+fips1","5.15.0-1089.98+fips1","5.15.0-1090.99+fips1","5.15.0-1091.100+fips1","5.15.0-1094.103+fips1","5.15.0-1095.104+fips1","5.15.0-1096.105+fips1","5.15.0-1097.106+fips1","5.15.0-1098.107+fips1","5.15.0-1101.110+fips1","5.15.0-1102.111+fips1","5.15.0-1103.112+fips1"],"bundled":350},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1109.118"}]}],"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","5.15.0-1081.90","5.15.0-1082.91","5.15.0-1084.93","5.15.0-1086.95","5.15.0-1087.96","5.15.0-1088.97","5.15.0-1089.98","5.15.0-1090.99","5.15.0-1091.100","5.15.0-1092.101","5.15.0-1094.103","5.15.0-1095.104","5.15.0-1096.105","5.15.0-1097.106","5.15.0-1098.107","5.15.0-1099.108","5.15.0-1101.110","5.15.0-1102.111","5.15.0-1103.112"],"bundled":350},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-22.22"}]}],"versions":["6.14.0-15.15","6.15.0-3.3","6.15.0-4.4","6.16.0-13.13","6.16.0-16.16","6.17.0-3.3","6.17.0-4.4","6.17.0-5.5","6.17.0-6.6","6.17.0-7.7","6.17.0-8.8","6.17.0-12.12","6.17.0-14.14","6.17.0-19.19","6.17.0-20.20"],"bundled":139},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1010.11"}]}],"versions":["6.14.0-1002.2","6.17.0-1001.2","6.17.0-1002.3","6.17.0-1003.4","6.17.0-1004.5","6.17.0-1005.6","6.17.0-1006.7","6.17.0-1008.9","6.17.0-1009.10"],"bundled":139},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1010.11~24.04.1"}]}],"versions":["6.17.0-1004.5~24.04.2","6.17.0-1006.7~24.04.1","6.17.0-1008.9~24.04.1","6.17.0-1009.10~24.04.1"],"bundled":139},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-110.110.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-110.110"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.56"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1037.40"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.51"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-110.110.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-110.110+fips2"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-110.110~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.51~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.56"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1012.12~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.3","6.17.0-1008.8~24.04.1","6.17.0-1009.9~24.04.3","6.17.0-1010.10~24.04.1"],"bundled":138},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1012.12"}]}],"versions":["6.14.0-1006.6","6.14.0-1009.9+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10"],"bundled":138},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1012.12~24.04.1"}]}],"versions":["6.17.0-1005.5~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.2","6.17.0-1010.10~24.04.1"],"bundled":138},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-22.22~24.04.1"}]}],"versions":["6.17.0-14.14~24.04.1","6.17.0-19.19~24.04.2","6.17.0-20.20~24.04.1"],"bundled":138},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1011.11~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.1","6.17.0-1010.10~24.04.1"],"bundled":138},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1012.12"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.2","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10"],"bundled":138},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1011.11"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10"],"bundled":138},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1047.48~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2"],"bundled":175},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1047.48"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47"],"bundled":175},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.54~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1"],"bundled":173},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.54"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53"],"bundled":173},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.54.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1"],"bundled":173},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.50~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1","6.8.0-1047.48~22.04.1"],"bundled":177},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.50"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45","6.8.0-1047.48"],"bundled":177},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2042.43"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42"],"bundled":175},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-azure-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1110.119~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","5.15.0-1081.90~20.04.1","5.15.0-1082.91~20.04.1","5.15.0-1086.95~20.04.1","5.15.0-1087.96~20.04.1","5.15.0-1088.97~20.04.1","5.15.0-1089.98~20.04.1","5.15.0-1091.100~20.04.1","5.15.0-1094.103~20.04.1","5.15.0-1095.104~20.04.1","5.15.0-1096.105~20.04.1","5.15.0-1097.106~20.04.1","5.15.0-1098.107~20.04.1","5.15.0-1102.111~20.04.1","5.15.0-1103.112~20.04.1"],"bundled":426},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1013.13~24.04.1"}]}],"versions":["6.17.0-1008.8~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1011.11~24.04.2"],"bundled":140},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1020.20"}]}],"versions":["6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1017.17"],"bundled":140},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1013.13"}]}],"versions":["6.14.0-1004.4","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11"],"bundled":140},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58"],"bundled":176},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1029.30"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29"],"bundled":609},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.22"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21"],"bundled":174},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1"],"bundled":393},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1.160000.2.22"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.38.1"}]}],"bundled":885}],"products":[{"vendor":"linux","product":"linux"}],"references":[{"url":"https://git.kernel.org/stable/c/9019e399684e3cc68c4a3f050e268f74d69c1317","tags":["web"]},{"url":"https://git.kernel.org/stable/c/fb36846cbcc936954f2ad2bffdff13d16c0be08a","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/91e448e69aca4bb0ba2e998eb3e555644db7322b","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/dbc61834b0412435df21c71410562d933e4eba49","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/3ed049fbfb4d75b4e0b8ab54c934f485129d5dc8","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/382748c05e58a9f1935f5a653c352422375566ea","tags":["web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68780","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-386q-4477-2c5h"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2025-68780","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68780.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-2025-68780","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0017.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35021","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.117","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.118","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.119","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.120","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2026-0018.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35022","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38373","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39713","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40242","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40308","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40346","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40358","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40361","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68174","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68200","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68297","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68337","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68349","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68354","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68376","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68725","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68741","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68816","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68818","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71104","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23138","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23139","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23169","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23230","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68301","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623881-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1236344","tags":["report"]},{"url":"https://bugzilla.suse.com/1240890","tags":["report"]},{"url":"https://bugzilla.suse.com/1240957","tags":["report"]},{"url":"https://bugzilla.suse.com/1249104","tags":["report"]},{"url":"https://bugzilla.suse.com/1255225","tags":["report"]},{"url":"https://bugzilla.suse.com/1255531","tags":["report"]},{"url":"https://bugzilla.suse.com/1256629","tags":["report"]},{"url":"https://bugzilla.suse.com/1256671","tags":["report"]},{"url":"https://bugzilla.suse.com/1258278","tags":["report"]},{"url":"https://bugzilla.suse.com/1260501","tags":["report"]},{"url":"https://bugzilla.suse.com/1260577","tags":["report"]},{"url":"https://bugzilla.suse.com/1262073","tags":["report"]},{"url":"https://bugzilla.suse.com/1262756","tags":["report"]},{"url":"https://bugzilla.suse.com/1263004","tags":["report"]},{"url":"https://bugzilla.suse.com/1263864","tags":["report"]},{"url":"https://bugzilla.suse.com/1263865","tags":["report"]},{"url":"https://bugzilla.suse.com/1264267","tags":["report"]},{"url":"https://bugzilla.suse.com/1264335","tags":["report"]},{"url":"https://bugzilla.suse.com/1264444","tags":["report"]},{"url":"https://bugzilla.suse.com/1264541","tags":["report"]},{"url":"https://bugzilla.suse.com/1264587","tags":["report"]},{"url":"https://bugzilla.suse.com/1264619","tags":["report"]},{"url":"https://bugzilla.suse.com/1264807","tags":["report"]},{"url":"https://bugzilla.suse.com/1264851","tags":["report"]},{"url":"https://bugzilla.suse.com/1265036","tags":["report"]},{"url":"https://bugzilla.suse.com/1265068","tags":["report"]},{"url":"https://bugzilla.suse.com/1265121","tags":["report"]},{"url":"https://bugzilla.suse.com/1265132","tags":["report"]},{"url":"https://bugzilla.suse.com/1265141","tags":["report"]},{"url":"https://bugzilla.suse.com/1265220","tags":["report"]},{"url":"https://bugzilla.suse.com/1266710","tags":["report"]},{"url":"https://bugzilla.suse.com/1266860","tags":["report"]},{"url":"https://bugzilla.suse.com/1266874","tags":["report"]},{"url":"https://bugzilla.suse.com/1266897","tags":["report"]},{"url":"https://bugzilla.suse.com/1266928","tags":["report"]},{"url":"https://bugzilla.suse.com/1267023","tags":["report"]},{"url":"https://bugzilla.suse.com/1267238","tags":["report"]},{"url":"https://bugzilla.suse.com/1267373","tags":["report"]},{"url":"https://bugzilla.suse.com/1267501","tags":["report"]},{"url":"https://bugzilla.suse.com/1267586","tags":["report"]},{"url":"https://bugzilla.suse.com/1267612","tags":["report"]},{"url":"https://bugzilla.suse.com/1267882","tags":["report"]},{"url":"https://bugzilla.suse.com/1267985","tags":["report"]},{"url":"https://bugzilla.suse.com/1268972","tags":["report"]},{"url":"https://bugzilla.suse.com/1268979","tags":["report"]},{"url":"https://bugzilla.suse.com/1269000","tags":["report"]},{"url":"https://bugzilla.suse.com/1269004","tags":["report"]},{"url":"https://bugzilla.suse.com/1269010","tags":["report"]},{"url":"https://bugzilla.suse.com/1269013","tags":["report"]},{"url":"https://bugzilla.suse.com/1269108","tags":["report"]},{"url":"https://bugzilla.suse.com/1269113","tags":["report"]},{"url":"https://bugzilla.suse.com/1269114","tags":["report"]},{"url":"https://bugzilla.suse.com/1269126","tags":["report"]},{"url":"https://bugzilla.suse.com/1269134","tags":["report"]},{"url":"https://bugzilla.suse.com/1269140","tags":["report"]},{"url":"https://bugzilla.suse.com/1269162","tags":["report"]},{"url":"https://bugzilla.suse.com/1269167","tags":["report"]},{"url":"https://bugzilla.suse.com/1269238","tags":["report"]},{"url":"https://bugzilla.suse.com/1269242","tags":["report"]},{"url":"https://bugzilla.suse.com/1269256","tags":["report"]},{"url":"https://bugzilla.suse.com/1269301","tags":["report"]},{"url":"https://bugzilla.suse.com/1269306","tags":["report"]},{"url":"https://bugzilla.suse.com/1269380","tags":["report"]},{"url":"https://bugzilla.suse.com/1269381","tags":["report"]},{"url":"https://bugzilla.suse.com/1269388","tags":["report"]},{"url":"https://bugzilla.suse.com/1269402","tags":["report"]},{"url":"https://bugzilla.suse.com/1269412","tags":["report"]},{"url":"https://bugzilla.suse.com/1269417","tags":["report"]},{"url":"https://bugzilla.suse.com/1269528","tags":["report"]},{"url":"https://bugzilla.suse.com/1269530","tags":["report"]},{"url":"https://bugzilla.suse.com/1269579","tags":["report"]},{"url":"https://bugzilla.suse.com/1269590","tags":["report"]},{"url":"https://bugzilla.suse.com/1269633","tags":["report"]},{"url":"https://bugzilla.suse.com/1269635","tags":["report"]},{"url":"https://bugzilla.suse.com/1269655","tags":["report"]},{"url":"https://bugzilla.suse.com/1269665","tags":["report"]},{"url":"https://bugzilla.suse.com/1269685","tags":["report"]},{"url":"https://bugzilla.suse.com/1269686","tags":["report"]},{"url":"https://bugzilla.suse.com/1269695","tags":["report"]},{"url":"https://bugzilla.suse.com/1269697","tags":["report"]},{"url":"https://bugzilla.suse.com/1269774","tags":["report"]},{"url":"https://bugzilla.suse.com/1269783","tags":["report"]},{"url":"https://bugzilla.suse.com/1269792","tags":["report"]},{"url":"https://bugzilla.suse.com/1269815","tags":["report"]},{"url":"https://bugzilla.suse.com/1269816","tags":["report"]},{"url":"https://bugzilla.suse.com/1269888","tags":["report"]},{"url":"https://bugzilla.suse.com/1269965","tags":["report"]},{"url":"https://bugzilla.suse.com/1269969","tags":["report"]},{"url":"https://bugzilla.suse.com/1269985","tags":["report"]},{"url":"https://bugzilla.suse.com/1269999","tags":["report"]},{"url":"https://bugzilla.suse.com/1270090","tags":["report"]},{"url":"https://bugzilla.suse.com/1270108","tags":["report"]},{"url":"https://bugzilla.suse.com/1270111","tags":["report"]},{"url":"https://bugzilla.suse.com/1270139","tags":["report"]},{"url":"https://bugzilla.suse.com/1270251","tags":["report"]},{"url":"https://bugzilla.suse.com/1270266","tags":["report"]},{"url":"https://bugzilla.suse.com/1270267","tags":["report"]},{"url":"https://bugzilla.suse.com/1271050","tags":["report"]},{"url":"https://bugzilla.suse.com/1271256","tags":["report"]},{"url":"https://bugzilla.suse.com/1271365","tags":["report"]},{"url":"https://bugzilla.suse.com/1271825","tags":["report"]},{"url":"https://bugzilla.suse.com/1272148","tags":["report"]},{"url":"https://bugzilla.suse.com/1272149","tags":["report"]},{"url":"https://bugzilla.suse.com/1272175","tags":["report"]},{"url":"https://bugzilla.suse.com/1272182","tags":["report"]},{"url":"https://bugzilla.suse.com/1272199","tags":["report"]},{"url":"https://bugzilla.suse.com/1272200","tags":["report"]},{"url":"https://bugzilla.suse.com/1272210","tags":["report"]},{"url":"https://bugzilla.suse.com/1272213","tags":["report"]},{"url":"https://bugzilla.suse.com/1272230","tags":["report"]},{"url":"https://bugzilla.suse.com/1272260","tags":["report"]},{"url":"https://bugzilla.suse.com/1272261","tags":["report"]},{"url":"https://bugzilla.suse.com/1272262","tags":["report"]},{"url":"https://bugzilla.suse.com/1272284","tags":["report"]},{"url":"https://bugzilla.suse.com/1272287","tags":["report"]},{"url":"https://bugzilla.suse.com/1272297","tags":["report"]},{"url":"https://bugzilla.suse.com/1272346","tags":["report"]},{"url":"https://bugzilla.suse.com/1272366","tags":["report"]},{"url":"https://bugzilla.suse.com/1272385","tags":["report"]},{"url":"https://bugzilla.suse.com/1272390","tags":["report"]},{"url":"https://bugzilla.suse.com/1272423","tags":["report"]},{"url":"https://bugzilla.suse.com/1272426","tags":["report"]},{"url":"https://bugzilla.suse.com/1272429","tags":["report"]},{"url":"https://bugzilla.suse.com/1272484","tags":["report"]},{"url":"https://bugzilla.suse.com/1272486","tags":["report"]},{"url":"https://bugzilla.suse.com/1272497","tags":["report"]},{"url":"https://bugzilla.suse.com/1272501","tags":["report"]},{"url":"https://bugzilla.suse.com/1272502","tags":["report"]},{"url":"https://bugzilla.suse.com/1272513","tags":["report"]},{"url":"https://bugzilla.suse.com/1272516","tags":["report"]},{"url":"https://bugzilla.suse.com/1272568","tags":["report"]},{"url":"https://bugzilla.suse.com/1272569","tags":["report"]},{"url":"https://bugzilla.suse.com/1272584","tags":["report"]},{"url":"https://bugzilla.suse.com/1272641","tags":["report"]},{"url":"https://bugzilla.suse.com/1272643","tags":["report"]},{"url":"https://bugzilla.suse.com/1272673","tags":["report"]},{"url":"https://bugzilla.suse.com/1272756","tags":["report"]},{"url":"https://bugzilla.suse.com/1272786","tags":["report"]},{"url":"https://bugzilla.suse.com/1272788","tags":["report"]},{"url":"https://bugzilla.suse.com/1272791","tags":["report"]},{"url":"https://bugzilla.suse.com/1272798","tags":["report"]},{"url":"https://bugzilla.suse.com/1272799","tags":["report"]},{"url":"https://bugzilla.suse.com/1272804","tags":["report"]},{"url":"https://bugzilla.suse.com/1272855","tags":["report"]},{"url":"https://bugzilla.suse.com/1272865","tags":["report"]},{"url":"https://bugzilla.suse.com/1272868","tags":["report"]},{"url":"https://bugzilla.suse.com/1272869","tags":["report"]},{"url":"https://bugzilla.suse.com/1272877","tags":["report"]},{"url":"https://bugzilla.suse.com/1272891","tags":["report"]},{"url":"https://bugzilla.suse.com/1272893","tags":["report"]},{"url":"https://bugzilla.suse.com/1272894","tags":["report"]},{"url":"https://bugzilla.suse.com/1272904","tags":["report"]},{"url":"https://bugzilla.suse.com/1272905","tags":["report"]},{"url":"https://bugzilla.suse.com/1272918","tags":["report"]},{"url":"https://bugzilla.suse.com/1272963","tags":["report"]},{"url":"https://bugzilla.suse.com/1272969","tags":["report"]},{"url":"https://bugzilla.suse.com/1272971","tags":["report"]},{"url":"https://bugzilla.suse.com/1272983","tags":["report"]},{"url":"https://bugzilla.suse.com/1272985","tags":["report"]},{"url":"https://bugzilla.suse.com/1273008","tags":["report"]},{"url":"https://bugzilla.suse.com/1273019","tags":["report"]},{"url":"https://bugzilla.suse.com/1273027","tags":["report"]},{"url":"https://bugzilla.suse.com/1273030","tags":["report"]},{"url":"https://bugzilla.suse.com/1273032","tags":["report"]},{"url":"https://bugzilla.suse.com/1273033","tags":["report"]},{"url":"https://bugzilla.suse.com/1273036","tags":["report"]},{"url":"https://bugzilla.suse.com/1273037","tags":["report"]},{"url":"https://bugzilla.suse.com/1273038","tags":["report"]},{"url":"https://bugzilla.suse.com/1273060","tags":["report"]},{"url":"https://bugzilla.suse.com/1273105","tags":["report"]},{"url":"https://bugzilla.suse.com/1273107","tags":["report"]},{"url":"https://bugzilla.suse.com/1273119","tags":["report"]},{"url":"https://bugzilla.suse.com/1273134","tags":["report"]},{"url":"https://bugzilla.suse.com/1273231","tags":["report"]},{"url":"https://bugzilla.suse.com/1273249","tags":["report"]},{"url":"https://bugzilla.suse.com/1273251","tags":["report"]},{"url":"https://bugzilla.suse.com/1273260","tags":["report"]},{"url":"https://bugzilla.suse.com/1273271","tags":["report"]},{"url":"https://bugzilla.suse.com/1273273","tags":["report"]},{"url":"https://bugzilla.suse.com/1273274","tags":["report"]},{"url":"https://bugzilla.suse.com/1273276","tags":["report"]},{"url":"https://bugzilla.suse.com/1273277","tags":["report"]},{"url":"https://bugzilla.suse.com/1273280","tags":["report"]},{"url":"https://bugzilla.suse.com/1273281","tags":["report"]},{"url":"https://bugzilla.suse.com/1273283","tags":["report"]},{"url":"https://bugzilla.suse.com/1273284","tags":["report"]},{"url":"https://bugzilla.suse.com/1273285","tags":["report"]},{"url":"https://bugzilla.suse.com/1273286","tags":["report"]},{"url":"https://bugzilla.suse.com/1273288","tags":["report"]},{"url":"https://bugzilla.suse.com/1273289","tags":["report"]},{"url":"https://bugzilla.suse.com/1273291","tags":["report"]},{"url":"https://bugzilla.suse.com/1273294","tags":["report"]},{"url":"https://bugzilla.suse.com/1273302","tags":["report"]},{"url":"https://bugzilla.suse.com/1273303","tags":["report"]},{"url":"https://bugzilla.suse.com/1273305","tags":["report"]},{"url":"https://bugzilla.suse.com/1273309","tags":["report"]},{"url":"https://bugzilla.suse.com/1273310","tags":["report"]},{"url":"https://bugzilla.suse.com/1273311","tags":["report"]},{"url":"https://bugzilla.suse.com/1273312","tags":["report"]},{"url":"https://bugzilla.suse.com/1273314","tags":["report"]},{"url":"https://bugzilla.suse.com/1273316","tags":["report"]},{"url":"https://bugzilla.suse.com/1273317","tags":["report"]},{"url":"https://bugzilla.suse.com/1273318","tags":["report"]},{"url":"https://bugzilla.suse.com/1273319","tags":["report"]},{"url":"https://bugzilla.suse.com/1273323","tags":["report"]},{"url":"https://bugzilla.suse.com/1273325","tags":["report"]},{"url":"https://bugzilla.suse.com/1273327","tags":["report"]},{"url":"https://bugzilla.suse.com/1273331","tags":["report"]},{"url":"https://bugzilla.suse.com/1273334","tags":["report"]},{"url":"https://bugzilla.suse.com/1273335","tags":["report"]},{"url":"https://bugzilla.suse.com/1273336","tags":["report"]},{"url":"https://bugzilla.suse.com/1273337","tags":["report"]},{"url":"https://bugzilla.suse.com/1273338","tags":["report"]},{"url":"https://bugzilla.suse.com/1273339","tags":["report"]},{"url":"https://bugzilla.suse.com/1273340","tags":["report"]},{"url":"https://bugzilla.suse.com/1273341","tags":["report"]},{"url":"https://bugzilla.suse.com/1273346","tags":["report"]},{"url":"https://bugzilla.suse.com/1273420","tags":["report"]},{"url":"https://bugzilla.suse.com/1273422","tags":["report"]},{"url":"https://bugzilla.suse.com/1273426","tags":["report"]},{"url":"https://bugzilla.suse.com/1273443","tags":["report"]},{"url":"https://bugzilla.suse.com/1273460","tags":["report"]},{"url":"https://bugzilla.suse.com/1273461","tags":["report"]},{"url":"https://bugzilla.suse.com/1273463","tags":["report"]},{"url":"https://bugzilla.suse.com/1273465","tags":["report"]},{"url":"https://bugzilla.suse.com/1273468","tags":["report"]},{"url":"https://bugzilla.suse.com/1273469","tags":["report"]},{"url":"https://bugzilla.suse.com/1273471","tags":["report"]},{"url":"https://bugzilla.suse.com/1273479","tags":["report"]},{"url":"https://bugzilla.suse.com/1273480","tags":["report"]},{"url":"https://bugzilla.suse.com/1273482","tags":["report"]},{"url":"https://bugzilla.suse.com/1273484","tags":["report"]},{"url":"https://bugzilla.suse.com/1273486","tags":["report"]},{"url":"https://bugzilla.suse.com/1273488","tags":["report"]},{"url":"https://bugzilla.suse.com/1273490","tags":["report"]},{"url":"https://bugzilla.suse.com/1273495","tags":["report"]},{"url":"https://bugzilla.suse.com/1273501","tags":["report"]},{"url":"https://bugzilla.suse.com/1273503","tags":["report"]},{"url":"https://bugzilla.suse.com/1273504","tags":["report"]},{"url":"https://bugzilla.suse.com/1273506","tags":["report"]},{"url":"https://bugzilla.suse.com/1273507","tags":["report"]},{"url":"https://bugzilla.suse.com/1273509","tags":["report"]},{"url":"https://bugzilla.suse.com/1273511","tags":["report"]},{"url":"https://bugzilla.suse.com/1273520","tags":["report"]},{"url":"https://bugzilla.suse.com/1273523","tags":["report"]},{"url":"https://bugzilla.suse.com/1273524","tags":["report"]},{"url":"https://bugzilla.suse.com/1273525","tags":["report"]},{"url":"https://bugzilla.suse.com/1273533","tags":["report"]},{"url":"https://bugzilla.suse.com/1273536","tags":["report"]},{"url":"https://bugzilla.suse.com/1273538","tags":["report"]},{"url":"https://bugzilla.suse.com/1273542","tags":["report"]},{"url":"https://bugzilla.suse.com/1273550","tags":["report"]},{"url":"https://bugzilla.suse.com/1273555","tags":["report"]},{"url":"https://bugzilla.suse.com/1273557","tags":["report"]},{"url":"https://bugzilla.suse.com/1273567","tags":["report"]},{"url":"https://bugzilla.suse.com/1273578","tags":["report"]},{"url":"https://bugzilla.suse.com/1273579","tags":["report"]},{"url":"https://bugzilla.suse.com/1273581","tags":["report"]},{"url":"https://bugzilla.suse.com/1273582","tags":["report"]},{"url":"https://bugzilla.suse.com/1273596","tags":["report"]},{"url":"https://bugzilla.suse.com/1273597","tags":["report"]},{"url":"https://bugzilla.suse.com/1273598","tags":["report"]},{"url":"https://bugzilla.suse.com/1273600","tags":["report"]},{"url":"https://bugzilla.suse.com/1273601","tags":["report"]},{"url":"https://bugzilla.suse.com/1273602","tags":["report"]},{"url":"https://bugzilla.suse.com/1273603","tags":["report"]},{"url":"https://bugzilla.suse.com/1273679","tags":["report"]},{"url":"https://bugzilla.suse.com/1273681","tags":["report"]},{"url":"https://bugzilla.suse.com/1273682","tags":["report"]},{"url":"https://bugzilla.suse.com/1273734","tags":["report"]},{"url":"https://bugzilla.suse.com/1273737","tags":["report"]},{"url":"https://bugzilla.suse.com/1273738","tags":["report"]},{"url":"https://bugzilla.suse.com/1273739","tags":["report"]},{"url":"https://bugzilla.suse.com/1273740","tags":["report"]},{"url":"https://bugzilla.suse.com/1273741","tags":["report"]},{"url":"https://bugzilla.suse.com/1273742","tags":["report"]},{"url":"https://bugzilla.suse.com/1273743","tags":["report"]},{"url":"https://bugzilla.suse.com/1273744","tags":["report"]},{"url":"https://bugzilla.suse.com/1273745","tags":["report"]},{"url":"https://bugzilla.suse.com/1273746","tags":["report"]},{"url":"https://bugzilla.suse.com/1273748","tags":["report"]},{"url":"https://bugzilla.suse.com/1273749","tags":["report"]},{"url":"https://bugzilla.suse.com/1273755","tags":["report"]},{"url":"https://bugzilla.suse.com/1273759","tags":["report"]},{"url":"https://bugzilla.suse.com/1273762","tags":["report"]},{"url":"https://bugzilla.suse.com/1273765","tags":["report"]},{"url":"https://bugzilla.suse.com/1273766","tags":["report"]},{"url":"https://bugzilla.suse.com/1273769","tags":["report"]},{"url":"https://bugzilla.suse.com/1273770","tags":["report"]},{"url":"https://bugzilla.suse.com/1273774","tags":["report"]},{"url":"https://bugzilla.suse.com/1273776","tags":["report"]},{"url":"https://bugzilla.suse.com/1273778","tags":["report"]},{"url":"https://bugzilla.suse.com/1273780","tags":["report"]},{"url":"https://bugzilla.suse.com/1273782","tags":["report"]},{"url":"https://bugzilla.suse.com/1273788","tags":["report"]},{"url":"https://bugzilla.suse.com/1273790","tags":["report"]},{"url":"https://bugzilla.suse.com/1273796","tags":["report"]},{"url":"https://bugzilla.suse.com/1273797","tags":["report"]},{"url":"https://bugzilla.suse.com/1273801","tags":["report"]},{"url":"https://bugzilla.suse.com/1273803","tags":["report"]},{"url":"https://bugzilla.suse.com/1273804","tags":["report"]},{"url":"https://bugzilla.suse.com/1273809","tags":["report"]},{"url":"https://bugzilla.suse.com/1273810","tags":["report"]},{"url":"https://bugzilla.suse.com/1273811","tags":["report"]},{"url":"https://bugzilla.suse.com/1273812","tags":["report"]},{"url":"https://bugzilla.suse.com/1273813","tags":["report"]},{"url":"https://bugzilla.suse.com/1273817","tags":["report"]},{"url":"https://bugzilla.suse.com/1273822","tags":["report"]},{"url":"https://bugzilla.suse.com/1273824","tags":["report"]},{"url":"https://bugzilla.suse.com/1273831","tags":["report"]},{"url":"https://bugzilla.suse.com/1273834","tags":["report"]},{"url":"https://bugzilla.suse.com/1273838","tags":["report"]},{"url":"https://bugzilla.suse.com/1273839","tags":["report"]},{"url":"https://bugzilla.suse.com/1273842","tags":["report"]},{"url":"https://bugzilla.suse.com/1273844","tags":["report"]},{"url":"https://bugzilla.suse.com/1273848","tags":["report"]},{"url":"https://bugzilla.suse.com/1273849","tags":["report"]},{"url":"https://bugzilla.suse.com/1273852","tags":["report"]},{"url":"https://bugzilla.suse.com/1273855","tags":["report"]},{"url":"https://bugzilla.suse.com/1273859","tags":["report"]},{"url":"https://bugzilla.suse.com/1273860","tags":["report"]},{"url":"https://bugzilla.suse.com/1273862","tags":["report"]},{"url":"https://bugzilla.suse.com/1273864","tags":["report"]},{"url":"https://bugzilla.suse.com/1273866","tags":["report"]},{"url":"https://bugzilla.suse.com/1273867","tags":["report"]},{"url":"https://bugzilla.suse.com/1273868","tags":["report"]},{"url":"https://bugzilla.suse.com/1273869","tags":["report"]},{"url":"https://bugzilla.suse.com/1273870","tags":["report"]},{"url":"https://bugzilla.suse.com/1273872","tags":["report"]},{"url":"https://bugzilla.suse.com/1273876","tags":["report"]},{"url":"https://bugzilla.suse.com/1273877","tags":["report"]},{"url":"https://bugzilla.suse.com/1273880","tags":["report"]},{"url":"https://bugzilla.suse.com/1273882","tags":["report"]},{"url":"https://bugzilla.suse.com/1273890","tags":["report"]},{"url":"https://bugzilla.suse.com/1273891","tags":["report"]},{"url":"https://bugzilla.suse.com/1273892","tags":["report"]},{"url":"https://bugzilla.suse.com/1273895","tags":["report"]},{"url":"https://bugzilla.suse.com/1273896","tags":["report"]},{"url":"https://bugzilla.suse.com/1273898","tags":["report"]},{"url":"https://bugzilla.suse.com/1273899","tags":["report"]},{"url":"https://bugzilla.suse.com/1273903","tags":["report"]},{"url":"https://bugzilla.suse.com/1273904","tags":["report"]},{"url":"https://bugzilla.suse.com/1273905","tags":["report"]},{"url":"https://bugzilla.suse.com/1273930","tags":["report"]},{"url":"https://bugzilla.suse.com/1273933","tags":["report"]},{"url":"https://bugzilla.suse.com/1273934","tags":["report"]},{"url":"https://bugzilla.suse.com/1273935","tags":["report"]},{"url":"https://bugzilla.suse.com/1273936","tags":["report"]},{"url":"https://bugzilla.suse.com/1273939","tags":["report"]},{"url":"https://bugzilla.suse.com/1273940","tags":["report"]},{"url":"https://bugzilla.suse.com/1273941","tags":["report"]},{"url":"https://bugzilla.suse.com/1273942","tags":["report"]},{"url":"https://bugzilla.suse.com/1273944","tags":["report"]},{"url":"https://bugzilla.suse.com/1273945","tags":["report"]},{"url":"https://bugzilla.suse.com/1273946","tags":["report"]},{"url":"https://bugzilla.suse.com/1273947","tags":["report"]},{"url":"https://bugzilla.suse.com/1273949","tags":["report"]},{"url":"https://bugzilla.suse.com/1273953","tags":["report"]},{"url":"https://bugzilla.suse.com/1273954","tags":["report"]},{"url":"https://bugzilla.suse.com/1273956","tags":["report"]},{"url":"https://bugzilla.suse.com/1273957","tags":["report"]},{"url":"https://bugzilla.suse.com/1273958","tags":["report"]},{"url":"https://bugzilla.suse.com/1273959","tags":["report"]},{"url":"https://bugzilla.suse.com/1273963","tags":["report"]},{"url":"https://bugzilla.suse.com/1273966","tags":["report"]},{"url":"https://bugzilla.suse.com/1273967","tags":["report"]},{"url":"https://bugzilla.suse.com/1273968","tags":["report"]},{"url":"https://bugzilla.suse.com/1273972","tags":["report"]},{"url":"https://bugzilla.suse.com/1273974","tags":["report"]},{"url":"https://bugzilla.suse.com/1273975","tags":["report"]},{"url":"https://bugzilla.suse.com/1273977","tags":["report"]},{"url":"https://bugzilla.suse.com/1273988","tags":["report"]},{"url":"https://bugzilla.suse.com/1273990","tags":["report"]},{"url":"https://bugzilla.suse.com/1273991","tags":["report"]},{"url":"https://bugzilla.suse.com/1273995","tags":["report"]},{"url":"https://bugzilla.suse.com/1273997","tags":["report"]},{"url":"https://bugzilla.suse.com/1273999","tags":["report"]},{"url":"https://bugzilla.suse.com/1274001","tags":["report"]},{"url":"https://bugzilla.suse.com/1274003","tags":["report"]},{"url":"https://bugzilla.suse.com/1274006","tags":["report"]},{"url":"https://bugzilla.suse.com/1274008","tags":["report"]},{"url":"https://bugzilla.suse.com/1274009","tags":["report"]},{"url":"https://bugzilla.suse.com/1274010","tags":["report"]},{"url":"https://bugzilla.suse.com/1274011","tags":["report"]},{"url":"https://bugzilla.suse.com/1274012","tags":["report"]},{"url":"https://bugzilla.suse.com/1274014","tags":["report"]},{"url":"https://bugzilla.suse.com/1274017","tags":["report"]},{"url":"https://bugzilla.suse.com/1274019","tags":["report"]},{"url":"https://bugzilla.suse.com/1274020","tags":["report"]},{"url":"https://bugzilla.suse.com/1274026","tags":["report"]},{"url":"https://bugzilla.suse.com/1274028","tags":["report"]},{"url":"https://bugzilla.suse.com/1274030","tags":["report"]},{"url":"https://bugzilla.suse.com/1274031","tags":["report"]},{"url":"https://bugzilla.suse.com/1274035","tags":["report"]},{"url":"https://bugzilla.suse.com/1274036","tags":["report"]},{"url":"https://bugzilla.suse.com/1274040","tags":["report"]},{"url":"https://bugzilla.suse.com/1274041","tags":["report"]},{"url":"https://bugzilla.suse.com/1274052","tags":["report"]},{"url":"https://bugzilla.suse.com/1274055","tags":["report"]},{"url":"https://bugzilla.suse.com/1274057","tags":["report"]},{"url":"https://bugzilla.suse.com/1274058","tags":["report"]},{"url":"https://bugzilla.suse.com/1274060","tags":["report"]},{"url":"https://bugzilla.suse.com/1274063","tags":["report"]},{"url":"https://bugzilla.suse.com/1274065","tags":["report"]},{"url":"https://bugzilla.suse.com/1274067","tags":["report"]},{"url":"https://bugzilla.suse.com/1274071","tags":["report"]},{"url":"https://bugzilla.suse.com/1274075","tags":["report"]},{"url":"https://bugzilla.suse.com/1274076","tags":["report"]},{"url":"https://bugzilla.suse.com/1274077","tags":["report"]},{"url":"https://bugzilla.suse.com/1274078","tags":["report"]},{"url":"https://bugzilla.suse.com/1274208","tags":["report"]},{"url":"https://bugzilla.suse.com/1274226","tags":["report"]},{"url":"https://bugzilla.suse.com/1274239","tags":["report"]},{"url":"https://bugzilla.suse.com/1274243","tags":["report"]},{"url":"https://bugzilla.suse.com/1274252","tags":["report"]},{"url":"https://bugzilla.suse.com/1274253","tags":["report"]},{"url":"https://bugzilla.suse.com/1274258","tags":["report"]},{"url":"https://bugzilla.suse.com/1274264","tags":["report"]},{"url":"https://bugzilla.suse.com/1274265","tags":["report"]},{"url":"https://bugzilla.suse.com/1274267","tags":["report"]},{"url":"https://bugzilla.suse.com/1274274","tags":["report"]},{"url":"https://bugzilla.suse.com/1274277","tags":["report"]},{"url":"https://bugzilla.suse.com/1274278","tags":["report"]},{"url":"https://bugzilla.suse.com/1274281","tags":["report"]},{"url":"https://bugzilla.suse.com/1274283","tags":["report"]},{"url":"https://bugzilla.suse.com/1274286","tags":["report"]},{"url":"https://bugzilla.suse.com/1274290","tags":["report"]},{"url":"https://bugzilla.suse.com/1274292","tags":["report"]},{"url":"https://bugzilla.suse.com/1274294","tags":["report"]},{"url":"https://bugzilla.suse.com/1274295","tags":["report"]},{"url":"https://bugzilla.suse.com/1274296","tags":["report"]},{"url":"https://bugzilla.suse.com/1274314","tags":["report"]},{"url":"https://bugzilla.suse.com/1274321","tags":["report"]},{"url":"https://bugzilla.suse.com/1274491","tags":["report"]},{"url":"https://bugzilla.suse.com/1274492","tags":["report"]},{"url":"https://bugzilla.suse.com/1274494","tags":["report"]},{"url":"https://bugzilla.suse.com/1274497","tags":["report"]},{"url":"https://bugzilla.suse.com/1274539","tags":["report"]},{"url":"https://bugzilla.suse.com/1274541","tags":["report"]},{"url":"https://bugzilla.suse.com/1274543","tags":["report"]},{"url":"https://bugzilla.suse.com/1274545","tags":["report"]},{"url":"https://bugzilla.suse.com/1274547","tags":["report"]},{"url":"https://bugzilla.suse.com/1274550","tags":["report"]},{"url":"https://bugzilla.suse.com/1274556","tags":["report"]},{"url":"https://bugzilla.suse.com/1274573","tags":["report"]},{"url":"https://bugzilla.suse.com/1274578","tags":["report"]},{"url":"https://bugzilla.suse.com/1274580","tags":["report"]},{"url":"https://bugzilla.suse.com/1274581","tags":["report"]},{"url":"https://bugzilla.suse.com/1274622","tags":["report"]},{"url":"https://bugzilla.suse.com/1274624","tags":["report"]},{"url":"https://bugzilla.suse.com/1274628","tags":["report"]},{"url":"https://bugzilla.suse.com/1274632","tags":["report"]},{"url":"https://bugzilla.suse.com/1274636","tags":["report"]},{"url":"https://bugzilla.suse.com/1274637","tags":["report"]},{"url":"https://bugzilla.suse.com/1274639","tags":["report"]},{"url":"https://bugzilla.suse.com/1274640","tags":["report"]},{"url":"https://bugzilla.suse.com/1274642","tags":["report"]},{"url":"https://bugzilla.suse.com/1274644","tags":["report"]},{"url":"https://bugzilla.suse.com/1274645","tags":["report"]},{"url":"https://bugzilla.suse.com/1274646","tags":["report"]},{"url":"https://bugzilla.suse.com/1274650","tags":["report"]},{"url":"https://bugzilla.suse.com/1274651","tags":["report"]},{"url":"https://bugzilla.suse.com/1274652","tags":["report"]},{"url":"https://bugzilla.suse.com/1274656","tags":["report"]},{"url":"https://bugzilla.suse.com/1274657","tags":["report"]},{"url":"https://bugzilla.suse.com/1274659","tags":["report"]},{"url":"https://bugzilla.suse.com/1274662","tags":["report"]},{"url":"https://bugzilla.suse.com/1274665","tags":["report"]},{"url":"https://bugzilla.suse.com/1274667","tags":["report"]},{"url":"https://bugzilla.suse.com/1274669","tags":["report"]},{"url":"https://bugzilla.suse.com/1274670","tags":["report"]},{"url":"https://bugzilla.suse.com/1274671","tags":["report"]},{"url":"https://bugzilla.suse.com/1274675","tags":["report"]},{"url":"https://bugzilla.suse.com/1274677","tags":["report"]},{"url":"https://bugzilla.suse.com/1274678","tags":["report"]},{"url":"https://bugzilla.suse.com/1274679","tags":["report"]},{"url":"https://bugzilla.suse.com/1274681","tags":["report"]},{"url":"https://bugzilla.suse.com/1274682","tags":["report"]},{"url":"https://bugzilla.suse.com/1274690","tags":["report"]},{"url":"https://bugzilla.suse.com/1274694","tags":["report"]},{"url":"https://bugzilla.suse.com/1274696","tags":["report"]},{"url":"https://bugzilla.suse.com/1274698","tags":["report"]},{"url":"https://bugzilla.suse.com/1274699","tags":["report"]},{"url":"https://bugzilla.suse.com/1274700","tags":["report"]},{"url":"https://bugzilla.suse.com/1274702","tags":["report"]},{"url":"https://bugzilla.suse.com/1274703","tags":["report"]},{"url":"https://bugzilla.suse.com/1274705","tags":["report"]},{"url":"https://bugzilla.suse.com/1274706","tags":["report"]},{"url":"https://bugzilla.suse.com/1274707","tags":["report"]},{"url":"https://bugzilla.suse.com/1274709","tags":["report"]},{"url":"https://bugzilla.suse.com/1274710","tags":["report"]},{"url":"https://bugzilla.suse.com/1274713","tags":["report"]},{"url":"https://bugzilla.suse.com/1274716","tags":["report"]},{"url":"https://bugzilla.suse.com/1274721","tags":["report"]},{"url":"https://bugzilla.suse.com/1274725","tags":["report"]},{"url":"https://bugzilla.suse.com/1274727","tags":["report"]},{"url":"https://bugzilla.suse.com/1274730","tags":["report"]},{"url":"https://bugzilla.suse.com/1274737","tags":["report"]},{"url":"https://bugzilla.suse.com/1274738","tags":["report"]},{"url":"https://bugzilla.suse.com/1274749","tags":["report"]},{"url":"https://bugzilla.suse.com/1274750","tags":["report"]},{"url":"https://bugzilla.suse.com/1274751","tags":["report"]},{"url":"https://bugzilla.suse.com/1274752","tags":["report"]},{"url":"https://bugzilla.suse.com/1274753","tags":["report"]},{"url":"https://bugzilla.suse.com/1274754","tags":["report"]},{"url":"https://bugzilla.suse.com/1274755","tags":["report"]},{"url":"https://bugzilla.suse.com/1274756","tags":["report"]},{"url":"https://bugzilla.suse.com/1274764","tags":["report"]},{"url":"https://bugzilla.suse.com/1274768","tags":["report"]},{"url":"https://bugzilla.suse.com/1274770","tags":["report"]},{"url":"https://bugzilla.suse.com/1274771","tags":["report"]},{"url":"https://bugzilla.suse.com/1274773","tags":["report"]},{"url":"https://bugzilla.suse.com/1274782","tags":["report"]},{"url":"https://bugzilla.suse.com/1274783","tags":["report"]},{"url":"https://bugzilla.suse.com/1274787","tags":["report"]},{"url":"https://bugzilla.suse.com/1274800","tags":["report"]},{"url":"https://bugzilla.suse.com/1274801","tags":["report"]},{"url":"https://bugzilla.suse.com/1274802","tags":["report"]},{"url":"https://bugzilla.suse.com/1274803","tags":["report"]},{"url":"https://bugzilla.suse.com/1274804","tags":["report"]},{"url":"https://bugzilla.suse.com/1274805","tags":["report"]},{"url":"https://bugzilla.suse.com/1274807","tags":["report"]},{"url":"https://bugzilla.suse.com/1274808","tags":["report"]},{"url":"https://bugzilla.suse.com/1274811","tags":["report"]},{"url":"https://bugzilla.suse.com/1274813","tags":["report"]},{"url":"https://bugzilla.suse.com/1274814","tags":["report"]},{"url":"https://bugzilla.suse.com/1274831","tags":["report"]},{"url":"https://bugzilla.suse.com/1274834","tags":["report"]},{"url":"https://bugzilla.suse.com/1274835","tags":["report"]},{"url":"https://bugzilla.suse.com/1274838","tags":["report"]},{"url":"https://bugzilla.suse.com/1274847","tags":["report"]},{"url":"https://bugzilla.suse.com/1274849","tags":["report"]},{"url":"https://bugzilla.suse.com/1274853","tags":["report"]},{"url":"https://bugzilla.suse.com/1274868","tags":["report"]},{"url":"https://bugzilla.suse.com/1274869","tags":["report"]},{"url":"https://bugzilla.suse.com/1274872","tags":["report"]},{"url":"https://bugzilla.suse.com/1274873","tags":["report"]},{"url":"https://bugzilla.suse.com/1274874","tags":["report"]},{"url":"https://bugzilla.suse.com/1274876","tags":["report"]},{"url":"https://bugzilla.suse.com/1274877","tags":["report"]},{"url":"https://bugzilla.suse.com/1274879","tags":["report"]},{"url":"https://bugzilla.suse.com/1274881","tags":["report"]},{"url":"https://bugzilla.suse.com/1274883","tags":["report"]},{"url":"https://bugzilla.suse.com/1274886","tags":["report"]},{"url":"https://bugzilla.suse.com/1274887","tags":["report"]},{"url":"https://bugzilla.suse.com/1274888","tags":["report"]},{"url":"https://bugzilla.suse.com/1274891","tags":["report"]},{"url":"https://bugzilla.suse.com/1274892","tags":["report"]},{"url":"https://bugzilla.suse.com/1274893","tags":["report"]},{"url":"https://bugzilla.suse.com/1274894","tags":["report"]},{"url":"https://bugzilla.suse.com/1274895","tags":["report"]},{"url":"https://bugzilla.suse.com/1274896","tags":["report"]},{"url":"https://bugzilla.suse.com/1274897","tags":["report"]},{"url":"https://bugzilla.suse.com/1274898","tags":["report"]},{"url":"https://bugzilla.suse.com/1274899","tags":["report"]},{"url":"https://bugzilla.suse.com/1274900","tags":["report"]},{"url":"https://bugzilla.suse.com/1274901","tags":["report"]},{"url":"https://bugzilla.suse.com/1274902","tags":["report"]},{"url":"https://bugzilla.suse.com/1274904","tags":["report"]},{"url":"https://bugzilla.suse.com/1274905","tags":["report"]},{"url":"https://bugzilla.suse.com/1274906","tags":["report"]},{"url":"https://bugzilla.suse.com/1274907","tags":["report"]},{"url":"https://bugzilla.suse.com/1274908","tags":["report"]},{"url":"https://bugzilla.suse.com/1274913","tags":["report"]},{"url":"https://bugzilla.suse.com/1274914","tags":["report"]},{"url":"https://bugzilla.suse.com/1274921","tags":["report"]},{"url":"https://bugzilla.suse.com/1274924","tags":["report"]},{"url":"https://bugzilla.suse.com/1274925","tags":["report"]},{"url":"https://bugzilla.suse.com/1274927","tags":["report"]},{"url":"https://bugzilla.suse.com/1274929","tags":["report"]},{"url":"https://bugzilla.suse.com/1274930","tags":["report"]},{"url":"https://bugzilla.suse.com/1274933","tags":["report"]},{"url":"https://bugzilla.suse.com/1274934","tags":["report"]},{"url":"https://bugzilla.suse.com/1274935","tags":["report"]},{"url":"https://bugzilla.suse.com/1274938","tags":["report"]},{"url":"https://bugzilla.suse.com/1274939","tags":["report"]},{"url":"https://bugzilla.suse.com/1274940","tags":["report"]},{"url":"https://bugzilla.suse.com/1274941","tags":["report"]},{"url":"https://bugzilla.suse.com/1274945","tags":["report"]},{"url":"https://bugzilla.suse.com/1274947","tags":["report"]},{"url":"https://bugzilla.suse.com/1274951","tags":["report"]},{"url":"https://bugzilla.suse.com/1274952","tags":["report"]},{"url":"https://bugzilla.suse.com/1274953","tags":["report"]},{"url":"https://bugzilla.suse.com/1274955","tags":["report"]},{"url":"https://bugzilla.suse.com/1274957","tags":["report"]},{"url":"https://bugzilla.suse.com/1274958","tags":["report"]},{"url":"https://bugzilla.suse.com/1274965","tags":["report"]},{"url":"https://bugzilla.suse.com/1274968","tags":["report"]},{"url":"https://bugzilla.suse.com/1274978","tags":["report"]},{"url":"https://bugzilla.suse.com/1274981","tags":["report"]},{"url":"https://bugzilla.suse.com/1275040","tags":["report"]},{"url":"https://bugzilla.suse.com/1275045","tags":["report"]},{"url":"https://bugzilla.suse.com/1275069","tags":["report"]},{"url":"https://bugzilla.suse.com/1275071","tags":["report"]},{"url":"https://bugzilla.suse.com/1275072","tags":["report"]},{"url":"https://bugzilla.suse.com/1275073","tags":["report"]},{"url":"https://bugzilla.suse.com/1275076","tags":["report"]},{"url":"https://bugzilla.suse.com/1275080","tags":["report"]},{"url":"https://bugzilla.suse.com/1275081","tags":["report"]},{"url":"https://bugzilla.suse.com/1275083","tags":["report"]},{"url":"https://bugzilla.suse.com/1275088","tags":["report"]},{"url":"https://bugzilla.suse.com/1275091","tags":["report"]},{"url":"https://bugzilla.suse.com/1275092","tags":["report"]},{"url":"https://bugzilla.suse.com/1275094","tags":["report"]},{"url":"https://bugzilla.suse.com/1275125","tags":["report"]},{"url":"https://bugzilla.suse.com/1275126","tags":["report"]},{"url":"https://bugzilla.suse.com/1275129","tags":["report"]},{"url":"https://bugzilla.suse.com/1275131","tags":["report"]},{"url":"https://bugzilla.suse.com/1275132","tags":["report"]},{"url":"https://bugzilla.suse.com/1275139","tags":["report"]},{"url":"https://bugzilla.suse.com/1275141","tags":["report"]},{"url":"https://bugzilla.suse.com/1275146","tags":["report"]},{"url":"https://bugzilla.suse.com/1275148","tags":["report"]},{"url":"https://bugzilla.suse.com/1275149","tags":["report"]},{"url":"https://bugzilla.suse.com/1275150","tags":["report"]},{"url":"https://bugzilla.suse.com/1275152","tags":["report"]},{"url":"https://bugzilla.suse.com/1275154","tags":["report"]},{"url":"https://bugzilla.suse.com/1275155","tags":["report"]},{"url":"https://bugzilla.suse.com/1275156","tags":["report"]},{"url":"https://bugzilla.suse.com/1275157","tags":["report"]},{"url":"https://bugzilla.suse.com/1275158","tags":["report"]},{"url":"https://bugzilla.suse.com/1275160","tags":["report"]},{"url":"https://bugzilla.suse.com/1275161","tags":["report"]},{"url":"https://bugzilla.suse.com/1275163","tags":["report"]},{"url":"https://bugzilla.suse.com/1275164","tags":["report"]},{"url":"https://bugzilla.suse.com/1275169","tags":["report"]},{"url":"https://bugzilla.suse.com/1275173","tags":["report"]},{"url":"https://bugzilla.suse.com/1275176","tags":["report"]},{"url":"https://bugzilla.suse.com/1275185","tags":["report"]},{"url":"https://bugzilla.suse.com/1275190","tags":["report"]},{"url":"https://bugzilla.suse.com/1275192","tags":["report"]},{"url":"https://bugzilla.suse.com/1275229","tags":["report"]},{"url":"https://bugzilla.suse.com/1275236","tags":["report"]},{"url":"https://bugzilla.suse.com/1275237","tags":["report"]},{"url":"https://bugzilla.suse.com/1275238","tags":["report"]},{"url":"https://bugzilla.suse.com/1275239","tags":["report"]},{"url":"https://bugzilla.suse.com/1275294","tags":["report"]},{"url":"https://bugzilla.suse.com/1275300","tags":["report"]},{"url":"https://bugzilla.suse.com/1275301","tags":["report"]},{"url":"https://bugzilla.suse.com/1275303","tags":["report"]},{"url":"https://bugzilla.suse.com/1275304","tags":["report"]},{"url":"https://bugzilla.suse.com/1275305","tags":["report"]},{"url":"https://bugzilla.suse.com/1275306","tags":["report"]},{"url":"https://bugzilla.suse.com/1275307","tags":["report"]},{"url":"https://bugzilla.suse.com/1275470","tags":["report"]},{"url":"https://bugzilla.suse.com/1275474","tags":["report"]},{"url":"https://bugzilla.suse.com/1275479","tags":["report"]},{"url":"https://bugzilla.suse.com/1275481","tags":["report"]},{"url":"https://bugzilla.suse.com/1275483","tags":["report"]},{"url":"https://bugzilla.suse.com/1275486","tags":["report"]},{"url":"https://bugzilla.suse.com/1275487","tags":["report"]},{"url":"https://bugzilla.suse.com/1275496","tags":["report"]},{"url":"https://bugzilla.suse.com/1275506","tags":["report"]},{"url":"https://bugzilla.suse.com/1275509","tags":["report"]},{"url":"https://bugzilla.suse.com/1275511","tags":["report"]},{"url":"https://bugzilla.suse.com/1275514","tags":["report"]},{"url":"https://bugzilla.suse.com/1275517","tags":["report"]},{"url":"https://bugzilla.suse.com/1275519","tags":["report"]},{"url":"https://bugzilla.suse.com/1275528","tags":["report"]},{"url":"https://bugzilla.suse.com/1275535","tags":["report"]},{"url":"https://bugzilla.suse.com/1275540","tags":["report"]},{"url":"https://bugzilla.suse.com/1275553","tags":["report"]},{"url":"https://bugzilla.suse.com/1275555","tags":["report"]},{"url":"https://bugzilla.suse.com/1275557","tags":["report"]},{"url":"https://bugzilla.suse.com/1275561","tags":["report"]},{"url":"https://bugzilla.suse.com/1275566","tags":["report"]},{"url":"https://bugzilla.suse.com/1275569","tags":["report"]},{"url":"https://bugzilla.suse.com/1275572","tags":["report"]},{"url":"https://bugzilla.suse.com/1275574","tags":["report"]},{"url":"https://bugzilla.suse.com/1275578","tags":["report"]},{"url":"https://bugzilla.suse.com/1275582","tags":["report"]},{"url":"https://bugzilla.suse.com/1275583","tags":["report"]},{"url":"https://bugzilla.suse.com/1275584","tags":["report"]},{"url":"https://bugzilla.suse.com/1275587","tags":["report"]},{"url":"https://bugzilla.suse.com/1275588","tags":["report"]},{"url":"https://bugzilla.suse.com/1275591","tags":["report"]},{"url":"https://bugzilla.suse.com/1275595","tags":["report"]},{"url":"https://bugzilla.suse.com/1275596","tags":["report"]},{"url":"https://bugzilla.suse.com/1275633","tags":["report"]},{"url":"https://bugzilla.suse.com/1275636","tags":["report"]},{"url":"https://bugzilla.suse.com/1275650","tags":["report"]},{"url":"https://bugzilla.suse.com/1275655","tags":["report"]},{"url":"https://bugzilla.suse.com/1275656","tags":["report"]},{"url":"https://bugzilla.suse.com/1275659","tags":["report"]},{"url":"https://bugzilla.suse.com/1275665","tags":["report"]},{"url":"https://bugzilla.suse.com/1275669","tags":["report"]},{"url":"https://bugzilla.suse.com/1275672","tags":["report"]},{"url":"https://bugzilla.suse.com/1275679","tags":["report"]},{"url":"https://bugzilla.suse.com/1275685","tags":["report"]},{"url":"https://bugzilla.suse.com/1275687","tags":["report"]},{"url":"https://bugzilla.suse.com/1275688","tags":["report"]},{"url":"https://bugzilla.suse.com/1275690","tags":["report"]},{"url":"https://bugzilla.suse.com/1275695","tags":["report"]},{"url":"https://bugzilla.suse.com/1275696","tags":["report"]},{"url":"https://bugzilla.suse.com/1275704","tags":["report"]},{"url":"https://bugzilla.suse.com/1275737","tags":["report"]},{"url":"https://bugzilla.suse.com/1275782","tags":["report"]},{"url":"https://bugzilla.suse.com/1275784","tags":["report"]},{"url":"https://bugzilla.suse.com/1275787","tags":["report"]},{"url":"https://bugzilla.suse.com/1275788","tags":["report"]},{"url":"https://bugzilla.suse.com/1275789","tags":["report"]},{"url":"https://bugzilla.suse.com/1275790","tags":["report"]},{"url":"https://bugzilla.suse.com/1275798","tags":["report"]},{"url":"https://bugzilla.suse.com/1275799","tags":["report"]},{"url":"https://bugzilla.suse.com/1275801","tags":["report"]},{"url":"https://bugzilla.suse.com/1275802","tags":["report"]},{"url":"https://bugzilla.suse.com/1275804","tags":["report"]},{"url":"https://bugzilla.suse.com/1275805","tags":["report"]},{"url":"https://bugzilla.suse.com/1275812","tags":["report"]},{"url":"https://bugzilla.suse.com/1275817","tags":["report"]},{"url":"https://bugzilla.suse.com/1275818","tags":["report"]},{"url":"https://bugzilla.suse.com/1275819","tags":["report"]},{"url":"https://bugzilla.suse.com/1275820","tags":["report"]},{"url":"https://bugzilla.suse.com/1275821","tags":["report"]},{"url":"https://bugzilla.suse.com/1275822","tags":["report"]},{"url":"https://bugzilla.suse.com/1275823","tags":["report"]},{"url":"https://bugzilla.suse.com/1275827","tags":["report"]},{"url":"https://bugzilla.suse.com/1275864","tags":["report"]},{"url":"https://bugzilla.suse.com/1275866","tags":["report"]},{"url":"https://bugzilla.suse.com/1275867","tags":["report"]},{"url":"https://bugzilla.suse.com/1275869","tags":["report"]},{"url":"https://bugzilla.suse.com/1275870","tags":["report"]},{"url":"https://bugzilla.suse.com/1275871","tags":["report"]},{"url":"https://bugzilla.suse.com/1275872","tags":["report"]},{"url":"https://bugzilla.suse.com/1275886","tags":["report"]},{"url":"https://bugzilla.suse.com/1275905","tags":["report"]},{"url":"https://bugzilla.suse.com/1275923","tags":["report"]},{"url":"https://bugzilla.suse.com/1275925","tags":["report"]},{"url":"https://bugzilla.suse.com/1275928","tags":["report"]},{"url":"https://bugzilla.suse.com/1275950","tags":["report"]},{"url":"https://bugzilla.suse.com/1275954","tags":["report"]},{"url":"https://bugzilla.suse.com/1275956","tags":["report"]},{"url":"https://bugzilla.suse.com/1275970","tags":["report"]},{"url":"https://bugzilla.suse.com/1275973","tags":["report"]},{"url":"https://bugzilla.suse.com/1275975","tags":["report"]},{"url":"https://bugzilla.suse.com/1275976","tags":["report"]},{"url":"https://bugzilla.suse.com/1275985","tags":["report"]},{"url":"https://bugzilla.suse.com/1276006","tags":["report"]},{"url":"https://bugzilla.suse.com/1276029","tags":["report"]},{"url":"https://bugzilla.suse.com/1276257","tags":["report"]},{"url":"https://bugzilla.suse.com/1276258","tags":["report"]},{"url":"https://bugzilla.suse.com/1276263","tags":["report"]},{"url":"https://bugzilla.suse.com/1276265","tags":["report"]},{"url":"https://bugzilla.suse.com/1276267","tags":["report"]},{"url":"https://bugzilla.suse.com/1276270","tags":["report"]},{"url":"https://bugzilla.suse.com/1276273","tags":["report"]},{"url":"https://bugzilla.suse.com/1276277","tags":["report"]},{"url":"https://bugzilla.suse.com/1276333","tags":["report"]},{"url":"https://bugzilla.suse.com/1276335","tags":["report"]},{"url":"https://bugzilla.suse.com/1276339","tags":["report"]},{"url":"https://bugzilla.suse.com/1276341","tags":["report"]},{"url":"https://bugzilla.suse.com/1276346","tags":["report"]},{"url":"https://bugzilla.suse.com/1276354","tags":["report"]},{"url":"https://bugzilla.suse.com/1276355","tags":["report"]},{"url":"https://bugzilla.suse.com/1276381","tags":["report"]},{"url":"https://bugzilla.suse.com/1276395","tags":["report"]},{"url":"https://bugzilla.suse.com/1276446","tags":["report"]},{"url":"https://bugzilla.suse.com/1276452","tags":["report"]},{"url":"https://bugzilla.suse.com/1276468","tags":["report"]},{"url":"https://bugzilla.suse.com/1276471","tags":["report"]},{"url":"https://bugzilla.suse.com/1276473","tags":["report"]},{"url":"https://bugzilla.suse.com/1276500","tags":["report"]},{"url":"https://bugzilla.suse.com/1276507","tags":["report"]},{"url":"https://bugzilla.suse.com/1276512","tags":["report"]},{"url":"https://bugzilla.suse.com/1276528","tags":["report"]},{"url":"https://bugzilla.suse.com/1276542","tags":["report"]},{"url":"https://bugzilla.suse.com/1276546","tags":["report"]},{"url":"https://bugzilla.suse.com/1276547","tags":["report"]},{"url":"https://bugzilla.suse.com/1276551","tags":["report"]},{"url":"https://bugzilla.suse.com/1276552","tags":["report"]},{"url":"https://bugzilla.suse.com/1276553","tags":["report"]},{"url":"https://bugzilla.suse.com/1276561","tags":["report"]},{"url":"https://bugzilla.suse.com/1276562","tags":["report"]},{"url":"https://bugzilla.suse.com/1276566","tags":["report"]},{"url":"https://bugzilla.suse.com/1276569","tags":["report"]},{"url":"https://bugzilla.suse.com/1276572","tags":["report"]},{"url":"https://bugzilla.suse.com/1276577","tags":["report"]},{"url":"https://bugzilla.suse.com/1276586","tags":["report"]},{"url":"https://bugzilla.suse.com/1276665","tags":["report"]},{"url":"https://bugzilla.suse.com/1276766","tags":["report"]},{"url":"https://bugzilla.suse.com/1276767","tags":["report"]},{"url":"https://bugzilla.suse.com/1276771","tags":["report"]},{"url":"https://bugzilla.suse.com/1276785","tags":["report"]},{"url":"https://bugzilla.suse.com/1276793","tags":["report"]},{"url":"https://bugzilla.suse.com/1276801","tags":["report"]},{"url":"https://bugzilla.suse.com/1276803","tags":["report"]},{"url":"https://bugzilla.suse.com/1276814","tags":["report"]},{"url":"https://bugzilla.suse.com/1276818","tags":["report"]},{"url":"https://bugzilla.suse.com/1276821","tags":["report"]},{"url":"https://bugzilla.suse.com/1276831","tags":["report"]},{"url":"https://bugzilla.suse.com/1276840","tags":["report"]},{"url":"https://bugzilla.suse.com/1276864","tags":["report"]},{"url":"https://bugzilla.suse.com/1276865","tags":["report"]},{"url":"https://bugzilla.suse.com/1276866","tags":["report"]},{"url":"https://bugzilla.suse.com/1276870","tags":["report"]},{"url":"https://bugzilla.suse.com/1276876","tags":["report"]},{"url":"https://bugzilla.suse.com/1276880","tags":["report"]},{"url":"https://bugzilla.suse.com/1276905","tags":["report"]},{"url":"https://bugzilla.suse.com/1276913","tags":["report"]},{"url":"https://bugzilla.suse.com/1276922","tags":["report"]},{"url":"https://bugzilla.suse.com/1276931","tags":["report"]},{"url":"https://bugzilla.suse.com/1276937","tags":["report"]},{"url":"https://bugzilla.suse.com/1276941","tags":["report"]},{"url":"https://bugzilla.suse.com/1276955","tags":["report"]},{"url":"https://bugzilla.suse.com/1276957","tags":["report"]},{"url":"https://bugzilla.suse.com/1276961","tags":["report"]},{"url":"https://bugzilla.suse.com/1277022","tags":["report"]},{"url":"https://bugzilla.suse.com/1277023","tags":["report"]},{"url":"https://bugzilla.suse.com/1277033","tags":["report"]},{"url":"https://bugzilla.suse.com/1277034","tags":["report"]},{"url":"https://bugzilla.suse.com/1277037","tags":["report"]},{"url":"https://bugzilla.suse.com/1277047","tags":["report"]},{"url":"https://bugzilla.suse.com/1277054","tags":["report"]},{"url":"https://bugzilla.suse.com/1277057","tags":["report"]},{"url":"https://bugzilla.suse.com/1277059","tags":["report"]},{"url":"https://bugzilla.suse.com/1277062","tags":["report"]},{"url":"https://bugzilla.suse.com/1277066","tags":["report"]},{"url":"https://bugzilla.suse.com/1277069","tags":["report"]},{"url":"https://bugzilla.suse.com/1277070","tags":["report"]},{"url":"https://bugzilla.suse.com/1277077","tags":["report"]},{"url":"https://bugzilla.suse.com/1277078","tags":["report"]},{"url":"https://bugzilla.suse.com/1277092","tags":["report"]},{"url":"https://bugzilla.suse.com/1277095","tags":["report"]},{"url":"https://bugzilla.suse.com/1277108","tags":["report"]},{"url":"https://bugzilla.suse.com/1277114","tags":["report"]},{"url":"https://bugzilla.suse.com/1277115","tags":["report"]},{"url":"https://bugzilla.suse.com/1277118","tags":["report"]},{"url":"https://bugzilla.suse.com/1277120","tags":["report"]},{"url":"https://bugzilla.suse.com/1277155","tags":["report"]},{"url":"https://bugzilla.suse.com/1277159","tags":["report"]},{"url":"https://bugzilla.suse.com/1277160","tags":["report"]},{"url":"https://bugzilla.suse.com/1277202","tags":["report"]},{"url":"https://bugzilla.suse.com/1277204","tags":["report"]},{"url":"https://bugzilla.suse.com/1277227","tags":["report"]},{"url":"https://bugzilla.suse.com/1277229","tags":["report"]},{"url":"https://bugzilla.suse.com/1277230","tags":["report"]},{"url":"https://bugzilla.suse.com/1277231","tags":["report"]},{"url":"https://bugzilla.suse.com/1277233","tags":["report"]},{"url":"https://bugzilla.suse.com/1277249","tags":["report"]},{"url":"https://bugzilla.suse.com/1277254","tags":["report"]},{"url":"https://bugzilla.suse.com/1277265","tags":["report"]},{"url":"https://bugzilla.suse.com/1277268","tags":["report"]},{"url":"https://bugzilla.suse.com/1277275","tags":["report"]},{"url":"https://bugzilla.suse.com/1277285","tags":["report"]},{"url":"https://bugzilla.suse.com/1277308","tags":["report"]},{"url":"https://bugzilla.suse.com/1277311","tags":["report"]},{"url":"https://bugzilla.suse.com/1277315","tags":["report"]},{"url":"https://bugzilla.suse.com/1277321","tags":["report"]},{"url":"https://bugzilla.suse.com/1277328","tags":["report"]},{"url":"https://bugzilla.suse.com/1277335","tags":["report"]},{"url":"https://bugzilla.suse.com/1277349","tags":["report"]},{"url":"https://bugzilla.suse.com/1277350","tags":["report"]},{"url":"https://bugzilla.suse.com/1277391","tags":["report"]},{"url":"https://bugzilla.suse.com/1277407","tags":["report"]},{"url":"https://bugzilla.suse.com/1277408","tags":["report"]},{"url":"https://bugzilla.suse.com/1277485","tags":["report"]},{"url":"https://bugzilla.suse.com/1277505","tags":["report"]},{"url":"https://bugzilla.suse.com/1277513","tags":["report"]},{"url":"https://bugzilla.suse.com/1277551","tags":["report"]},{"url":"https://bugzilla.suse.com/1277553","tags":["report"]},{"url":"https://bugzilla.suse.com/1277561","tags":["report"]},{"url":"https://bugzilla.suse.com/1277574","tags":["report"]},{"url":"https://bugzilla.suse.com/1277636","tags":["report"]},{"url":"https://bugzilla.suse.com/1277641","tags":["report"]},{"url":"https://bugzilla.suse.com/1277649","tags":["report"]},{"url":"https://bugzilla.suse.com/1277655","tags":["report"]},{"url":"https://bugzilla.suse.com/1277656","tags":["report"]},{"url":"https://bugzilla.suse.com/1277660","tags":["report"]},{"url":"https://bugzilla.suse.com/1277668","tags":["report"]},{"url":"https://bugzilla.suse.com/1277680","tags":["report"]},{"url":"https://bugzilla.suse.com/1277688","tags":["report"]},{"url":"https://bugzilla.suse.com/1277726","tags":["report"]},{"url":"https://bugzilla.suse.com/1277728","tags":["report"]},{"url":"https://bugzilla.suse.com/1277738","tags":["report"]},{"url":"https://bugzilla.suse.com/1277748","tags":["report"]},{"url":"https://bugzilla.suse.com/1277761","tags":["report"]},{"url":"https://bugzilla.suse.com/1277764","tags":["report"]},{"url":"https://bugzilla.suse.com/1277773","tags":["report"]},{"url":"https://bugzilla.suse.com/1277775","tags":["report"]},{"url":"https://bugzilla.suse.com/1277776","tags":["report"]},{"url":"https://bugzilla.suse.com/1277782","tags":["report"]},{"url":"https://bugzilla.suse.com/1277783","tags":["report"]},{"url":"https://bugzilla.suse.com/1277813","tags":["report"]},{"url":"https://bugzilla.suse.com/1277818","tags":["report"]},{"url":"https://bugzilla.suse.com/1277822","tags":["report"]},{"url":"https://bugzilla.suse.com/1277845","tags":["report"]},{"url":"https://bugzilla.suse.com/1277862","tags":["report"]},{"url":"https://bugzilla.suse.com/1277874","tags":["report"]},{"url":"https://bugzilla.suse.com/1277876","tags":["report"]},{"url":"https://bugzilla.suse.com/1277898","tags":["report"]},{"url":"https://bugzilla.suse.com/1277901","tags":["report"]},{"url":"https://bugzilla.suse.com/1277908","tags":["report"]},{"url":"https://bugzilla.suse.com/1277918","tags":["report"]},{"url":"https://bugzilla.suse.com/1278039","tags":["report"]},{"url":"https://bugzilla.suse.com/1278070","tags":["report"]},{"url":"https://bugzilla.suse.com/1278088","tags":["report"]},{"url":"https://bugzilla.suse.com/1278094","tags":["report"]},{"url":"https://bugzilla.suse.com/1278098","tags":["report"]},{"url":"https://bugzilla.suse.com/1278113","tags":["report"]},{"url":"https://bugzilla.suse.com/1278155","tags":["report"]},{"url":"https://bugzilla.suse.com/1278180","tags":["report"]},{"url":"https://bugzilla.suse.com/1278233","tags":["report"]},{"url":"https://bugzilla.suse.com/1278236","tags":["report"]},{"url":"https://bugzilla.suse.com/1278240","tags":["report"]},{"url":"https://bugzilla.suse.com/1278253","tags":["report"]},{"url":"https://bugzilla.suse.com/1278293","tags":["report"]},{"url":"https://bugzilla.suse.com/1278324","tags":["report"]},{"url":"https://bugzilla.suse.com/1278331","tags":["report"]},{"url":"https://bugzilla.suse.com/1278334","tags":["report"]},{"url":"https://bugzilla.suse.com/1278395","tags":["report"]},{"url":"https://bugzilla.suse.com/1278416","tags":["report"]},{"url":"https://bugzilla.suse.com/1278703","tags":["report"]},{"url":"https://bugzilla.suse.com/1278716","tags":["report"]},{"url":"https://bugzilla.suse.com/1278733","tags":["report"]},{"url":"https://bugzilla.suse.com/1279487","tags":["report"]},{"url":"https://bugzilla.suse.com/1279537","tags":["report"]},{"url":"https://bugzilla.suse.com/1279580","tags":["report"]},{"url":"https://bugzilla.suse.com/1279813","tags":["report"]},{"url":"https://bugzilla.suse.com/1279842","tags":["report"]},{"url":"https://bugzilla.suse.com/1279847","tags":["report"]},{"url":"https://bugzilla.suse.com/1279887","tags":["report"]},{"url":"https://bugzilla.suse.com/1280139","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31530","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52929","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53341","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63906","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63920","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63921","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63925","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63928","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63987","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64002","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64275","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64296","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64305","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64333","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64338","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64341","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64342","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64364","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64376","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64383","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64384","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64385","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64401","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64415","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64423","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64433","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64477","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64478","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64486","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64487","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64503","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64517","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64518","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64519","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64524","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64526","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64543","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64544","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64545","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64549","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64551","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64561","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64562","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64571","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64573","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68144","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68193","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68199","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68260","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68296","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68333","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68338","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68358","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68371","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68377","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68419","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68432","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68433","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72036","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72296","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72341","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72342","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72389","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72414","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72437","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72438","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72485","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72487","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72488","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74296","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74375","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74377","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74390","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74397","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74517","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74518","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74523","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74545","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74555","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74571","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74598","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74610","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74615","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74616","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74695","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74712","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74722","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74723","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80530","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80533","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80561","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80629","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80693","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80838","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623887-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623897-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202623902-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-68780","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-68780","tags":["report"]},{"url":"https://git.kernel.org/linus/382748c05e58a9f1935f5a653c352422375566ea","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8096-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8096-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8096-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8096-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8116-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8096-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8141-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8163-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8163-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8177-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8179-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8177-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8183-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8184-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8179-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8185-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8183-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8179-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8203-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8204-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8185-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8179-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8243-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8245-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8257-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8258-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8260-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8261-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8265-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8440-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-49465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-37354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-41014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-46830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-47666","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-49968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40252","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40281","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68177","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68308","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68366","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68367","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68372","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68727","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68733","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68785","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68814","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68818","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68821","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23047","tags":["report"]},{"url":"https://launchpad.net/bugs/2143853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-53114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-56538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39953","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39955","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39971","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40029","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23404","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68353","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68791","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68802","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68380","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53421","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-53662","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-54207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40353","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-50004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47337","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2025-68780","title":"sched/deadline: only set free_cpus for online runqueues","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\"sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u003eonline\") introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\"sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\") removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com\n\nAnother occurs when the last deadline task is migrated from a\nCPU that has an offlined runqueue. The dequeue_task member of\nthe deadline scheduler class will eventually call cpudl_clear\nand set the free_cpus bit for the CPU.\n\nThis commit modifies the cpudl_clear function to be aware of the\nonline state of the deadline runqueue so that the free_cpus mask\ncan be updated appropriately.\n\nIt is no longer necessary to manage the mask outside of the\ncpudl_set/clear functions so the cpudl_set/clear_freecpu\nfunctions are removed. In addition, since the free_cpus mask is\nnow only updated under the cpudl lock the code was changed to\nuse the non-atomic __cpumask functions.","status":"published","published":"2026-01-13T15:28:55.483Z","modified":"2026-05-11T21:53:12.601Z","updated_at":"2026-11-02T14:32:35.742256Z"}],"euvd":[{"id":"EUVD-2026-2336","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\"sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u003eonline\") introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\"sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\") removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com\n\nAnother occurs when the last deadline task is migrated from a\nCPU that has an offlined runqueue. The dequeue_task member of\nthe deadline scheduler class will eventually call cpudl_clear\nand set the free_cpus bit for the CPU.\n\nThis commit modifies the cpudl_clear function to be aware of the\nonline state of the deadline runqueue so that the free_cpus mask\ncan be updated appropriately.\n\nIt is no longer necessary to manage the mask outside of the\ncpudl_set/clear functions so the cpudl_set/clear_freecpu\nfunctions are removed. In addition, since the free_cpus mask is\nnow only updated under the cpudl lock the code was changed to\nuse the non-atomic __cpumask functions.","status":"published","published":"2026-01-13T15:28:55Z","modified":"2026-05-11T21:53:12Z","updated_at":"2026-11-02T19:04:46.041212Z"}],"ghsa":[{"id":"GHSA-386q-4477-2c5h","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\"sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u003eonline\") introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\"sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\") removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com\n\nAnother occurs when the last deadline task is migrated from a\nCPU that has an offlined runqueue. The dequeue_task member of\nthe deadline scheduler class will eventually call cpudl_clear\nand set the free_cpus bit for the CPU.\n\nThis commit modifies the cpudl_clear function to be aware of the\nonline state of the deadline runqueue so that the free_cpus mask\ncan be updated appropriately.\n\nIt is no longer necessary to manage the mask outside of the\ncpudl_set/clear functions so the cpudl_set/clear_freecpu\nfunctions are removed. In addition, since the free_cpus mask is\nnow only updated under the cpudl lock the code was changed to\nuse the non-atomic __cpumask functions.","status":"published","published":"2026-01-13T18:31:03Z","modified":"2026-01-19T15:30:35Z","updated_at":"2026-11-02T15:05:39.898984Z"}],"nvd":[{"id":"CVE-2025-68780","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\"sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u003eonline\") introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\"sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\") removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com\n\nAnother occurs when the last deadline task is migrated from a\nCPU that has an offlined runqueue. The dequeue_task member of\nthe deadline scheduler class will eventually call cpudl_clear\nand set the free_cpus bit for the CPU.\n\nThis commit modifies the cpudl_clear function to be aware of the\nonline state of the deadline runqueue so that the free_cpus mask\ncan be updated appropriately.\n\nIt is no longer necessary to manage the mask outside of the\ncpudl_set/clear functions so the cpudl_set/clear_freecpu\nfunctions are removed. In addition, since the free_cpus mask is\nnow only updated under the cpudl lock the code was changed to\nuse the non-atomic __cpumask functions.","status":"published","published":"2026-01-13T16:15:57.657Z","modified":"2026-06-17T09:59:34.603Z","updated_at":"2026-11-02T14:11:56.616231Z"}],"osv":[{"id":"OESA-2026-1759","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\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\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/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntimers: Fix NULL function pointer race in timer_shutdown_sync()\n\nThere is a race condition between timer_shutdown_sync() and timer\nexpiration that can lead to hitting a WARN_ON in expire_timers().\n\nThe issue occurs when timer_shutdown_sync() clears the timer function\nto NULL while the timer is still running on another CPU. The race\nscenario looks like this:\n\nCPU0\t\t\t\t\tCPU1\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tbase-\u0026gt;running_timer = timer;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t[call_timer_fn enter]\n\t\t\t\t\tmod_timer()\n\t\t\t\t\t...\ntimer_shutdown_sync()\nlock_timer_base()\n// For now, will not detach the timer but only clear its function to NULL\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\t\t\t\t\t[call_timer_fn exit]\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\tbase-\u0026gt;running_timer = NULL;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t...\n\t\t\t\t\t// Now timer is pending while its function set to NULL.\n\t\t\t\t\t// next timer trigger\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tWARN_ON_ONCE(!fn) // hit\n\t\t\t\t\t...\nlock_timer_base()\n// Now timer will detach\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\nThe problem is that timer_shutdown_sync() clears the timer function\nregardless of whether the timer is currently running. This can leave a\npending timer with a NULL function pointer, which triggers the\nWARN_ON_ONCE(!fn) check in expire_timers().\n\nFix this by only clearing the timer function when actually detaching the\ntimer. If the timer is running, leave the function pointer intact, which is\nsafe because the timer will be properly detached when it finishes running.(CVE-2025-68214)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/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\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:44.306450654Z","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:45.721983Z"},{"id":"OESA-2026-1760","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\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\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/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntimers: Fix NULL function pointer race in timer_shutdown_sync()\n\nThere is a race condition between timer_shutdown_sync() and timer\nexpiration that can lead to hitting a WARN_ON in expire_timers().\n\nThe issue occurs when timer_shutdown_sync() clears the timer function\nto NULL while the timer is still running on another CPU. The race\nscenario looks like this:\n\nCPU0\t\t\t\t\tCPU1\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tbase-\u0026gt;running_timer = timer;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t[call_timer_fn enter]\n\t\t\t\t\tmod_timer()\n\t\t\t\t\t...\ntimer_shutdown_sync()\nlock_timer_base()\n// For now, will not detach the timer but only clear its function to NULL\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\t\t\t\t\t[call_timer_fn exit]\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\tbase-\u0026gt;running_timer = NULL;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t...\n\t\t\t\t\t// Now timer is pending while its function set to NULL.\n\t\t\t\t\t// next timer trigger\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tWARN_ON_ONCE(!fn) // hit\n\t\t\t\t\t...\nlock_timer_base()\n// Now timer will detach\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\nThe problem is that timer_shutdown_sync() clears the timer function\nregardless of whether the timer is currently running. This can leave a\npending timer with a NULL function pointer, which triggers the\nWARN_ON_ONCE(!fn) check in expire_timers().\n\nFix this by only clearing the timer function when actually detaching the\ntimer. If the timer is running, leave the function pointer intact, which is\nsafe because the timer will be properly detached when it finishes running.(CVE-2025-68214)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/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\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in ksmbd_tree_connect_put under concurrency\n\nUnder high concurrency, A tree-connection object (tcon) is freed on\na disconnect path while another path still holds a reference and later\nexecutes *_put()/write on it.(CVE-2025-68817)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntpm: Cap the number of PCR banks\n\ntpm2_get_pcr_allocation() does not cap any upper limit for the number of\nbanks. Cap the limit to eight banks so that out of bounds values coming\nfrom external I/O cause on only limited harm.(CVE-2025-71077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: change all pageblocks migrate type on coalescing\n\nWhen a page is freed it coalesces with a buddy into a higher order page\nwhile possible.  When the buddy page migrate type differs, it is expected\nto be updated to match the one of the page being freed.\n\nHowever, only the first pageblock of the buddy page is updated, while the\nrest of the pageblocks are left unchanged.\n\nThat causes warnings in later expand() and other code paths (like below),\nsince an inconsistency between migration type of the list containing the\npage and the page-owned pageblocks migration types is introduced.\n\n[  308.986589] ------------[ cut here ]------------\n[  308.987227] page type is 0, passed migratetype is 1 (nr=256)\n[  308.987275] WARNING: CPU: 1 PID: 5224 at mm/page_alloc.c:812 expand+0x23c/0x270\n[  308.987293] Modules linked in: algif_hash(E) af_alg(E) nft_fib_inet(E) nft_fib_ipv4(E) nft_fib_ipv6(E) nft_fib(E) nft_reject_inet(E) nf_reject_ipv4(E) nf_reject_ipv6(E) nft_reject(E) nft_ct(E) nft_chain_nat(E) nf_nat(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) nf_tables(E) s390_trng(E) vfio_ccw(E) mdev(E) vfio_iommu_type1(E) vfio(E) sch_fq_codel(E) drm(E) i2c_core(E) drm_panel_orientation_quirks(E) loop(E) nfnetlink(E) vsock_loopback(E) vmw_vsock_virtio_transport_common(E) vsock(E) ctcm(E) fsm(E) diag288_wdt(E) watchdog(E) zfcp(E) scsi_transport_fc(E) ghash_s390(E) prng(E) aes_s390(E) des_generic(E) des_s390(E) libdes(E) sha3_512_s390(E) sha3_256_s390(E) sha_common(E) paes_s390(E) crypto_engine(E) pkey_cca(E) pkey_ep11(E) zcrypt(E) rng_core(E) pkey_pckmo(E) pkey(E) autofs4(E)\n[  308.987439] Unloaded tainted modules: hmac_s390(E):2\n[  308.987650] CPU: 1 UID: 0 PID: 5224 Comm: mempig_verify Kdump: loaded Tainted: G            E       6.18.0-gcc-bpf-debug #431 PREEMPT\n[  308.987657] Tainted: [E]=UNSIGNED_MODULE\n[  308.987661] Hardware name: IBM 3906 M04 704 (z/VM 7.3.0)\n[  308.987666] Krnl PSW : 0404f00180000000 00000349976fa600 (expand+0x240/0x270)\n[  308.987676]            R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:3 PM:0 RI:0 EA:3\n[  308.987682] Krnl GPRS: 0000034980000004 0000000000000005 0000000000000030 000003499a0e6d88\n[  308.987688]            0000000000000005 0000034980000005 000002be803ac000 0000023efe6c8300\n[  308.987692]            0000000000000008 0000034998d57290 000002be00000100 0000023e00000008\n[  308.987696]            0000000000000000 0000000000000000 00000349976fa5fc 000002c99b1eb6f0\n[  308.987708] Krnl Code: 00000349976fa5f0: c020008a02f2\tlarl\t%r2,000003499883abd4\n                          00000349976fa5f6: c0e5ffe3f4b5\tbrasl\t%r14,0000034997378f60\n                         #00000349976fa5fc: af000000\t\tmc\t0,0\n                         \u0026gt;00000349976fa600: a7f4ff4c\t\tbrc\t15,00000349976fa498\n                          00000349976fa604: b9040026\t\tlgr\t%r2,%r6\n                          00000349976fa608: c0300088317f\tlarl\t%r3,0000034998800906\n                          00000349976fa60e: c0e5fffdb6e1\tbrasl\t%r14,00000349976b13d0\n                          00000349976fa614: af000000\t\tmc\t0,0\n[  308.987734] Call Trace:\n[  308.987738]  [\u0026lt;00000349976fa600\u0026gt;] expand+0x240/0x270\n[  308.987744] ([\u0026lt;00000349976fa5fc\u0026gt;] expand+0x23c/0x270)\n[  308.987749]  [\u0026lt;00000349976ff95e\u0026gt;] rmqueue_bulk+0x71e/0x940\n[  308.987754]  [\u0026lt;00000349976ffd7e\u0026gt;] __rmqueue_pcplist+0x1fe/0x2a0\n[  308.987759]  [\u0026lt;0000034997700966\u0026gt;] rmqueue.isra.0+0xb46/0xf40\n[  308.987763]  [\u0026lt;0000034997703ec8\u0026gt;] get_page_from_freelist+0x198/0x8d0\n[  308.987768]  [\u0026lt;0000034997706fa8\u0026gt;] __alloc_frozen_pages_noprof+0x198/0x400\n[  308.987774]  [\u0026lt;00000349977536f8\u0026gt;] alloc_pages_mpol+0xb8/0x220\n[  308.987781]  [\u0026lt;0000034997753bf6\u0026gt;] folio_alloc_mpol_noprof+0x26/0xc0\n[  308.987786]  [\u0026lt;0000034997753e4c\u0026gt;] vma_alloc_folio_noprof+0x6c/0xa0\n[  308.987791]  [\u0026lt;0000034997775b22\u0026gt;] vma_alloc_anon_folio_pmd+0x42/0x240\n[  308.987799]  [\u0026lt;000003499777bfea\u0026gt;] __do_huge_pmd_anonymous_page+0x3a/0x210\n[  308.987804]  [\u0026lt;00000349976cb0\n---truncated---(CVE-2025-71134)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: properly keep track of conduit reference\n\nProblem description\n-------------------\n\nDSA has a mumbo-jumbo of reference handling of the conduit net device\nand its kobject which, sadly, is just wrong and doesn\u0026apos;t make sense.\n\nThere are two distinct problems.\n\n1. The OF path, which uses of_find_net_device_by_node(), never releases\n   the elevated refcount on the conduit\u0026apos;s kobject. Nominally, the OF and\n   non-OF paths should result in objects having identical reference\n   counts taken, and it is already suspicious that\n   dsa_dev_to_net_device() has a put_device() call which is missing in\n   dsa_port_parse_of(), but we can actually even verify that an issue\n   exists. With CONFIG_DEBUG_KOBJECT_RELEASE=y, if we run this command\n   \u0026quot;before\u0026quot; and \u0026quot;after\u0026quot; applying this patch:\n\n(unbind the conduit driver for net device eno2)\necho 0000:00:00.2 \u0026gt; /sys/bus/pci/drivers/fsl_enetc/unbind\n\nwe see these lines in the output diff which appear only with the patch\napplied:\n\nkobject: \u0026apos;eno2\u0026apos; (ffff002009a3a6b8): kobject_release, parent 0000000000000000 (delayed 1000)\nkobject: \u0026apos;109\u0026apos; (ffff0020099d59a0): kobject_release, parent 0000000000000000 (delayed 1000)\n\n2. After we find the conduit interface one way (OF) or another (non-OF),\n   it can get unregistered at any time, and DSA remains with a long-lived,\n   but in this case stale, cpu_dp-\u0026gt;conduit pointer. Holding the net\n   device\u0026apos;s underlying kobject isn\u0026apos;t actually of much help, it just\n   prevents it from being freed (but we never need that kobject\n   directly). What helps us to prevent the net device from being\n   unregistered is the parallel netdev reference mechanism (dev_hold()\n   and dev_put()).\n\nActually we actually use that netdev tracker mechanism implicitly on\nuser ports since commit 2f1e8ea726e9 (\u0026quot;net: dsa: link interfaces with\nthe DSA master to get rid of lockdep warnings\u0026quot;), via netdev_upper_dev_link().\nBut time still passes at DSA switch probe time between the initial\nof_find_net_device_by_node() code and the user port creation time, time\nduring which the conduit could unregister itself and DSA wouldn\u0026apos;t know\nabout it.\n\nSo we have to run of_find_net_device_by_node() under rtnl_lock() to\nprevent that from happening, and release the lock only with the netdev\ntracker having acquired the reference.\n\nDo we need to keep the reference until dsa_unregister_switch() /\ndsa_switch_shutdown()?\n1: Maybe yes. A switch device will still be registered even if all user\n   ports failed to probe, see commit 86f8b1c01a0a (\u0026quot;net: dsa: Do not\n   make user port errors fatal\u0026quot;), and the cpu_dp-\u0026gt;conduit pointers\n   remain valid.  I haven\u0026apos;t audited all call paths to see whether they\n   will actually use the conduit in lack of any user port, but if they\n   do, it seems safer to not rely on user ports for that reference.\n2. Definitely yes. We support changing the conduit which a user port is\n   associated to, and we can get into a situation where we\u0026apos;ve moved all\n   user ports away from a conduit, thus no longer hold any reference to\n   it via the net device tracker. But we shouldn\u0026apos;t let it go nonetheless\n   - see the next change in relation to dsa_tree_find_first_conduit()\n   and LAG conduits which disappear.\n   We have to be prepared to return to the physical conduit, so the CPU\n   port must explicitly keep another reference to it. This is also to\n   say: the user ports and their CPU ports may not always keep a\n   reference to the same conduit net device, and both are needed.\n\nAs for the conduit\u0026apos;s kobject for the /sys/class/net/ entry, we don\u0026apos;t\ncare about it, we can release it as soon as we hold the net device\nobject itself.\n\nHistory and blame attribution\n-----------------------------\n\nThe code has been refactored so many times, it is very difficult to\nfollow and properly attribute a blame, but I\u0026apos;ll try to make a short\nhistory which I hope to be correct.\n\nWe have two distinct probing paths:\n- one for OF, introduced in 2016 i\n---truncated---(CVE-2025-71152)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: rtl8150: fix memory leak on usb_submit_urb() failure\n\nIn async_set_registers(), when usb_submit_urb() fails, the allocated\n  async_req structure and URB are not freed, causing a memory leak.\n\n  The completion callback async_set_reg_cb() is responsible for freeing\n  these allocations, but it is only called after the URB is successfully\n  submitted and completes (successfully or with error). If submission\n  fails, the callback never runs and the memory is leaked.\n\n  Fix this by freeing both the URB and the request structure in the error\n  path when usb_submit_urb() fails.(CVE-2025-71154)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix bsg_done() causing double free\n\nKernel panic observed on system,\n\n[5353358.825191] BUG: unable to handle page fault for address: ff5f5e897b024000\n[5353358.825194] #PF: supervisor write access in kernel mode\n[5353358.825195] #PF: error_code(0x0002) - not-present page\n[5353358.825196] PGD 100006067 P4D 0\n[5353358.825198] Oops: 0002 [#1] PREEMPT SMP NOPTI\n[5353358.825200] CPU: 5 PID: 2132085 Comm: qlafwupdate.sub Kdump: loaded Tainted: G        W    L    -------  ---  5.14.0-503.34.1.el9_5.x86_64 #1\n[5353358.825203] Hardware name: HPE ProLiant DL360 Gen11/ProLiant DL360 Gen11, BIOS 2.44 01/17/2025\n[5353358.825204] RIP: 0010:memcpy_erms+0x6/0x10\n[5353358.825211] RSP: 0018:ff591da8f4f6b710 EFLAGS: 00010246\n[5353358.825212] RAX: ff5f5e897b024000 RBX: 0000000000007090 RCX: 0000000000001000\n[5353358.825213] RDX: 0000000000001000 RSI: ff591da8f4fed090 RDI: ff5f5e897b024000\n[5353358.825214] RBP: 0000000000010000 R08: ff5f5e897b024000 R09: 0000000000000000\n[5353358.825215] R10: ff46cf8c40517000 R11: 0000000000000001 R12: 0000000000008090\n[5353358.825216] R13: ff591da8f4f6b720 R14: 0000000000001000 R15: 0000000000000000\n[5353358.825218] FS:  00007f1e88d47740(0000) GS:ff46cf935f940000(0000) knlGS:0000000000000000\n[5353358.825219] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[5353358.825220] CR2: ff5f5e897b024000 CR3: 0000000231532004 CR4: 0000000000771ef0\n[5353358.825221] PKRU: 55555554\n[5353358.825222] Call Trace:\n[5353358.825223]  \u0026lt;TASK\u0026gt;\n[5353358.825224]  ? show_trace_log_lvl+0x1c4/0x2df\n[5353358.825229]  ? show_trace_log_lvl+0x1c4/0x2df\n[5353358.825232]  ? sg_copy_buffer+0xc8/0x110\n[5353358.825236]  ? __die_body.cold+0x8/0xd\n[5353358.825238]  ? page_fault_oops+0x134/0x170\n[5353358.825242]  ? kernelmode_fixup_or_oops+0x84/0x110\n[5353358.825244]  ? exc_page_fault+0xa8/0x150\n[5353358.825247]  ? asm_exc_page_fault+0x22/0x30\n[5353358.825252]  ? memcpy_erms+0x6/0x10\n[5353358.825253]  sg_copy_buffer+0xc8/0x110\n[5353358.825259]  qla2x00_process_vendor_specific+0x652/0x1320 [qla2xxx]\n[5353358.825317]  qla24xx_bsg_request+0x1b2/0x2d0 [qla2xxx]\n\nMost routines in qla_bsg.c call bsg_done() only for success cases.\nHowever a few invoke it for failure case as well leading to a double\nfree. Validate before calling bsg_done().(CVE-2025-71238)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: avoid kernel-infoleak from struct iw_point\n\nstruct iw_point has a 32bit hole on 64bit arches.\n\nstruct iw_point {\n  void __user   *pointer;       /* Pointer to the data  (in user space) */\n  __u16         length;         /* number of fields or size in bytes */\n  __u16         flags;          /* Optional params */\n};\n\nMake sure to zero the structure to avoid disclosing 32bits of kernel data\nto user space.(CVE-2026-22978)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: provide locking for v4_end_grace\n\nWriting to v4_end_grace can race with server shutdown and result in\nmemory being accessed after it was freed - reclaim_str_hashtbl in\nparticularly.\n\nWe cannot hold nfsd_mutex across the nfsd4_end_grace() call as that is\nheld while client_tracking_op-\u0026gt;init() is called and that can wait for\nan upcall to nfsdcltrack which can write to v4_end_grace, resulting in a\ndeadlock.\n\nnfsd4_end_grace() is also called by the landromat work queue and this\ndoesn\u0026apos;t require locking as server shutdown will stop the work and wait\nfor it before freeing anything that nfsd4_end_grace() might access.\n\nHowever, we must be sure that writing to v4_end_grace doesn\u0026apos;t restart\nthe work item after shutdown has already waited for it.  For this we\nadd a new flag protected with nn-\u0026gt;client_lock.  It is set only while it\nis safe to make client tracking calls, and v4_end_grace only schedules\nwork while the flag is set with the spinlock held.\n\nSo this patch adds a nfsd_net field \u0026quot;client_tracking_active\u0026quot; which is\nset as described.  Another field \u0026quot;grace_end_forced\u0026quot;, is set when\nv4_end_grace is written.  After this is set, and providing\nclient_tracking_active is set, the laundromat is scheduled.\nThis \u0026quot;grace_end_forced\u0026quot; field bypasses other checks for whether the\ngrace period has finished.\n\nThis resolves a race which can result in use-after-free.(CVE-2026-22980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: replace overzealous BUG_ON in osdmap_apply_incremental()\n\nIf the osdmap is (maliciously) corrupted such that the incremental\nosdmap epoch is different from what is expected, there is no need to\nBUG.  Instead, just declare the incremental osdmap to be invalid.(CVE-2026-22990)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: return the handler error from mon_handle_auth_done()\n\nCurrently any error from ceph_auth_handle_reply_done() is propagated\nvia finish_auth() but isn\u0026apos;t returned from mon_handle_auth_done().  This\nresults in higher layers learning that (despite the monitor considering\nus to be successfully authenticated) something went wrong in the\nauthentication phase and reacting accordingly, but msgr2 still trying\nto proceed with establishing the session in the background.  In the\ncase of secure mode this can trigger a WARN in setup_crypto() and later\nlead to a NULL pointer dereference inside of prepare_auth_signature().(CVE-2026-22992)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: authencesn - reject too-short AAD (assoclen\u0026lt;8) to match ESP/ESN spec\n\nauthencesn assumes an ESP/ESN-formatted AAD. When assoclen is shorter than\nthe minimum expected length, crypto_authenc_esn_decrypt() can advance past\nthe end of the destination scatterlist and trigger a NULL pointer dereference\nin scatterwalk_map_and_copy(), leading to a kernel panic (DoS).\n\nAdd a minimum AAD length check to fail fast on invalid inputs.(CVE-2026-23060)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: fix potential underflow in virtio_transport_get_credit()\n\nThe credit calculation in virtio_transport_get_credit() uses unsigned\narithmetic:\n\n  ret = vvs-\u0026gt;peer_buf_alloc - (vvs-\u0026gt;tx_cnt - vvs-\u0026gt;peer_fwd_cnt);\n\nIf the peer shrinks its advertised buffer (peer_buf_alloc) while bytes\nare in flight, the subtraction can underflow and produce a large\npositive value, potentially allowing more data to be queued than the\npeer can handle.\n\nReuse virtio_transport_has_space() which already handles this case and\nadd a comment to make it clear why we are doing that.\n\n[Stefano: use virtio_transport_has_space() instead of duplicating the code]\n[Stefano: tweak the commit message](CVE-2026-23069)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregmap: Fix race condition in hwspinlock irqsave routine\n\nPreviously, the address of the shared member \u0026apos;\u0026amp;map-\u0026gt;spinlock_flags\u0026apos; was\npassed directly to \u0026apos;hwspin_lock_timeout_irqsave\u0026apos;. This creates a race\ncondition where multiple contexts contending for the lock could overwrite\nthe shared flags variable, potentially corrupting the state for the\ncurrent lock owner.\n\nFix this by using a local stack variable \u0026apos;flags\u0026apos; to store the IRQ state\ntemporarily.(CVE-2026-23071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: cap TX credit to local buffer size\n\nThe virtio transports derives its TX credit directly from peer_buf_alloc,\nwhich is set from the remote endpoint\u0026apos;s SO_VM_SOCKETS_BUFFER_SIZE value.\n\nOn the host side this means that the amount of data we are willing to\nqueue for a connection is scaled by a guest-chosen buffer size, rather\nthan the host\u0026apos;s own vsock configuration. A malicious guest can advertise\na large buffer and read slowly, causing the host to allocate a\ncorrespondingly large amount of sk_buff memory.\nThe same thing would happen in the guest with a malicious host, since\nvirtio transports share the same code base.\n\nIntroduce a small helper, virtio_transport_tx_buf_size(), that\nreturns min(peer_buf_alloc, buf_alloc), and use it wherever we consume\npeer_buf_alloc.\n\nThis ensures the effective TX window is bounded by both the peer\u0026apos;s\nadvertised buffer and our own buf_alloc (already clamped to\nbuffer_max_size via SO_VM_SOCKETS_BUFFER_MAX_SIZE), so a remote peer\ncannot force the other to queue more data than allowed by its own\nvsock settings.\n\nOn an unpatched Ubuntu 22.04 host (~64 GiB RAM), running a PoC with\n32 guest vsock connections advertising 2 GiB each and reading slowly\ndrove Slab/SUnreclaim from ~0.5 GiB to ~57 GiB; the system only\nrecovered after killing the QEMU process. That said, if QEMU memory is\nlimited with cgroups, the maximum memory used will be limited.\n\nWith this patch applied:\n\n  Before:\n    MemFree:        ~61.6 GiB\n    Slab:           ~142 MiB\n    SUnreclaim:     ~117 MiB\n\n  After 32 high-credit connections:\n    MemFree:        ~61.5 GiB\n    Slab:           ~178 MiB\n    SUnreclaim:     ~152 MiB\n\nOnly ~35 MiB increase in Slab/SUnreclaim, no host OOM, and the guest\nremains responsive.\n\nCompatibility with non-virtio transports:\n\n  - VMCI uses the AF_VSOCK buffer knobs to size its queue pairs per\n    socket based on the local vsk-\u0026gt;buffer_* values; the remote side\n    cannot enlarge those queues beyond what the local endpoint\n    configured.\n\n  - Hyper-V\u0026apos;s vsock transport uses fixed-size VMBus ring buffers and\n    an MTU bound; there is no peer-controlled credit field comparable\n    to peer_buf_alloc, and the remote endpoint cannot drive in-flight\n    kernel memory above those ring sizes.\n\n  - The loopback path reuses virtio_transport_common.c, so it\n    naturally follows the same semantics as the virtio transport.\n\nThis change is limited to virtio_transport_common.c and thus affects\nvirtio-vsock, vhost-vsock, and loopback, bringing them in line with the\n\u0026quot;remote window intersected with local policy\u0026quot; behaviour that VMCI and\nHyper-V already effectively have.\n\n[Stefano: small adjustments after changing the previous patch]\n[Stefano: tweak the commit message](CVE-2026-23086)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: limit BOND_MODE_8023AD to Ethernet devices\n\nBOND_MODE_8023AD makes sense for ARPHRD_ETHER only.\n\nsyzbot reported:\n\n BUG: KASAN: global-out-of-bounds in __hw_addr_create net/core/dev_addr_lists.c:63 [inline]\n BUG: KASAN: global-out-of-bounds in __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118\nRead of size 16 at addr ffffffff8bf94040 by task syz.1.3580/19497\n\nCPU: 1 UID: 0 PID: 19497 Comm: syz.1.3580 Tainted: G             L      syzkaller #0 PREEMPT(full)\nTainted: [L]=SOFTLOCKUP\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120\n  print_address_description mm/kasan/report.c:378 [inline]\n  print_report+0xca/0x240 mm/kasan/report.c:482\n  kasan_report+0x118/0x150 mm/kasan/report.c:595\n check_region_inline mm/kasan/generic.c:-1 [inline]\n  kasan_check_range+0x2b0/0x2c0 mm/kasan/generic.c:200\n  __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105\n  __hw_addr_create net/core/dev_addr_lists.c:63 [inline]\n  __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118\n  __dev_mc_add net/core/dev_addr_lists.c:868 [inline]\n  dev_mc_add+0xa1/0x120 net/core/dev_addr_lists.c:886\n  bond_enslave+0x2b8b/0x3ac0 drivers/net/bonding/bond_main.c:2180\n  do_set_master+0x533/0x6d0 net/core/rtnetlink.c:2963\n  do_setlink+0xcf0/0x41c0 net/core/rtnetlink.c:3165\n  rtnl_changelink net/core/rtnetlink.c:3776 [inline]\n  __rtnl_newlink net/core/rtnetlink.c:3935 [inline]\n  rtnl_newlink+0x161c/0x1c90 net/core/rtnetlink.c:4072\n  rtnetlink_rcv_msg+0x7cf/0xb70 net/core/rtnetlink.c:6958\n  netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2550\n  netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n  netlink_unicast+0x82f/0x9e0 net/netlink/af_netlink.c:1344\n  netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1894\n  sock_sendmsg_nosec net/socket.c:727 [inline]\n  __sock_sendmsg+0x21c/0x270 net/socket.c:742\n  ____sys_sendmsg+0x505/0x820 net/socket.c:2592\n  ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2646\n  __sys_sendmsg+0x164/0x220 net/socket.c:2678\n  do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n  __do_fast_syscall_32+0x1dc/0x560 arch/x86/entry/syscall_32.c:307\n  do_fast_syscall_32+0x34/0x80 arch/x86/entry/syscall_32.c:332\n entry_SYSENTER_compat_after_hwframe+0x84/0x8e\n \u0026lt;/TASK\u0026gt;\n\nThe buggy address belongs to the variable:\n lacpdu_mcast_addr+0x0/0x40(CVE-2026-23099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvlan: Make the addrs_lock be per port\n\nMake the addrs_lock be per port, not per ipvlan dev.\n\nInitial code seems to be written in the assumption,\nthat any address change must occur under RTNL.\nBut it is not so for the case of IPv6. So\n\n1) Introduce per-port addrs_lock.\n\n2) It was needed to fix places where it was forgotten\nto take lock (ipvlan_open/ipvlan_close)\n\nThis appears to be a very minor problem though.\nSince it\u0026apos;s highly unlikely that ipvlan_add_addr() will\nbe called on 2 CPU simultaneously. But nevertheless,\nthis could cause:\n\n1) False-negative of ipvlan_addr_busy(): one interface\niterated through all port-\u0026gt;ipvlans + ipvlan-\u0026gt;addrs\nunder some ipvlan spinlock, and another added IP\nunder its own lock. Though this is only possible\nfor IPv6, since looks like only ipvlan_addr6_event() can be\ncalled without rtnl_lock.\n\n2) Race since ipvlan_ht_addr_add(port) is called under\ndifferent ipvlan-\u0026gt;addrs_lock locks\n\nThis should not affect performance, since add/remove IP\nis a rare situation and spinlock is not taken on fast\npaths.(CVE-2026-23103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag\n\nThis is more of a preventive patch to make the code more consistent and\nto prevent possible exploits that employ child qlen manipulations on qfq.\nuse cl_is_active instead of relying on the child qdisc\u0026apos;s qlen to determine\nclass activation.(CVE-2026-23105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()\n\nnft_map_catchall_activate() has an inverted element activity check\ncompared to its non-catchall counterpart nft_mapelem_activate() and\ncompared to what is logically required.\n\nnft_map_catchall_activate() is called from the abort path to re-activate\ncatchall map elements that were deactivated during a failed transaction.\nIt should skip elements that are already active (they don\u0026apos;t need\nre-activation) and process elements that are inactive (they need to be\nrestored). Instead, the current code does the opposite: it skips inactive\nelements and processes active ones.\n\nCompare the non-catchall activate callback, which is correct:\n\n  nft_mapelem_activate():\n    if (nft_set_elem_active(ext, iter-\u0026gt;genmask))\n        return 0;   /* skip active, process inactive */\n\nWith the buggy catchall version:\n\n  nft_map_catchall_activate():\n    if (!nft_set_elem_active(ext, genmask))\n        continue;   /* skip inactive, process active */\n\nThe consequence is that when a DELSET operation is aborted,\nnft_setelem_data_activate() is never called for the catchall element.\nFor NFT_GOTO verdict elements, this means nft_data_hold() is never\ncalled to restore the chain-\u0026gt;use reference count. Each abort cycle\npermanently decrements chain-\u0026gt;use. Once chain-\u0026gt;use reaches zero,\nDELCHAIN succeeds and frees the chain while catchall verdict elements\nstill reference it, resulting in a use-after-free.\n\nThis is exploitable for local privilege escalation from an unprivileged\nuser via user namespaces + nftables on distributions that enable\nCONFIG_USER_NS and CONFIG_NF_TABLES.\n\nFix by removing the negation so the check matches nft_mapelem_activate():\nskip active elements, process inactive ones.(CVE-2026-23111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nl2tp: avoid one data-race in l2tp_tunnel_del_work()\n\nWe should read sk-\u0026gt;sk_socket only when dealing with kernel sockets.\n\nsyzbot reported the following data-race:\n\nBUG: KCSAN: data-race in l2tp_tunnel_del_work / sk_common_release\n\nwrite to 0xffff88811c182b20 of 8 bytes by task 5365 on cpu 0:\n  sk_set_socket include/net/sock.h:2092 [inline]\n  sock_orphan include/net/sock.h:2118 [inline]\n  sk_common_release+0xae/0x230 net/core/sock.c:4003\n  udp_lib_close+0x15/0x20 include/net/udp.h:325\n  inet_release+0xce/0xf0 net/ipv4/af_inet.c:437\n  __sock_release net/socket.c:662 [inline]\n  sock_close+0x6b/0x150 net/socket.c:1455\n  __fput+0x29b/0x650 fs/file_table.c:468\n  ____fput+0x1c/0x30 fs/file_table.c:496\n  task_work_run+0x131/0x1a0 kernel/task_work.c:233\n  resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n  __exit_to_user_mode_loop kernel/entry/common.c:44 [inline]\n  exit_to_user_mode_loop+0x1fe/0x740 kernel/entry/common.c:75\n  __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]\n  syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]\n  syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline]\n  syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline]\n  do_syscall_64+0x1e1/0x2b0 arch/x86/entry/syscall_64.c:100\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nread to 0xffff88811c182b20 of 8 bytes by task 827 on cpu 1:\n  l2tp_tunnel_del_work+0x2f/0x1a0 net/l2tp/l2tp_core.c:1418\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0x4ce/0x9d0 kernel/workqueue.c:3340\n  worker_thread+0x582/0x770 kernel/workqueue.c:3421\n  kthread+0x489/0x510 kernel/kthread.c:463\n  ret_from_fork+0x149/0x290 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246\n\nvalue changed: 0xffff88811b818000 -\u0026gt; 0x0000000000000000(CVE-2026-23120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: annotate data-race in ndisc_router_discovery()\n\nsyzbot found that ndisc_router_discovery() could read and write\nin6_dev-\u0026gt;ra_mtu without holding a lock [1]\n\nThis looks fine, IFLA_INET6_RA_MTU is best effort.\n\nAdd READ_ONCE()/WRITE_ONCE() to document the race.\n\nNote that we might also reject illegal MTU values\n(mtu \u0026lt; IPV6_MIN_MTU || mtu \u0026gt; skb-\u0026gt;dev-\u0026gt;mtu) in a future patch.\n\n[1]\nBUG: KCSAN: data-race in ndisc_router_discovery / ndisc_router_discovery\n\nread to 0xffff888119809c20 of 4 bytes by task 25817 on cpu 1:\n  ndisc_router_discovery+0x151d/0x1c90 net/ipv6/ndisc.c:1558\n  ndisc_rcv+0x2ad/0x3d0 net/ipv6/ndisc.c:1841\n  icmpv6_rcv+0xe5a/0x12f0 net/ipv6/icmp.c:989\n  ip6_protocol_deliver_rcu+0xb2a/0x10d0 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0xf0/0x1d0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x5e/0x140 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x27c/0x470 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x336/0x340 net/ipv6/ip6_input.c:79\n...\n\nwrite to 0xffff888119809c20 of 4 bytes by task 25816 on cpu 0:\n  ndisc_router_discovery+0x155a/0x1c90 net/ipv6/ndisc.c:1559\n  ndisc_rcv+0x2ad/0x3d0 net/ipv6/ndisc.c:1841\n  icmpv6_rcv+0xe5a/0x12f0 net/ipv6/icmp.c:989\n  ip6_protocol_deliver_rcu+0xb2a/0x10d0 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0xf0/0x1d0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x5e/0x140 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x27c/0x470 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x336/0x340 net/ipv6/ip6_input.c:79\n...\n\nvalue changed: 0x00000000 -\u0026gt; 0xe5400659(CVE-2026-23124)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetdevsim: fix a race issue related to the operation on bpf_bound_progs list\n\nThe netdevsim driver lacks a protection mechanism for operations on the\nbpf_bound_progs list. When the nsim_bpf_create_prog() performs\nlist_add_tail, it is possible that nsim_bpf_destroy_prog() is\nsimultaneously performs list_del. Concurrent operations on the list may\nlead to list corruption and trigger a kernel crash as follows:\n\n[  417.290971] kernel BUG at lib/list_debug.c:62!\n[  417.290983] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\n[  417.290992] CPU: 10 PID: 168 Comm: kworker/10:1 Kdump: loaded Not tainted 6.19.0-rc5 #1\n[  417.291003] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  417.291007] Workqueue: events bpf_prog_free_deferred\n[  417.291021] RIP: 0010:__list_del_entry_valid_or_report+0xa7/0xc0\n[  417.291034] Code: a8 ff 0f 0b 48 89 fe 48 89 ca 48 c7 c7 48 a1 eb ae e8 ed fb a8 ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 80 a1 eb ae e8 d9 fb a8 ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 d0 a1 eb ae 48 89 f2 48 89 c6 e8 c2 fb a8\n[  417.291040] RSP: 0018:ffffb16a40807df8 EFLAGS: 00010246\n[  417.291046] RAX: 000000000000006d RBX: ffff8e589866f500 RCX: 0000000000000000\n[  417.291051] RDX: 0000000000000000 RSI: ffff8e59f7b23180 RDI: ffff8e59f7b23180\n[  417.291055] RBP: ffffb16a412c9000 R08: 0000000000000000 R09: 0000000000000003\n[  417.291059] R10: ffffb16a40807c80 R11: ffffffffaf9edce8 R12: ffff8e594427ac20\n[  417.291063] R13: ffff8e59f7b44780 R14: ffff8e58800b7a05 R15: 0000000000000000\n[  417.291074] FS:  0000000000000000(0000) GS:ffff8e59f7b00000(0000) knlGS:0000000000000000\n[  417.291079] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  417.291083] CR2: 00007fc4083efe08 CR3: 00000001c3626006 CR4: 0000000000770ee0\n[  417.291088] PKRU: 55555554\n[  417.291091] Call Trace:\n[  417.291096]  \u0026lt;TASK\u0026gt;\n[  417.291103]  nsim_bpf_destroy_prog+0x31/0x80 [netdevsim]\n[  417.291154]  __bpf_prog_offload_destroy+0x2a/0x80\n[  417.291163]  bpf_prog_dev_bound_destroy+0x6f/0xb0\n[  417.291171]  bpf_prog_free_deferred+0x18e/0x1a0\n[  417.291178]  process_one_work+0x18a/0x3a0\n[  417.291188]  worker_thread+0x27b/0x3a0\n[  417.291197]  ? __pfx_worker_thread+0x10/0x10\n[  417.291207]  kthread+0xe5/0x120\n[  417.291214]  ? __pfx_kthread+0x10/0x10\n[  417.291221]  ret_from_fork+0x31/0x50\n[  417.291230]  ? __pfx_kthread+0x10/0x10\n[  417.291236]  ret_from_fork_asm+0x1a/0x30\n[  417.291246]  \u0026lt;/TASK\u0026gt;\n\nAdd a mutex lock, to prevent simultaneous addition and deletion operations\non the list.(CVE-2026-23126)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath10k: fix dma_free_coherent() pointer\n\ndma_alloc_coherent() allocates a DMA mapped buffer and stores the\naddresses in XXX_unaligned fields.  Those should be reused when freeing\nthe buffer rather than the aligned addresses.(CVE-2026-23133)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: reset sparse-read state in osd_fault()\n\nWhen a fault occurs, the connection is abandoned, reestablished, and any\npending operations are retried. The OSD client tracks the progress of a\nsparse-read reply using a separate state machine, largely independent of\nthe messenger\u0026apos;s state.\n\nIf a connection is lost mid-payload or the sparse-read state machine\nreturns an error, the sparse-read state is not reset. The OSD client\nwill then interpret the beginning of a new reply as the continuation of\nthe old one. If this makes the sparse-read machinery enter a failure\nstate, it may never recover, producing loops like:\n\n  libceph:  [0] got 0 extents\n  libceph: data len 142248331 != extent len 0\n  libceph: osd0 (1)...:6801 socket error on read\n  libceph: data len 142248331 != extent len 0\n  libceph: osd0 (1)...:6801 socket error on read\n\nTherefore, reset the sparse-read state in osd_fault(), ensuring retries\nstart from a clean state.(CVE-2026-23136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nof: unittest: Fix memory leak in unittest_data_add()\n\nIn unittest_data_add(), if of_resolve_phandles() fails, the allocated\nunittest_data is not freed, leading to a memory leak.\n\nFix this by using scope-based cleanup helper __free(kfree) for automatic\nresource cleanup. This ensures unittest_data is automatically freed when\nit goes out of scope in error paths.\n\nFor the success path, use retain_and_null_ptr() to transfer ownership\nof the memory to the device tree and prevent double freeing.(CVE-2026-23137)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conncount: update last_gc only when GC has been performed\n\nCurrently last_gc is being updated everytime a new connection is\ntracked, that means that it is updated even if a GC wasn\u0026apos;t performed.\nWith a sufficiently high packet rate, it is possible to always bypass\nthe GC, causing the list to grow infinitely.\n\nUpdate the last_gc value only when a GC has been actually performed.(CVE-2026-23139)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix iloc.bh leak in ext4_xattr_inode_update_ref\n\nThe error branch for ext4_xattr_inode_update_ref forget to release the\nrefcount for iloc.bh. Find this when review code.(CVE-2026-23145)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix segmentation of forwarding fraglist GRO\n\nThis patch enhances GSO segment handling by properly checking\nthe SKB_GSO_DODGY flag for frag_list GSO packets, addressing\nlow throughput issues observed when a station accesses IPv4\nservers via hotspots with an IPv6-only upstream interface.\n\nSpecifically, it fixes a bug in GSO segmentation when forwarding\nGRO packets containing a frag_list. The function skb_segment_list\ncannot correctly process GRO skbs that have been converted by XLAT,\nsince XLAT only translates the header of the head skb. Consequently,\nskbs in the frag_list may remain untranslated, resulting in protocol\ninconsistencies and reduced throughput.\n\nTo address this, the patch explicitly sets the SKB_GSO_DODGY flag\nfor GSO packets in XLAT\u0026apos;s IPv4/IPv6 protocol translation helpers\n(bpf_skb_proto_4_to_6 and bpf_skb_proto_6_to_4). This marks GSO\npackets as potentially modified after protocol translation. As a\nresult, GSO segmentation will avoid using skb_segment_list and\ninstead falls back to skb_segment for packets with the SKB_GSO_DODGY\nflag. This ensures that only safe and fully translated frag_list\npackets are processed by skb_segment_list, resolving protocol\ninconsistencies and improving throughput when forwarding GRO packets\nconverted by XLAT.(CVE-2026-23154)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nefivarfs: fix error propagation in efivar_entry_get()\n\nefivar_entry_get() always returns success even if the underlying\n__efivar_entry_get() fails, masking errors.\n\nThis may result in uninitialized heap memory being copied to userspace\nin the efivarfs_file_read() path.\n\nFix it by returning the error from __efivar_entry_get().(CVE-2026-23156)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: fix race in mptcp_pm_nl_flush_addrs_doit()\n\nsyzbot and Eulgyu Kim reported crashes in mptcp_pm_nl_get_local_id()\nand/or mptcp_pm_nl_is_backup()\n\nRoot cause is list_splice_init() in mptcp_pm_nl_flush_addrs_doit()\nwhich is not RCU ready.\n\nlist_splice_init_rcu() can not be called here while holding pernet-\u0026gt;lock\nspinlock.\n\nMany thanks to Eulgyu Kim for providing a repro and testing our patches.(CVE-2026-23169)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: TC, delete flows only for existing peers\n\nWhen deleting TC steering flows, iterate only over actual devcom\npeers instead of assuming all possible ports exist. This avoids\ntouching non-existent peers and ensures cleanup is limited to\ndevices the driver is currently connected to.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000008\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 133c8a067 P4D 0\n Oops: Oops: 0002 [#1] SMP\n CPU: 19 UID: 0 PID: 2169 Comm: tc Not tainted 6.18.0+ #156 NONE\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:mlx5e_tc_del_fdb_peers_flow+0xbe/0x200 [mlx5_core]\n Code: 00 00 a8 08 74 a8 49 8b 46 18 f6 c4 02 74 9f 4c 8d bf a0 12 00 00 4c 89 ff e8 0e e7 96 e1 49 8b 44 24 08 49 8b 0c 24 4c 89 ff \u0026lt;48\u0026gt; 89 41 08 48 89 08 49 89 2c 24 49 89 5c 24 08 e8 7d ce 96 e1 49\n RSP: 0018:ff11000143867528 EFLAGS: 00010246\n RAX: 0000000000000000 RBX: dead000000000122 RCX: 0000000000000000\n RDX: ff11000143691580 RSI: ff110001026e5000 RDI: ff11000106f3d2a0\n RBP: dead000000000100 R08: 00000000000003fd R09: 0000000000000002\n R10: ff11000101c75690 R11: ff1100085faea178 R12: ff11000115f0ae78\n R13: 0000000000000000 R14: ff11000115f0a800 R15: ff11000106f3d2a0\n FS:  00007f35236bf740(0000) GS:ff110008dc809000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000008 CR3: 0000000157a01001 CR4: 0000000000373eb0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  mlx5e_tc_del_flow+0x46/0x270 [mlx5_core]\n  mlx5e_flow_put+0x25/0x50 [mlx5_core]\n  mlx5e_delete_flower+0x2a6/0x3e0 [mlx5_core]\n  tc_setup_cb_reoffload+0x20/0x80\n  fl_reoffload+0x26f/0x2f0 [cls_flower]\n  ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]\n  ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]\n  tcf_block_playback_offloads+0x9e/0x1c0\n  tcf_block_unbind+0x7b/0xd0\n  tcf_block_setup+0x186/0x1d0\n  tcf_block_offload_cmd.isra.0+0xef/0x130\n  tcf_block_offload_unbind+0x43/0x70\n  __tcf_block_put+0x85/0x160\n  ingress_destroy+0x32/0x110 [sch_ingress]\n  __qdisc_destroy+0x44/0x100\n  qdisc_graft+0x22b/0x610\n  tc_get_qdisc+0x183/0x4d0\n  rtnetlink_rcv_msg+0x2d7/0x3d0\n  ? rtnl_calcit.isra.0+0x100/0x100\n  netlink_rcv_skb+0x53/0x100\n  netlink_unicast+0x249/0x320\n  ? __alloc_skb+0x102/0x1f0\n  netlink_sendmsg+0x1e3/0x420\n  __sock_sendmsg+0x38/0x60\n  ____sys_sendmsg+0x1ef/0x230\n  ? copy_msghdr_from_user+0x6c/0xa0\n  ___sys_sendmsg+0x7f/0xc0\n  ? ___sys_recvmsg+0x8a/0xc0\n  ? __sys_sendto+0x119/0x180\n  __sys_sendmsg+0x61/0xb0\n  do_syscall_64+0x55/0x640\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f35238bb764\n Code: 15 b9 86 0c 00 f7 d8 64 89 02 b8 ff ff ff ff eb bf 0f 1f 44 00 00 f3 0f 1e fa 80 3d e5 08 0d 00 00 74 13 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 4c c3 0f 1f 00 55 48 89 e5 48 83 ec 20 89 55\n RSP: 002b:00007ffed4c35638 EFLAGS: 00000202 ORIG_RAX: 000000000000002e\n RAX: ffffffffffffffda RBX: 000055a2efcc75e0 RCX: 00007f35238bb764\n RDX: 0000000000000000 RSI: 00007ffed4c356a0 RDI: 0000000000000003\n RBP: 00007ffed4c35710 R08: 0000000000000010 R09: 00007f3523984b20\n R10: 0000000000000004 R11: 0000000000000202 R12: 00007ffed4c35790\n R13: 000000006947df8f R14: 000055a2efcc75e0 R15: 00007ffed4c35780(CVE-2026-23173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: aloop: Fix racy access at PCM trigger\n\nThe PCM trigger callback of aloop driver tries to check the PCM state\nand stop the stream of the tied substream in the corresponding cable.\nSince both check and stop operations are performed outside the cable\nlock, this may result in UAF when a program attempts to trigger\nfrequently while opening/closing the tied stream, as spotted by\nfuzzers.\n\nFor addressing the UAF, this patch changes two things:\n- It covers the most of code in loopback_check_format() with\n  cable-\u0026gt;lock spinlock, and add the proper NULL checks.  This avoids\n  already some racy accesses.\n- In addition, now we try to check the state of the capture PCM stream\n  that may be stopped in this function, which was the major pain point\n  leading to UAF.(CVE-2026-23191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: Don\u0026apos;t clobber irqfd routing type when deassigning irqfd\n\nWhen deassigning a KVM_IRQFD, don\u0026apos;t clobber the irqfd\u0026apos;s copy of the IRQ\u0026apos;s\nrouting entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86\nand arm64, which explicitly look for KVM_IRQ_ROUTING_MSI.  Instead, to\nhandle a concurrent routing update, verify that the irqfd is still active\nbefore consuming the routing information.  As evidenced by the x86 and\narm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below),\nclobbering the entry type without notifying arch code is surprising and\nerror prone.\n\nAs a bonus, checking that the irqfd is active provides a convenient\nlocation for documenting _why_ KVM must not consume the routing entry for\nan irqfd that is in the process of being deassigned: once the irqfd is\ndeleted from the list (which happens *before* the eventfd is detached), it\nwill no longer receive updates via kvm_irq_routing_update(), and so KVM\ncould deliver an event using stale routing information (relative to\nKVM_SET_GSI_ROUTING returning to userspace).\n\nAs an even better bonus, explicitly checking for the irqfd being active\nfixes a similar bug to the one the clobbering is trying to prevent: if an\nirqfd is deactivated, and then its routing is changed,\nkvm_irq_routing_update() won\u0026apos;t invoke kvm_arch_update_irqfd_routing()\n(because the irqfd isn\u0026apos;t in the list).  And so if the irqfd is in bypass\nmode, IRQs will continue to be posted using the old routing information.\n\nAs for kvm_arch_irq_bypass_del_producer(), clobbering the routing type\nresults in KVM incorrectly keeping the IRQ in bypass mode, which is\nespecially problematic on AMD as KVM tracks IRQs that are being posted to\na vCPU in a list whose lifetime is tied to the irqfd.\n\nWithout the help of KASAN to detect use-after-free, the most common\nsympton on AMD is a NULL pointer deref in amd_iommu_update_ga() due to\nthe memory for irqfd structure being re-allocated and zeroed, resulting\nin irqfd-\u0026gt;irq_bypass_data being NULL when read by\navic_update_iommu_vcpu_affinity():\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000018\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 40cf2b9067 P4D 40cf2b9067 PUD 408362a067 PMD 0\n  Oops: Oops: 0000 [#1] SMP\n  CPU: 6 UID: 0 PID: 40383 Comm: vfio_irq_test\n  Tainted: G     U  W  O        6.19.0-smp--5dddc257e6b2-irqfd #31 NONE\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025\n  RIP: 0010:amd_iommu_update_ga+0x19/0xe0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   avic_update_iommu_vcpu_affinity+0x3d/0x90 [kvm_amd]\n   __avic_vcpu_load+0xf4/0x130 [kvm_amd]\n   kvm_arch_vcpu_load+0x89/0x210 [kvm]\n   vcpu_load+0x30/0x40 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x45/0x620 [kvm]\n   kvm_vcpu_ioctl+0x571/0x6a0 [kvm]\n   __se_sys_ioctl+0x6d/0xb0\n   do_syscall_64+0x6f/0x9d0\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x46893b\n    \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nIf AVIC is inhibited when the irfd is deassigned, the bug will manifest as\nlist corruption, e.g. on the next irqfd assignment.\n\n  list_add corruption. next-\u0026gt;prev should be prev (ffff8d474d5cd588),\n                       but was 0000000000000000. (next=ffff8d8658f86530).\n  ------------[ cut here ]------------\n  kernel BUG at lib/list_debug.c:31!\n  Oops: invalid opcode: 0000 [#1] SMP\n  CPU: 128 UID: 0 PID: 80818 Comm: vfio_irq_test\n  Tainted: G     U  W  O        6.19.0-smp--f19dc4d680ba-irqfd #28 NONE\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025\n  RIP: 0010:__list_add_valid_or_report+0x97/0xc0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   avic_pi_update_irte+0x28e/0x2b0 [kvm_amd]\n   kvm_pi_update_irte+0xbf/0x190 [kvm]\n   kvm_arch_irq_bypass_add_producer+0x72/0x90 [kvm]\n   irq_bypass_register_consumer+0xcd/0x170 [irqbypa\n---truncated---(CVE-2026-23198)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_u32: use skb_header_pointer_careful()\n\nskb_header_pointer() does not fully validate negative @offset values.\n\nUse skb_header_pointer_careful() instead.\n\nGangMin Kim provided a report and a repro fooling u32_classify():\n\nBUG: KASAN: slab-out-of-bounds in u32_classify+0x1180/0x11b0\nnet/sched/cls_u32.c:221(CVE-2026-23204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usb-audio: Prevent excessive number of frames\n\nIn this case, the user constructed the parameters with maxpacksize 40\nfor rate 22050 / pps 1000, and packsize[0] 22 packsize[1] 23. The buffer\nsize for each data URB is maxpacksize * packets, which in this example\nis 40 * 6 = 240; When the user performs a write operation to send audio\ndata into the ALSA PCM playback stream, the calculated number of frames\nis packsize[0] * packets = 264, which exceeds the allocated URB buffer\nsize, triggering the out-of-bounds (OOB) issue reported by syzbot [1].\n\nAdded a check for the number of single data URB frames when calculating\nthe number of frames to prevent [1].\n\n[1]\nBUG: KASAN: slab-out-of-bounds in copy_to_urb+0x261/0x460 sound/usb/pcm.c:1487\nWrite of size 264 at addr ffff88804337e800 by task syz.0.17/5506\nCall Trace:\n copy_to_urb+0x261/0x460 sound/usb/pcm.c:1487\n prepare_playback_urb+0x953/0x13d0 sound/usb/pcm.c:1611\n prepare_outbound_urb+0x377/0xc50 sound/usb/endpoint.c:333(CVE-2026-23208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: annotate data-races around slave-\u0026gt;last_rx\n\nslave-\u0026gt;last_rx and slave-\u0026gt;target_last_arp_rx[...] can be read and written\nlocklessly. Add READ_ONCE() and WRITE_ONCE() annotations.\n\nsyzbot reported:\n\nBUG: KCSAN: data-race in bond_rcv_validate / bond_rcv_validate\n\nwrite to 0xffff888149f0d428 of 8 bytes by interrupt on cpu 1:\n  bond_rcv_validate+0x202/0x7a0 drivers/net/bonding/bond_main.c:3335\n  bond_handle_frame+0xde/0x5e0 drivers/net/bonding/bond_main.c:1533\n  __netif_receive_skb_core+0x5b1/0x1950 net/core/dev.c:6039\n  __netif_receive_skb_one_core net/core/dev.c:6150 [inline]\n  __netif_receive_skb+0x59/0x270 net/core/dev.c:6265\n  netif_receive_skb_internal net/core/dev.c:6351 [inline]\n  netif_receive_skb+0x4b/0x2d0 net/core/dev.c:6410\n...\n\nwrite to 0xffff888149f0d428 of 8 bytes by interrupt on cpu 0:\n  bond_rcv_validate+0x202/0x7a0 drivers/net/bonding/bond_main.c:3335\n  bond_handle_frame+0xde/0x5e0 drivers/net/bonding/bond_main.c:1533\n  __netif_receive_skb_core+0x5b1/0x1950 net/core/dev.c:6039\n  __netif_receive_skb_one_core net/core/dev.c:6150 [inline]\n  __netif_receive_skb+0x59/0x270 net/core/dev.c:6265\n  netif_receive_skb_internal net/core/dev.c:6351 [inline]\n  netif_receive_skb+0x4b/0x2d0 net/core/dev.c:6410\n  br_netif_receive_skb net/bridge/br_input.c:30 [inline]\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n...\n\nvalue changed: 0x0000000100005365 -\u0026gt; 0x0000000100005366(CVE-2026-23212)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbus: fsl-mc: fix use-after-free in driver_override_show()\n\nThe driver_override_show() function reads the driver_override string\nwithout holding the device_lock. However, driver_override_store() uses\ndriver_set_override(), which modifies and frees the string while holding\nthe device_lock.\n\nThis can result in a concurrent use-after-free if the string is freed\nby the store function while being read by the show function.\n\nFix this by holding the device_lock around the read operation.(CVE-2026-23221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: split cached_fid bitfields to avoid shared-byte RMW races\n\nis_open, has_lease and on_list are stored in the same bitfield byte in\nstruct cached_fid but are updated in different code paths that may run\nconcurrently. Bitfield assignments generate byte read–modify–write\noperations (e.g. `orb $mask, addr` on x86_64), so updating one flag can\nrestore stale values of the others.\n\nA possible interleaving is:\n    CPU1: load old byte (has_lease=1, on_list=1)\n    CPU2: clear both flags (store 0)\n    CPU1: RMW store (old | IS_OPEN) -\u0026gt; reintroduces cleared bits\n\nTo avoid this class of races, convert these flags to separate bool\nfields.(CVE-2026-23230)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:55.317925454Z","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:45.721983Z"},{"id":"OESA-2026-1761","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\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\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/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: atlantic: fix fragment overflow handling in RX path\n\nThe atlantic driver can receive packets with more than MAX_SKB_FRAGS (17)\nfragments when handling large multi-descriptor packets. This causes an\nout-of-bounds write in skb_add_rx_frag_netmem() leading to kernel panic.\n\nThe issue occurs because the driver doesn\u0026apos;t check the total number of\nfragments before calling skb_add_rx_frag(). When a packet requires more\nthan MAX_SKB_FRAGS fragments, the fragment index exceeds the array bounds.\n\nFix by assuming there will be an extra frag if buff-\u0026gt;len \u0026gt; AQ_CFG_RX_HDR_SIZE,\nthen all fragments are accounted for. And reusing the existing check to\nprevent the overflow earlier in the code path.\n\nThis crash occurred in production with an Aquantia AQC113 10G NIC.\n\nStack trace from production environment:\n```\nRIP: 0010:skb_add_rx_frag_netmem+0x29/0xd0\nCode: 90 f3 0f 1e fa 0f 1f 44 00 00 48 89 f8 41 89\nca 48 89 d7 48 63 ce 8b 90 c0 00 00 00 48 c1 e1 04 48 01 ca 48 03 90\nc8 00 00 00 \u0026lt;48\u0026gt; 89 7a 30 44 89 52 3c 44 89 42 38 40 f6 c7 01 75 74 48\n89 fa 83\nRSP: 0018:ffffa9bec02a8d50 EFLAGS: 00010287\nRAX: ffff925b22e80a00 RBX: ffff925ad38d2700 RCX:\nfffffffe0a0c8000\nRDX: ffff9258ea95bac0 RSI: ffff925ae0a0c800 RDI:\n0000000000037a40\nRBP: 0000000000000024 R08: 0000000000000000 R09:\n0000000000000021\nR10: 0000000000000848 R11: 0000000000000000 R12:\nffffa9bec02a8e24\nR13: ffff925ad8615570 R14: 0000000000000000 R15:\nffff925b22e80a00\nFS: 0000000000000000(0000)\nGS:ffff925e47880000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffff9258ea95baf0 CR3: 0000000166022004 CR4:\n0000000000f72ef0\nPKRU: 55555554\nCall Trace:\n\u0026lt;IRQ\u0026gt;\naq_ring_rx_clean+0x175/0xe60 [atlantic]\n? aq_ring_rx_clean+0x14d/0xe60 [atlantic]\n? aq_ring_tx_clean+0xdf/0x190 [atlantic]\n? kmem_cache_free+0x348/0x450\n? aq_vec_poll+0x81/0x1d0 [atlantic]\n? __napi_poll+0x28/0x1c0\n? net_rx_action+0x337/0x420\n```\n\nChanges in v4:\n- Add Fixes: tag to satisfy patch validation requirements.\n\nChanges in v3:\n- Fix by assuming there will be an extra frag if buff-\u0026gt;len \u0026gt; AQ_CFG_RX_HDR_SIZE,\n  then all fragments are accounted for.(CVE-2025-68301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/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\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:45.881631165Z","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:45.721983Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2025-68780","title":"CVE-2025-68780 in linux - Patched by Root","description":"Root has patched CVE-2025-68780 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:17:46.647978668Z","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.631993Z"},{"id":"ROOT-OS-UBUNTU-2204-CVE-2025-68780","title":"CVE-2025-68780 in linux - Patched by Root","description":"Root has patched CVE-2025-68780 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T13:52:25Z","modified":"2026-11-06T14:17:18.658967482Z","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-06T14:57:22.237547Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2025-68780","title":"CVE-2025-68780 in linux - Patched by Root","description":"Root has patched CVE-2025-68780 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T15:54:27Z","modified":"2026-11-06T16:17:53.571620134Z","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-06T16:59:13.24938Z"},{"id":"AZL-74495","title":"CVE-2025-68780 affecting package kernel for versions less than 6.6.121.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\"sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u003eonline\") introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\"sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\") removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com\n\nAnother occurs when the last deadline task is migrated from a\nCPU that has an offlined runqueue. The dequeue_task member of\nthe deadline scheduler class will eventually call cpudl_clear\nand set the free_cpus bit for the CPU.\n\nThis commit modifies the cpudl_clear function to be aware of the\nonline state of the deadline runqueue so that the free_cpus mask\ncan be updated appropriately.\n\nIt is no longer necessary to manage the mask outside of the\ncpudl_set/clear functions so the cpudl_set/clear_freecpu\nfunctions are removed. In addition, since the free_cpus mask is\nnow only updated under the cpudl lock the code was changed to\nuse the non-atomic __cpumask functions.","status":"published","published":"2026-01-13T16:15:57Z","modified":"2026-04-21T04:47:12.580582Z","updated_at":"2026-11-02T15:28:09.474476Z"},{"id":"BELL-CVE-2025-68780","status":"published","published":"2026-01-15T06:07:43.636486Z","modified":"2026-06-25T07:18:31.777035364Z","updated_at":"2026-11-02T15:28:22.77042Z"},{"id":"CVE-2025-68780","title":"sched/deadline: only set free_cpus for online runqueues","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\"sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u003eonline\") introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\"sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\") removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com\n\nAnother occurs when the last deadline task is migrated from a\nCPU that has an offlined runqueue. The dequeue_task member of\nthe deadline scheduler class will eventually call cpudl_clear\nand set the free_cpus bit for the CPU.\n\nThis commit modifies the cpudl_clear function to be aware of the\nonline state of the deadline runqueue so that the free_cpus mask\ncan be updated appropriately.\n\nIt is no longer necessary to manage the mask outside of the\ncpudl_set/clear functions so the cpudl_set/clear_freecpu\nfunctions are removed. In addition, since the free_cpus mask is\nnow only updated under the cpudl lock the code was changed to\nuse the non-atomic __cpumask functions.","status":"published","published":"2026-01-13T15:28:55.483Z","modified":"2026-10-28T02:30:48.189626672Z","updated_at":"2026-11-02T15:44:52.859856Z"},{"id":"DEBIAN-CVE-2025-68780","description":"In the Linux kernel, the following vulnerability has been resolved:  sched/deadline: only set free_cpus for online runqueues  Commit 16b269436b72 (\"sched/deadline: Modify cpudl::free_cpus to reflect rd-\u003eonline\") introduced the cpudl_set/clear_freecpu functions to allow the cpu_dl::free_cpus mask to be manipulated by the deadline scheduler class rq_on/offline callbacks so the mask would also reflect this state.  Commit 9659e1eeee28 (\"sched/deadline: Remove cpu_active_mask from cpudl_find()\") removed the check of the cpu_active_mask to save some processing on the premise that the cpudl::free_cpus mask already reflected the runqueue online state.  Unfortunately, there are cases where it is possible for the cpudl_clear function to set the free_cpus bit for a CPU when the deadline runqueue is offline. When this occurs while a CPU is connected to the default root domain the flag may retain the bad state after the CPU has been unplugged. Later, a different CPU that is transitioning through the default root domain may push a deadline task to the powered down CPU when cpudl_find sees its free_cpus bit is set. If this happens the task will not have the opportunity to run.  One example is outlined here: https://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com  Another occurs when the last deadline task is migrated from a CPU that has an offlined runqueue. The dequeue_task member of the deadline scheduler class will eventually call cpudl_clear and set the free_cpus bit for the CPU.  This commit modifies the cpudl_clear function to be aware of the online state of the deadline runqueue so that the free_cpus mask can be updated appropriately.  It is no longer necessary to manage the mask outside of the cpudl_set/clear functions so the cpudl_set/clear_freecpu functions are removed. In addition, since the free_cpus mask is now only updated under the cpudl lock the code was changed to use the non-atomic __cpumask functions.","status":"published","published":"2026-01-13T16:15:57.657Z","modified":"2026-09-01T20:05:57.58774846Z","updated_at":"2026-11-02T15:45:48.025964Z"},{"id":"DLA-4476-1","title":"linux-6.1 - security update","status":"published","published":"2026-02-10T00:00:00Z","modified":"2026-02-10T18:30:13.970662Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"DSA-6126-1","title":"linux - security update","status":"published","published":"2026-02-09T00:00:00Z","modified":"2026-03-09T02:09:24.491665Z","updated_at":"2026-11-02T15:46:18.296714Z"},{"id":"DSA-6127-1","title":"linux - security update","status":"published","published":"2026-02-09T00:00:00Z","modified":"2026-03-09T02:09:43.378453Z","updated_at":"2026-11-02T15:46:18.296714Z"},{"id":"MGASA-2026-0017","title":"Updated kernel, kmod-virtualbox \u0026 kmod-xtables-addons packages fix security vulnerabilities","description":"Upstream kernel version 6.6.120 fixes bugs and vulnerabilities.\nThe kmod-virtualbox \u0026 kmod-xtables-addons packages have been updated to\nwork with this new kernel.\n","status":"published","published":"2026-01-24T20:25:04Z","modified":"2026-04-16T04:43:32.882687097Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"MGASA-2026-0018","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.120 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2026-01-26T20:03:34Z","modified":"2026-04-16T04:42:12.477260681Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"openSUSE-SU-2026:21910-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-68214: timers: Fix NULL function pointer race in timer_shutdown_sync() (bsc#1255225).\n- CVE-2025-68358: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() (bsc#1255531).\n- CVE-2025-68780: sched/deadline: only set free_cpus for online runqueues (bsc#1256671).\n- CVE-2025-71075: scsi: aic94xx: fix use-after-free in device removal path (bsc#1256629).\n- CVE-2026-23113: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (bsc#1258278).\n- CVE-2026-23306: scsi: pm8001: Fix use-after-free in pm8001_queue_command() (bsc#1260501).\n- CVE-2026-23348: cxl/mem: Clarify @host for devm_cxl_add_nvdimm() (bsc#1260577).\n- CVE-2026-31418: netfilter: ipset: drop logically empty buckets in mtype_del (bsc#1262073).\n- CVE-2026-31530: cxl/port: Fix use after free of parent_port in cxl_detach_ep() (bsc#1262756).\n- CVE-2026-31531: ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop() (bsc#1263004).\n- CVE-2026-43116: netfilter: ctnetlink: ensure safe access to master conntrack (bsc#1264619).\n- CVE-2026-43125: dlm: validate length in dlm_search_rsb_tree (bsc#1264541).\n- CVE-2026-43163: md/bitmap: fix GPF in write_page caused by resize race (bsc#1264335).\n- CVE-2026-43239: smb: client: prevent races in -\u003equery_interfaces() (bsc#1264444).\n- CVE-2026-43271: md-cluster: fix NULL pointer dereference in process_metadata_update (bsc#1264587).\n- CVE-2026-43299: btrfs: do not ASSERT() when the fs flips RO inside btrfs_repair_io_failure() (bsc#1264851).\n- CVE-2026-43331: x86/kexec: Disable KCOV instrumentation after load_segments() (bsc#1265132).\n- CVE-2026-43355: iio: light: bh1780: fix PM runtime leak on error path (bsc#1265036).\n- CVE-2026-43363: x86/apic: Disable x2apic on resume if the kernel expects so (bsc#1265068).\n- CVE-2026-43416: powerpc, perf: Check that current-\u003emm is alive before getting user callchain (bsc#1265121).\n- CVE-2026-43439: cgroup: fix race between task migration and iteration (bsc#1265141).\n- CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807).\n- CVE-2026-45860: netfilter: nf_conncount: increase the connection clean up limit to 64 (bsc#1266710).\n- CVE-2026-45897: netfilter: nft_counter: serialize reset with spinlock (bsc#1266897).\n- CVE-2026-45968: cpuidle: Skip governor when only one idle state is available (bsc#1267023).\n- CVE-2026-46007: hwmon: (powerz) Avoid cacheline sharing for DMA buffer (bsc#1267586).\n- CVE-2026-46070: md/raid5: validate payload size before accessing journal metadata (bsc#1267501).\n- CVE-2026-46107: dm-thin: fix metadata refcount underflow (bsc#1267612).\n- CVE-2026-46115: block: add pgmap check to biovec_phys_mergeable (bsc#1266874).\n- CVE-2026-46133: RDMA/rxe: Reject unknown opcodes before ICRC processing (bsc#1266928).\n- CVE-2026-46135: nvmet-tcp: remove redundant calls to nvmet_tcp_fatal_error() (bsc#1267373).\n- CVE-2026-46195: smb: client: validate dacloffset before building DACL pointers (bsc#1266860).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-52920: netfilter: xt_policy: fix strict mode inbound policy matching (bsc#1269013).\n- CVE-2026-52928: af_unix: Reject SIOCATMARK on non-stream sockets (bsc#1269010).\n- CVE-2026-52929: sctp: stream: fully roll back denied add-stream state (bsc#1269004).\n- CVE-2026-52935: xfrm: espintcp: do not reuse an in-progress partial send (bsc#1268979).\n- CVE-2026-52939: net/rds: fix NULL deref in rds_ib_send_cqe_handler() on masked atomic completion (bsc#1268972).\n- CVE-2026-52946: fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling (bsc#1269113).\n- CVE-2026-52977: futex: Prevent lockup in requeue-PI during signal/ timeout wakeup (bsc#1269242).\n- CVE-2026-52990: fsnotify: fix inode reference leak in fsnotify_recalc_mask() (bsc#1269108).\n- CVE-2026-52991: sched/psi: fix race between file release and pressure write (bsc#1269134).\n- CVE-2026-52994: vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting (bsc#1269126).\n- CVE-2026-53001: netfilter: xtables: restrict several matches to inet family (bsc#1269114).\n- CVE-2026-53031: bpf: Validate node_id in arena_alloc_pages() (bsc#1269380).\n- CVE-2026-53033: bpf, sockmap: Take state lock for af_unix iter (bsc#1269388).\n- CVE-2026-53034: bpf, sockmap: Fix af_unix null-ptr-deref in proto update (bsc#1269140).\n- CVE-2026-53048: gfs2: prevent NULL pointer dereference during unmount (bsc#1269162).\n- CVE-2026-53059: dm log: fix out-of-bounds write due to region_count overflow (bsc#1269655).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53076: bpf: Fix OOB in pcpu_init_value (bsc#1269695).\n- CVE-2026-53077: net/rds: Restrict use of RDS/IB to the initial network namespace (bsc#1269412).\n- CVE-2026-53089: bpf: Fix use-after-free in offloaded map/prog info fill (bsc#1269783).\n- CVE-2026-53091: net: account for encap headers in qdisc pkt len (bsc#1269530).\n- CVE-2026-53092: bpf: Fix linked reg delta tracking when src_reg == dst_reg (bsc#1269528).\n- CVE-2026-53094: bpf: Fix stale offload-\u003eprog pointer after constant blinding (bsc#1269965).\n- CVE-2026-53096: bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path (bsc#1269969).\n- CVE-2026-53109: powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy (bsc#1269417).\n- CVE-2026-53110: s390: always declare expoline thunks (bsc#1269985).\n- CVE-2026-53111: bpf: test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap (bsc#1269167).\n- CVE-2026-53114: perf: Extend the bit width of the arch-specific flag (bsc#1269999).\n- CVE-2026-53126: blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() (bsc#1269635).\n- CVE-2026-53129: fs/mbcache: cancel shrink work before destroying the cache (bsc#1269633).\n- CVE-2026-53142: drm/xe/display: fix oops in suspend/shutdown without display (bsc#1269402).\n- CVE-2026-53154: mm/hugetlb: restore reservation on error in hugetlb folio copy paths (bsc#1269665).\n- CVE-2026-53163: locking/rtmutex: Skip remove_waiter() when waiter is not enqueued (bsc#1269306).\n- CVE-2026-53180: timers/migration: Fix livelock in tmigr_handle_remote_up() (bsc#1269888).\n- CVE-2026-53207: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison (bsc#1269590).\n- CVE-2026-53219: netfilter: x_tables: avoid leaking percpu counter pointers (bsc#1269686).\n- CVE-2026-53220: netfilter: revalidate bridge ports (bsc#1269381).\n- CVE-2026-53223: net: guard timestamp cmsgs to real error queue skbs (bsc#1269301).\n- CVE-2026-53228: ipv6: sit: reload inner IPv6 header after GSO offloads (bsc#1269256).\n- CVE-2026-53238: netlabel: validate unlabeled address and mask attribute lengths (bsc#1269774).\n- CVE-2026-53264: net/sched: act_api: use RCU with deferred freeing for action lifecycle (bsc#1269238).\n- CVE-2026-53269: netfilter: synproxy: add mutex to guard hook reference counting (bsc#1269579).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53291: ALSA: hda/conexant: Fix missing error check for jack detection (bsc#1269697).\n- CVE-2026-53309: ocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison (bsc#1269815).\n- CVE-2026-53330: drm/amd/display: Fix out-of-bounds read in (bsc#1270090).\n- CVE-2026-53336: nvmem: layouts: onie-tlv: fix hang on unknown types (bsc#1270108).\n- CVE-2026-53337: net: bonding: fix NULL pointer dereference in bond_do_ioctl() (bsc#1270251).\n- CVE-2026-53341: fhandle: fix UAF due to unlocked -\u003emnt_ns read in may_decode_fh() (bsc#1270139).\n- CVE-2026-53353: hsr: Remove WARN_ONCE() in hsr_addr_is_self() (bsc#1270111).\n- CVE-2026-53365: vsock/virtio: fix zerocopy completion for multi-skb sends (bsc#1271365).\n- CVE-2026-63801: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (bsc#1272230).\n- CVE-2026-63803: hdlc_ppp: sync per-proto timers before freeing hdlc state (bsc#1272284).\n- CVE-2026-63804: gfs2: fix use-after-free in gfs2_qd_dealloc (bsc#1272287).\n- CVE-2026-63808: exfat: fix potential use-after-free in exfat_find_dir_entry() (bsc#1272260).\n- CVE-2026-63810: block: Avoid mounting the bdev pseudo-filesystem in userspace (bsc#1272297).\n- CVE-2026-63823: keys: Pin request_key_auth payload in instantiate paths (bsc#1272182).\n- CVE-2026-63828: apparmor: mediate the implicit connect of TCP fast open sendmsg (bsc#1272175).\n- CVE-2026-63860: RDMA/core: Prefer NLA_NUL_STRING (bsc#1272429).\n- CVE-2026-63865: bpf: Drop task_to_inode and inet_conn_established from lsm sleepable hooks (bsc#1272486).\n- CVE-2026-63868: net: garp: fix unsigned integer underflow in garp_pdu_parse_attr (bsc#1272497).\n- CVE-2026-63879: drm/amdgpu: fix amdgpu_hmm_range_get_pages (bsc#1272569).\n- CVE-2026-63887: scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf (bsc#1272385).\n- CVE-2026-63888: scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd() (bsc#1272390).\n- CVE-2026-63889: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (bsc#1272423).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63891: thunderbolt: property: Cap recursion depth in __tb_property_parse_dir() (bsc#1272641).\n- CVE-2026-63901: USB: serial: digi_acceleport: fix memory corruption with small endpoints (bsc#1272501).\n- CVE-2026-63917: ip6: vti: Use ip6_tnl.net in vti6_changelink() (bsc#1272904).\n- CVE-2026-63918: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname (bsc#1272905).\n- CVE-2026-63920: ipv6: validate extension header length before copying to cmsg (bsc#1272877).\n- CVE-2026-63921: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate() (bsc#1272918).\n- CVE-2026-63922,CVE-2026-63924: ipv6: exthdrs: refresh nh after handling HAO option (bsc#1272855).\n- CVE-2026-63925: macsec: fix replay protection at XPN lower-PN wrap (bsc#1273008).\n- CVE-2026-63926: bpf: sockmap: fix tail fragment offset in bpf_msg_push_data (bsc#1273019).\n- CVE-2026-63941: KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor (bsc#1272869).\n- CVE-2026-63969: ipv6: fix possible infinite loop in rt6_fill_node() (bsc#1272484).\n- CVE-2026-63970: vsock/virtio: bind uarg before filling zerocopy skb (bsc#1272673).\n- CVE-2026-63984: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() (bsc#1272865).\n- CVE-2026-63985: ethtool: eeprom: add more safeties to EEPROM Netlink fallback (bsc#1272963).\n- CVE-2026-63986: ethtool: tsinfo: don't pass ERR_PTR to genlmsg_cancel on prepare failure (bsc#1272969).\n- CVE-2026-63987: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (bsc#1272971).\n- CVE-2026-63990: bonding: refuse to enslave CAN devices (bsc#1273027).\n- CVE-2026-63992: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() (bsc#1272868).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-63995: ethtool: cmis: validate start_cmd_payload_size from module (bsc#1273033).\n- CVE-2026-63996: ethtool: cmis: require exact CDB reply length (bsc#1273032).\n- CVE-2026-63997: ethtool: module: avoid leaking a netdev ref on module flash errors (bsc#1273036).\n- CVE-2026-63998: ethtool: module: call ethnl_ops_complete() on module flash errors (bsc#1273037).\n- CVE-2026-63999: ethtool: rss: fix indir_table and hkey leak on get_rxfh failure (bsc#1273038).\n- CVE-2026-64000: net: hsr: fix potential OOB access in supervision frame handling (bsc#1273030).\n- CVE-2026-64002: ipv4: free net-\u003eipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (bsc#1273774).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64004: net/iucv: fix locking in .getsockopt (bsc#1273804).\n- CVE-2026-64005: net/smc: Do not re-initialize smc hashtables (bsc#1273831).\n- CVE-2026-64006: netfilter: nf_tables: fix dst corruption in same register operation (bsc#1273834).\n- CVE-2026-64007: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (bsc#1273105).\n- CVE-2026-64017: blk-mq: pop cached request if it is usable (bsc#1273770).\n- CVE-2026-64024: tcp: fix stale per-CPU tcp_tw_isn leak enabling ISN prediction (bsc#1273107).\n- CVE-2026-64033: RDMA/rtrs: Fix use-after-free in path file creation cleanup (bsc#1273134).\n- CVE-2026-64047: net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring (bsc#1273060).\n- CVE-2026-64048: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot (bsc#1273484).\n- CVE-2026-64052: block: bio-integrity: Fix null-ptr-deref in bio_integrity_map_user() (bsc#1272983).\n- CVE-2026-64053: block: don't overwrite bip_vcnt in bio_integrity_copy_user() (bsc#1272985).\n- CVE-2026-64054: net: shaper: reject duplicate leaves in GROUP request (bsc#1272894).\n- CVE-2026-64055: net: ethernet: cortina: Carry over frag counter (bsc#1272893).\n- CVE-2026-64056: net: ethernet: cortina: Make RX SKB per-port (bsc#1272502).\n- CVE-2026-64071: nvme-pci: fix use-after-free in nvme_free_host_mem() (bsc#1273486).\n- CVE-2026-64073: irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT (bsc#1273490).\n- CVE-2026-64088: batman-adv: tt: fix negative tt_buff_len (bsc#1273463).\n- CVE-2026-64089: batman-adv: tt: fix negative last_changeset_len (bsc#1272513).\n- CVE-2026-64093: batman-adv: tp_meter: directly shut down timer on cleanup (bsc#1273461).\n- CVE-2026-64099: drm/v3d: Fix use-after-free of CPU job query arrays on error path (bsc#1273465).\n- CVE-2026-64102: RDMA/siw: Reject MPA FPDU length underflow before signed receive math (bsc#1272516).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64109: af_unix: Fix UAF read of tail-\u003elen in unix_stream_data_wait() (bsc#1273748).\n- CVE-2026-64111: lsm: hold cred_guard_mutex for lsm_set_self_attr() (bsc#1273740).\n- CVE-2026-64112: rbd: eliminate a race in lock_dwork draining on unmap (bsc#1273741).\n- CVE-2026-64113: ixgbevf: fix use-after-free in VEPA multicast source pruning (bsc#1272262).\n- CVE-2026-64114: ipv4: raw: reject IP_HDRINCL packets with ihl \u003c 5 (bsc#1273742).\n- CVE-2026-64115: vsock/vmci: fix UAF when peer resets connection during handshake (bsc#1273745).\n- CVE-2026-64118: qed: fix double free in qed_cxt_tables_alloc() (bsc#1273749).\n- CVE-2026-64119: l2tp: use list_del_rcu in l2tp_session_unhash (bsc#1273746).\n- CVE-2026-64121: net: ifb: report ethtool stats over num_tx_queues (bsc#1273743).\n- CVE-2026-64125: net: bcmgenet: keep RBUF EEE/PM disabled (bsc#1272346).\n- CVE-2026-64131: mm/memory: fix spurious warning when unmapping device-private/exclusive pages (bsc#1274063).\n- CVE-2026-64146: erofs: fix metabuf leak in inode xattr initialization (bsc#1273681).\n- CVE-2026-64147: pds_core: fix debugfs_lookup dentry leak and error handling (bsc#1273119).\n- CVE-2026-64148: pds_core: fix error handling in pdsc_devcmd_wait (bsc#1273956).\n- CVE-2026-64162: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (bsc#1272366).\n- CVE-2026-64164: btrfs: tracepoints: fix sleep while in atomic context in btrfs_sync_file() (bsc#1273957).\n- CVE-2026-64177: phonet/pep: disable BH around forwarded sk_receive_skb() (bsc#1272148).\n- CVE-2026-64179: net: wwan: iosm: fix potential memory leaks in ipc_imem_init() (bsc#1272149).\n- CVE-2026-64180: mm/memory_hotplug: fix memory block reference leak on remove (bsc#1273679).\n- CVE-2026-64184: mm/damon/sysfs-schemes: call missing mem_cgroup_iter_break() (bsc#1272199).\n- CVE-2026-64185: sysfs: don't remove existing directory on update failure (bsc#1272200).\n- CVE-2026-64190: net: team: fix NULL pointer dereference in team_xmit during mode change (bsc#1272210).\n- CVE-2026-64192: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized (bsc#1272213).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64214: powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise()\n  (bsc#1272799).\n- CVE-2026-64217: netfs: Fix overrun check in netfs_extract_user_iter() (bsc#1272798).\n- CVE-2026-64222: octeontx2-pf: avoid double free of pool-\u003estack on AQ init failure (bsc#1272788).\n- CVE-2026-64224: octeontx2-pf: fix double free in rvu_rep_rsrc_init() (bsc#1272804).\n- CVE-2026-64225: octeontx2-af: CGX: add bounds check to cgx_speed_mbps index (bsc#1272786).\n- CVE-2026-64232: block: recompute nr_integrity_segments in blk_insert_cloned_request (bsc#1272791).\n- CVE-2026-64239: mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() (bsc#1273898).\n- CVE-2026-64244: drivers/base/memory: set mem-\u003ealtmap after successful device registration (bsc#1273812).\n- CVE-2026-64253: kernel/fork: clear PF_BLOCK_TS in copy_process() (bsc#1273904).\n- CVE-2026-64256: xfs: don't wrap around quota ids in dqiterate (bsc#1273271).\n- CVE-2026-64265: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req (bsc#1273947).\n- CVE-2026-64268: RDMA/siw: bound Read Response placement to the RREAD length (bsc#1273276).\n- CVE-2026-64269: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg (bsc#1273280).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64286: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU (bsc#1274058).\n- CVE-2026-64287: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU (bsc#1273325).\n- CVE-2026-64294: mm: do file ownership checks with the proper mount idmap (bsc#1273525).\n- CVE-2026-64296: exfat: bound uniname advance in exfat_find_dir_entry() (bsc#1273975).\n- CVE-2026-64298: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (bsc#1273550).\n- CVE-2026-64300: perf/aux: Fix page UAF in map_range() (bsc#1273852).\n- CVE-2026-64307: crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG) (bsc#1273567).\n- CVE-2026-64315: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1274028).\n- CVE-2026-64316: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1273598).\n- CVE-2026-64317: isofs: bound Rock Ridge symlink components to the SL record (bsc#1273936).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64321: nvme: target: rdma: fix ndev refcount leak on queue connect (bsc#1273864).\n- CVE-2026-64322: udf: validate sparing table length as an entry count, not a byte count (bsc#1273958).\n- CVE-2026-64323: udf: validate VAT header length against the VAT inode size (bsc#1273305).\n- CVE-2026-64326: block: skip sync_blockdev() on surprise removal in bdev_mark_dead() (bsc#1273312).\n- CVE-2026-64327: usb: gadget: f_fs: Initialize epfile-\u003ein early to fix endpoint direction checks (bsc#1273283).\n- CVE-2026-64354: bpf: Validate BTF repeated field counts before expansion (bsc#1274060).\n- CVE-2026-64355: bpf: Reject fragmented frames in devmap (bsc#1273422).\n- CVE-2026-64364: HID: multitouch: fix out-of-bounds bit access on mt_io_flags (bsc#1273495).\n- CVE-2026-64368: mm/slab: do not limit zeroing to orig_size when only red zoning is enabled (bsc#1273997).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64375: proc: protect ptrace_may_access() with exec_update_lock (FD links) (bsc#1273868).\n- CVE-2026-64378: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (bsc#1273603).\n- CVE-2026-64381: smb: client: Fix next buffer leak in receive_encrypted_standard() (bsc#1273860).\n- CVE-2026-64382: smb: client: fix double-free in SMB2_open() replay (bsc#1273291).\n- CVE-2026-64383: smb: client: fix double-free in SMB2_flush() replay (bsc#1273426).\n- CVE-2026-64384: smb: client: fix change notify replay double-free (bsc#1274541).\n- CVE-2026-64385: smb: client: fix double-free in SMB2_ioctl() replay (bsc#1274539).\n- CVE-2026-64386: smb: client: fix query_info() replay double-free (bsc#1274543).\n- CVE-2026-64387: smb: client: fix query directory replay double-free (bsc#1274545).\n- CVE-2026-64411: netfilter: ebtables: terminate table name before find_table_lock() (bsc#1274077).\n- CVE-2026-64412: netfilter: ebtables: module names must be null-terminated (bsc#1273780).\n- CVE-2026-64415: mm/swap: add cond_resched() in swap_reclaim_full_clusters to prevent softlockup (bsc#1273317).\n- CVE-2026-64416: mm: swap_cgroup: fix NULL deref in lookup_swap_cgroup_id on swapless host (bsc#1273286).\n- CVE-2026-64423: ipv4: igmp: remove multicast group from hash table on device destruction (bsc#1274274).\n- CVE-2026-64434: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref (bsc#1273880).\n- CVE-2026-64436: net: af_key: initialize alg_key_len for IPComp states (bsc#1274277).\n- CVE-2026-64450: tipc: fix out-of-bounds read in broadcast Gap ACK blocks (bsc#1273523).\n- CVE-2026-64452: 6lowpan: fix NHC entry use-after-free on error path (bsc#1273460).\n- CVE-2026-64458: mm/damon/ops-common: handle extreme intervals in damon_hot_score() (bsc#1273788).\n- CVE-2026-64463: usb: typec: tcpci_rt1711h: unregister TCPCI port with devres (bsc#1273273).\n- CVE-2026-64472: vfio/mlx5: Fix racy bitfields and tighten struct layout (bsc#1274075).\n- CVE-2026-64477: x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled (bsc#1274264).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64518: tcp: Fix out-of-bounds access for twsk in tcp_ao_established_key() (bsc#1273524).\n- CVE-2026-64519: NFSD: Fix infinite loop in layout state revocation (bsc#1274252).\n- CVE-2026-64526: ethtool: tsconfig: fix missing ethnl_ops_complete() (bsc#1274052).\n- CVE-2026-64534: nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error (bsc#1273803).\n- CVE-2026-64535: nvmet-tcp: Fix potential UAF when ddgst mismatch (bsc#1273809).\n- CVE-2026-64537: bridge: cfm: reject invalid CCM interval at configuration time (bsc#1273289).\n- CVE-2026-64538: ipv6: Fix null-ptr-deref in fib6_nh_mtu_change() (bsc#1273335).\n- CVE-2026-64541: net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket (bsc#1273303).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64543: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() (bsc#1273311).\n- CVE-2026-64545: net, bpf: check master for NULL in xdp_master_redirect() (bsc#1273318).\n- CVE-2026-64548: bpf, sockmap: reject overflowing copy + len in bpf_msg_push_data() (bsc#1273337).\n- CVE-2026-64551: sctp: validate STALE_COOKIE cause length before reading staleness (bsc#1273813).\n- CVE-2026-64552: virtio-net: fix len check in receive_big() (bsc#1273323).\n- CVE-2026-64553: net: psample: fix info leak in PSAMPLE_ATTR_DATA (bsc#1273336).\n- CVE-2026-64554: netfilter: bridge: fix stale prevhdr pointer in br_ip6_fragment() (bsc#1273340).\n- CVE-2026-64555: KVM: arm64: nv: Fix SPSR_EL2 restore in kvm_hyp_handle_mops() (bsc#1273331).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64563: rhashtable: clear stale iter-\u003ep on table restart (bsc#1273995).\n- CVE-2026-64567: btrfs: reject free space cache with more entries than pages (bsc#1274006).\n- CVE-2026-64569: mpls: fix NULL deref in mpls_valid_fib_dump_req() on CONFIG_INET=n (bsc#1274009).\n- CVE-2026-64572: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (bsc#1274014).\n- CVE-2026-64576: nexthop: initialize extack in nh_res_bucket_migrate() (bsc#1274030).\n- CVE-2026-64577: gtp: check skb_pull_data() return in gtp1u_send_echo_resp() (bsc#1274031).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64581: xfrm: fix sk_dst_cache double-free in xfrm_user_policy() (bsc#1274041).\n- CVE-2026-64582: RDMA/rxe: Fix a use-after-free problem in rxe_mmap (bsc#1274040).\n- CVE-2026-64586: wifi: brcmfmac: drain bus_reset work on device removal (bsc#1274492).\n- CVE-2026-68082: libceph: fix two unsafe bare decodes in decode_lockers() (bsc#1274581).\n- CVE-2026-68086: mm/khugepaged: write all dirty file folios when collapsing (bsc#1274713).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68105: drm/amdgpu: Fix kernel panic during driver load failure (bsc#1274849).\n- CVE-2026-68116: vxlan: mdb: Fix source list corruption on a failed replace (bsc#1274876).\n- CVE-2026-68117: tipc: clear sock-\u003esk on the failed-insert path in tipc_sk_create() (bsc#1274881).\n- CVE-2026-68120: rtase: Workaround for TX hang caused by hardware packet parsing (bsc#1274887).\n- CVE-2026-68121: pppoe: reload header pointer after dev_hard_header() (bsc#1274888).\n- CVE-2026-68123: openvswitch: fix GSO userspace truncation underflow (bsc#1275169).\n- CVE-2026-68124: mctp: serial: handle zero-length frames to prevent rx buffer overflow (bsc#1275192).\n- CVE-2026-68127: ila: reload IPv6 header after pskb_may_pull in checksum adjust (bsc#1275237).\n- CVE-2026-68128: ice: reject out-of-range ptype in ice_parser_profile_init (bsc#1275238).\n- CVE-2026-68129: gve: fix Rx queue stall on alloc failure (bsc#1275517).\n- CVE-2026-68132: super: fix emergency thaw deadlock on frozen block devices (bsc#1275553).\n- CVE-2026-68133: ice: fix PTP Call Trace during PTP release (bsc#1275555).\n- CVE-2026-68135: net: hip04: fix RX buffer leak on build_skb failure (bsc#1275557).\n- CVE-2026-68136: net: gro: fix double aggregation of flush-marked skbs (bsc#1275474).\n- CVE-2026-68138: net/sched: serialize qdisc_rtab_list against concurrent get/put (bsc#1274941).\n- CVE-2026-68139: net/mlx5e: Use sender devcom for MPV master-up (bsc#1275578).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68142: geneve: require CAP_NET_ADMIN in the device netns for changelink (bsc#1275582).\n- CVE-2026-68143: net: slip: serialize receive against buffer reallocation (bsc#1275583).\n- CVE-2026-68144: phonet: pep: fix use-after-free in pep_get_sb() (bsc#1275481).\n- CVE-2026-68145: iomap: fix out-of-bounds bitmap_set() with zero-length range (bsc#1275584).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68149: fs: preserve ACL_DONT_CACHE state in forget_cached_acl() (bsc#1275294).\n- CVE-2026-68152: amt: fix use-after-free in AMT delayed works (bsc#1275300).\n- CVE-2026-68153: libceph: remove debugfs files before client teardown (bsc#1275301).\n- CVE-2026-68154: libceph: reject zero bucket types in crush_decode (bsc#1275303).\n- CVE-2026-68155: libceph: Reject monmaps advertising zero monitors (bsc#1275304).\n- CVE-2026-68156: libceph: refresh auth-\u003eauthorizer_buf{,_len} after authorizer update (bsc#1275305).\n- CVE-2026-68157: libceph: guard missing CRUSH type name lookup (bsc#1275306).\n- CVE-2026-68158: libceph: Fix multiplication overflow in decode_new_up_state_weight() (bsc#1275307).\n- CVE-2026-68159: libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE (bsc#1275470).\n- CVE-2026-68161: sctp: close UDP tunnel sockets during netns teardown (bsc#1274892).\n- CVE-2026-68164: mm/damon/core: disallow overlapping input ranges for damon_set_regions() (bsc#1274955).\n- CVE-2026-68165: mm/damon/core: validate ranges in damon_set_regions() (bsc#1274927).\n- CVE-2026-68166: userfaultfd: prevent registration of special VMAs (bsc#1274930).\n- CVE-2026-68169: mptcp: pm: userspace: fix use-after-free in get_local_id (bsc#1274952).\n- CVE-2026-68183: firmware: stratix10-svc: fix memory leaks and list corruption bugs (bsc#1274957).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68205: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() (bsc#1274934).\n- CVE-2026-68238: drm/amdgpu: Release VFCT ACPI table reference (bsc#1275704).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68267: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists (bsc#1275139).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68284: bpf, sockmap: Fix cork use-after-free in tcp_bpf_sendmsg() (bsc#1275970).\n- CVE-2026-68286: drop_monitor: perform u64_stats updates under IRQ-disabled section (bsc#1275973).\n- CVE-2026-68288: net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD (bsc#1275975).\n- CVE-2026-68289: tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream() (bsc#1275976).\n- CVE-2026-68293: net/mlx5: Fix MCIA register buffer overflow on 32 dword reads (bsc#1275091).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68296: net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM (bsc#1275045).\n- CVE-2026-68297: tipc: fix u16 MTU truncation in media and bearer MTU validation (bsc#1275040).\n- CVE-2026-68299: vmxnet3: fix BUG_ON in vmxnet3_get_hdr_len() for Geneve packets (bsc#1275088).\n- CVE-2026-68300: sctp: auth: verify auth requirement when auth_chunk is NULL (bsc#1275083).\n- CVE-2026-68302: amt: re-read skb header pointers after every pull (bsc#1275081).\n- CVE-2026-68313: tipc: fix infinite loop in __tipc_nl_compat_dumpit (bsc#1274665).\n- CVE-2026-68315: sctp: validate stream count in sctp_process_strreset_inreq() (bsc#1274662).\n- CVE-2026-68319: pds_core: fix deadlock between reset thread and remove (bsc#1274657).\n- CVE-2026-68320: sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid (bsc#1274659).\n- CVE-2026-68321: net: txgbe: fix FDIR filter leak on remove (bsc#1274652).\n- CVE-2026-68322: rds: Fix inet6_addr_lst NULL dereference when IPv6 is disabled (bsc#1274656).\n- CVE-2026-68325: iommu/amd: Bound the early ACPI HID map (bsc#1274651).\n- CVE-2026-68328: nfp: Check resource mutex allocation (bsc#1274646).\n- CVE-2026-68329: iommu/amd: Wait for completion instead of returning early in iommu_completion_wait() (bsc#1274645).\n- CVE-2026-68331: dpaa2-eth: put MAC endpoint device on disconnect (bsc#1274642).\n- CVE-2026-68333: dpaa2-switch: put MAC endpoint device on disconnect (bsc#1274644).\n- CVE-2026-68335: rds: drop incoming messages that cross network namespace boundaries (bsc#1274640).\n- CVE-2026-68336: bonding: fix devconf_all NULL dereference when IPv6 is disabled (bsc#1274639).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68375: bnxt_en: Handle partially initialized auxiliary devices (bsc#1274835).\n- CVE-2026-68377: net/sched: act_tunnel_key: Defer dst_release to RCU callback (bsc#1274831).\n- CVE-2026-68386: bpf, sockmap: Reject unhashed UDP sockets on sockmap update (bsc#1274814).\n- CVE-2026-68393: Bluetooth: hci_sync: extend conn_hash lookup critical sections (bsc#1274904).\n- CVE-2026-68395: ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered (bsc#1274900).\n- CVE-2026-68397: net/iucv: take a reference on the socket found in afiucv_hs_rcv() (bsc#1274898).\n- CVE-2026-68398: ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF (bsc#1274908).\n- CVE-2026-68399: bpf: Fix UAF in sock clone early bailouts (bsc#1274897).\n- CVE-2026-68408: wifi: cfg80211: convert pmsr_free_wk to wiphy_work to fix deadlock (bsc#1274709).\n- CVE-2026-68417: RDMA/siw: publish QP after initialization (bsc#1274696).\n- CVE-2026-68418: RDMA/irdma: Prevent user-triggered null deref on QP create (bsc#1274690).\n- CVE-2026-68419: RDMA/irdma: Prevent rereg_mr for non-mem regions (bsc#1274698).\n- CVE-2026-68422: btrfs: fix root leak if its reloc root is unexpected in merge_reloc_roots() (bsc#1274706).\n- CVE-2026-68425: IB/mad: Drop unmatched RMPP responses before reassembly (bsc#1274700).\n- CVE-2026-68426: xfrm: fix stale skb-\u003eprev after async crypto steals a GSO segment (bsc#1274705).\n- CVE-2026-68432: vxlan: require CAP_NET_ADMIN in the device netns for changelink (bsc#1274800).\n- CVE-2026-68433: libceph: bound get_version reply decode to front len (bsc#1274801).\n- CVE-2026-68442: btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps (bsc#1274773).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68450: btrfs: free mapping node on duplicate reloc root insert (bsc#1274834).\n- CVE-2026-68470: wifi: mac80211: validate extension-frame layout before RX (bsc#1276500).\n- CVE-2026-68480: x86/bugs: Make Safe-RET robust against interrupt injection (bsc#1274208).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72020: ipvs: reset full ip_vs_seq structs in ip_vs_conn_new (bsc#1275506).\n- CVE-2026-72022: llc: fix SAP refcount leak in llc_ui_autobind() (bsc#1276785).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72032: net/mlx5: HWS, fix matcher leak on resize target setup failure (bsc#1276955).\n- CVE-2026-72034: fhandle: reject detached mounts in capable_wrt_mount() (bsc#1276957).\n- CVE-2026-72035: net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1276961).\n- CVE-2026-72036: net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1277034).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72046: gve: fix header buffer corruption with header-split and HW-GRO (bsc#1275519).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72069: locking/rt: Fix the incorrect RCU protection in rt_spin_unlock() (bsc#1275528).\n- CVE-2026-72072: net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete (bsc#1277155).\n- CVE-2026-72083: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE (bsc#1275535).\n- CVE-2026-72084: scsi: target: core: Generate correct identifiers for PR OUT transport IDs (bsc#1275540).\n- CVE-2026-72100: dm-integrity: fix a bug if the bio is out of limits (bsc#1277311).\n- CVE-2026-72101: dm-integrity: fix leaking uninitialized kernel memory (bsc#1276831).\n- CVE-2026-72103: dm: avoid leaking the caller's thread keyring via the table device file (bsc#1277315).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72132: NFS: Charge unstable writes by request size, not folio size (bsc#1277551).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72137: xfrm: nat_keepalive: avoid double free on send error (bsc#1275587).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72176: mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error (bsc#1277230).\n- CVE-2026-72177: mm/damon/sysfs-schemes: fix dir put orders in access_pattern_add_dirs() (bsc#1277227).\n- CVE-2026-72217: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing (bsc#1275655).\n- CVE-2026-72221: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (bsc#1275665).\n- CVE-2026-72222: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (bsc#1275669).\n- CVE-2026-72234: batman-adv: access unicast_ttvn skb-\u003edata only after skb realloc (bsc#1275672).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72251: netfilter: nf_nat_sip: reload possible stale data pointer (bsc#1275827).\n- CVE-2026-72254: netfilter: nft_fib: reject fib expression on the netdev egress hook (bsc#1277204).\n- CVE-2026-72280: KVM: arm64: nv: Drop bogus WARN for write to ZCR_EL2 (bsc#1277726).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72288: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling (bsc#1275886).\n- CVE-2026-72289: KVM: arm64: vgic: Check the interrupt is still ours before migrating it (bsc#1275905).\n- CVE-2026-72296: net: ife: require ETH_HLEN to be pullable in ife_decode() (bsc#1275923).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72307: mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace() (bsc#1277160).\n- CVE-2026-72308: mlxsw: fix refcount leak in mlxsw_sp_port_lag_join() (bsc#1277159).\n- CVE-2026-72317: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (bsc#1275925).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72337: Bluetooth: 6lowpan: avoid untracked enable work (bsc#1277773).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72341: net/mlx5e: Fix publication race for priv-\u003echannel_stats[] (bsc#1277660).\n- CVE-2026-72342: net/mlx5e: Fix HV VHCA stats agent registration race (bsc#1277775).\n- CVE-2026-72343: net/mlx5e: Fix HV VHCA stats zero-sized buffer allocation (bsc#1277776).\n- CVE-2026-72345: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback (bsc#1277782).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72366: netfs: Fix netfs_create_write_req() to handle async cache object creation (bsc#1276333).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72389: bridge: stp: Fix a potential use-after-free when deleting a bridge (bsc#1273869).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72414: net: dsa: sja1105: round up PTP perout pin duration (bsc#1278039).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72430: net/sched: act_ct: fix nf_connlabels leak on two error paths (bsc#1277118).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72464: xprtrdma: Post receive buffers after RPC completion (bsc#1277069).\n- CVE-2026-72466: xprtrdma: Fix bcall rep leak and unbounded peek (bsc#1277057).\n- CVE-2026-72467: xprtrdma: Check frwr_wp_create() during connect (bsc#1277059).\n- CVE-2026-72468: xprtrdma: Initialize re_id before removal registration (bsc#1277062).\n- CVE-2026-72469: xprtrdma: Fix ep kref imbalance on ADDR_CHANGE (bsc#1277047).\n- CVE-2026-72473: xprtrdma: Avoid 250 ms delay on backlog wakeup (bsc#1277037).\n- CVE-2026-72485: coresight: platform: defer connection counter increment until alloc succeeds (bsc#1276771).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-72494: RDMA/irdma: Replace waitqueue and flag with completion (bsc#1276941).\n- CVE-2026-72495: RDMA/bnxt_re: Avoid repeated requests to allocate WC pages (bsc#1276937).\n- CVE-2026-72497: RDMA/bnxt_re: Add a max slot check for SQ (bsc#1276913).\n- CVE-2026-72499: RDMA/bnxt_re: Free CQ toggle page after firmware teardown (bsc#1276551).\n- CVE-2026-72500: RDMA/bnxt_re: Free SRQ toggle page after firmware teardown (bsc#1276552).\n- CVE-2026-72501: RDMA/bnxt_re: Initialize dpi variable to zero (bsc#1276546).\n- CVE-2026-72502: tcp: ipv6: clamp default adverting MSS to avoid GSO_BY_FRAGS (0xFFFF) (bsc#1276542).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74269: bnxt: fix head underflow on XDP head-grow (bsc#1276507).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74286: net: pfcp: allocate per-cpu tstats for PFCP netdevs (bsc#1276471).\n- CVE-2026-74296: RDMA/mlx5: Release the HW-provided UAR index rather than the SW one (bsc#1276452).\n- CVE-2026-74297: RDMA/mlx5: Fix undefined shift of user RQ WQE size (bsc#1276446).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74316: NFSD: Handle layout stid in nfsd4_drop_revoked_stid() (bsc#1276870).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74318: btrfs: fix deadlock cloning inline extent when using flushoncommit (bsc#1276864).\n- CVE-2026-74321: btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() (bsc#1277202).\n- CVE-2026-74334: RDMA/nldev: Fix locking when accessing mr-\u003epd (bsc#1277095).\n- CVE-2026-74345: RDMA/siw: Fix endpoint/socket association handling (bsc#1277285).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74394: RDMA/srpt: fix integer overflow in immediate data length check (bsc#1277408).\n- CVE-2026-74395: RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference (bsc#1277077).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74474: vxlan: use pskb_network_may_pull() for transmit path header pulls (bsc#1276335).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74481: mm/page_reporting: use system_freezable_wq to fix UAF during suspend (bsc#1276355).\n- CVE-2026-74482: mm/huge_memory: unlock i_mmap_rwsem before releasing after-split folios (bsc#1276346).\n- CVE-2026-74495: igbvf: Fix leak in TX DMA error cleanup (bsc#1275864).\n- CVE-2026-74496: fou: Fix use-after-free in fou_create() (bsc#1275867).\n- CVE-2026-74510: Bluetooth: mgmt: fix UAF in pair command cancellation (bsc#1275950).\n- CVE-2026-74512: audit: fix potential use-after-free in audit_del_rule() (bsc#1275954).\n- CVE-2026-74513: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister (bsc#1275956).\n- CVE-2026-74517: KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs (bsc#1276258).\n- CVE-2026-74518: mm/hugetlb: fix list corruption in allocate_file_region_entries() (bsc#1275798).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74527: octeontx2-af: Block VFs from clobbering special CGX PKIND state (bsc#1275805).\n- CVE-2026-74533: Bluetooth: ISO: fix race of kfree vs kref_get_unless_zero (bsc#1275804).\n- CVE-2026-74534: Bluetooth: ISO: Fix data-race on iso_pi(sk) in socket and HCI event paths (bsc#1275801).\n- CVE-2026-74535: Bluetooth: ISO: avoid deadlocks in iso_sock_timeout (bsc#1275812).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74537: Bluetooth: ISO: hold sk properly in iso_conn_ready (bsc#1275687).\n- CVE-2026-74545: rtase: fix double free of multi-frag skb on DMA map failure (bsc#1275679).\n- CVE-2026-74548: forcedeth: fix UAF of txrx_stats in nv_remove (bsc#1275695).\n- CVE-2026-74550: net: do not send ICMP/NDISC Redirects when peer allocation fails (bsc#1275688).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74556: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer (bsc#1275696).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74563: rds: tcp: hold the RCU lock across ipv6_chk_addr() in rds_tcp_laddr_check() (bsc#1275574).\n- CVE-2026-74566: keys: make keyring key-chunk byte order agree with keyring_diff_objects() (bsc#1275566).\n- CVE-2026-74567: keys: fix out-of-bounds read in keyring_get_key_chunk() (bsc#1275569).\n- CVE-2026-74571: btrfs: skip global block reserve accounting for rescue mounts (bsc#1275561).\n- CVE-2026-74577: net: mpls: initialize rtm_tos in mpls_getroute() (bsc#1275572).\n- CVE-2026-74581: net: ipv6: clear suppressed fib6 rule result (bsc#1275782).\n- CVE-2026-74582: packet: use consistent hard_header_len in non-ring send paths (bsc#1275784).\n- CVE-2026-74584: RDMA/bnxt_re: zero shared page before exposing to userspace (bsc#1277066).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74610: tls: don't leave a full plaintext sk_msg ring unpushed (bsc#1277054).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74644: mm/damon/ops-common: putback folios on invalid migrate nid (bsc#1277033).\n- CVE-2026-74665: net: fix skb length accounting after generic XDP frag adjustment (bsc#1277407).\n- CVE-2026-74669: ipvs: clear IPv4 options after rebasing tunnel ICMP errors (bsc#1277391).\n- CVE-2026-74695: netfilter: nf_flow_table: drop existing skb dst before skb_dst_set_noref() (bsc#1276931).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74712: vdpa/mlx5: Fix buffer length in create_direct_keys() (bsc#1276577).\n- CVE-2026-74717: net/mlx5: fw_tracer, return NULL on create error (bsc#1276569).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74722: btrfs: fix memory leak in btrfs_do_encoded_write() (bsc#1276561).\n- CVE-2026-74723: btrfs: lzo: reject inline extents without valid headers (bsc#1276562).\n- CVE-2026-74730: NFS: Pin the 'struct nfs_server' during a FREE_STATEID call (bsc#1276566).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-80529: xfs: don't swallow dquot recovery verification errors (bsc#1277688).\n- CVE-2026-80530: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN (bsc#1277668).\n- CVE-2026-80531: xfs: avoid UAF on sc-\u003etempip in xrep_tempfile_create (bsc#1277680).\n- CVE-2026-80533: xfs: don't walk off the end of a null sc-\u003esa.agi_bp in AGI repair (bsc#1277636).\n- CVE-2026-80534: xfs: fix ilock leak on error in xfs_dq_get_next_id (bsc#1277022).\n- CVE-2026-80535: xfs: don't double-lock when deleting a self-referential directory (bsc#1277641).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80558: libceph: Avoid using invalid osd indices from primary_temp (bsc#1277485).\n- CVE-2026-80561: libceph: fix multiple unsafe decodes in decode_locker() (bsc#1277265).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80590: inet: frags: strip GSO state from fragments before reassembly (bsc#1277275).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80609: qede: fix out-of-bounds check for cqe-\u003elen_list (bsc#1278334).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80721: Bluetooth: ISO: ensure no dangling hcon references in iso_conn (bsc#1277845).\n- CVE-2026-80727: x86/mce: Set up the polling timer before CMCI discovery (bsc#1278703).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80813: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() (bsc#1279537).\n- CVE-2026-80838: vxlan: keep the last remote linked during FDB flush (bsc#1279842).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Limit firmware log name prints to field size (git-fixes).\n- accel/ivpu: Validate firmware log buffer metadata (git-fixes).\n- accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr (git-fixes).\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- accessibility: speakup: Fix incorrect string length computation in report_char_chartab_status() (git-fixes).\n- accessibility: speakup: unregister tty ldisc on later init failures (git-fixes).\n- ACPI: APEI: Fix ERST timeout unit conversion (git-fixes).\n- ACPI: battery: Adjust charging status validation check (git-fixes).\n- ACPI: EC: Avoid _REG disconnect on GPIO IRQ defer (git-fixes).\n- ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root (git-fixes).\n- ACPI: pfr_update: fix stack buffer overflow in query_capability() (git-fixes).\n- ACPI: processor: idle: Expand _LPI package sanity checks (git-fixes).\n- ACPI: processor: validate MADT IOAPIC entry bounds (git-fixes).\n- ACPI: processor_idle: Mark LPI enter functions as __cpuidle (git-fixes).\n- ACPI: scan: fix bus ID cleanup on device_add() failures (git-fixes).\n- ACPI: video: Release PCI device reference after lookup (git-fixes).\n- ALSA: 6fire: bound the MIDI event length from the device (git-fixes).\n- ALSA: 6fire: Fix UAF at error handling during probe (stable-fixes).\n- ALSA: bcd2000: clear the URB pointers on disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: control: Don't add invalid kcontrols to LED layer (git-fixes).\n- ALSA: core: Fix use-after-free in snd_card_do_free() (git-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Check card index validity at probe (stable-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/ext: preserve PPLCCTL bits when clearing reset (git-fixes).\n- ALSA: hda/realtek: Enable headset mic on F+ FLAPTOP r (stable-fixes).\n- ALSA: hda: Fix connection list comparison in proc output (git-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hpi: Check transport errors during HPI6000 adapter initialization (git-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcxhr: initialize mutexes before requesting threaded IRQ (git-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: scarlett2: Use a private URB for the notification endpoint (git-fixes).\n- ALSA: seq: Don't leak the extension cell pointer in the bounce payload (git-fixes).\n- ALSA: seq: midi: Optimize event_input locking with RCU (git-fixes).\n- ALSA: seq: midi: Serialize input teardown with event_input (git-fixes).\n- ALSA: ump: Fix corrupted data bytes at MIDI 1.0 SysEx to UMP conversion (git-fixes).\n- ALSA: usb-audio: Complete cleanup after system-resume errors (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_novation_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write on Type II inbound URBs (git-fixes).\n- ALSA: usb: Fix UAF at delayed release of MIDI2 EPs (git-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usbusx2y: validate URB actual_length in interrupt callback (git-fixes).\n- ALSA: usx2y: bound the hwdep mmap fault offset (git-fixes).\n- ALSA: via82xx: Remove unreachable branch in snd_via686_pcm_pointer() (git-fixes).\n- apparmor: advertise the tcp fast open fix is applied (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: adau1761: sort the register default table (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add DMI entry for MSI Thin A15 B7UC (git-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: apple: mca: increase SERDES reset delay (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses (git-fixes).\n- ASoC: cs35l33: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l34: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l41: sort the register default table (git-fixes).\n- ASoC: cs35l45: sort the register default table (git-fixes).\n- ASoC: cs4265: sort the register default table (git-fixes).\n- ASoC: cx2072x: sort the register default table (git-fixes).\n- ASoC: dapm: Fix off-by-one check on the second enum channel (git-fixes).\n- ASoC: fix unmet dependencies on PPC_BESTCOMM and SND_SOC_AC97_BUS (git-fixes).\n- ASoC: fsl-asoc-card: defer probe when the CPU DAI device is not ready (git-fixes).\n- ASoC: fsl: mpc5200-i2s: Free DMA resources on probe failure (git-fixes).\n- ASoC: fsl_audmix: rework runtime PM handling in probe (git-fixes).\n- ASoC: fsl_easrc: sort the register default table (git-fixes).\n- ASoC: hdac_hda: Fix hlink refcount leak on component registration failure (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: avs: Do not ignore -ENOENT when loading a topology (git-fixes).\n- ASoC: Intel: avs: Fix unbalanced module reference count (git-fixes).\n- AsoC: intel: sst: fix PCI device reference leak on probe failure (git-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: loongson: Fix error handling in ACPI property parsing (git-fixes).\n- ASoC: max9860: sort the register default table (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Shorten memif_data table using macros (stable-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Support \u003e32 bit DMA addresses (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: use local `dev` pointer in driver callbacks (stable-fixes).\n- ASoC: mediatek: mt8183: Check runtime resume during probe (git-fixes).\n- ASoC: mediatek: mt8192-afe-pcm: Simplify probe() with local dev variable (stable-fixes).\n- ASoC: mediatek: mt8192: Check runtime resume during probe (git-fixes).\n- ASoC: meson: Keep link pointers valid on realloc failure (git-fixes).\n- ASoC: ml26124: sort the register default table (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: pcm512x: sort the register default table (git-fixes).\n- ASoC: pxa: Use devm_clk_get_optional() for extclk clock (git-fixes).\n- ASoC: qcom: q6apm: keep the graph start count in sync with the DSP (git-fixes).\n- ASoC: rt274: sort the register default table (git-fixes).\n- ASoC: rt286: sort the register default table (git-fixes).\n- ASoC: rt298: sort the register default table (git-fixes).\n- ASoC: rt700-sdw: always drain jack work on remove (git-fixes).\n- ASoC: rt700: drop duplicate reg_default entry (git-fixes).\n- ASoC: rt700: sort the register default table (git-fixes).\n- ASoC: rt711-sdca: sort the register default tables (git-fixes).\n- ASoC: rt711: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-dmic: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt715-sdca: drop duplicate reg_default entries (git-fixes).\n- ASoC: rt715-sdca: sort the register default tables (git-fixes).\n- ASoC: rt715: sort the register default table (git-fixes).\n- ASoC: rt1017-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt1316-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318: sort the register default table (git-fixes).\n- ASoC: samsung: aries_audio_probe: double of_node_put due to direct assignment without of_node_get (git-fixes).\n- ASoC: sgtl5000: sort the register default table (git-fixes).\n- ASoC: SOF: sof-audio: Fix error path in sof_widget_setup_unlocked() (git-fixes).\n- ASoC: SOF: validate topology volume range before allocation (git-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti-sas: sort the register default table (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tas2552: sort the register default table (git-fixes).\n- ASoC: tas2764: sort the register default table (git-fixes).\n- ASoC: tas2780: sort the register default table (git-fixes).\n- ASoC: tegra210_i2s: sort the register default table (git-fixes).\n- ASoC: tegra210_mixer: sort the register default table (git-fixes).\n- ASoC: tegra: Fix the MIXER enable default value (git-fixes).\n- ASoC: tegra: Sort MBDRC register defaults (git-fixes).\n- ASoC: xilinx: formatter_pcm: fix stream_data leak on open error (git-fixes).\n- ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- batman-adv: bla: fix freeing of claims on meshif deletion (git-fixes).\n- batman-adv: bla: prevent CRC corruptions after claim flush (git-fixes).\n- batman-adv: dat: avoid unaligned fault in IP extraction (git-fixes).\n- batman-adv: fix stale receive device on merged fragments (git-fixes).\n- batman-adv: mcast: ensure unshared skb for multicast packets (git-fixes).\n- batman-adv: mcast: linearize skbuff for packet generation (git-fixes).\n- batman-adv: reject unrepresentable multicast TVLV offsets (git-fixes).\n- blk-mq: reinsert cached request to the list (bsc#1273770).\n- Bluetooth: btintel: bound firmware ID by TLV length (git-fixes).\n- Bluetooth: btintel: Fix diagnostics event detection (git-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btintel_pcie: Clear automask on spurious interrupts (git-fixes).\n- Bluetooth: btintel_pcie: fix tx_handle bounds off-by-one (git-fixes).\n- Bluetooth: btintel_pcie: validate packet_len before skb_put_data (git-fixes).\n- Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware (git-fixes).\n- Bluetooth: btmtk: Do not discard the subsystem reset timeout (git-fixes).\n- Bluetooth: btmtk: Fix short read errors in btmtk_usb_uhw_reg_read() (stable-fixes).\n- Bluetooth: btmtksdio: Fix out-of-bounds DMA read in the TX path (git-fixes).\n- Bluetooth: btmtksdio: Take exclusive ownership of the SKB before TX (git-fixes).\n- Bluetooth: btqca: Fix qca_set_bdaddr() waiting for wrong HCI event (git-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Fix BD_ADDR byte order in btusb_set_bdaddr_wcn6855() (git-fixes).\n- Bluetooth: btusb: Fix short read errors in btusb_qca_send_vendor_req() (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: do not leak an hci_conn when a second LE connect is rejected (git-fixes).\n- Bluetooth: eir: Fix OOB read in eir_get_service_data() (git-fixes).\n- Bluetooth: hci_aml: validate firmware segment lengths (git-fixes).\n- Bluetooth: hci_bcm4377: Ignore reserved PHY in ext adv reports on BCM4378 (git-fixes).\n- Bluetooth: hci_bcm: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_conn: fix the SCO setup context lifetime (git-fixes).\n- Bluetooth: hci_conn: hold conn reference in abort_conn_sync() (git-fixes).\n- Bluetooth: hci_conn: re-enable advertising only for peripheral role (git-fixes).\n- Bluetooth: hci_core: Fix race condition during device registration (git-fixes).\n- Bluetooth: hci_core: use skb_get() instead of skb_clone() for req_skb (git-fixes).\n- Bluetooth: hci_event: clear HCI_LE_ADV only on a created connection (git-fixes).\n- Bluetooth: hci_event: fix LE list UAF on reset (git-fixes).\n- Bluetooth: hci_event: validate LE Set CIG Parameters response (git-fixes).\n- Bluetooth: hci_h5: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_intel: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sync: Clear HCI_CMD_PENDING when dropping the last request (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: free the advertising instance on the failure and cancel paths (git-fixes).\n- Bluetooth: hci_sync: make hci_cmd_sync_run_once return -EEXIST if exists (stable-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del() (git-fixes).\n- Bluetooth: hci_uart: Fix false success return in hci_uart_setup() (git-fixes).\n- Bluetooth: ISO: do not force BT_LISTEN after a failed BIG sync (git-fixes).\n- Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect (git-fixes).\n- Bluetooth: mgmt: fix locking in unpair_device/disconnect_sync (git-fixes).\n- Bluetooth: MGMT: free the HCI command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: free the mesh send cancel command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: reject HCI_CMD_SYNC params_len above 255 (git-fixes).\n- Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update (git-fixes).\n- Bluetooth: MSFT: validate evt_prefix_len against the response length (git-fixes).\n- Bluetooth: qca: fix NVM tag length underflow in TLV parser (git-fixes).\n- Bluetooth: RFCOMM: serialize security confirmation handling (git-fixes).\n- Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept (git-fixes).\n- Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (git-fixes).\n- Bluetooth: virtio_bt: avoid OOB read of build info string (git-fixes).\n- bnxt_en: Check return value of bnxt_hwrm_vnic_cfg (jsc#PED-16798).\n- bnxt_en: Delay for 5 seconds after AER DPC for all chips (jsc#PED-16798).\n- bnxt_en: Don't assume XDP is never enabled in bnxt_init_dflt_ring_mode() (jsc#PED-16798).\n- bnxt_en: Drop pci_save_state() after pci_restore_state() (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction for V3_CMP (jsc#PED-16798).\n- bnxt_en: Move bnxt_rss_ext_op into header (jsc#PED-16798).\n- bnxt_en: Refactor some basic ring setup and adjustment logic (jsc#PED-16798).\n- bnxt_en: Restore default stat ctxs for ULP when resource is available (jsc#PED-16798).\n- bnxt_en: Set bp-\u003emax_tpa according to what the FW supports (jsc#PED-16798).\n- bnxt_en: Use absolute target ns from ptp_clock_request (jsc#PED-16798).\n- bnxt_en: use bnxt_xdp_buff for xdp context (jsc#PED-16798).\n- bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation (git-fixes).\n- bus: mhi: host: Fix controller cleanup on EDL sysfs failure (git-fixes).\n- bus: mhi: host: Flush the posted write after writing to MHI_SOC_RESET_REQ_OFFSET (git-fixes).\n- bus: ti-sysc: Fix /chosen node reference leak (git-fixes).\n- cacheinfo: don't propagate DT/ACPI error when arch supplies info (arm64) (git-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: use netdevice_tracker for j1939_{priv,session,ecu} tracking (stable-fixes).\n- char: xilinx_hwicap: unregister class on init errors (git-fixes).\n- cleanup: add a scoped version of CLASS() (stable-fixes).\n- cleanup: fix scoped_class() (git-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- cpufreq: intel_pstate: Add and use hybrid_get_cpu_type() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Avoid SMP calls to get cpu-type (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Fix hwp_get_cpu_scaling() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use correct scaling factor on Raptor Lake-E (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use CPPC to get scaling factors (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use HYBRID_SCALING_FACTOR_ADL for Bartlett Lake (bsc#1240957 bsc#1249104 bsc#1265220).\n- crypto: aspeed - Propagate platform_get_irq() errors (git-fixes).\n- crypto: atmel-sha204a - fix heap info leak on I2C transfer failure (git-fixes).\n- crypto: atmel-tdes - use scatterlist length before DMA mapping (git-fixes).\n- crypto: ccm - Set rfc4309 maxauthsize from child (git-fixes).\n- crypto: ccp - Abort doing SEV INIT if SNP INIT fails (stable-fixes).\n- crypto: ccp - Add new SEV/SNP platform shutdown API (stable-fixes).\n- crypto: ccp - Always pass in an error pointer to __sev_platform_shutdown_locked() (git-fixes).\n- crypto: ccp - Fix __sev_snp_shutdown_locked (git-fixes).\n- crypto: ccp - Fix dereferencing uninitialized error pointer (git-fixes).\n- crypto: ccp - Fix memory leak in SEV INIT_EX path (git-fixes).\n- crypto: ccp - Fix possible deadlock in SEV init failure path (git-fixes).\n- crypto: ccp - Fix SNP panic notifier unregistration (git-fixes).\n- crypto: ccp - Move dev_info/err messages for SEV/SNP init and shutdown (stable-fixes).\n- crypto: ccp - Move SEV/SNP Platform initialization to KVM (stable-fixes).\n- crypto: ccp - Register SNP panic notifier only if SNP is enabled (stable-fixes).\n- crypto: ccp - Reset TMR size at SNP Shutdown (stable-fixes).\n- crypto: doc - Remove extra parenthesis (git-fixes).\n- crypto: hisilicon/sec2 - fix CCM algorithm long packet failure (git-fixes).\n- crypto: keembay - Fix AEAD unregister count in error path (git-fixes).\n- crypto: keembay - Initialize completion before requesting IRQ (git-fixes).\n- crypto: keembay - publish OF module alias for OCS AES/SM4 (git-fixes).\n- crypto: lskcipher - propagate errors from unaligned crypt (git-fixes).\n- crypto: mxs-dcp - fix source scatterlist length access (git-fixes).\n- crypto: qat - cancel work on re-enable SR-IOV timeout (git-fixes).\n- crypto: qat - clear AES key schedule from stack (git-fixes).\n- crypto: qce - fix CCM AAD buffer underallocation (git-fixes).\n- crypto: qce - fix error path in devm_qce_register_algs (git-fixes).\n- crypto: qcom-rng - Allow zero as a random number (git-fixes).\n- crypto: qcom-rng - Enable clock in hwrng case (git-fixes).\n- crypto: rk3288 - fail ahash requests on HASH idle timeout (git-fixes).\n- crypto: sa2ul - stop probe if context pool creation fails (git-fixes).\n- crypto: sl3516 - drop invalid sg_dma_len checks before DMA mapping (git-fixes).\n- crypto: tegra - Don't touch bo refcount in host1x bo pin/unpin (stable-fixes).\n- crypto: tegra - fix rctx-\u003ecryptlen calculation in tegra_gcm_do_one_req() (git-fixes).\n- cxl/acpi: Fix CXL_ACPI and CXL_PMEM Kconfig tristate mismatch (git-fixes).\n- cxl: Adjust the startup priority of cxl_pmem to be higher (git-fixes).\n- default_gfp(): avoid using the \"newfangled\" __VA_OPT__ trick (bsc#1280139).\n- device property: fix infinite loop in fwnode_for_each_child_node() (git-fixes).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dma-mapping: add __dma_from_device_group_begin()/end() (bsc#1267586).\n- dmaengine: dw-edma: Clear stale requests on termination (git-fixes).\n- dmaengine: dw-edma: Complete descriptors before pausing (git-fixes).\n- dmaengine: dw-edma: Fix HDMA channel status register access (git-fixes).\n- dmaengine: dw-edma: Initialize IRQ data before requesting IRQs (git-fixes).\n- dmaengine: dw-edma: Serialize abort state updates (git-fixes).\n- dmaengine: dw-edma: Serialize channel state checks (git-fixes).\n- dmaengine: dw-edma: Terminate all descriptors without callbacks (git-fixes).\n- dmaengine: fsl-edma: tracing: no ptr dereference during log output (git-fixes).\n- dmaengine: hisilicon: Return -ENOMEM on dynamic memory allocation in probe (git-fixes).\n- dmaengine: mediatek: mtk-uart-apdma: Return -ENOMEM on memory allocation failure (git-fixes).\n- dmaengine: qcom-bam-dma: fix autosuspend cleanup during removal (git-fixes).\n- dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers (git-fixes).\n- dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout (git-fixes).\n- dmaengine: zynqmp_dma: fix kernel doc for zynqmp_dma_remove() (git-fixes).\n- driver core: soc: Unregister bus on early device registration failure (git-fixes).\n- drivers/virt: pkvm: Fix end calculation in mmio_guard_ioremap_hook() (git-fixes).\n- Drivers: hv: Use meaningful errnos for hypercall status codes (git-fixes).\n- drm/amd/display: Add AV mute wait frames to dce110_set_avmute (stable-fixes).\n- drm/amd/display: avoid divide-by-zero in __is_lut_linear() (git-fixes).\n- drm/amd/display: Check for tg ops in dce110_set_avmute (git-fixes).\n- drm/amd/display: dce100: skip non-DP stream encoders for DP MST (stable-fixes).\n- drm/amd/display: fix BT.2020 YCbCr limited output CSC matrix (git-fixes).\n- drm/amd/display: fix BT.2020 YCbCr output CSC matrices for DCE (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix NULL pointer dereference in amdgpu_dm_crtc_set_vblank() (git-fixes).\n- drm/amd/display: Increase HDMI AV mute wait from 2 to 3 frames (stable-fixes).\n- drm/amd/display: Remove unused-but-set variable hubp from (git-fixes).\n- drm/amd/display: validate plane degamma LUT size for private color prop (git-fixes).\n- drm/amd/pm: adjust the visibility of pp_table sysfs node (stable-fixes).\n- drm/amd/pm: fix gpu metrics energy accumulator for smu 13.0.0/13.0.7 (git-fixes).\n- drm/amd/pm: fix smu14 power limit range calculation (stable-fixes).\n- drm/amd/pm: make pp_features read-only when scpm is enabled (stable-fixes).\n- drm/amd/pm: Use same metric table for APU (stable-fixes).\n- drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read (git-fixes).\n- drm/amdgpu/gfx6: Fixup emit_cntxcntl() (git-fixes).\n- drm/amdgpu/gfx6: Fixup emitting SWITCH_BUFFER packets (git-fixes).\n- drm/amdgpu/gfx6: Use PFP on the compute queues too (git-fixes).\n- drm/amdgpu/gfx8: drop unecessary BUG_ON() (stable-fixes).\n- drm/amdgpu/gfx9.4.3: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx9: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx11: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx12: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in SMU7 lookup (git-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup (git-fixes).\n- drm/amdgpu/sdma4.4.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma6.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma7.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/uvd: Fix forcing MSG, FB BOs into VCPU segment when it isn't at 0 (v2) (stable-fixes).\n- drm/amdgpu/uvd: Place VCPU BO only in VRAM for UVD 4.x and older (stable-fixes).\n- drm/amdgpu/vce: fix integer overflow in image size (stable-fixes).\n- drm/amdgpu/vcn4: avoid rereading IB param length (stable-fixes).\n- drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check (git-fixes).\n- drm/amdgpu: cap GTT size to physical RAM on APUs (stable-fixes).\n- drm/amdgpu: check ASPM on the dGPU host link (git-fixes).\n- drm/amdgpu: disallow multiple FENCE chunks in one submit (git-fixes).\n- drm/amdgpu: fix aperture iounmap skipped on device removal (git-fixes).\n- drm/amdgpu: fix autosuspend cleanup during removal (git-fixes).\n- drm/amdgpu: fix bo-\u003epin leaking in amdgpu_bo_create_reserved (stable-fixes).\n- drm/amdgpu: fix division by zero with invalid uvd dimensions (stable-fixes).\n- drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid() (stable-fixes).\n- drm/amdgpu: fix nbif 6.3.1 l1 low power not functional (git-fixes).\n- drm/amdgpu: Fix UVD decode image min size calculation (stable-fixes).\n- drm/amdgpu: Fix UVD dpb min size calculation for H264 (stable-fixes).\n- drm/amdgpu: Fix UVD min buffer sizes (stable-fixes).\n- drm/amdgpu: Fix VCE 3 ring align_mask (git-fixes).\n- drm/amdgpu: Fix VFCT bus number matching with soft filter (stable-fixes).\n- drm/amdgpu: Implement insert_end for VCE 3 (git-fixes).\n- drm/amdgpu: invoke pm_genpd_remove() before freeing genpd (stable-fixes).\n- drm/amdgpu: move debug_vm handling to amdgpu_cs_parser_fini (git-fixes).\n- drm/amdgpu: read TRUNCATE_COORD_MODE on gfx12 (git-fixes).\n- drm/amdgpu: reject oversized IBs with per-ring packet limits (stable-fixes).\n- drm/amdgpu: Reject UVD message with dimensions above 4096 (stable-fixes).\n- drm/amdgpu: Reject UVD message with invalid number of h265 refs (stable-fixes).\n- drm/amdgpu: remove unused function parameter (stable-fixes).\n- drm/amdgpu: restore UMD profile pstate after runtime resume (stable-fixes).\n- drm/amdgpu: validate GEM_CREATE domain combinations (stable-fixes).\n- drm/amdkfd: Check bounds in allocate_event_notification_slot (stable-fixes).\n- drm/amdkfd: fix 32-bit overflow in CWSR total size calculation (stable-fixes).\n- drm/amdkfd: Fix missing authorization check in KFD_IOC_DBG_TRAP_DISABLE (stable-fixes).\n- drm/amdkfd: fix QID bit leak in pqm_create_queue() (stable-fixes).\n- drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore (git-fixes).\n- drm/amdkfd: Handle invalid event type in CRIU event restore (stable-fixes).\n- drm/amdkfd: Use kvcalloc to allocate arrays (stable-fixes).\n- drm/bridge: cdns-mhdp8546: Return an error pointer on allocation failure (git-fixes).\n- drm/bridge: dw-hdmi: fix i2c adapter leak on probe failure (git-fixes).\n- drm/bridge: ps8640: propagate AUX transfer register errors (git-fixes).\n- drm/bridge: tc358767: clamp the reported AUX read size to the request (git-fixes).\n- drm/connector/hdmi: Fix out of bounds memory read (git-fixes).\n- drm/connector: Fix epoch_counter docs to reflect reality (git-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/hibmc: Fix list of formats on the primary plane (git-fixes).\n- drm/hibmc: Use drm_atomic_helper_check_plane_state() (git-fixes).\n- drm/i915/hdcp: check streams bounds before overflow (git-fixes).\n- drm/i915/hdcp: Move to using intel_display in intel_hdcp (stable-fixes).\n- drm/i915/hdcp: require monotonically increasing seq_num_v (git-fixes).\n- drm/i915/hdcp: Skip inactive MST connectors when building stream list (stable-fixes).\n- drm/i915/vrr: Check HAS_VRR() first in intel_vrr_is_capable() (stable-fixes).\n- drm/i915/vrr: require valid min/max vfreq for VRR (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/lima: call drm_mm_init() with a valid allocation range (git-fixes).\n- drm/msm/a6xx: Fix RBBM_CLOCK_CNTL3_TP0 value in a730_hwcg (git-fixes).\n- drm/msm/a6xx: Fix stale rpmh votes after suspend (git-fixes).\n- drm/msm/dpu: Drop sneaky dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: Drop dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: round 6G byte clock rate to the PLL-achievable value (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau: unsubscribe the channel-kill event before the fence context (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/panel-edp: fix i2c adapter leak on probe failure (git-fixes).\n- drm/panel: samsung-s6d16d0: Power off on prepare failure (git-fixes).\n- drm/panthor: fix firmware control interface bounds checks (git-fixes).\n- drm/panthor: return PTR_ERR() from devm_drm_dev_alloc() (git-fixes).\n- drm/panthor: skip zero-sized firmware sections (git-fixes).\n- drm/radeon: fix autosuspend cleanup during teardown (git-fixes).\n- drm/radeon: fix r100_copy_blit for large BOs (stable-fixes).\n- drm/radeon: restore hardware polling in fence_is_signaled to fix performance regression (git-fixes).\n- drm/rockchip: vop2: Recognise 10-bit YUV422 as YUV format (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates for ssd132x (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates in ssd133x (git-fixes).\n- drm/sun4i: crtc: Propagate layer initialization error (git-fixes).\n- drm/sun4i: Drop node references while building component list (git-fixes).\n- drm/sun4i: dw-hdmi: Drop TCON TOP port reference (git-fixes).\n- drm/sun4i: fix refcount leak in sun4i_backend_init_sat() (git-fixes).\n- drm/sun4i: hdmi-phy: Fix H6 8-bit MPLL config at 594 MHz (git-fixes).\n- drm/sun4i: hdmi: Don't leak sync polarity bits into packet control (git-fixes).\n- drm/sun4i: tcon: Drop remote endpoint reference (git-fixes).\n- drm/sun4i: tcon: Drop TCON TOP device reference (git-fixes).\n- drm/sun4i: tcon: Set output mux for DSI and LVDS (git-fixes).\n- drm/sun4i: vi scaler: Fix coefficient selection (git-fixes).\n- drm/tegra: dsi: Re-add clear enable register if DSI was powered by bootloader (git-fixes).\n- drm/tegra: fbdev: Do not assign to struct drm_fb_helper.info (git-fixes).\n- drm/tve200: add OF module alias for autoloading (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/xe/oa: Check managed mutex initialization errors (git-fixes).\n- drm/xe/oa: Fix sync entry leak on OA config emit failure (git-fixes).\n- drm/xe/oa: Remove sysfs entry on idr_alloc failure in xe_oa_add_config_ioctl() (git-fixes).\n- drm/xe: Introduce xe_gt_dbg_printer() (stable-fixes).\n- drm/xe: Order ring writes before ring tail updates (git-fixes).\n- drm/xe: Stub out new pagefault layer (stable-fixes).\n- drm/xe: tests: fix error message in xe_migrate_sanity_test() (git-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: fix race between partial drm_dev_register() failure and ioctl (git-fixes).\n- drm: lcdif: Wait for vblank before disabling DMA (git-fixes).\n- drm: Remove unused header in drm_dumb_buffers.c (git-fixes).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- erspan: Initialize options_len before referencing options (bsc#1274727).\n- ethtool: rss: fix hkey leak when indir_size is 0 (git-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_cursor() (git-fixes).\n- fbdev: core: Fix pointer desynchronization in fb_io_read() (git-fixes).\n- fbdev: kyro: Validate overlay viewport coordinates (git-fixes).\n- fbdev: omapfb: panel-dsi-cm: initialize lock before registering display (git-fixes).\n- fbdev: tdfxfb: fix PCI enable cleanup with pcim_enable_device() (git-fixes).\n- fbdev: uvesafb: unregister connector callback on init failure (git-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Avoid IDR updates while cleaning channels (git-fixes).\n- firmware: arm_scmi: Clean up channels on setup failure (git-fixes).\n- firmware: arm_scmi: Drop handle on protocol bind failures (git-fixes).\n- firmware: arm_scmi: Fix requested device removal race (git-fixes).\n- firmware: arm_scmi: Free transport channel on IDR failure (git-fixes).\n- firmware: arm_scmi: Protect device request lookup with RCU (git-fixes).\n- firmware: arm_scmi: Publish channel state before callbacks (git-fixes).\n- firmware: arm_scmi: Quiesce notifications before teardown (git-fixes).\n- firmware: arm_scmi: Rate-limit queue-full warnings in IRQ context (git-fixes).\n- firmware: arm_scmi: Reject out of range DT protocol IDs (git-fixes).\n- firmware: arm_scmi: Roll back partial protocol table registration (git-fixes).\n- firmware: arm_scmi: Unregister device notifier before IDR teardown (git-fixes).\n- firmware: arm_scmi: Unrequest devices if driver registration fails (git-fixes).\n- firmware: arm_scmi: Unwind P2A receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Unwind TX receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Use channel ID for transport teardown (git-fixes).\n- firmware_loader: do not queue completed sysfs fallback requests (git-fixes).\n- fpga: altera-cvp: Avoid out-of-bounds read in trailing byte write (git-fixes).\n- fpga: dfl: fme: add error handling (git-fixes).\n- fpga: stratix10-soc: Fix SVC mailbox handling during reconfiguration (git-fixes).\n- fuse: fix race between interrupt and resend (git-fixes).\n- gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind (git-fixes).\n- gpu: host1x: Avoid stack over-read in debug output helpers (git-fixes).\n- gpu: host1x: Fix offset calculation in trace_write_gather (git-fixes).\n- gpu: host1x: Fix use-after-free in host1x_bo_clear_cached_mappings (stable-fixes).\n- HID: asus: fix missing hid_is_usb() check (git-fixes).\n- HID: asus: simplify RGB init sequence (stable-fixes).\n- HID: bpf: serialize device reference release in struct_ops destroy path (git-fixes).\n- HID: core: fix number/pointer type confusion on long items (git-fixes).\n- HID: core: fix OOB read of field-\u003eusage in hid_set_field() (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: hyperv: validate initial device info bounds (git-fixes).\n- HID: i2c-hid: Fix \"(null)\" output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: goodix: Disable VDD on VDDIO enable failure (git-fixes).\n- HID: lg4ff: validate report length before fixed offsets (git-fixes).\n- HID: logitech-dj: Fix maxfield check in DJ short report validation (git-fixes).\n- HID: logitech-dj: fix wrong detection of bad DJ_SHORT output report (git-fixes).\n- HID: logitech-dj: Prevent REPORT_ID_DJ_SHORT related user initiated OOB write (stable-fixes).\n- HID: logitech-dj: Standardise hid_report_enum variable nomenclature (stable-fixes).\n- HID: magicmouse: do not keep a stale msc-\u003einput if no input is claimed (git-fixes).\n- HID: magicmouse: fix battery reporting for Bluetooth Magic Trackpad USB-C (git-fixes).\n- HID: magicmouse: Prevent out-of-bounds (OOB) read during DOUBLE_REPORT_ID (stable-fixes).\n- HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() (git-fixes).\n- HID: magicmouse: re-enable multitouch after reset-resume (git-fixes).\n- HID: mcp2221: validate report size in mcp2221_raw_event() (git-fixes).\n- HID: multitouch: reclassify HTIX5288 to WIN_8_FORCE_MULTI_INPUT_NSMU (git-fixes).\n- HID: nintendo: Fix imu_timestamp_us double increment per report (git-fixes).\n- HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler() (git-fixes).\n- HID: nintendo: register input device after capabilities are set (git-fixes).\n- HID: nintendo: stop device IO before hid_hw_stop on probe failure (git-fixes).\n- HID: picolcd: clamp eeprom debugfs read to bytes actually received (git-fixes).\n- HID: pidff: Rework pidff_set_time() to fix warnings (stable-fixes).\n- HID: pidff: Use ARRAY_SIZE macro instead of sizeof (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: roccat: bound device-supplied profile index (git-fixes).\n- HID: roccat: free buffered reports when destroying device (git-fixes).\n- HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature (git-fixes).\n- HID: sensor: custom: Fix field sysfs group cleanup on failure (git-fixes).\n- HID: sensor: custom: Fix use-after-free in enable_sensor (git-fixes).\n- HID: synchronize input before cleaning up a failed probe (git-fixes).\n- HID: tmff: Use 64-bit arithmetic for force feedback scaling (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- hwmon: (ads7828) Fix external VREF regulator handling (git-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (chipcap2) fix channels in humidity alarm notifications (git-fixes).\n- hwmon: (coretemp) Fix core_data leak on CPUs without PTS (git-fixes).\n- hwmon: (corsair-cpro) Create debugfs entries after hwmon registration (git-fixes).\n- hwmon: (corsair-cpro) Remove debugfs entries when probe fails (git-fixes).\n- hwmon: (corsair-psu) fix possible out-of-bounds access on missing string termination (git-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (ina2xx) Add support for has_alerts configuration flag (stable-fixes).\n- hwmon: (ina2xx) Add support for INA234 (stable-fixes).\n- hwmon: (ina2xx) Add support for INA260 (stable-fixes).\n- hwmon: (ina2xx) Fix various overflow issues (git-fixes).\n- hwmon: (ina2xx) Make it easier to add more devices (stable-fixes).\n- hwmon: (ina2xx) Shift INA234 shunt and current registers (stable-fixes).\n- hwmon: (ina226) Add support for SY24655 (stable-fixes).\n- hwmon: (ltc4282) Avoid overflow in maximum power calculation (git-fixes).\n- hwmon: (ltc4282) Clamp negative current limits (git-fixes).\n- hwmon: (ltc4282) Fix parsing adi,current-limit-sense-microvolt (git-fixes).\n- hwmon: (ltc4282) Make sure clk_init_data is fully initialized (git-fixes).\n- hwmon: (max6621) fix negative temperature offset and crit readings (git-fixes).\n- hwmon: (max6621) fix temperature clamp range (git-fixes).\n- hwmon: (nzxt-smart2) Check return value of init_device() in probe (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficient calculations (git-fixes).\n- hwmon: Switch back to struct platform_driver::remove() (stable-fixes).\n- hwrng: ks-sa - Fix runtime PM cleanup on registration failure (git-fixes).\n- hwrng: omap - Fix probe error path cleanup (git-fixes).\n- hwtracing: hisi_ptt: Propagate DMA reset timeout in trace_start() (git-fixes).\n- i2c: core: fix debugfs UAF on adapter removal (git-fixes).\n- i2c: imx: fix locked bus on SMBus block-read of 0 (atomic) (git-fixes).\n- i2c: imx: separate atomic, dma and non-dma use case (stable-fixes).\n- i2c: mux: demux-pinctrl: fix OF node leak on kstrdup failure (git-fixes).\n- i2c: mux: Fix channel node leak on adapter add failure (git-fixes).\n- i2c: ocores: Disable clock on failed resume (git-fixes).\n- i3c: dw: avoid shift-out-of-bounds when DAA assigns no devices (git-fixes).\n- i3c: dw: rename \"pclk\" to \"apb\" to match dt-binding (git-fixes).\n- i3c: master: Fix device_register() error path (git-fixes).\n- i3c: master: Fix info leak and UAF in device unregister path (git-fixes).\n- i3c: master: Fix potential UAF in i3c_device_uevent() (git-fixes).\n- i3c: master: svc: bound IBI payload to the requested max_payload_len (git-fixes).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: dmard09: Implement IIO_CHAN_INFO_SCALE (git-fixes).\n- iio: adc: max34408: add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- iio: adc: pac1921: fix wrong channel used in trigger handler read (git-fixes).\n- iio: buffer: Fix potential use-after-free in anonymous buffer release (git-fixes).\n- iio: buffer: Make IIO DMA fence release RCU-safe (git-fixes).\n- iio: buffer: Tie IIO dma fence lock lifetime to the fence (git-fixes).\n- iio: chemical: atlas-sensor: fix PM reference leak in buffer postenable (git-fixes).\n- iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF (git-fixes).\n- iio: chemical: sgp30: Handle IAQ thread creation failure (git-fixes).\n- iio: dac: m62332: Fix regulator reference count imbalance (git-fixes).\n- iio: gyro: mpu3050: fix sign of raw angular velocity readings (git-fixes).\n- iio: light: cm32181: return zero after writing calibscale (git-fixes).\n- iio: light: gp2ap002: Disable regulators on resume failure (git-fixes).\n- iio: light: gp2ap002: re-enable irq if runtime suspend fails (git-fixes).\n- iio: light: isl29028: return zero in write_raw() on success (git-fixes).\n- iio: light: ltrf216a: fix runtime PM reference leak in error path (git-fixes).\n- iio: light: opt4001: Fix incompatible pointer type passed to div_u64_rem() (git-fixes).\n- iio: light: opt4001: Fix power down clearing bits of the wrong register (git-fixes).\n- iio: light: opt4001: Fix reversed GENMASK() arguments in fault count mask (git-fixes).\n- iio: light: opt4001: Reject integration times with a non-zero seconds part (git-fixes).\n- iio: light: tsl2583: return zero in write_raw() on success (git-fixes).\n- iio: light: tsl2772: fix ALS calibscale readback (git-fixes).\n- iio: orientation: hid-sensor-rotation: Avoid race between callback setup and device exposure (git-fixes).\n- iio: pressure: dps310: fix NULL pointer dereference on ACPI probe (git-fixes).\n- iio: pressure: mpl115: Fix runtime PM cleanup (git-fixes).\n- iio: srf04: fix pm_runtime handling on probe error path (git-fixes).\n- iio: temperature: hid-sensor-temperature: switch to non-devm iio_device_register() (git-fixes).\n- Input: atkbd - skip deactivate for HONOR ZQC-P (git-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Book Pro 14's internal keyboard (stable-fixes).\n- Input: cs40l50-vibra - validate custom data from user space (git-fixes).\n- Input: evdev - fix information leak in evdev_pass_values() (stable-fixes).\n- Input: evdev - sanitize event type index when fetching event masks (stable-fixes).\n- Input: focaltech - fix array out-of-bounds in focaltech_process_rel_packet (git-fixes).\n- Input: focaltech - use signed coordinates to prevent underflow (git-fixes).\n- Input: hynitron_cstxxx - validate touch count and finger IDs (git-fixes).\n- Input: iforce - validate input packet lengths (stable-fixes).\n- Input: iqs5xx - validate firmware record destination span (git-fixes).\n- Input: mms114 - fix Y-resolution configuration (git-fixes).\n- Input: psxpad-spi - set driver data before use (git-fixes).\n- Input: reject inhibit and uninhibit requests on unregistering devices (git-fixes).\n- Input: sur40 - fix input device registration ordering (stable-fixes).\n- Input: sur40 - fix V4L error path cleanup (stable-fixes).\n- Input: synaptics-rmi4 - block s_input when F54 queue is busy (git-fixes).\n- Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer (git-fixes).\n- Input: synaptics-rmi4 - fix F55 transmitter electrode count typo (git-fixes).\n- Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue (git-fixes).\n- Input: synaptics-rmi4 - zero report size on F54 work error (git-fixes).\n- Input: xpad - add support for ZENAIM LEVERLESS (stable-fixes).\n- interconnect: Fix use after free in icc_get() and of_icc_get_by_index() (git-fixes).\n- io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (git-fixes).\n- io_uring/net: Avoid msghdr on op_connect/op_bind async data (git-fixes).\n- iommu/arm-smmu-v3: Manage teardown with devm (stable-fixes).\n- ip_tunnel: Use ip_tunnel_info() helper instead of 'info + 1' (bsc#1274727).\n- ipmi: ipmb: validate write message length (git-fixes).\n- ipmi: si: Fix NULL pointer dereference after failed registration (git-fixes).\n- KVM: arm64: Ensure FFA ranges are page aligned (git-fixes).\n- KVM: arm64: Fix bounds checking in do_ffa_mem_reclaim() (git-fixes).\n- KVM: arm64: Fix sign-extension of MMIO loads (git-fixes).\n- KVM: arm64: vgic: Reset in_kernel on private IRQ allocation failure (git-fixes).\n- KVM: arm64: Zero out the stack initialized data in the FFA handler (git-fixes).\n- KVM: nSVM: Always inject a #GP if mapping VMCB12 fails on nested VMRUN (git-fixes).\n- KVM: nSVM: Remove a user-triggerable WARN on nested_svm_load_cr3() succeeding (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (git-fixes).\n- KVM: PPC: Book3S HV: Add support for compat CPU capabilities for KVM on PowerNV (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Validate arch_compat against host compatibility mode (bsc#1263864 ltc#217835).\n- KVM: PPC: Document KVM_PPC_GET_COMPAT_CAPS ioctl (bsc#1263864 ltc#217835).\n- KVM: PPC: Introduce KVM_CAP_PPC_COMPAT_CAPS and wire up ioctl (bsc#1263864 ltc#217835).\n- KVM: SEV: Use to_kvm_sev_info() for fetching kvm_sev_info struct (git-fixes).\n- KVM: SVM: Add support to initialize SEV/SNP functionality in KVM (bsc#1279887).\n- KVM: SVM: Explicitly mark vmcb01 dirty after modifying VMCB intercepts (git-fixes).\n- KVM: SVM: Serialize accesses to the owner and mirror list with separate lock (git-fixes).\n- KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active (git-fixes).\n- KVM: TDX: Account all non-transient page allocations for per-TD structures (git-fixes).\n- KVM: TDX: Fix x2APIC MSR handling in tdx_has_emulated_msr() (git-fixes).\n- KVM: VMX: Don't register posted interrupt wakeup handler if alloc_kvm_area() fails (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86/mmu: Recover TDP MMU NX huge pages using MMU read lock (bsc#1271050).\n- KVM: x86/mmu: Rename kvm_tdp_mmu_zap_sp() to better indicate its purpose (bsc#1271050).\n- KVM: x86/mmu: Track possible NX huge pages separately for TDP vs. Shadow MMU (bsc#1271050).\n- KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears because it was cleared from the PIC (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears when Xen emulation is enabled (git-fixes).\n- KVM: x86: Fix array_index_nospec() protection in kvm_vcpu_ioctl_x86_set_mce() (git-fixes).\n- KVM: x86: Fix emulated CPUID features being applied to wrong sub-leaf (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- leds: pca9532: Fix inverted GPIO output polarity (git-fixes).\n- leds: pca9532: Fix phantom device registration on missing hardware (git-fixes).\n- lib/string: fix memchr_inv() for large ranges (git-fixes).\n- lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen() (git-fixes).\n- mac802154: fix data race and NULL deref on local-\u003eassoc_dev (git-fixes).\n- mac802154: fix netdev use-after-free in beacon worker (git-fixes).\n- mac802154: fix use-after-free of sdata via queued RX frames (git-fixes).\n- mailbox: pcc: Fix command timeout due to missed interrupt (git-fixes).\n- mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler (git-fixes).\n- mailbox: qcom-cpucp: handle NULL data in send_data callback (git-fixes).\n- mailbox: qcom-ipcc: fix duplicate channel allocation across holes (git-fixes).\n- mailbox: rockchip: disable pclk on probe failure and unbind (git-fixes).\n- maple_tree: fix argument name in header (git-fixes).\n- md/raid1: create serial pool adding rdev to array with serialize_policy=1 (bsc#1272261).\n- media: airspy: Return queued buffers on start_streaming() failure (git-fixes).\n- media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref (git-fixes).\n- media: amphion: Remove obsolete frame_count check in venc_start_session (git-fixes).\n- media: bcm2835-unicam: Fix asc leaked in error/remove path (git-fixes).\n- media: cec-pin: Fix event FIFO ordering (git-fixes).\n- media: cec: disable delayed work before freeing an interrupted transmit (git-fixes).\n- media: cec: extron-da-hd-4k-plus: add sanity check (git-fixes).\n- media: cec: meson: ao-cec-g12a: name the CEC core regmap to avoid debugfs clash (git-fixes).\n- media: cec: Serialize exclusive follower delivery (git-fixes).\n- media: cec: stm32: prevent out-of-bounds write on RX overflow (git-fixes).\n- media: cedrus: clean up media device on probe failure (git-fixes).\n- media: cedrus: fix memory leak in cedrus_init_ctrls() (git-fixes).\n- media: chips-media: wave5: Guard bit depth check with initial_info_obtained (git-fixes).\n- media: chips-media: wave5: Move src_buf Removal to finish_encode (git-fixes).\n- media: cobalt: Avoid freeing ALSA private data twice (git-fixes).\n- media: cx231xx: fix devres lifetime (git-fixes).\n- media: cx231xx: reject geometry changes while the VBI queue is busy (git-fixes).\n- media: cx23885: add ioremap return check and cleanup (git-fixes).\n- media: cx23885: cancel NetUP CI work before teardown (git-fixes).\n- media: em28xx: defer audio-only extension registration (git-fixes).\n- media: em28xx: fix use-after-free of dev_next-\u003edevlist on disconnect (git-fixes).\n- media: go7007: defer the ALSA v4l2 put until card release (git-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: i2c: alvium: fix critical pointer access in alvium_ctrl_init (git-fixes).\n- media: i2c: alvium: Fix: Correct name of register in alvium_set_ctrl_auto_exposure (git-fixes).\n- media: i2c: imx219: Rename VTS to FRM_LENGTH (stable-fixes).\n- media: i2c: imx415: Return test pattern write errors (git-fixes).\n- media: i2c: ov02a10: fix endpoint parsing use-after-free (git-fixes).\n- media: i2c: ov7740: fix use-after-destroy in remove (git-fixes).\n- media: i2c: rdacm21: Fix missing media_entity_cleanup() (git-fixes).\n- media: imx219: Fix maximum frame length in lines (git-fixes).\n- media: intel/ipu6: fix async notifier cleanup leak on parse error (git-fixes).\n- media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges (git-fixes).\n- media: ipu6: Do not free aux device pdata after init (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_HAUPPAUGE_NEW keymap define (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_RC5_TV keymap define (git-fixes).\n- media: mc-entity: Add missing kerneldoc (git-fixes).\n- media: mediatek: vcodec: bound AV1 tile-start copy to the array capacity (git-fixes).\n- media: meson: vdec: Fix memory leak in error path of vdec_open (git-fixes).\n- media: meson: vdec: fix NULL pointer deref in vdec_try_fmt_common (git-fixes).\n- media: msi2500: Return queued buffers on start_streaming() failure (git-fixes).\n- media: nuvoton: npcm-video: fix error handling in npcm_video_init() (git-fixes).\n- media: nuvoton: npcm-video: fix memory leaks in probe and remove (git-fixes).\n- media: nxp: imx8-isi: Add missing v4l2_subdev_cleanup() in crossbar and pipe (git-fixes).\n- media: nxp: imx8-isi: Clean up already-initialized pipes on probe failure (git-fixes).\n- media: nxp: imx8-isi: Correct color map between V4L2 and ISI (git-fixes).\n- media: nxp: imx8-isi: Fix missing v4l2_subdev_cleanup() in pipe init error path (git-fixes).\n- media: nxp: imx8-isi: Fix potential out-of-bounds issues (git-fixes).\n- media: nxp: imx8-isi: Fix scale factor calculation for hardware rounding (git-fixes).\n- media: nxp: imx8-isi: Fix stream ID validation bypass in crossbar routing (git-fixes).\n- media: nxp: imx8-isi: Use BIT_ULL() for 64-bit stream masks (git-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: platform: mtk-mdp3: fix NULL deref on failed SCP lookup (git-fixes).\n- media: platform: mtk-mdp3: Fix SCP device refcounting (git-fixes).\n- media: pwc: Drain fill_buf on start_streaming() failure (git-fixes).\n- media: pwc: Return queued buffers on start_streaming() failure (git-fixes).\n- media: qcom: camss: Fix RDI streaming for CSID GEN2 (git-fixes).\n- media: radio-si476x: Unregister v4l2_device on probe failure (git-fixes).\n- media: rc: sunxi-cir: Unregister rc device on probe failure (git-fixes).\n- media: rtl2832: fix use-after-free in rtl2832_remove() (git-fixes).\n- media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: Return queued buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak (git-fixes).\n- media: s2255: bound JPEG frame size before copying into the buffer (git-fixes).\n- media: s2255: check firmware size before reading trailing marker (git-fixes).\n- media: saa7134: Fix a possible memory leak in saa7134_video_init1 (git-fixes).\n- media: saa7164: fix cleanup on resource allocation failure (git-fixes).\n- media: stm32: dcmi: unregister notifier on probe failure (git-fixes).\n- media: sun4i-csi: Return queued buffers on start_streaming() failure (git-fixes).\n- media: tda18250: fix possible integer overflow (git-fixes).\n- media: tegra-video: vi: fix invalid u32 return value in format lookup (git-fixes).\n- media: usbtv: keep device alive while ALSA card exists (git-fixes).\n- media: v4l2-async: avoid deleting unlinked ASC entry on link error (git-fixes).\n- media: v4l2-async: Unregister sub-device if asc_list is empty (git-fixes).\n- media: v4l2-ctrls-request: add NULL check in v4l2_ctrl_request_complete() (git-fixes).\n- media: v4l2-ctrls: Allow unknown HDR10 white point and luminance (git-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-fwnode: Fix fwnode leak in v4l2_fwnode_parse_link (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: v4l2-subdev: Fail {enable,disable}_streams and s_streaming nicely (git-fixes).\n- media: venus: fix payload size calculation in parse_raw_formats() (git-fixes).\n- media: venus: fix payload size returned by parse_caps() and parse_alloc_mode() (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer (git-fixes).\n- media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity (git-fixes).\n- media: vicodec: fix out-of-bounds write in FWHT encoder (git-fixes).\n- media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure (git-fixes).\n- media: vimc: fix pixel format lookup in enum_framesizes (git-fixes).\n- media: vivid: add vivid_update_reduced_fps() (git-fixes).\n- media: vivid: check for vb2_is_busy() when toggling caps (git-fixes).\n- media: vivid: fix cleanup bugs in vivid_init() (git-fixes).\n- media: zoran: Avoid freeing a registered video_device twice (git-fixes).\n- mei: pull kvfree out of spinlock (git-fixes).\n- mfd: iqs62x: Reject zero-length firmware records (git-fixes).\n- mfd: rave-sp: validate received frame payload lengths (git-fixes).\n- mfd: sm501: Fix potential memory leaks during remove (git-fixes).\n- misc: bcm-vk: Use acquire/release for msgq_inited (git-fixes).\n- misc: fastrpc: fix channel ctx ref leak when session alloc fails (git-fixes).\n- misc: fastrpc: fix memory leak in fastrpc_channel_ctx_free (git-fixes).\n- misc: fastrpc: Remove buffer from list prior to unmap operation (git-fixes).\n- misc: fastrpc: take fl-\u003elock when moving mmaps on interrupted invoke (git-fixes).\n- misc: nsm: bound the device-reported response length (git-fixes).\n- misc: rtsx: add missing write register handling (git-fixes).\n- misc: sgi-gru: remove interrupt-context page-table walks (git-fixes).\n- misc: vmc_vmci: Fix potential memory leak in vmci_event_subscribe() (git-fixes).\n- mkspec-dtb: Move DTS prefix into package list.\n- mkspec-dtb: Move provides-obsoletes to package list.\n- mkspec-dtb: Put per-architecture package lists into a hash.\n- mkspec-dtb: re-indent.\n- mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition (git-fixes).\n- mmc: omap_hsmmc: fix busy_timeout overflow in ns conversion on 32-bit (git-fixes).\n- mmc: sdhci: unmap the bounce buffer before device release (git-fixes).\n- mmc: via-sdmmc: stop card-detect handling on probe failure (git-fixes).\n- mtd: afs: validate v2 image info bounds (git-fixes).\n- mtd: fix double free and WARN_ON in add_mtd_device() error paths (git-fixes).\n- mtd: mtdoops: free page bitmap when the backing MTD is removed (git-fixes).\n- mtd: mtdswap: Avoid freeing registered blktrans device twice (git-fixes).\n- mtd: mtdswap: remove debugfs stats file on teardown (git-fixes).\n- mtd: nand: mtk-ecc: stop on ECC idle timeouts (git-fixes).\n- mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() (git-fixes).\n- mtd: rawnand: validate ONFI extended parameter page sections (git-fixes).\n- mtd: spinand: fix direct mapping creation sizes (stable-fixes).\n- mtd: spinand: repeat reading in regular mode if continuous reading fails (stable-fixes).\n- mtd: spinand: try a regular dirmap if creating a dirmap for continuous reading fails (stable-fixes).\n- mtd: ubi: Release device reference on busy detach (git-fixes).\n- mtd: ubi: skip programming unused bits in ubi headers (stable-fixes).\n- net: Add options as a flexible array to struct ip_tunnel_info (bsc#1274727).\n- net: mana: Add debug knob to skip TX timeout recovery reset (git-fixes).\n- net: mana: Add handler for sriov configure (bsc#1272756).\n- net: mana: Cap MSI-X vectors to the device MSI-X table size (git-fixes).\n- net: mana: Extend RX CQE coalescing up to 8 packets (git-fixes).\n- net: mana: Fall back to scattered pages for GDMA queues (git-fixes).\n- net: mana: force full-page RX buffers via ethtool private flag (bsc#1269792).\n- net: mana: refactor mana_get_strings() and mana_get_sset_count() to use switch (bsc#1269792).\n- net: mana: Route ring-buffer access through offset-based helpers (git-fixes).\n- net: tap: set skb-\u003edev before parsing virtio net header in tap_get_user_xdp() (git-fixes bsc#1274550).\n- net: thunderbolt: Count delivered packets in rx_packets and rx_bytes (git-fixes).\n- net: thunderbolt: Mark the connection down when bringing it up fails (git-fixes).\n- net: thunderbolt: Release the Rx HopID that was handed out on mismatch (git-fixes).\n- net: thunderbolt: Tear down DMA paths before stopping the rings (git-fixes).\n- net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup() (git-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: ipheth: fix carrier_work UAF on disconnect (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (git-fixes).\n- nfc: digital: clamp SENSF_RES length to the destination buffer (git-fixes).\n- nfc: digital: Do not dump a NULL response in command completion (git-fixes).\n- nfc: fdp: bound the device-reported read length and fix an skb leak (git-fixes).\n- nfc: llcp: avoid userspace overflow on invalid optlen (git-fixes).\n- nfc: llcp: bound SNL TLV parsing to the skb and add length checks (git-fixes).\n- nfc: llcp: bound the connect_sn TLV walk to the skb (git-fixes).\n- nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (git-fixes).\n- nfc: llcp: read llcp_sock-\u003elocal under the socket lock in getsockopt (git-fixes).\n- nfc: llcp: reject PDUs shorter than the LLCP header (git-fixes).\n- nfc: microread: validate target discovery payload lengths (git-fixes).\n- nfc: nci: fix double completion race in nci_data_exchange_complete (git-fixes).\n- nfc: nci: fix out-of-bounds write in nci_target_auto_activated() (git-fixes).\n- nfc: nci: fix uninit-value in the RF discover/activated NTF handlers (git-fixes).\n- nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing (git-fixes).\n- nfc: nci: free destination parameters when closing a connection (git-fixes).\n- nfc: pn533: hold a reference to the request skb during send_frame (git-fixes).\n- nfc: pn533: purge fragmented skbs during cleanup (git-fixes).\n- nfc: st21nfca: validate ATR_REQ length against the received frame (git-fixes).\n- nouveau/gem: reserve the bo in the info ioctl around the vma lookup (git-fixes).\n- nvme-tcp: fix usage of page_frag_cache (bsc#1267882).\n- nvmet-rdma: fix queue leak when connect backlog is exceeded (git-fixes).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- PCI/ASPM: Use pcie_capability_clear_and_set_word() for ASPM disable/restore (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (git-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (git-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI: Add ACS quirk for Pericom PI7C9X2G608 switches [12d8:2608] (git-fixes).\n- PCI: hv: Set irq_retrigger callback for the Hyper-V PCI MSI irqchip (git-fixes).\n- PCI: j721e: Fix incorrect max_lanes for J7200 (git-fixes).\n- PCI: meson: Fix GPIO state while requesting PERST# (git-fixes).\n- PCI: plda: Fix IRQ domain leaks in the error paths of plda_init_interrupts() (git-fixes).\n- PCI: plda: Fix use-after-free of event IRQs during teardown (git-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- pinctrl: bcm2835: Don't remove an unregistered GPIO chip (git-fixes).\n- pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip (git-fixes).\n- pinctrl: rockchip: Reset the pin count when recalculating SoC data (git-fixes).\n- platform/chrome: cros_ec_debugfs: Clean up console log on probe failure (git-fixes).\n- platform/chrome: cros_ec_debugfs: Unregister panic notifier (git-fixes).\n- platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count (git-fixes).\n- platform/chrome: sensorhub: Bound the EC-reported sensor number (git-fixes).\n- platform/chrome: sensorhub: Fix dropped timestamp events and log spam (git-fixes).\n- platform/chrome: sensorhub: Fix memory overread in ring handler (git-fixes).\n- platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL (git-fixes).\n- platform/surface: acpi-notify: Check ACPI companion before use (git-fixes).\n- platform/x86/amd/hsmp: Reject negative power cap writes in hwmon (git-fixes).\n- platform/x86: asus-wmi: fix resource leaks on probe failure (git-fixes).\n- platform/x86: dell-privacy: Fix race condition (git-fixes).\n- platform/x86: dell-wmi-base: Fix resource leak on module load failure (git-fixes).\n- platform/x86: dell-wmi-sysman: Don't hex dump attribute security buffer (git-fixes).\n- platform/x86: dell-wmi-sysman: Fix instance ID bounds (git-fixes).\n- platform/x86: hp-bioscfg: accept reduced ACPI packages from older HP BIOS (git-fixes).\n- platform/x86: hp-bioscfg: advance elem past consumed array elements (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store() (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read on empty password write (git-fixes).\n- platform/x86: hp-bioscfg: fix new_password_store() overwriting current_password (git-fixes).\n- platform/x86: hp-bioscfg: fix off-by-one write in hp_get_string_from_buffer() (git-fixes).\n- platform/x86: hp-bioscfg: fix ORD_LIST_ELEMENTS never being parsed (git-fixes).\n- platform/x86: hp-bioscfg: fix password encoding bounds check (git-fixes).\n- platform/x86: hp-bioscfg: warn on element type mismatch instead of failing (git-fixes).\n- platform/x86: ishtp_eclite: Fix ACPI device reference leak in probe error path (git-fixes).\n- platform/x86: ISST: Add a NULL check for sst_inst (git-fixes).\n- platform/x86: ISST: Just allow 2 bits for SST feature enable (git-fixes).\n- platform/x86: ISST: Return error during profile addition (git-fixes).\n- platform/x86: ISST: Use PP level enable mask (git-fixes).\n- platform/x86: ISST: Validate level in perf mask ioctls (git-fixes).\n- platform/x86: ISST: Validate logical CPU id and clos id (git-fixes).\n- platform/x86: ISST: Validate parameter for core power state (git-fixes).\n- platform/x86: ISST: Validate parameter for frequency and priority (git-fixes).\n- platform/x86: ISST: Validate socket ID in clos_assoc ioctl (git-fixes).\n- PM: hibernate: Fix memory leak in snapshot_write_next() error path (git-fixes).\n- PM: sleep: Fix off-by-one in wakelocks number limit check (git-fixes).\n- power: supply: bd99954: Drop bad register fields (git-fixes).\n- power: supply: bq27xxx: bq27z561: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq28z610: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq27520g4: fix REG_TTES address (git-fixes).\n- power: supply: bq256xx: drain usb_work before freeing the charger (git-fixes).\n- power: supply: bq24257: fix use-after-free on remove (git-fixes).\n- power: supply: bq25890: Fix power_supply reference leak (git-fixes).\n- power: supply: charger-manager: register regulators before exposing sysfs (git-fixes).\n- power: supply: cros_usbpd-charger: bound the EC-reported port count (git-fixes).\n- power: supply: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS (git-fixes).\n- power: supply: isp1704_charger: cancel work on remove (git-fixes).\n- power: supply: lp8727: fix use-after-free in lp8727_release_irq() (git-fixes).\n- power: supply: lp8788-charger: fix use-after-free on remove (git-fixes).\n- power: supply: max17040: drop incorrect I2C functionality check (git-fixes).\n- power: supply: max17040: propagate register read errors (git-fixes).\n- power: supply: max17040: synchronize work cancellation on suspend (git-fixes).\n- power: supply: qcom_battmgr: terminate the strings from firmware (git-fixes).\n- power: supply: rt9455: quiesce delayed work before teardown (git-fixes).\n- power: supply: sbs-battery: Use a per-device serial number buffer (git-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: twl4030_charger: cancel workers via devm (git-fixes).\n- power: supply: ucs1002: fix use-after-free on remove (git-fixes).\n- powercap: intel_rapl_tpmi: Handle PMU registration failure during probe (git-fixes).\n- powerpc/dt_cpu_ftrs: Set CPU_FTR_P11_PVR for Power11 and later processors (bsc#1263864 ltc#217835).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/pseries: Ensure vpa,slb_shadow \u0026 dtl are unregistered during crash (bsc#1271256).\n- powerpc/pseries: lparcfg - fix kbuf[] underflow (bsc#1274753 ltc#221289 bsc#1274754 ltc#221288 bsc#1274752\n  ltc#221290).\n- powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak (bsc#1274751 ltc#221105 bsc#1274750 ltc#221106).\n- powerpc/pseries: pci - logic bug (bsc#1274749 ltc#221282 bsc#1274755 ltc#221284 bsc#1274756 ltc#221283).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in non-uapi headers (bsc#1263864 ltc#217835).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in uapi headers (bsc#1263864 ltc#217835).\n- ppdev: prevent overflow when setting port timeout (git-fixes).\n- rapidio/tsi721: prevent a bad dereference in tsi721_db_dpc() (git-fixes).\n- rapidio: clear mport-\u003enet when rio_add_net() fails (git-fixes).\n- rapidio: mport_cdev: fix use-after-free in dma_req_free() (git-fixes).\n- RDMA/bnxt_re: Avoid displaying the kernel pointer (git-fixes).\n- RDMA/bnxt_re: Proper rollback if the ioremap fails (git-fixes).\n- RDMA/irdma: Remove redundant legacy_mode checks (git-fixes).\n- RDMA/mana_ib: drain QP references after partial table insertion (git-fixes).\n- RDMA/mana_ib: unify QP lookup table (git-fixes).\n- RDMA/mlx5: Fix integer overflow of user QP buffer size (git-fixes).\n- regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving dangling of_node pointer (git-fixes).\n- regulator: core: use system_freezable_wq for init complete work (git-fixes).\n- regulator: max8998_pmic_dt_parse_pdata: of_node_put on reg_np after ownership transferred to rdata (git-fixes).\n- regulator: qcom-refgen: correct the regulator type to CURRENT (git-fixes).\n- regulator: qcom-rpmh: Fix PMIC5 BOB bypass mode handling (git-fixes).\n- remoteproc: qcom: Fix glink-\u003enode reference leak in qcom_add_glink_subdev (git-fixes).\n- remoteproc: qcom_q6v5_adsp: Fix reference leak for device node (git-fixes).\n- remoteproc: scp: Fix device reference leak on failed lookup (git-fixes).\n- Revert \"drm/amdgpu: fix aperture mapping leak\" (git-fixes).\n- Revert \"media: v4l2-dev: fix error handling in __video_register_device()\" (git-fixes).\n- Revert \"net: thunderbolt: Enable end-to-end flow control also in transmit\" (git-fixes).\n- Revert \"thermal/drivers/hwmon: Cleanup coding style a bit\" (stable-fixes).\n- Revert \"wifi: mt76: Disable napi when removing device\" (git-fixes).\n- rpmsg: core: Fix incorrect return value documentation (git-fixes).\n- rpmsg: glink: smem: order FIFO read after availability check (git-fixes).\n- rtc: gamecube: check return value of devm_rtc_register_device() (git-fixes).\n- rtc: pcf8563: fix clock provider leak on unbind (git-fixes).\n- rtc: pcf85363: Add error checking to regmap calls in probe() (git-fixes).\n- rtc: rzn1: Disable alarm interrupt before reprogramming alarm registers (git-fixes).\n- rtc: rzn1: Fix weekday underflow when alarm crosses month boundary (git-fixes).\n- rtc: zynqmp: Return optional clock lookup errors (git-fixes).\n- s390/pkey: Check length in pkey_pckmo handler implementation (bsc#1270266).\n- s390/pkey: Check length in PKEY_VERIFYPROTK ioctl (bsc#1270267).\n- sched/psi: Create the psimon kthread outside of cgroup_mutex (bsc#1269134).\n- scsi: fnic: Abort timed-out NVMe LS requests (bsc#1236344).\n- scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths (bsc#1236344).\n- scsi: fnic: Add FDLS role handling for NVMe initiators (bsc#1236344).\n- scsi: fnic: Add the NVMe/FC transport path (bsc#1236344).\n- scsi: fnic: Advertise NVMe initiator service parameters (bsc#1236344).\n- scsi: fnic: Bump up version number (bsc#1236344).\n- scsi: fnic: Decode firmware role configuration (bsc#1236344).\n- scsi: fnic: Do not use GFP_ZERO for mempools (bsc#1236344).\n- scsi: fnic: Expose NVMe transport state in debugfs (bsc#1236344).\n- scsi: fnic: Handle NVMe LS frames in FDLS (bsc#1236344).\n- scsi: fnic: Make debug logging protocol independent (bsc#1236344).\n- scsi: fnic: Make fnic_queuecommand() easier to analyze (bsc#1236344).\n- scsi: fnic: Refactor in_remove flag and call to fnic_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Remove a useless struct mempool forward declaration (bsc#1236344).\n- scsi: fnic: Rename fnic_scsi_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Route completions and resets by initiator role (bsc#1236344).\n- scsi: fnic: Self-assignment of intr_time_type has no effect (bsc#1236344).\n- scsi: fnic: Send NVMe LS requests through FDLS (bsc#1236344).\n- scsi: fnic: Switch to use %ptSp (bsc#1236344).\n- scsi: fnic: Track NVMe transport statistics (bsc#1236344).\n- scsi: fnic: Use fnic_num for non-SCSI identifiers (bsc#1236344).\n- scsi: fnic: Use mempool for receive frames (bsc#1236344).\n- scsi: qla2xxx: Add support to report MPI FW state (bsc#1275737).\n- scsi: qla2xxx: Declare qla2xxx_mqueuecommand() static (bsc#1275737).\n- scsi: qla2xxx: Use nr_cpu_ids instead of NR_CPUS for qp_cpu_map allocation (bsc#1275737).\n- scsi: storvsc: Support manual scans for all Hyper-V targets (git-fixes).\n- sctp: avoid auth_enable sysctl UAF during netns teardown (git-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- serial: 8250_dma: Clear stale RX state on shutdown (git-fixes).\n- serial: amba-pl011: unprepare console clock on unregister (git-fixes).\n- serial: core: clear freed pointers on uart_register_driver() failure (git-fixes).\n- serial: imx: serialize imx_uart_ports lifetime (git-fixes).\n- serial: ma35d1: Fix OF node reference leaks in console init (git-fixes).\n- serial: qcom-geni: do not advance stale DMA completions (git-fixes).\n- serial: qcom-geni: fix TX DMA buffer flush (git-fixes).\n- serial: sc16is7xx: enable THRI before filling TX FIFO (git-fixes).\n- serial: sc16is7xx: rename EFR mutex with generic name (stable-fixes).\n- serial: sc16is7xx: use guards for simple mutex locks (stable-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb/client: handle overlapping allocated ranges in fallocate (bsc#1274902).\n- smb: client: harden POSIX SID length parsing (bsc#1273557).\n- smb: client: require net admin for CIFS SWN netlink (bsc#1273966).\n- smb: client: resolve SWN tcon from live registrations (bsc#1273872).\n- soc: fsl: qe: check platform_driver_register() in qe_ic_of_init() (git-fixes).\n- soc: qcom: rpmh-rsc: manage PM notifiers with devres (git-fixes).\n- soc: samsung: exynos-pmu: fix of_node refcount leak in exynos_get_pmu_regmap() (git-fixes).\n- software node: Fix software_node_get_reference_args() with index -1 (git-fixes).\n- soundwire: qcom: Fix port exhaustion check in stream_alloc_ports (git-fixes).\n- speakup: keyhelp: guard letter_offsets possible out-of-range indexing (git-fixes).\n- spi: bcm63xx-hsspi: disable clocks on resume failure (git-fixes).\n- spi: bcm63xx: disable clock on resume failure (git-fixes).\n- spi: bcmbca-hsspi: disable clocks on resume failure (git-fixes).\n- spi: davinci: switch to managed controller allocation (git-fixes).\n- spi: Fix DMA mapping ownership on partial map failure (git-fixes).\n- spi: img-spfi: don't disable runtime PM on DMA deferred probe (git-fixes).\n- spi: oc-tiny: switch to managed controller allocation (git-fixes).\n- spi: spi-cadence: enable SPI_CONTROLLER_MUST_TX (git-fixes).\n- spi: spi-cadence: Move TX FIFO full busy-wait into FIFO (git-fixes).\n- spi: spi-cadence: supports transmission with bits_per_word of 16 and 32 (stable-fixes).\n- spi: spi-fsl-dspi: Avoid setup_accel logic for DMA transfers (stable-fixes).\n- spi: sprd-adi: Fix probe succeeding without registering the controller (git-fixes).\n- staging: fbtft: Use sysfs_emit_at() to print to sysfs file (git-fixes).\n- staging: media: tegra-video: fix of_node_put() on VIP parse errors (git-fixes).\n- staging: media: tegra-video: vi: fix probe failure on skipped last port (git-fixes).\n- staging: octeon: add missing tasklet_kill in cvm_oct_tx_shutdown (git-fixes).\n- staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init() (git-fixes).\n- staging: rtl8723bs: fix missing shared-key auth challenge length check (git-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() (git-fixes).\n- staging: rtl8723bs: fix OOB read in WMM_param_handler() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: use kfree_sensitive() for key material (git-fixes).\n- staging: rtl8723bs: validate monitor transmit frame lengths (git-fixes).\n- staging: sm750fb: Add missing Kconfig dependency (git-fixes).\n- staging: sm750fb: gate dualview dataflow using g_dualview (git-fixes).\n- thermal/drivers/imx: Disable clock on runtime resume failure (git-fixes).\n- thermal/drivers/qoriq: Disable clock on resume failure (git-fixes).\n- thermal/drivers/rcar: Fix error checking in probe() (git-fixes).\n- thermal: intel: int3400: clean up ODVP on probe failures (git-fixes).\n- thermal: sysfs: switch to use scnprintf() to suppress truncation warning (git-fixes).\n- thunderbolt: Bound the DROM dual link port number before indexing sw-\u003eports (git-fixes).\n- thunderbolt: Fix bandwidth group reservation indexing (git-fixes).\n- thunderbolt: icm: Preserve USB4 proxy data-valid bit (git-fixes).\n- tlclk: if sscanf() fails, fall back to 0, not random value (git-fixes).\n- tpm: st33zp24: Return zero on status read failure (git-fixes).\n- tpm: st33zp24: Validate locality read result (git-fixes).\n- tpm: tpm_i2c_nuvoton: disable IRQ on wait timeout (git-fixes).\n- tty: clear cdev pointer after cdev_add() failure (git-fixes).\n- tty: hvc: restrict HVC_DCC to ARMv6+ and ARM64 (git-fixes).\n- tty: skip cdev_del() when no cdev is registered (git-fixes).\n- uio: Fix stale info pointer in failed registration path (git-fixes).\n- usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm() (git-fixes).\n- usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect (git-fixes).\n- usb: atm: usbatm: fix invalid ci_range initialization (git-fixes).\n- USB: c67x00: fix use-after-free in c67x00_add_iso_urb() (git-fixes).\n- usb: cdnsp: fix incorrect endian conversions for APB timeout register (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (git-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: core: sysfs: add lock to bos_descriptors_read() (stable-fixes).\n- usb: dwc2: add missing @remotewakeup kernel-doc parameter (git-fixes).\n- usb: dwc2: gadget: Exit partial power down state when changing USB pull-up (git-fixes).\n- usb: dwc3: clear forceRM when issuing EndTransfer (git-fixes).\n- usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: fix UAF when probe runs concurrent to dyn ID removal (git-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed (git-fixes).\n- usb: gadget: configfs: fix out-of-bounds read of qw_sign (git-fixes).\n- usb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths (git-fixes).\n- usb: gadget: f_fs: Prevent deadlock during ep0 read loop (git-fixes).\n- usb: gadget: f_midi: initialize work in f_midi_alloc() (git-fixes).\n- usb: gadget: f_ncm: Use unsigned int for ndp_index (git-fixes).\n- usb: gadget: f_tcm: fix deadlock in usbg_make_tpg() (git-fixes).\n- usb: gadget: f_uac1_legacy: remove broken string configfs attributes (git-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- USB: gadget: fsl-udc: fix dev_printk() device (git-fixes).\n- usb: gadget: midi2: Fix null-pointer dereference in f_midi2_free_ep_reqs (git-fixes).\n- usb: gadget: midi2: remove default configfs groups on teardown (git-fixes).\n- usb: gadget: pch_udc: remove excess kernel-doc member for registered (git-fixes).\n- usb: gadget: r8a66597: avoid double free of ep0_req in probe error path (git-fixes).\n- usb: gadget: snps_udc_plat: clean up PHY on probe deferral (git-fixes).\n- usb: gadget: u_audio: Fix use-after-free on sound card disconnect (git-fixes).\n- usb: gadget: uac: validate rate list length before storing (git-fixes).\n- USB: gadget: Use str_enable_disable-like helpers (stable-fixes).\n- usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and uvc_function_unbind() (git-fixes).\n- usb: ljca: bound bank_num in ljca_enumerate_gpio() (git-fixes).\n- usb: mtu3: allow system suspend during active gadget connection (git-fixes).\n- usb: musb: omap2430: clean up probe error handling (stable-fixes).\n- usb: musb: omap2430: Do not put borrowed of_node in probe (git-fixes).\n- usb: musb: omap2430: Fix use-after-free in omap2430_probe() (git-fixes).\n- USB: phy: fsl-usb: fix missing static keywords (git-fixes).\n- usb: renesas_usbhs: Fix power-off ordering on unbind (git-fixes).\n- USB: serial: digi_acceleport: fix port registration order (git-fixes).\n- USB: serial: ftdi_sio: add support for E+H FXA291 (stable-fixes).\n- USB: serial: option: add TDTECH MT5710-CN (stable-fixes).\n- USB: serial: option: fix slab OOB read in interrupt URB callback (git-fixes).\n- USB: serial: spcp8x5: drop broken carrier detect support (git-fixes).\n- USB: storage: add NO_ATA_1X quirk for Longmai USB Key (stable-fixes).\n- usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop (git-fixes).\n- usb: typec: qcom-pmic-typec: drain cc_debounce_dwork if port_start() fails (git-fixes).\n- usb: typec: qcom-pmic: cancel reset_work on stop (git-fixes).\n- usb: typec: tcpci: pass correct rx_type to tcpm_pd_receive() (git-fixes).\n- usb: typec: thunderbolt: Disable work before freeing tbt on remove (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: unregister debugfs entries on teardown (git-fixes).\n- usb: typec: ucsi: use UCSI_TIMEOUT_MS for sync command completion (git-fixes).\n- usb: usbfs: fix use-after-free of usb_device in usbdev_release() (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: xhci: Handle USB3 port events when there is one roothub (git-fixes).\n- vfs: Add a sysctl for automated deletion of dentry (bsc#1240890 bsc#1276586).\n- vt: add permission check for KDSKBMETA ioctl (stable-fixes).\n- vt: stabilize tty reference in kbd_keycode with tty_port_tty_get (stable-fixes).\n- w1: ds28e17: reject an oversize length on an I2C block read (git-fixes).\n- w1: ds2482: Fix signedness bug in ds2482_w1_triplet() (git-fixes).\n- watchdog: bd96801_wdt: Fix timeout for enabled WDG (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath6kl: avoid buffer overreads in WMI event handlers (git-fixes).\n- wifi: ath6kl: clamp assoc request/response lengths before subtracting IE offsets (git-fixes).\n- wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump (git-fixes).\n- wifi: ath11k: Avoid buffer overread in ath11k_wmi_tlv_op_rx() (git-fixes).\n- wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate (git-fixes).\n- wifi: ath11k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath12k: Avoid buffer overread in ath12k_wmi_op_rx() (git-fixes).\n- wifi: ath12k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: brcmfmac: Fix memory leak in brcmf_sdio_read_control() (git-fixes).\n- wifi: brcmfmac: fix P2P action frame handling without device vif (git-fixes).\n- wifi: brcmfmac: initialize SDIO data work before cleanup (git-fixes).\n- wifi: cfg80211: bound element ID read when checking non-inheritance (git-fixes).\n- wifi: cfg80211: cancel sched scan results work on unregister (git-fixes).\n- wifi: cfg80211: derive S1G beacon TSF from S1G fields (git-fixes).\n- wifi: cfg80211: reject unsupported PMSR FTM location requests (git-fixes).\n- wifi: cfg80211: validate PMSR FTM preamble range (git-fixes).\n- wifi: cfg80211: validate PMSR measurement type data (git-fixes).\n- wifi: ipw2100: fix potential memory leak in ipw2100_pci_init_one() (git-fixes).\n- wifi: iwlwifi: fix counter type in iwl_fwrt_dump_error_logs (git-fixes).\n- wifi: iwlwifi: guard against division by zero in iwl_dbg_tlv_alloc_fragments (git-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mei: pass correct argument to function (git-fixes).\n- wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser (git-fixes).\n- wifi: libertas: fix memory leak in helper_firmware_cb() (git-fixes).\n- wifi: mac80211: disconnect on CSA to channel 0 (git-fixes).\n- wifi: mac80211: fix fils_discovery double free on alloc failure (git-fixes).\n- wifi: mac80211: fix per-STA profile length in cross-link CSA parsing (git-fixes).\n- wifi: mac80211: fix unsol_bcast_probe_resp double free on alloc failure (git-fixes).\n- wifi: mac80211: free AP_VLAN bc_buf SKBs outside IRQ lock (git-fixes).\n- wifi: mac80211: send TWT teardown to peer after setup TX failure (git-fixes).\n- wifi: mac80211: skip default WMM setup for AP_VLAN links (git-fixes).\n- wifi: mac80211: skip unused probe response countdown offsets (git-fixes).\n- wifi: mt76: check txfree done event on the WED hw path (git-fixes).\n- wifi: mt76: fix 4th chain ACK RSSI bitmask in sta_poll (git-fixes).\n- wifi: mt76: fix ER-SU 106-tone RU check in RX rate decode (git-fixes).\n- wifi: mt76: fix HE DCM max-RU capability encoding (git-fixes).\n- wifi: mt76: fix non-AQL packet accounting for MLO stations (git-fixes).\n- wifi: mt76: fix stranded frames in mt76_txq_schedule_pending (git-fixes).\n- wifi: mt76: mt76x02: do not WARN on invalid rx descriptor length (git-fixes).\n- wifi: mt76: mt792x: Fix memory leak in SDIO TX path (git-fixes).\n- wifi: mt76: mt792x: fix use-after-free in mt76_rx_poll_complete (git-fixes).\n- wifi: mt76: mt7615: avoid waiting for mac work under the mt76 mutex (git-fixes).\n- wifi: mt76: mt7915: avoid nss underflow in mt7915_mcu_get_sta_nss (git-fixes).\n- wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear (git-fixes).\n- wifi: mt76: mt7915: fix double hif2 init on the non-WED path (git-fixes).\n- wifi: mt76: mt7915: fix ext PHY use-after-free on register error path (git-fixes).\n- wifi: mt76: mt7915: fix net_fill_forward_path for non-DBDC mt7986 (git-fixes).\n- wifi: mt76: mt7915: poll the correct SLP CTRL register for the second adie (git-fixes).\n- wifi: mt76: mt7915: release hif2 reference on probe IRQ failure (git-fixes).\n- wifi: mt76: mt7915: unlink TWT flow if the MCU rejects the agreement (git-fixes).\n- wifi: mt76: mt7915: unwind state on add_interface failure (git-fixes).\n- wifi: mt76: mt7915: use little-endian for bss_info_ra wire fields (git-fixes).\n- wifi: mt76: mt7915: write RX header translation bit to the correct register (git-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: mt7921: validate CLC firmware records (git-fixes).\n- wifi: mt76: mt7925: ensure tx headroom in usb_sdio_tx_prepare_skb (git-fixes).\n- wifi: mt76: mt7925: fix msg len mismatch between driver and firmware (git-fixes).\n- wifi: mt76: mt7925: update clc before setting sar power table (git-fixes).\n- wifi: mt76: mt7996: bound TLV walk in mt7996_mcu_get_chip_config (git-fixes).\n- wifi: mt76: mt7996: don't report a zero TX bitrate (git-fixes).\n- wifi: mt76: mt7996: fix capability of EHT-MCS 15 in MRU (git-fixes).\n- wifi: mt76: mt7996: fix reg addr remap when addr is 0 (git-fixes).\n- wifi: mt76: mt7996: reserve space for the CSA-abort countdown TLV (git-fixes).\n- wifi: mt76: mt7996: set MT76_MCU_RESET before waking MCU waiters on full reset (git-fixes).\n- wifi: mt76: mt7996: validate RX band_idx before dereferencing phys (git-fixes).\n- wifi: mt76: only consume the WO drop bit on WED v2 devices (git-fixes).\n- wifi: mt76: report data NSS for STBC frames in RX rate decode (git-fixes).\n- wifi: mwifiex: Detach sync cmd buffer on interrupted wait (git-fixes).\n- wifi: nl80211: free RNR data on MBSSID mismatch (git-fixes).\n- wifi: nl80211: validate nested MBSSID IE blobs (git-fixes).\n- wifi: p54: validate RX frame length in p54_rx_eeprom_readback() (git-fixes).\n- wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop (git-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtlwifi: pci: fix error path in rtl_pci_probe() (git-fixes).\n- wifi: rtlwifi: rtl8192du: check QoS TID before indexing tids (git-fixes).\n- wifi: rtlwifi: rtl8192du: Fix possible memory leak in rtl92du_init_sw_vars() (git-fixes).\n- wifi: rtw88: Fix potential memory leak in rtw_txq_push_skb() (git-fixes).\n- wifi: rtw88: pci: fix resource leak on failed NAPI setup (git-fixes).\n- wifi: rtw89: fix HE extended capability length check (git-fixes).\n- wifi: zd1211rw: reject secondary interfaces to prevent conflicts (git-fixes).\n- x86/virt/tdx: Print TDX module version during init (git-fixes).\n- x86/virt/tdx: Retrieve TDX module version (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_alloc_driver() failure (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_register_driver() failure (git-fixes).\n- xhci: fix lost bounce buffers on TDs spanning several ring segments (git-fixes).\n","status":"published","published":"2026-09-22T15:26:20Z","modified":"2026-09-25T18:23:13.136758616Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"SUSE-SU-2026:23881-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-68214: timers: Fix NULL function pointer race in timer_shutdown_sync() (bsc#1255225).\n- CVE-2025-68358: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() (bsc#1255531).\n- CVE-2025-68780: sched/deadline: only set free_cpus for online runqueues (bsc#1256671).\n- CVE-2025-71075: scsi: aic94xx: fix use-after-free in device removal path (bsc#1256629).\n- CVE-2026-23113: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (bsc#1258278).\n- CVE-2026-23306: scsi: pm8001: Fix use-after-free in pm8001_queue_command() (bsc#1260501).\n- CVE-2026-23348: cxl/mem: Clarify @host for devm_cxl_add_nvdimm() (bsc#1260577).\n- CVE-2026-31418: netfilter: ipset: drop logically empty buckets in mtype_del (bsc#1262073).\n- CVE-2026-31530: cxl/port: Fix use after free of parent_port in cxl_detach_ep() (bsc#1262756).\n- CVE-2026-31531: ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop() (bsc#1263004).\n- CVE-2026-43116: netfilter: ctnetlink: ensure safe access to master conntrack (bsc#1264619).\n- CVE-2026-43125: dlm: validate length in dlm_search_rsb_tree (bsc#1264541).\n- CVE-2026-43163: md/bitmap: fix GPF in write_page caused by resize race (bsc#1264335).\n- CVE-2026-43239: smb: client: prevent races in -\u003equery_interfaces() (bsc#1264444).\n- CVE-2026-43271: md-cluster: fix NULL pointer dereference in process_metadata_update (bsc#1264587).\n- CVE-2026-43299: btrfs: do not ASSERT() when the fs flips RO inside btrfs_repair_io_failure() (bsc#1264851).\n- CVE-2026-43331: x86/kexec: Disable KCOV instrumentation after load_segments() (bsc#1265132).\n- CVE-2026-43355: iio: light: bh1780: fix PM runtime leak on error path (bsc#1265036).\n- CVE-2026-43363: x86/apic: Disable x2apic on resume if the kernel expects so (bsc#1265068).\n- CVE-2026-43416: powerpc, perf: Check that current-\u003emm is alive before getting user callchain (bsc#1265121).\n- CVE-2026-43439: cgroup: fix race between task migration and iteration (bsc#1265141).\n- CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807).\n- CVE-2026-45860: netfilter: nf_conncount: increase the connection clean up limit to 64 (bsc#1266710).\n- CVE-2026-45897: netfilter: nft_counter: serialize reset with spinlock (bsc#1266897).\n- CVE-2026-45968: cpuidle: Skip governor when only one idle state is available (bsc#1267023).\n- CVE-2026-46007: hwmon: (powerz) Avoid cacheline sharing for DMA buffer (bsc#1267586).\n- CVE-2026-46070: md/raid5: validate payload size before accessing journal metadata (bsc#1267501).\n- CVE-2026-46107: dm-thin: fix metadata refcount underflow (bsc#1267612).\n- CVE-2026-46115: block: add pgmap check to biovec_phys_mergeable (bsc#1266874).\n- CVE-2026-46133: RDMA/rxe: Reject unknown opcodes before ICRC processing (bsc#1266928).\n- CVE-2026-46135: nvmet-tcp: remove redundant calls to nvmet_tcp_fatal_error() (bsc#1267373).\n- CVE-2026-46195: smb: client: validate dacloffset before building DACL pointers (bsc#1266860).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-52920: netfilter: xt_policy: fix strict mode inbound policy matching (bsc#1269013).\n- CVE-2026-52928: af_unix: Reject SIOCATMARK on non-stream sockets (bsc#1269010).\n- CVE-2026-52929: sctp: stream: fully roll back denied add-stream state (bsc#1269004).\n- CVE-2026-52935: xfrm: espintcp: do not reuse an in-progress partial send (bsc#1268979).\n- CVE-2026-52939: net/rds: fix NULL deref in rds_ib_send_cqe_handler() on masked atomic completion (bsc#1268972).\n- CVE-2026-52946: fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling (bsc#1269113).\n- CVE-2026-52977: futex: Prevent lockup in requeue-PI during signal/ timeout wakeup (bsc#1269242).\n- CVE-2026-52990: fsnotify: fix inode reference leak in fsnotify_recalc_mask() (bsc#1269108).\n- CVE-2026-52991: sched/psi: fix race between file release and pressure write (bsc#1269134).\n- CVE-2026-52994: vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting (bsc#1269126).\n- CVE-2026-53001: netfilter: xtables: restrict several matches to inet family (bsc#1269114).\n- CVE-2026-53031: bpf: Validate node_id in arena_alloc_pages() (bsc#1269380).\n- CVE-2026-53033: bpf, sockmap: Take state lock for af_unix iter (bsc#1269388).\n- CVE-2026-53034: bpf, sockmap: Fix af_unix null-ptr-deref in proto update (bsc#1269140).\n- CVE-2026-53048: gfs2: prevent NULL pointer dereference during unmount (bsc#1269162).\n- CVE-2026-53059: dm log: fix out-of-bounds write due to region_count overflow (bsc#1269655).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53076: bpf: Fix OOB in pcpu_init_value (bsc#1269695).\n- CVE-2026-53077: net/rds: Restrict use of RDS/IB to the initial network namespace (bsc#1269412).\n- CVE-2026-53089: bpf: Fix use-after-free in offloaded map/prog info fill (bsc#1269783).\n- CVE-2026-53091: net: account for encap headers in qdisc pkt len (bsc#1269530).\n- CVE-2026-53092: bpf: Fix linked reg delta tracking when src_reg == dst_reg (bsc#1269528).\n- CVE-2026-53094: bpf: Fix stale offload-\u003eprog pointer after constant blinding (bsc#1269965).\n- CVE-2026-53096: bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path (bsc#1269969).\n- CVE-2026-53109: powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy (bsc#1269417).\n- CVE-2026-53110: s390: always declare expoline thunks (bsc#1269985).\n- CVE-2026-53111: bpf: test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap (bsc#1269167).\n- CVE-2026-53114: perf: Extend the bit width of the arch-specific flag (bsc#1269999).\n- CVE-2026-53126: blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() (bsc#1269635).\n- CVE-2026-53129: fs/mbcache: cancel shrink work before destroying the cache (bsc#1269633).\n- CVE-2026-53142: drm/xe/display: fix oops in suspend/shutdown without display (bsc#1269402).\n- CVE-2026-53154: mm/hugetlb: restore reservation on error in hugetlb folio copy paths (bsc#1269665).\n- CVE-2026-53163: locking/rtmutex: Skip remove_waiter() when waiter is not enqueued (bsc#1269306).\n- CVE-2026-53180: timers/migration: Fix livelock in tmigr_handle_remote_up() (bsc#1269888).\n- CVE-2026-53207: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison (bsc#1269590).\n- CVE-2026-53219: netfilter: x_tables: avoid leaking percpu counter pointers (bsc#1269686).\n- CVE-2026-53220: netfilter: revalidate bridge ports (bsc#1269381).\n- CVE-2026-53223: net: guard timestamp cmsgs to real error queue skbs (bsc#1269301).\n- CVE-2026-53228: ipv6: sit: reload inner IPv6 header after GSO offloads (bsc#1269256).\n- CVE-2026-53238: netlabel: validate unlabeled address and mask attribute lengths (bsc#1269774).\n- CVE-2026-53264: net/sched: act_api: use RCU with deferred freeing for action lifecycle (bsc#1269238).\n- CVE-2026-53269: netfilter: synproxy: add mutex to guard hook reference counting (bsc#1269579).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53291: ALSA: hda/conexant: Fix missing error check for jack detection (bsc#1269697).\n- CVE-2026-53309: ocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison (bsc#1269815).\n- CVE-2026-53330: drm/amd/display: Fix out-of-bounds read in (bsc#1270090).\n- CVE-2026-53336: nvmem: layouts: onie-tlv: fix hang on unknown types (bsc#1270108).\n- CVE-2026-53337: net: bonding: fix NULL pointer dereference in bond_do_ioctl() (bsc#1270251).\n- CVE-2026-53341: fhandle: fix UAF due to unlocked -\u003emnt_ns read in may_decode_fh() (bsc#1270139).\n- CVE-2026-53353: hsr: Remove WARN_ONCE() in hsr_addr_is_self() (bsc#1270111).\n- CVE-2026-53365: vsock/virtio: fix zerocopy completion for multi-skb sends (bsc#1271365).\n- CVE-2026-63801: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (bsc#1272230).\n- CVE-2026-63803: hdlc_ppp: sync per-proto timers before freeing hdlc state (bsc#1272284).\n- CVE-2026-63804: gfs2: fix use-after-free in gfs2_qd_dealloc (bsc#1272287).\n- CVE-2026-63808: exfat: fix potential use-after-free in exfat_find_dir_entry() (bsc#1272260).\n- CVE-2026-63810: block: Avoid mounting the bdev pseudo-filesystem in userspace (bsc#1272297).\n- CVE-2026-63823: keys: Pin request_key_auth payload in instantiate paths (bsc#1272182).\n- CVE-2026-63828: apparmor: mediate the implicit connect of TCP fast open sendmsg (bsc#1272175).\n- CVE-2026-63860: RDMA/core: Prefer NLA_NUL_STRING (bsc#1272429).\n- CVE-2026-63865: bpf: Drop task_to_inode and inet_conn_established from lsm sleepable hooks (bsc#1272486).\n- CVE-2026-63868: net: garp: fix unsigned integer underflow in garp_pdu_parse_attr (bsc#1272497).\n- CVE-2026-63879: drm/amdgpu: fix amdgpu_hmm_range_get_pages (bsc#1272569).\n- CVE-2026-63887: scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf (bsc#1272385).\n- CVE-2026-63888: scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd() (bsc#1272390).\n- CVE-2026-63889: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (bsc#1272423).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63891: thunderbolt: property: Cap recursion depth in __tb_property_parse_dir() (bsc#1272641).\n- CVE-2026-63901: USB: serial: digi_acceleport: fix memory corruption with small endpoints (bsc#1272501).\n- CVE-2026-63917: ip6: vti: Use ip6_tnl.net in vti6_changelink() (bsc#1272904).\n- CVE-2026-63918: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname (bsc#1272905).\n- CVE-2026-63920: ipv6: validate extension header length before copying to cmsg (bsc#1272877).\n- CVE-2026-63921: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate() (bsc#1272918).\n- CVE-2026-63922,CVE-2026-63924: ipv6: exthdrs: refresh nh after handling HAO option (bsc#1272855).\n- CVE-2026-63925: macsec: fix replay protection at XPN lower-PN wrap (bsc#1273008).\n- CVE-2026-63926: bpf: sockmap: fix tail fragment offset in bpf_msg_push_data (bsc#1273019).\n- CVE-2026-63941: KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor (bsc#1272869).\n- CVE-2026-63969: ipv6: fix possible infinite loop in rt6_fill_node() (bsc#1272484).\n- CVE-2026-63970: vsock/virtio: bind uarg before filling zerocopy skb (bsc#1272673).\n- CVE-2026-63984: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() (bsc#1272865).\n- CVE-2026-63985: ethtool: eeprom: add more safeties to EEPROM Netlink fallback (bsc#1272963).\n- CVE-2026-63986: ethtool: tsinfo: don't pass ERR_PTR to genlmsg_cancel on prepare failure (bsc#1272969).\n- CVE-2026-63987: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (bsc#1272971).\n- CVE-2026-63990: bonding: refuse to enslave CAN devices (bsc#1273027).\n- CVE-2026-63992: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() (bsc#1272868).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-63995: ethtool: cmis: validate start_cmd_payload_size from module (bsc#1273033).\n- CVE-2026-63996: ethtool: cmis: require exact CDB reply length (bsc#1273032).\n- CVE-2026-63997: ethtool: module: avoid leaking a netdev ref on module flash errors (bsc#1273036).\n- CVE-2026-63998: ethtool: module: call ethnl_ops_complete() on module flash errors (bsc#1273037).\n- CVE-2026-63999: ethtool: rss: fix indir_table and hkey leak on get_rxfh failure (bsc#1273038).\n- CVE-2026-64000: net: hsr: fix potential OOB access in supervision frame handling (bsc#1273030).\n- CVE-2026-64002: ipv4: free net-\u003eipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (bsc#1273774).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64004: net/iucv: fix locking in .getsockopt (bsc#1273804).\n- CVE-2026-64005: net/smc: Do not re-initialize smc hashtables (bsc#1273831).\n- CVE-2026-64006: netfilter: nf_tables: fix dst corruption in same register operation (bsc#1273834).\n- CVE-2026-64007: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (bsc#1273105).\n- CVE-2026-64017: blk-mq: pop cached request if it is usable (bsc#1273770).\n- CVE-2026-64024: tcp: fix stale per-CPU tcp_tw_isn leak enabling ISN prediction (bsc#1273107).\n- CVE-2026-64033: RDMA/rtrs: Fix use-after-free in path file creation cleanup (bsc#1273134).\n- CVE-2026-64047: net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring (bsc#1273060).\n- CVE-2026-64048: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot (bsc#1273484).\n- CVE-2026-64052: block: bio-integrity: Fix null-ptr-deref in bio_integrity_map_user() (bsc#1272983).\n- CVE-2026-64053: block: don't overwrite bip_vcnt in bio_integrity_copy_user() (bsc#1272985).\n- CVE-2026-64054: net: shaper: reject duplicate leaves in GROUP request (bsc#1272894).\n- CVE-2026-64055: net: ethernet: cortina: Carry over frag counter (bsc#1272893).\n- CVE-2026-64056: net: ethernet: cortina: Make RX SKB per-port (bsc#1272502).\n- CVE-2026-64071: nvme-pci: fix use-after-free in nvme_free_host_mem() (bsc#1273486).\n- CVE-2026-64073: irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT (bsc#1273490).\n- CVE-2026-64088: batman-adv: tt: fix negative tt_buff_len (bsc#1273463).\n- CVE-2026-64089: batman-adv: tt: fix negative last_changeset_len (bsc#1272513).\n- CVE-2026-64093: batman-adv: tp_meter: directly shut down timer on cleanup (bsc#1273461).\n- CVE-2026-64099: drm/v3d: Fix use-after-free of CPU job query arrays on error path (bsc#1273465).\n- CVE-2026-64102: RDMA/siw: Reject MPA FPDU length underflow before signed receive math (bsc#1272516).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64109: af_unix: Fix UAF read of tail-\u003elen in unix_stream_data_wait() (bsc#1273748).\n- CVE-2026-64111: lsm: hold cred_guard_mutex for lsm_set_self_attr() (bsc#1273740).\n- CVE-2026-64112: rbd: eliminate a race in lock_dwork draining on unmap (bsc#1273741).\n- CVE-2026-64113: ixgbevf: fix use-after-free in VEPA multicast source pruning (bsc#1272262).\n- CVE-2026-64114: ipv4: raw: reject IP_HDRINCL packets with ihl \u003c 5 (bsc#1273742).\n- CVE-2026-64115: vsock/vmci: fix UAF when peer resets connection during handshake (bsc#1273745).\n- CVE-2026-64118: qed: fix double free in qed_cxt_tables_alloc() (bsc#1273749).\n- CVE-2026-64119: l2tp: use list_del_rcu in l2tp_session_unhash (bsc#1273746).\n- CVE-2026-64121: net: ifb: report ethtool stats over num_tx_queues (bsc#1273743).\n- CVE-2026-64125: net: bcmgenet: keep RBUF EEE/PM disabled (bsc#1272346).\n- CVE-2026-64131: mm/memory: fix spurious warning when unmapping device-private/exclusive pages (bsc#1274063).\n- CVE-2026-64146: erofs: fix metabuf leak in inode xattr initialization (bsc#1273681).\n- CVE-2026-64147: pds_core: fix debugfs_lookup dentry leak and error handling (bsc#1273119).\n- CVE-2026-64148: pds_core: fix error handling in pdsc_devcmd_wait (bsc#1273956).\n- CVE-2026-64162: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (bsc#1272366).\n- CVE-2026-64164: btrfs: tracepoints: fix sleep while in atomic context in btrfs_sync_file() (bsc#1273957).\n- CVE-2026-64177: phonet/pep: disable BH around forwarded sk_receive_skb() (bsc#1272148).\n- CVE-2026-64179: net: wwan: iosm: fix potential memory leaks in ipc_imem_init() (bsc#1272149).\n- CVE-2026-64180: mm/memory_hotplug: fix memory block reference leak on remove (bsc#1273679).\n- CVE-2026-64184: mm/damon/sysfs-schemes: call missing mem_cgroup_iter_break() (bsc#1272199).\n- CVE-2026-64185: sysfs: don't remove existing directory on update failure (bsc#1272200).\n- CVE-2026-64190: net: team: fix NULL pointer dereference in team_xmit during mode change (bsc#1272210).\n- CVE-2026-64192: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized (bsc#1272213).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64214: powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise()\n  (bsc#1272799).\n- CVE-2026-64217: netfs: Fix overrun check in netfs_extract_user_iter() (bsc#1272798).\n- CVE-2026-64222: octeontx2-pf: avoid double free of pool-\u003estack on AQ init failure (bsc#1272788).\n- CVE-2026-64224: octeontx2-pf: fix double free in rvu_rep_rsrc_init() (bsc#1272804).\n- CVE-2026-64225: octeontx2-af: CGX: add bounds check to cgx_speed_mbps index (bsc#1272786).\n- CVE-2026-64232: block: recompute nr_integrity_segments in blk_insert_cloned_request (bsc#1272791).\n- CVE-2026-64239: mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() (bsc#1273898).\n- CVE-2026-64244: drivers/base/memory: set mem-\u003ealtmap after successful device registration (bsc#1273812).\n- CVE-2026-64253: kernel/fork: clear PF_BLOCK_TS in copy_process() (bsc#1273904).\n- CVE-2026-64256: xfs: don't wrap around quota ids in dqiterate (bsc#1273271).\n- CVE-2026-64265: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req (bsc#1273947).\n- CVE-2026-64268: RDMA/siw: bound Read Response placement to the RREAD length (bsc#1273276).\n- CVE-2026-64269: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg (bsc#1273280).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64286: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU (bsc#1274058).\n- CVE-2026-64287: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU (bsc#1273325).\n- CVE-2026-64294: mm: do file ownership checks with the proper mount idmap (bsc#1273525).\n- CVE-2026-64296: exfat: bound uniname advance in exfat_find_dir_entry() (bsc#1273975).\n- CVE-2026-64298: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (bsc#1273550).\n- CVE-2026-64300: perf/aux: Fix page UAF in map_range() (bsc#1273852).\n- CVE-2026-64307: crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG) (bsc#1273567).\n- CVE-2026-64315: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1274028).\n- CVE-2026-64316: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1273598).\n- CVE-2026-64317: isofs: bound Rock Ridge symlink components to the SL record (bsc#1273936).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64321: nvme: target: rdma: fix ndev refcount leak on queue connect (bsc#1273864).\n- CVE-2026-64322: udf: validate sparing table length as an entry count, not a byte count (bsc#1273958).\n- CVE-2026-64323: udf: validate VAT header length against the VAT inode size (bsc#1273305).\n- CVE-2026-64326: block: skip sync_blockdev() on surprise removal in bdev_mark_dead() (bsc#1273312).\n- CVE-2026-64327: usb: gadget: f_fs: Initialize epfile-\u003ein early to fix endpoint direction checks (bsc#1273283).\n- CVE-2026-64354: bpf: Validate BTF repeated field counts before expansion (bsc#1274060).\n- CVE-2026-64355: bpf: Reject fragmented frames in devmap (bsc#1273422).\n- CVE-2026-64364: HID: multitouch: fix out-of-bounds bit access on mt_io_flags (bsc#1273495).\n- CVE-2026-64368: mm/slab: do not limit zeroing to orig_size when only red zoning is enabled (bsc#1273997).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64375: proc: protect ptrace_may_access() with exec_update_lock (FD links) (bsc#1273868).\n- CVE-2026-64378: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (bsc#1273603).\n- CVE-2026-64381: smb: client: Fix next buffer leak in receive_encrypted_standard() (bsc#1273860).\n- CVE-2026-64382: smb: client: fix double-free in SMB2_open() replay (bsc#1273291).\n- CVE-2026-64383: smb: client: fix double-free in SMB2_flush() replay (bsc#1273426).\n- CVE-2026-64384: smb: client: fix change notify replay double-free (bsc#1274541).\n- CVE-2026-64385: smb: client: fix double-free in SMB2_ioctl() replay (bsc#1274539).\n- CVE-2026-64386: smb: client: fix query_info() replay double-free (bsc#1274543).\n- CVE-2026-64387: smb: client: fix query directory replay double-free (bsc#1274545).\n- CVE-2026-64411: netfilter: ebtables: terminate table name before find_table_lock() (bsc#1274077).\n- CVE-2026-64412: netfilter: ebtables: module names must be null-terminated (bsc#1273780).\n- CVE-2026-64415: mm/swap: add cond_resched() in swap_reclaim_full_clusters to prevent softlockup (bsc#1273317).\n- CVE-2026-64416: mm: swap_cgroup: fix NULL deref in lookup_swap_cgroup_id on swapless host (bsc#1273286).\n- CVE-2026-64423: ipv4: igmp: remove multicast group from hash table on device destruction (bsc#1274274).\n- CVE-2026-64434: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref (bsc#1273880).\n- CVE-2026-64436: net: af_key: initialize alg_key_len for IPComp states (bsc#1274277).\n- CVE-2026-64450: tipc: fix out-of-bounds read in broadcast Gap ACK blocks (bsc#1273523).\n- CVE-2026-64452: 6lowpan: fix NHC entry use-after-free on error path (bsc#1273460).\n- CVE-2026-64458: mm/damon/ops-common: handle extreme intervals in damon_hot_score() (bsc#1273788).\n- CVE-2026-64463: usb: typec: tcpci_rt1711h: unregister TCPCI port with devres (bsc#1273273).\n- CVE-2026-64472: vfio/mlx5: Fix racy bitfields and tighten struct layout (bsc#1274075).\n- CVE-2026-64477: x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled (bsc#1274264).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64518: tcp: Fix out-of-bounds access for twsk in tcp_ao_established_key() (bsc#1273524).\n- CVE-2026-64519: NFSD: Fix infinite loop in layout state revocation (bsc#1274252).\n- CVE-2026-64526: ethtool: tsconfig: fix missing ethnl_ops_complete() (bsc#1274052).\n- CVE-2026-64534: nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error (bsc#1273803).\n- CVE-2026-64535: nvmet-tcp: Fix potential UAF when ddgst mismatch (bsc#1273809).\n- CVE-2026-64537: bridge: cfm: reject invalid CCM interval at configuration time (bsc#1273289).\n- CVE-2026-64538: ipv6: Fix null-ptr-deref in fib6_nh_mtu_change() (bsc#1273335).\n- CVE-2026-64541: net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket (bsc#1273303).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64543: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() (bsc#1273311).\n- CVE-2026-64545: net, bpf: check master for NULL in xdp_master_redirect() (bsc#1273318).\n- CVE-2026-64548: bpf, sockmap: reject overflowing copy + len in bpf_msg_push_data() (bsc#1273337).\n- CVE-2026-64551: sctp: validate STALE_COOKIE cause length before reading staleness (bsc#1273813).\n- CVE-2026-64552: virtio-net: fix len check in receive_big() (bsc#1273323).\n- CVE-2026-64553: net: psample: fix info leak in PSAMPLE_ATTR_DATA (bsc#1273336).\n- CVE-2026-64554: netfilter: bridge: fix stale prevhdr pointer in br_ip6_fragment() (bsc#1273340).\n- CVE-2026-64555: KVM: arm64: nv: Fix SPSR_EL2 restore in kvm_hyp_handle_mops() (bsc#1273331).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64563: rhashtable: clear stale iter-\u003ep on table restart (bsc#1273995).\n- CVE-2026-64567: btrfs: reject free space cache with more entries than pages (bsc#1274006).\n- CVE-2026-64569: mpls: fix NULL deref in mpls_valid_fib_dump_req() on CONFIG_INET=n (bsc#1274009).\n- CVE-2026-64572: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (bsc#1274014).\n- CVE-2026-64576: nexthop: initialize extack in nh_res_bucket_migrate() (bsc#1274030).\n- CVE-2026-64577: gtp: check skb_pull_data() return in gtp1u_send_echo_resp() (bsc#1274031).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64581: xfrm: fix sk_dst_cache double-free in xfrm_user_policy() (bsc#1274041).\n- CVE-2026-64582: RDMA/rxe: Fix a use-after-free problem in rxe_mmap (bsc#1274040).\n- CVE-2026-64586: wifi: brcmfmac: drain bus_reset work on device removal (bsc#1274492).\n- CVE-2026-68082: libceph: fix two unsafe bare decodes in decode_lockers() (bsc#1274581).\n- CVE-2026-68086: mm/khugepaged: write all dirty file folios when collapsing (bsc#1274713).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68105: drm/amdgpu: Fix kernel panic during driver load failure (bsc#1274849).\n- CVE-2026-68116: vxlan: mdb: Fix source list corruption on a failed replace (bsc#1274876).\n- CVE-2026-68117: tipc: clear sock-\u003esk on the failed-insert path in tipc_sk_create() (bsc#1274881).\n- CVE-2026-68120: rtase: Workaround for TX hang caused by hardware packet parsing (bsc#1274887).\n- CVE-2026-68121: pppoe: reload header pointer after dev_hard_header() (bsc#1274888).\n- CVE-2026-68123: openvswitch: fix GSO userspace truncation underflow (bsc#1275169).\n- CVE-2026-68124: mctp: serial: handle zero-length frames to prevent rx buffer overflow (bsc#1275192).\n- CVE-2026-68127: ila: reload IPv6 header after pskb_may_pull in checksum adjust (bsc#1275237).\n- CVE-2026-68128: ice: reject out-of-range ptype in ice_parser_profile_init (bsc#1275238).\n- CVE-2026-68129: gve: fix Rx queue stall on alloc failure (bsc#1275517).\n- CVE-2026-68132: super: fix emergency thaw deadlock on frozen block devices (bsc#1275553).\n- CVE-2026-68133: ice: fix PTP Call Trace during PTP release (bsc#1275555).\n- CVE-2026-68135: net: hip04: fix RX buffer leak on build_skb failure (bsc#1275557).\n- CVE-2026-68136: net: gro: fix double aggregation of flush-marked skbs (bsc#1275474).\n- CVE-2026-68138: net/sched: serialize qdisc_rtab_list against concurrent get/put (bsc#1274941).\n- CVE-2026-68139: net/mlx5e: Use sender devcom for MPV master-up (bsc#1275578).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68142: geneve: require CAP_NET_ADMIN in the device netns for changelink (bsc#1275582).\n- CVE-2026-68143: net: slip: serialize receive against buffer reallocation (bsc#1275583).\n- CVE-2026-68144: phonet: pep: fix use-after-free in pep_get_sb() (bsc#1275481).\n- CVE-2026-68145: iomap: fix out-of-bounds bitmap_set() with zero-length range (bsc#1275584).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68149: fs: preserve ACL_DONT_CACHE state in forget_cached_acl() (bsc#1275294).\n- CVE-2026-68152: amt: fix use-after-free in AMT delayed works (bsc#1275300).\n- CVE-2026-68153: libceph: remove debugfs files before client teardown (bsc#1275301).\n- CVE-2026-68154: libceph: reject zero bucket types in crush_decode (bsc#1275303).\n- CVE-2026-68155: libceph: Reject monmaps advertising zero monitors (bsc#1275304).\n- CVE-2026-68156: libceph: refresh auth-\u003eauthorizer_buf{,_len} after authorizer update (bsc#1275305).\n- CVE-2026-68157: libceph: guard missing CRUSH type name lookup (bsc#1275306).\n- CVE-2026-68158: libceph: Fix multiplication overflow in decode_new_up_state_weight() (bsc#1275307).\n- CVE-2026-68159: libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE (bsc#1275470).\n- CVE-2026-68161: sctp: close UDP tunnel sockets during netns teardown (bsc#1274892).\n- CVE-2026-68164: mm/damon/core: disallow overlapping input ranges for damon_set_regions() (bsc#1274955).\n- CVE-2026-68165: mm/damon/core: validate ranges in damon_set_regions() (bsc#1274927).\n- CVE-2026-68166: userfaultfd: prevent registration of special VMAs (bsc#1274930).\n- CVE-2026-68169: mptcp: pm: userspace: fix use-after-free in get_local_id (bsc#1274952).\n- CVE-2026-68183: firmware: stratix10-svc: fix memory leaks and list corruption bugs (bsc#1274957).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68205: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() (bsc#1274934).\n- CVE-2026-68238: drm/amdgpu: Release VFCT ACPI table reference (bsc#1275704).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68267: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists (bsc#1275139).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68284: bpf, sockmap: Fix cork use-after-free in tcp_bpf_sendmsg() (bsc#1275970).\n- CVE-2026-68286: drop_monitor: perform u64_stats updates under IRQ-disabled section (bsc#1275973).\n- CVE-2026-68288: net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD (bsc#1275975).\n- CVE-2026-68289: tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream() (bsc#1275976).\n- CVE-2026-68293: net/mlx5: Fix MCIA register buffer overflow on 32 dword reads (bsc#1275091).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68296: net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM (bsc#1275045).\n- CVE-2026-68297: tipc: fix u16 MTU truncation in media and bearer MTU validation (bsc#1275040).\n- CVE-2026-68299: vmxnet3: fix BUG_ON in vmxnet3_get_hdr_len() for Geneve packets (bsc#1275088).\n- CVE-2026-68300: sctp: auth: verify auth requirement when auth_chunk is NULL (bsc#1275083).\n- CVE-2026-68302: amt: re-read skb header pointers after every pull (bsc#1275081).\n- CVE-2026-68313: tipc: fix infinite loop in __tipc_nl_compat_dumpit (bsc#1274665).\n- CVE-2026-68315: sctp: validate stream count in sctp_process_strreset_inreq() (bsc#1274662).\n- CVE-2026-68319: pds_core: fix deadlock between reset thread and remove (bsc#1274657).\n- CVE-2026-68320: sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid (bsc#1274659).\n- CVE-2026-68321: net: txgbe: fix FDIR filter leak on remove (bsc#1274652).\n- CVE-2026-68322: rds: Fix inet6_addr_lst NULL dereference when IPv6 is disabled (bsc#1274656).\n- CVE-2026-68325: iommu/amd: Bound the early ACPI HID map (bsc#1274651).\n- CVE-2026-68328: nfp: Check resource mutex allocation (bsc#1274646).\n- CVE-2026-68329: iommu/amd: Wait for completion instead of returning early in iommu_completion_wait() (bsc#1274645).\n- CVE-2026-68331: dpaa2-eth: put MAC endpoint device on disconnect (bsc#1274642).\n- CVE-2026-68333: dpaa2-switch: put MAC endpoint device on disconnect (bsc#1274644).\n- CVE-2026-68335: rds: drop incoming messages that cross network namespace boundaries (bsc#1274640).\n- CVE-2026-68336: bonding: fix devconf_all NULL dereference when IPv6 is disabled (bsc#1274639).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68375: bnxt_en: Handle partially initialized auxiliary devices (bsc#1274835).\n- CVE-2026-68377: net/sched: act_tunnel_key: Defer dst_release to RCU callback (bsc#1274831).\n- CVE-2026-68386: bpf, sockmap: Reject unhashed UDP sockets on sockmap update (bsc#1274814).\n- CVE-2026-68393: Bluetooth: hci_sync: extend conn_hash lookup critical sections (bsc#1274904).\n- CVE-2026-68395: ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered (bsc#1274900).\n- CVE-2026-68397: net/iucv: take a reference on the socket found in afiucv_hs_rcv() (bsc#1274898).\n- CVE-2026-68398: ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF (bsc#1274908).\n- CVE-2026-68399: bpf: Fix UAF in sock clone early bailouts (bsc#1274897).\n- CVE-2026-68408: wifi: cfg80211: convert pmsr_free_wk to wiphy_work to fix deadlock (bsc#1274709).\n- CVE-2026-68417: RDMA/siw: publish QP after initialization (bsc#1274696).\n- CVE-2026-68418: RDMA/irdma: Prevent user-triggered null deref on QP create (bsc#1274690).\n- CVE-2026-68419: RDMA/irdma: Prevent rereg_mr for non-mem regions (bsc#1274698).\n- CVE-2026-68422: btrfs: fix root leak if its reloc root is unexpected in merge_reloc_roots() (bsc#1274706).\n- CVE-2026-68425: IB/mad: Drop unmatched RMPP responses before reassembly (bsc#1274700).\n- CVE-2026-68426: xfrm: fix stale skb-\u003eprev after async crypto steals a GSO segment (bsc#1274705).\n- CVE-2026-68432: vxlan: require CAP_NET_ADMIN in the device netns for changelink (bsc#1274800).\n- CVE-2026-68433: libceph: bound get_version reply decode to front len (bsc#1274801).\n- CVE-2026-68442: btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps (bsc#1274773).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68450: btrfs: free mapping node on duplicate reloc root insert (bsc#1274834).\n- CVE-2026-68470: wifi: mac80211: validate extension-frame layout before RX (bsc#1276500).\n- CVE-2026-68480: x86/bugs: Make Safe-RET robust against interrupt injection (bsc#1274208).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72020: ipvs: reset full ip_vs_seq structs in ip_vs_conn_new (bsc#1275506).\n- CVE-2026-72022: llc: fix SAP refcount leak in llc_ui_autobind() (bsc#1276785).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72032: net/mlx5: HWS, fix matcher leak on resize target setup failure (bsc#1276955).\n- CVE-2026-72034: fhandle: reject detached mounts in capable_wrt_mount() (bsc#1276957).\n- CVE-2026-72035: net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1276961).\n- CVE-2026-72036: net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1277034).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72046: gve: fix header buffer corruption with header-split and HW-GRO (bsc#1275519).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72069: locking/rt: Fix the incorrect RCU protection in rt_spin_unlock() (bsc#1275528).\n- CVE-2026-72072: net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete (bsc#1277155).\n- CVE-2026-72083: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE (bsc#1275535).\n- CVE-2026-72084: scsi: target: core: Generate correct identifiers for PR OUT transport IDs (bsc#1275540).\n- CVE-2026-72100: dm-integrity: fix a bug if the bio is out of limits (bsc#1277311).\n- CVE-2026-72101: dm-integrity: fix leaking uninitialized kernel memory (bsc#1276831).\n- CVE-2026-72103: dm: avoid leaking the caller's thread keyring via the table device file (bsc#1277315).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72132: NFS: Charge unstable writes by request size, not folio size (bsc#1277551).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72137: xfrm: nat_keepalive: avoid double free on send error (bsc#1275587).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72176: mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error (bsc#1277230).\n- CVE-2026-72177: mm/damon/sysfs-schemes: fix dir put orders in access_pattern_add_dirs() (bsc#1277227).\n- CVE-2026-72217: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing (bsc#1275655).\n- CVE-2026-72221: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (bsc#1275665).\n- CVE-2026-72222: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (bsc#1275669).\n- CVE-2026-72234: batman-adv: access unicast_ttvn skb-\u003edata only after skb realloc (bsc#1275672).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72251: netfilter: nf_nat_sip: reload possible stale data pointer (bsc#1275827).\n- CVE-2026-72254: netfilter: nft_fib: reject fib expression on the netdev egress hook (bsc#1277204).\n- CVE-2026-72280: KVM: arm64: nv: Drop bogus WARN for write to ZCR_EL2 (bsc#1277726).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72288: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling (bsc#1275886).\n- CVE-2026-72289: KVM: arm64: vgic: Check the interrupt is still ours before migrating it (bsc#1275905).\n- CVE-2026-72296: net: ife: require ETH_HLEN to be pullable in ife_decode() (bsc#1275923).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72307: mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace() (bsc#1277160).\n- CVE-2026-72308: mlxsw: fix refcount leak in mlxsw_sp_port_lag_join() (bsc#1277159).\n- CVE-2026-72317: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (bsc#1275925).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72337: Bluetooth: 6lowpan: avoid untracked enable work (bsc#1277773).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72341: net/mlx5e: Fix publication race for priv-\u003echannel_stats[] (bsc#1277660).\n- CVE-2026-72342: net/mlx5e: Fix HV VHCA stats agent registration race (bsc#1277775).\n- CVE-2026-72343: net/mlx5e: Fix HV VHCA stats zero-sized buffer allocation (bsc#1277776).\n- CVE-2026-72345: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback (bsc#1277782).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72366: netfs: Fix netfs_create_write_req() to handle async cache object creation (bsc#1276333).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72389: bridge: stp: Fix a potential use-after-free when deleting a bridge (bsc#1273869).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72414: net: dsa: sja1105: round up PTP perout pin duration (bsc#1278039).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72430: net/sched: act_ct: fix nf_connlabels leak on two error paths (bsc#1277118).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72464: xprtrdma: Post receive buffers after RPC completion (bsc#1277069).\n- CVE-2026-72466: xprtrdma: Fix bcall rep leak and unbounded peek (bsc#1277057).\n- CVE-2026-72467: xprtrdma: Check frwr_wp_create() during connect (bsc#1277059).\n- CVE-2026-72468: xprtrdma: Initialize re_id before removal registration (bsc#1277062).\n- CVE-2026-72469: xprtrdma: Fix ep kref imbalance on ADDR_CHANGE (bsc#1277047).\n- CVE-2026-72473: xprtrdma: Avoid 250 ms delay on backlog wakeup (bsc#1277037).\n- CVE-2026-72485: coresight: platform: defer connection counter increment until alloc succeeds (bsc#1276771).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-72494: RDMA/irdma: Replace waitqueue and flag with completion (bsc#1276941).\n- CVE-2026-72495: RDMA/bnxt_re: Avoid repeated requests to allocate WC pages (bsc#1276937).\n- CVE-2026-72497: RDMA/bnxt_re: Add a max slot check for SQ (bsc#1276913).\n- CVE-2026-72499: RDMA/bnxt_re: Free CQ toggle page after firmware teardown (bsc#1276551).\n- CVE-2026-72500: RDMA/bnxt_re: Free SRQ toggle page after firmware teardown (bsc#1276552).\n- CVE-2026-72501: RDMA/bnxt_re: Initialize dpi variable to zero (bsc#1276546).\n- CVE-2026-72502: tcp: ipv6: clamp default adverting MSS to avoid GSO_BY_FRAGS (0xFFFF) (bsc#1276542).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74269: bnxt: fix head underflow on XDP head-grow (bsc#1276507).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74286: net: pfcp: allocate per-cpu tstats for PFCP netdevs (bsc#1276471).\n- CVE-2026-74296: RDMA/mlx5: Release the HW-provided UAR index rather than the SW one (bsc#1276452).\n- CVE-2026-74297: RDMA/mlx5: Fix undefined shift of user RQ WQE size (bsc#1276446).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74316: NFSD: Handle layout stid in nfsd4_drop_revoked_stid() (bsc#1276870).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74318: btrfs: fix deadlock cloning inline extent when using flushoncommit (bsc#1276864).\n- CVE-2026-74321: btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() (bsc#1277202).\n- CVE-2026-74334: RDMA/nldev: Fix locking when accessing mr-\u003epd (bsc#1277095).\n- CVE-2026-74345: RDMA/siw: Fix endpoint/socket association handling (bsc#1277285).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74394: RDMA/srpt: fix integer overflow in immediate data length check (bsc#1277408).\n- CVE-2026-74395: RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference (bsc#1277077).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74474: vxlan: use pskb_network_may_pull() for transmit path header pulls (bsc#1276335).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74481: mm/page_reporting: use system_freezable_wq to fix UAF during suspend (bsc#1276355).\n- CVE-2026-74482: mm/huge_memory: unlock i_mmap_rwsem before releasing after-split folios (bsc#1276346).\n- CVE-2026-74495: igbvf: Fix leak in TX DMA error cleanup (bsc#1275864).\n- CVE-2026-74496: fou: Fix use-after-free in fou_create() (bsc#1275867).\n- CVE-2026-74510: Bluetooth: mgmt: fix UAF in pair command cancellation (bsc#1275950).\n- CVE-2026-74512: audit: fix potential use-after-free in audit_del_rule() (bsc#1275954).\n- CVE-2026-74513: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister (bsc#1275956).\n- CVE-2026-74517: KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs (bsc#1276258).\n- CVE-2026-74518: mm/hugetlb: fix list corruption in allocate_file_region_entries() (bsc#1275798).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74527: octeontx2-af: Block VFs from clobbering special CGX PKIND state (bsc#1275805).\n- CVE-2026-74533: Bluetooth: ISO: fix race of kfree vs kref_get_unless_zero (bsc#1275804).\n- CVE-2026-74534: Bluetooth: ISO: Fix data-race on iso_pi(sk) in socket and HCI event paths (bsc#1275801).\n- CVE-2026-74535: Bluetooth: ISO: avoid deadlocks in iso_sock_timeout (bsc#1275812).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74537: Bluetooth: ISO: hold sk properly in iso_conn_ready (bsc#1275687).\n- CVE-2026-74545: rtase: fix double free of multi-frag skb on DMA map failure (bsc#1275679).\n- CVE-2026-74548: forcedeth: fix UAF of txrx_stats in nv_remove (bsc#1275695).\n- CVE-2026-74550: net: do not send ICMP/NDISC Redirects when peer allocation fails (bsc#1275688).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74556: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer (bsc#1275696).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74563: rds: tcp: hold the RCU lock across ipv6_chk_addr() in rds_tcp_laddr_check() (bsc#1275574).\n- CVE-2026-74566: keys: make keyring key-chunk byte order agree with keyring_diff_objects() (bsc#1275566).\n- CVE-2026-74567: keys: fix out-of-bounds read in keyring_get_key_chunk() (bsc#1275569).\n- CVE-2026-74571: btrfs: skip global block reserve accounting for rescue mounts (bsc#1275561).\n- CVE-2026-74577: net: mpls: initialize rtm_tos in mpls_getroute() (bsc#1275572).\n- CVE-2026-74581: net: ipv6: clear suppressed fib6 rule result (bsc#1275782).\n- CVE-2026-74582: packet: use consistent hard_header_len in non-ring send paths (bsc#1275784).\n- CVE-2026-74584: RDMA/bnxt_re: zero shared page before exposing to userspace (bsc#1277066).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74610: tls: don't leave a full plaintext sk_msg ring unpushed (bsc#1277054).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74644: mm/damon/ops-common: putback folios on invalid migrate nid (bsc#1277033).\n- CVE-2026-74665: net: fix skb length accounting after generic XDP frag adjustment (bsc#1277407).\n- CVE-2026-74669: ipvs: clear IPv4 options after rebasing tunnel ICMP errors (bsc#1277391).\n- CVE-2026-74695: netfilter: nf_flow_table: drop existing skb dst before skb_dst_set_noref() (bsc#1276931).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74712: vdpa/mlx5: Fix buffer length in create_direct_keys() (bsc#1276577).\n- CVE-2026-74717: net/mlx5: fw_tracer, return NULL on create error (bsc#1276569).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74722: btrfs: fix memory leak in btrfs_do_encoded_write() (bsc#1276561).\n- CVE-2026-74723: btrfs: lzo: reject inline extents without valid headers (bsc#1276562).\n- CVE-2026-74730: NFS: Pin the 'struct nfs_server' during a FREE_STATEID call (bsc#1276566).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-80529: xfs: don't swallow dquot recovery verification errors (bsc#1277688).\n- CVE-2026-80530: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN (bsc#1277668).\n- CVE-2026-80531: xfs: avoid UAF on sc-\u003etempip in xrep_tempfile_create (bsc#1277680).\n- CVE-2026-80533: xfs: don't walk off the end of a null sc-\u003esa.agi_bp in AGI repair (bsc#1277636).\n- CVE-2026-80534: xfs: fix ilock leak on error in xfs_dq_get_next_id (bsc#1277022).\n- CVE-2026-80535: xfs: don't double-lock when deleting a self-referential directory (bsc#1277641).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80558: libceph: Avoid using invalid osd indices from primary_temp (bsc#1277485).\n- CVE-2026-80561: libceph: fix multiple unsafe decodes in decode_locker() (bsc#1277265).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80590: inet: frags: strip GSO state from fragments before reassembly (bsc#1277275).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80609: qede: fix out-of-bounds check for cqe-\u003elen_list (bsc#1278334).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80721: Bluetooth: ISO: ensure no dangling hcon references in iso_conn (bsc#1277845).\n- CVE-2026-80727: x86/mce: Set up the polling timer before CMCI discovery (bsc#1278703).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80813: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() (bsc#1279537).\n- CVE-2026-80838: vxlan: keep the last remote linked during FDB flush (bsc#1279842).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Limit firmware log name prints to field size (git-fixes).\n- accel/ivpu: Validate firmware log buffer metadata (git-fixes).\n- accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr (git-fixes).\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- accessibility: speakup: Fix incorrect string length computation in report_char_chartab_status() (git-fixes).\n- accessibility: speakup: unregister tty ldisc on later init failures (git-fixes).\n- ACPI: APEI: Fix ERST timeout unit conversion (git-fixes).\n- ACPI: battery: Adjust charging status validation check (git-fixes).\n- ACPI: EC: Avoid _REG disconnect on GPIO IRQ defer (git-fixes).\n- ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root (git-fixes).\n- ACPI: pfr_update: fix stack buffer overflow in query_capability() (git-fixes).\n- ACPI: processor: idle: Expand _LPI package sanity checks (git-fixes).\n- ACPI: processor: validate MADT IOAPIC entry bounds (git-fixes).\n- ACPI: processor_idle: Mark LPI enter functions as __cpuidle (git-fixes).\n- ACPI: scan: fix bus ID cleanup on device_add() failures (git-fixes).\n- ACPI: video: Release PCI device reference after lookup (git-fixes).\n- ALSA: 6fire: bound the MIDI event length from the device (git-fixes).\n- ALSA: 6fire: Fix UAF at error handling during probe (stable-fixes).\n- ALSA: bcd2000: clear the URB pointers on disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: control: Don't add invalid kcontrols to LED layer (git-fixes).\n- ALSA: core: Fix use-after-free in snd_card_do_free() (git-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Check card index validity at probe (stable-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/ext: preserve PPLCCTL bits when clearing reset (git-fixes).\n- ALSA: hda/realtek: Enable headset mic on F+ FLAPTOP r (stable-fixes).\n- ALSA: hda: Fix connection list comparison in proc output (git-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hpi: Check transport errors during HPI6000 adapter initialization (git-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcxhr: initialize mutexes before requesting threaded IRQ (git-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: scarlett2: Use a private URB for the notification endpoint (git-fixes).\n- ALSA: seq: Don't leak the extension cell pointer in the bounce payload (git-fixes).\n- ALSA: seq: midi: Optimize event_input locking with RCU (git-fixes).\n- ALSA: seq: midi: Serialize input teardown with event_input (git-fixes).\n- ALSA: ump: Fix corrupted data bytes at MIDI 1.0 SysEx to UMP conversion (git-fixes).\n- ALSA: usb-audio: Complete cleanup after system-resume errors (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_novation_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write on Type II inbound URBs (git-fixes).\n- ALSA: usb: Fix UAF at delayed release of MIDI2 EPs (git-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usbusx2y: validate URB actual_length in interrupt callback (git-fixes).\n- ALSA: usx2y: bound the hwdep mmap fault offset (git-fixes).\n- ALSA: via82xx: Remove unreachable branch in snd_via686_pcm_pointer() (git-fixes).\n- apparmor: advertise the tcp fast open fix is applied (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: adau1761: sort the register default table (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add DMI entry for MSI Thin A15 B7UC (git-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: apple: mca: increase SERDES reset delay (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses (git-fixes).\n- ASoC: cs35l33: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l34: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l41: sort the register default table (git-fixes).\n- ASoC: cs35l45: sort the register default table (git-fixes).\n- ASoC: cs4265: sort the register default table (git-fixes).\n- ASoC: cx2072x: sort the register default table (git-fixes).\n- ASoC: dapm: Fix off-by-one check on the second enum channel (git-fixes).\n- ASoC: fix unmet dependencies on PPC_BESTCOMM and SND_SOC_AC97_BUS (git-fixes).\n- ASoC: fsl-asoc-card: defer probe when the CPU DAI device is not ready (git-fixes).\n- ASoC: fsl: mpc5200-i2s: Free DMA resources on probe failure (git-fixes).\n- ASoC: fsl_audmix: rework runtime PM handling in probe (git-fixes).\n- ASoC: fsl_easrc: sort the register default table (git-fixes).\n- ASoC: hdac_hda: Fix hlink refcount leak on component registration failure (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: avs: Do not ignore -ENOENT when loading a topology (git-fixes).\n- ASoC: Intel: avs: Fix unbalanced module reference count (git-fixes).\n- AsoC: intel: sst: fix PCI device reference leak on probe failure (git-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: loongson: Fix error handling in ACPI property parsing (git-fixes).\n- ASoC: max9860: sort the register default table (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Shorten memif_data table using macros (stable-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Support \u003e32 bit DMA addresses (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: use local `dev` pointer in driver callbacks (stable-fixes).\n- ASoC: mediatek: mt8183: Check runtime resume during probe (git-fixes).\n- ASoC: mediatek: mt8192-afe-pcm: Simplify probe() with local dev variable (stable-fixes).\n- ASoC: mediatek: mt8192: Check runtime resume during probe (git-fixes).\n- ASoC: meson: Keep link pointers valid on realloc failure (git-fixes).\n- ASoC: ml26124: sort the register default table (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: pcm512x: sort the register default table (git-fixes).\n- ASoC: pxa: Use devm_clk_get_optional() for extclk clock (git-fixes).\n- ASoC: qcom: q6apm: keep the graph start count in sync with the DSP (git-fixes).\n- ASoC: rt274: sort the register default table (git-fixes).\n- ASoC: rt286: sort the register default table (git-fixes).\n- ASoC: rt298: sort the register default table (git-fixes).\n- ASoC: rt700-sdw: always drain jack work on remove (git-fixes).\n- ASoC: rt700: drop duplicate reg_default entry (git-fixes).\n- ASoC: rt700: sort the register default table (git-fixes).\n- ASoC: rt711-sdca: sort the register default tables (git-fixes).\n- ASoC: rt711: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-dmic: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt715-sdca: drop duplicate reg_default entries (git-fixes).\n- ASoC: rt715-sdca: sort the register default tables (git-fixes).\n- ASoC: rt715: sort the register default table (git-fixes).\n- ASoC: rt1017-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt1316-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318: sort the register default table (git-fixes).\n- ASoC: samsung: aries_audio_probe: double of_node_put due to direct assignment without of_node_get (git-fixes).\n- ASoC: sgtl5000: sort the register default table (git-fixes).\n- ASoC: SOF: sof-audio: Fix error path in sof_widget_setup_unlocked() (git-fixes).\n- ASoC: SOF: validate topology volume range before allocation (git-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti-sas: sort the register default table (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tas2552: sort the register default table (git-fixes).\n- ASoC: tas2764: sort the register default table (git-fixes).\n- ASoC: tas2780: sort the register default table (git-fixes).\n- ASoC: tegra210_i2s: sort the register default table (git-fixes).\n- ASoC: tegra210_mixer: sort the register default table (git-fixes).\n- ASoC: tegra: Fix the MIXER enable default value (git-fixes).\n- ASoC: tegra: Sort MBDRC register defaults (git-fixes).\n- ASoC: xilinx: formatter_pcm: fix stream_data leak on open error (git-fixes).\n- ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- batman-adv: bla: fix freeing of claims on meshif deletion (git-fixes).\n- batman-adv: bla: prevent CRC corruptions after claim flush (git-fixes).\n- batman-adv: dat: avoid unaligned fault in IP extraction (git-fixes).\n- batman-adv: fix stale receive device on merged fragments (git-fixes).\n- batman-adv: mcast: ensure unshared skb for multicast packets (git-fixes).\n- batman-adv: mcast: linearize skbuff for packet generation (git-fixes).\n- batman-adv: reject unrepresentable multicast TVLV offsets (git-fixes).\n- blk-mq: reinsert cached request to the list (bsc#1273770).\n- Bluetooth: btintel: bound firmware ID by TLV length (git-fixes).\n- Bluetooth: btintel: Fix diagnostics event detection (git-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btintel_pcie: Clear automask on spurious interrupts (git-fixes).\n- Bluetooth: btintel_pcie: fix tx_handle bounds off-by-one (git-fixes).\n- Bluetooth: btintel_pcie: validate packet_len before skb_put_data (git-fixes).\n- Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware (git-fixes).\n- Bluetooth: btmtk: Do not discard the subsystem reset timeout (git-fixes).\n- Bluetooth: btmtk: Fix short read errors in btmtk_usb_uhw_reg_read() (stable-fixes).\n- Bluetooth: btmtksdio: Fix out-of-bounds DMA read in the TX path (git-fixes).\n- Bluetooth: btmtksdio: Take exclusive ownership of the SKB before TX (git-fixes).\n- Bluetooth: btqca: Fix qca_set_bdaddr() waiting for wrong HCI event (git-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Fix BD_ADDR byte order in btusb_set_bdaddr_wcn6855() (git-fixes).\n- Bluetooth: btusb: Fix short read errors in btusb_qca_send_vendor_req() (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: do not leak an hci_conn when a second LE connect is rejected (git-fixes).\n- Bluetooth: eir: Fix OOB read in eir_get_service_data() (git-fixes).\n- Bluetooth: hci_aml: validate firmware segment lengths (git-fixes).\n- Bluetooth: hci_bcm4377: Ignore reserved PHY in ext adv reports on BCM4378 (git-fixes).\n- Bluetooth: hci_bcm: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_conn: fix the SCO setup context lifetime (git-fixes).\n- Bluetooth: hci_conn: hold conn reference in abort_conn_sync() (git-fixes).\n- Bluetooth: hci_conn: re-enable advertising only for peripheral role (git-fixes).\n- Bluetooth: hci_core: Fix race condition during device registration (git-fixes).\n- Bluetooth: hci_core: use skb_get() instead of skb_clone() for req_skb (git-fixes).\n- Bluetooth: hci_event: clear HCI_LE_ADV only on a created connection (git-fixes).\n- Bluetooth: hci_event: fix LE list UAF on reset (git-fixes).\n- Bluetooth: hci_event: validate LE Set CIG Parameters response (git-fixes).\n- Bluetooth: hci_h5: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_intel: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sync: Clear HCI_CMD_PENDING when dropping the last request (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: free the advertising instance on the failure and cancel paths (git-fixes).\n- Bluetooth: hci_sync: make hci_cmd_sync_run_once return -EEXIST if exists (stable-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del() (git-fixes).\n- Bluetooth: hci_uart: Fix false success return in hci_uart_setup() (git-fixes).\n- Bluetooth: ISO: do not force BT_LISTEN after a failed BIG sync (git-fixes).\n- Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect (git-fixes).\n- Bluetooth: mgmt: fix locking in unpair_device/disconnect_sync (git-fixes).\n- Bluetooth: MGMT: free the HCI command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: free the mesh send cancel command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: reject HCI_CMD_SYNC params_len above 255 (git-fixes).\n- Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update (git-fixes).\n- Bluetooth: MSFT: validate evt_prefix_len against the response length (git-fixes).\n- Bluetooth: qca: fix NVM tag length underflow in TLV parser (git-fixes).\n- Bluetooth: RFCOMM: serialize security confirmation handling (git-fixes).\n- Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept (git-fixes).\n- Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (git-fixes).\n- Bluetooth: virtio_bt: avoid OOB read of build info string (git-fixes).\n- bnxt_en: Check return value of bnxt_hwrm_vnic_cfg (jsc#PED-16798).\n- bnxt_en: Delay for 5 seconds after AER DPC for all chips (jsc#PED-16798).\n- bnxt_en: Don't assume XDP is never enabled in bnxt_init_dflt_ring_mode() (jsc#PED-16798).\n- bnxt_en: Drop pci_save_state() after pci_restore_state() (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction for V3_CMP (jsc#PED-16798).\n- bnxt_en: Move bnxt_rss_ext_op into header (jsc#PED-16798).\n- bnxt_en: Refactor some basic ring setup and adjustment logic (jsc#PED-16798).\n- bnxt_en: Restore default stat ctxs for ULP when resource is available (jsc#PED-16798).\n- bnxt_en: Set bp-\u003emax_tpa according to what the FW supports (jsc#PED-16798).\n- bnxt_en: Use absolute target ns from ptp_clock_request (jsc#PED-16798).\n- bnxt_en: use bnxt_xdp_buff for xdp context (jsc#PED-16798).\n- bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation (git-fixes).\n- bus: mhi: host: Fix controller cleanup on EDL sysfs failure (git-fixes).\n- bus: mhi: host: Flush the posted write after writing to MHI_SOC_RESET_REQ_OFFSET (git-fixes).\n- bus: ti-sysc: Fix /chosen node reference leak (git-fixes).\n- cacheinfo: don't propagate DT/ACPI error when arch supplies info (arm64) (git-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: use netdevice_tracker for j1939_{priv,session,ecu} tracking (stable-fixes).\n- char: xilinx_hwicap: unregister class on init errors (git-fixes).\n- cleanup: add a scoped version of CLASS() (stable-fixes).\n- cleanup: fix scoped_class() (git-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- cpufreq: intel_pstate: Add and use hybrid_get_cpu_type() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Avoid SMP calls to get cpu-type (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Fix hwp_get_cpu_scaling() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use correct scaling factor on Raptor Lake-E (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use CPPC to get scaling factors (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use HYBRID_SCALING_FACTOR_ADL for Bartlett Lake (bsc#1240957 bsc#1249104 bsc#1265220).\n- crypto: aspeed - Propagate platform_get_irq() errors (git-fixes).\n- crypto: atmel-sha204a - fix heap info leak on I2C transfer failure (git-fixes).\n- crypto: atmel-tdes - use scatterlist length before DMA mapping (git-fixes).\n- crypto: ccm - Set rfc4309 maxauthsize from child (git-fixes).\n- crypto: ccp - Abort doing SEV INIT if SNP INIT fails (stable-fixes).\n- crypto: ccp - Add new SEV/SNP platform shutdown API (stable-fixes).\n- crypto: ccp - Always pass in an error pointer to __sev_platform_shutdown_locked() (git-fixes).\n- crypto: ccp - Fix __sev_snp_shutdown_locked (git-fixes).\n- crypto: ccp - Fix dereferencing uninitialized error pointer (git-fixes).\n- crypto: ccp - Fix memory leak in SEV INIT_EX path (git-fixes).\n- crypto: ccp - Fix possible deadlock in SEV init failure path (git-fixes).\n- crypto: ccp - Fix SNP panic notifier unregistration (git-fixes).\n- crypto: ccp - Move dev_info/err messages for SEV/SNP init and shutdown (stable-fixes).\n- crypto: ccp - Move SEV/SNP Platform initialization to KVM (stable-fixes).\n- crypto: ccp - Register SNP panic notifier only if SNP is enabled (stable-fixes).\n- crypto: ccp - Reset TMR size at SNP Shutdown (stable-fixes).\n- crypto: doc - Remove extra parenthesis (git-fixes).\n- crypto: hisilicon/sec2 - fix CCM algorithm long packet failure (git-fixes).\n- crypto: keembay - Fix AEAD unregister count in error path (git-fixes).\n- crypto: keembay - Initialize completion before requesting IRQ (git-fixes).\n- crypto: keembay - publish OF module alias for OCS AES/SM4 (git-fixes).\n- crypto: lskcipher - propagate errors from unaligned crypt (git-fixes).\n- crypto: mxs-dcp - fix source scatterlist length access (git-fixes).\n- crypto: qat - cancel work on re-enable SR-IOV timeout (git-fixes).\n- crypto: qat - clear AES key schedule from stack (git-fixes).\n- crypto: qce - fix CCM AAD buffer underallocation (git-fixes).\n- crypto: qce - fix error path in devm_qce_register_algs (git-fixes).\n- crypto: qcom-rng - Allow zero as a random number (git-fixes).\n- crypto: qcom-rng - Enable clock in hwrng case (git-fixes).\n- crypto: rk3288 - fail ahash requests on HASH idle timeout (git-fixes).\n- crypto: sa2ul - stop probe if context pool creation fails (git-fixes).\n- crypto: sl3516 - drop invalid sg_dma_len checks before DMA mapping (git-fixes).\n- crypto: tegra - Don't touch bo refcount in host1x bo pin/unpin (stable-fixes).\n- crypto: tegra - fix rctx-\u003ecryptlen calculation in tegra_gcm_do_one_req() (git-fixes).\n- cxl/acpi: Fix CXL_ACPI and CXL_PMEM Kconfig tristate mismatch (git-fixes).\n- cxl: Adjust the startup priority of cxl_pmem to be higher (git-fixes).\n- default_gfp(): avoid using the \"newfangled\" __VA_OPT__ trick (bsc#1280139).\n- device property: fix infinite loop in fwnode_for_each_child_node() (git-fixes).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dma-mapping: add __dma_from_device_group_begin()/end() (bsc#1267586).\n- dmaengine: dw-edma: Clear stale requests on termination (git-fixes).\n- dmaengine: dw-edma: Complete descriptors before pausing (git-fixes).\n- dmaengine: dw-edma: Fix HDMA channel status register access (git-fixes).\n- dmaengine: dw-edma: Initialize IRQ data before requesting IRQs (git-fixes).\n- dmaengine: dw-edma: Serialize abort state updates (git-fixes).\n- dmaengine: dw-edma: Serialize channel state checks (git-fixes).\n- dmaengine: dw-edma: Terminate all descriptors without callbacks (git-fixes).\n- dmaengine: fsl-edma: tracing: no ptr dereference during log output (git-fixes).\n- dmaengine: hisilicon: Return -ENOMEM on dynamic memory allocation in probe (git-fixes).\n- dmaengine: mediatek: mtk-uart-apdma: Return -ENOMEM on memory allocation failure (git-fixes).\n- dmaengine: qcom-bam-dma: fix autosuspend cleanup during removal (git-fixes).\n- dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers (git-fixes).\n- dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout (git-fixes).\n- dmaengine: zynqmp_dma: fix kernel doc for zynqmp_dma_remove() (git-fixes).\n- driver core: soc: Unregister bus on early device registration failure (git-fixes).\n- drivers/virt: pkvm: Fix end calculation in mmio_guard_ioremap_hook() (git-fixes).\n- Drivers: hv: Use meaningful errnos for hypercall status codes (git-fixes).\n- drm/amd/display: Add AV mute wait frames to dce110_set_avmute (stable-fixes).\n- drm/amd/display: avoid divide-by-zero in __is_lut_linear() (git-fixes).\n- drm/amd/display: Check for tg ops in dce110_set_avmute (git-fixes).\n- drm/amd/display: dce100: skip non-DP stream encoders for DP MST (stable-fixes).\n- drm/amd/display: fix BT.2020 YCbCr limited output CSC matrix (git-fixes).\n- drm/amd/display: fix BT.2020 YCbCr output CSC matrices for DCE (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix NULL pointer dereference in amdgpu_dm_crtc_set_vblank() (git-fixes).\n- drm/amd/display: Increase HDMI AV mute wait from 2 to 3 frames (stable-fixes).\n- drm/amd/display: Remove unused-but-set variable hubp from (git-fixes).\n- drm/amd/display: validate plane degamma LUT size for private color prop (git-fixes).\n- drm/amd/pm: adjust the visibility of pp_table sysfs node (stable-fixes).\n- drm/amd/pm: fix gpu metrics energy accumulator for smu 13.0.0/13.0.7 (git-fixes).\n- drm/amd/pm: fix smu14 power limit range calculation (stable-fixes).\n- drm/amd/pm: make pp_features read-only when scpm is enabled (stable-fixes).\n- drm/amd/pm: Use same metric table for APU (stable-fixes).\n- drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read (git-fixes).\n- drm/amdgpu/gfx6: Fixup emit_cntxcntl() (git-fixes).\n- drm/amdgpu/gfx6: Fixup emitting SWITCH_BUFFER packets (git-fixes).\n- drm/amdgpu/gfx6: Use PFP on the compute queues too (git-fixes).\n- drm/amdgpu/gfx8: drop unecessary BUG_ON() (stable-fixes).\n- drm/amdgpu/gfx9.4.3: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx9: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx11: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx12: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in SMU7 lookup (git-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup (git-fixes).\n- drm/amdgpu/sdma4.4.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma6.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma7.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/uvd: Fix forcing MSG, FB BOs into VCPU segment when it isn't at 0 (v2) (stable-fixes).\n- drm/amdgpu/uvd: Place VCPU BO only in VRAM for UVD 4.x and older (stable-fixes).\n- drm/amdgpu/vce: fix integer overflow in image size (stable-fixes).\n- drm/amdgpu/vcn4: avoid rereading IB param length (stable-fixes).\n- drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check (git-fixes).\n- drm/amdgpu: cap GTT size to physical RAM on APUs (stable-fixes).\n- drm/amdgpu: check ASPM on the dGPU host link (git-fixes).\n- drm/amdgpu: disallow multiple FENCE chunks in one submit (git-fixes).\n- drm/amdgpu: fix aperture iounmap skipped on device removal (git-fixes).\n- drm/amdgpu: fix autosuspend cleanup during removal (git-fixes).\n- drm/amdgpu: fix bo-\u003epin leaking in amdgpu_bo_create_reserved (stable-fixes).\n- drm/amdgpu: fix division by zero with invalid uvd dimensions (stable-fixes).\n- drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid() (stable-fixes).\n- drm/amdgpu: fix nbif 6.3.1 l1 low power not functional (git-fixes).\n- drm/amdgpu: Fix UVD decode image min size calculation (stable-fixes).\n- drm/amdgpu: Fix UVD dpb min size calculation for H264 (stable-fixes).\n- drm/amdgpu: Fix UVD min buffer sizes (stable-fixes).\n- drm/amdgpu: Fix VCE 3 ring align_mask (git-fixes).\n- drm/amdgpu: Fix VFCT bus number matching with soft filter (stable-fixes).\n- drm/amdgpu: Implement insert_end for VCE 3 (git-fixes).\n- drm/amdgpu: invoke pm_genpd_remove() before freeing genpd (stable-fixes).\n- drm/amdgpu: move debug_vm handling to amdgpu_cs_parser_fini (git-fixes).\n- drm/amdgpu: read TRUNCATE_COORD_MODE on gfx12 (git-fixes).\n- drm/amdgpu: reject oversized IBs with per-ring packet limits (stable-fixes).\n- drm/amdgpu: Reject UVD message with dimensions above 4096 (stable-fixes).\n- drm/amdgpu: Reject UVD message with invalid number of h265 refs (stable-fixes).\n- drm/amdgpu: remove unused function parameter (stable-fixes).\n- drm/amdgpu: restore UMD profile pstate after runtime resume (stable-fixes).\n- drm/amdgpu: validate GEM_CREATE domain combinations (stable-fixes).\n- drm/amdkfd: Check bounds in allocate_event_notification_slot (stable-fixes).\n- drm/amdkfd: fix 32-bit overflow in CWSR total size calculation (stable-fixes).\n- drm/amdkfd: Fix missing authorization check in KFD_IOC_DBG_TRAP_DISABLE (stable-fixes).\n- drm/amdkfd: fix QID bit leak in pqm_create_queue() (stable-fixes).\n- drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore (git-fixes).\n- drm/amdkfd: Handle invalid event type in CRIU event restore (stable-fixes).\n- drm/amdkfd: Use kvcalloc to allocate arrays (stable-fixes).\n- drm/bridge: cdns-mhdp8546: Return an error pointer on allocation failure (git-fixes).\n- drm/bridge: dw-hdmi: fix i2c adapter leak on probe failure (git-fixes).\n- drm/bridge: ps8640: propagate AUX transfer register errors (git-fixes).\n- drm/bridge: tc358767: clamp the reported AUX read size to the request (git-fixes).\n- drm/connector/hdmi: Fix out of bounds memory read (git-fixes).\n- drm/connector: Fix epoch_counter docs to reflect reality (git-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/hibmc: Fix list of formats on the primary plane (git-fixes).\n- drm/hibmc: Use drm_atomic_helper_check_plane_state() (git-fixes).\n- drm/i915/hdcp: check streams bounds before overflow (git-fixes).\n- drm/i915/hdcp: Move to using intel_display in intel_hdcp (stable-fixes).\n- drm/i915/hdcp: require monotonically increasing seq_num_v (git-fixes).\n- drm/i915/hdcp: Skip inactive MST connectors when building stream list (stable-fixes).\n- drm/i915/vrr: Check HAS_VRR() first in intel_vrr_is_capable() (stable-fixes).\n- drm/i915/vrr: require valid min/max vfreq for VRR (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/lima: call drm_mm_init() with a valid allocation range (git-fixes).\n- drm/msm/a6xx: Fix RBBM_CLOCK_CNTL3_TP0 value in a730_hwcg (git-fixes).\n- drm/msm/a6xx: Fix stale rpmh votes after suspend (git-fixes).\n- drm/msm/dpu: Drop sneaky dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: Drop dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: round 6G byte clock rate to the PLL-achievable value (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau: unsubscribe the channel-kill event before the fence context (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/panel-edp: fix i2c adapter leak on probe failure (git-fixes).\n- drm/panel: samsung-s6d16d0: Power off on prepare failure (git-fixes).\n- drm/panthor: fix firmware control interface bounds checks (git-fixes).\n- drm/panthor: return PTR_ERR() from devm_drm_dev_alloc() (git-fixes).\n- drm/panthor: skip zero-sized firmware sections (git-fixes).\n- drm/radeon: fix autosuspend cleanup during teardown (git-fixes).\n- drm/radeon: fix r100_copy_blit for large BOs (stable-fixes).\n- drm/radeon: restore hardware polling in fence_is_signaled to fix performance regression (git-fixes).\n- drm/rockchip: vop2: Recognise 10-bit YUV422 as YUV format (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates for ssd132x (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates in ssd133x (git-fixes).\n- drm/sun4i: crtc: Propagate layer initialization error (git-fixes).\n- drm/sun4i: Drop node references while building component list (git-fixes).\n- drm/sun4i: dw-hdmi: Drop TCON TOP port reference (git-fixes).\n- drm/sun4i: fix refcount leak in sun4i_backend_init_sat() (git-fixes).\n- drm/sun4i: hdmi-phy: Fix H6 8-bit MPLL config at 594 MHz (git-fixes).\n- drm/sun4i: hdmi: Don't leak sync polarity bits into packet control (git-fixes).\n- drm/sun4i: tcon: Drop remote endpoint reference (git-fixes).\n- drm/sun4i: tcon: Drop TCON TOP device reference (git-fixes).\n- drm/sun4i: tcon: Set output mux for DSI and LVDS (git-fixes).\n- drm/sun4i: vi scaler: Fix coefficient selection (git-fixes).\n- drm/tegra: dsi: Re-add clear enable register if DSI was powered by bootloader (git-fixes).\n- drm/tegra: fbdev: Do not assign to struct drm_fb_helper.info (git-fixes).\n- drm/tve200: add OF module alias for autoloading (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/xe/oa: Check managed mutex initialization errors (git-fixes).\n- drm/xe/oa: Fix sync entry leak on OA config emit failure (git-fixes).\n- drm/xe/oa: Remove sysfs entry on idr_alloc failure in xe_oa_add_config_ioctl() (git-fixes).\n- drm/xe: Introduce xe_gt_dbg_printer() (stable-fixes).\n- drm/xe: Order ring writes before ring tail updates (git-fixes).\n- drm/xe: Stub out new pagefault layer (stable-fixes).\n- drm/xe: tests: fix error message in xe_migrate_sanity_test() (git-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: fix race between partial drm_dev_register() failure and ioctl (git-fixes).\n- drm: lcdif: Wait for vblank before disabling DMA (git-fixes).\n- drm: Remove unused header in drm_dumb_buffers.c (git-fixes).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- erspan: Initialize options_len before referencing options (bsc#1274727).\n- ethtool: rss: fix hkey leak when indir_size is 0 (git-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_cursor() (git-fixes).\n- fbdev: core: Fix pointer desynchronization in fb_io_read() (git-fixes).\n- fbdev: kyro: Validate overlay viewport coordinates (git-fixes).\n- fbdev: omapfb: panel-dsi-cm: initialize lock before registering display (git-fixes).\n- fbdev: tdfxfb: fix PCI enable cleanup with pcim_enable_device() (git-fixes).\n- fbdev: uvesafb: unregister connector callback on init failure (git-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Avoid IDR updates while cleaning channels (git-fixes).\n- firmware: arm_scmi: Clean up channels on setup failure (git-fixes).\n- firmware: arm_scmi: Drop handle on protocol bind failures (git-fixes).\n- firmware: arm_scmi: Fix requested device removal race (git-fixes).\n- firmware: arm_scmi: Free transport channel on IDR failure (git-fixes).\n- firmware: arm_scmi: Protect device request lookup with RCU (git-fixes).\n- firmware: arm_scmi: Publish channel state before callbacks (git-fixes).\n- firmware: arm_scmi: Quiesce notifications before teardown (git-fixes).\n- firmware: arm_scmi: Rate-limit queue-full warnings in IRQ context (git-fixes).\n- firmware: arm_scmi: Reject out of range DT protocol IDs (git-fixes).\n- firmware: arm_scmi: Roll back partial protocol table registration (git-fixes).\n- firmware: arm_scmi: Unregister device notifier before IDR teardown (git-fixes).\n- firmware: arm_scmi: Unrequest devices if driver registration fails (git-fixes).\n- firmware: arm_scmi: Unwind P2A receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Unwind TX receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Use channel ID for transport teardown (git-fixes).\n- firmware_loader: do not queue completed sysfs fallback requests (git-fixes).\n- fpga: altera-cvp: Avoid out-of-bounds read in trailing byte write (git-fixes).\n- fpga: dfl: fme: add error handling (git-fixes).\n- fpga: stratix10-soc: Fix SVC mailbox handling during reconfiguration (git-fixes).\n- fuse: fix race between interrupt and resend (git-fixes).\n- gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind (git-fixes).\n- gpu: host1x: Avoid stack over-read in debug output helpers (git-fixes).\n- gpu: host1x: Fix offset calculation in trace_write_gather (git-fixes).\n- gpu: host1x: Fix use-after-free in host1x_bo_clear_cached_mappings (stable-fixes).\n- HID: asus: fix missing hid_is_usb() check (git-fixes).\n- HID: asus: simplify RGB init sequence (stable-fixes).\n- HID: bpf: serialize device reference release in struct_ops destroy path (git-fixes).\n- HID: core: fix number/pointer type confusion on long items (git-fixes).\n- HID: core: fix OOB read of field-\u003eusage in hid_set_field() (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: hyperv: validate initial device info bounds (git-fixes).\n- HID: i2c-hid: Fix \"(null)\" output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: goodix: Disable VDD on VDDIO enable failure (git-fixes).\n- HID: lg4ff: validate report length before fixed offsets (git-fixes).\n- HID: logitech-dj: Fix maxfield check in DJ short report validation (git-fixes).\n- HID: logitech-dj: fix wrong detection of bad DJ_SHORT output report (git-fixes).\n- HID: logitech-dj: Prevent REPORT_ID_DJ_SHORT related user initiated OOB write (stable-fixes).\n- HID: logitech-dj: Standardise hid_report_enum variable nomenclature (stable-fixes).\n- HID: magicmouse: do not keep a stale msc-\u003einput if no input is claimed (git-fixes).\n- HID: magicmouse: fix battery reporting for Bluetooth Magic Trackpad USB-C (git-fixes).\n- HID: magicmouse: Prevent out-of-bounds (OOB) read during DOUBLE_REPORT_ID (stable-fixes).\n- HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() (git-fixes).\n- HID: magicmouse: re-enable multitouch after reset-resume (git-fixes).\n- HID: mcp2221: validate report size in mcp2221_raw_event() (git-fixes).\n- HID: multitouch: reclassify HTIX5288 to WIN_8_FORCE_MULTI_INPUT_NSMU (git-fixes).\n- HID: nintendo: Fix imu_timestamp_us double increment per report (git-fixes).\n- HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler() (git-fixes).\n- HID: nintendo: register input device after capabilities are set (git-fixes).\n- HID: nintendo: stop device IO before hid_hw_stop on probe failure (git-fixes).\n- HID: picolcd: clamp eeprom debugfs read to bytes actually received (git-fixes).\n- HID: pidff: Rework pidff_set_time() to fix warnings (stable-fixes).\n- HID: pidff: Use ARRAY_SIZE macro instead of sizeof (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: roccat: bound device-supplied profile index (git-fixes).\n- HID: roccat: free buffered reports when destroying device (git-fixes).\n- HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature (git-fixes).\n- HID: sensor: custom: Fix field sysfs group cleanup on failure (git-fixes).\n- HID: sensor: custom: Fix use-after-free in enable_sensor (git-fixes).\n- HID: synchronize input before cleaning up a failed probe (git-fixes).\n- HID: tmff: Use 64-bit arithmetic for force feedback scaling (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- hwmon: (ads7828) Fix external VREF regulator handling (git-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (chipcap2) fix channels in humidity alarm notifications (git-fixes).\n- hwmon: (coretemp) Fix core_data leak on CPUs without PTS (git-fixes).\n- hwmon: (corsair-cpro) Create debugfs entries after hwmon registration (git-fixes).\n- hwmon: (corsair-cpro) Remove debugfs entries when probe fails (git-fixes).\n- hwmon: (corsair-psu) fix possible out-of-bounds access on missing string termination (git-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (ina2xx) Add support for has_alerts configuration flag (stable-fixes).\n- hwmon: (ina2xx) Add support for INA234 (stable-fixes).\n- hwmon: (ina2xx) Add support for INA260 (stable-fixes).\n- hwmon: (ina2xx) Fix various overflow issues (git-fixes).\n- hwmon: (ina2xx) Make it easier to add more devices (stable-fixes).\n- hwmon: (ina2xx) Shift INA234 shunt and current registers (stable-fixes).\n- hwmon: (ina226) Add support for SY24655 (stable-fixes).\n- hwmon: (ltc4282) Avoid overflow in maximum power calculation (git-fixes).\n- hwmon: (ltc4282) Clamp negative current limits (git-fixes).\n- hwmon: (ltc4282) Fix parsing adi,current-limit-sense-microvolt (git-fixes).\n- hwmon: (ltc4282) Make sure clk_init_data is fully initialized (git-fixes).\n- hwmon: (max6621) fix negative temperature offset and crit readings (git-fixes).\n- hwmon: (max6621) fix temperature clamp range (git-fixes).\n- hwmon: (nzxt-smart2) Check return value of init_device() in probe (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficient calculations (git-fixes).\n- hwmon: Switch back to struct platform_driver::remove() (stable-fixes).\n- hwrng: ks-sa - Fix runtime PM cleanup on registration failure (git-fixes).\n- hwrng: omap - Fix probe error path cleanup (git-fixes).\n- hwtracing: hisi_ptt: Propagate DMA reset timeout in trace_start() (git-fixes).\n- i2c: core: fix debugfs UAF on adapter removal (git-fixes).\n- i2c: imx: fix locked bus on SMBus block-read of 0 (atomic) (git-fixes).\n- i2c: imx: separate atomic, dma and non-dma use case (stable-fixes).\n- i2c: mux: demux-pinctrl: fix OF node leak on kstrdup failure (git-fixes).\n- i2c: mux: Fix channel node leak on adapter add failure (git-fixes).\n- i2c: ocores: Disable clock on failed resume (git-fixes).\n- i3c: dw: avoid shift-out-of-bounds when DAA assigns no devices (git-fixes).\n- i3c: dw: rename \"pclk\" to \"apb\" to match dt-binding (git-fixes).\n- i3c: master: Fix device_register() error path (git-fixes).\n- i3c: master: Fix info leak and UAF in device unregister path (git-fixes).\n- i3c: master: Fix potential UAF in i3c_device_uevent() (git-fixes).\n- i3c: master: svc: bound IBI payload to the requested max_payload_len (git-fixes).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: dmard09: Implement IIO_CHAN_INFO_SCALE (git-fixes).\n- iio: adc: max34408: add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- iio: adc: pac1921: fix wrong channel used in trigger handler read (git-fixes).\n- iio: buffer: Fix potential use-after-free in anonymous buffer release (git-fixes).\n- iio: buffer: Make IIO DMA fence release RCU-safe (git-fixes).\n- iio: buffer: Tie IIO dma fence lock lifetime to the fence (git-fixes).\n- iio: chemical: atlas-sensor: fix PM reference leak in buffer postenable (git-fixes).\n- iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF (git-fixes).\n- iio: chemical: sgp30: Handle IAQ thread creation failure (git-fixes).\n- iio: dac: m62332: Fix regulator reference count imbalance (git-fixes).\n- iio: gyro: mpu3050: fix sign of raw angular velocity readings (git-fixes).\n- iio: light: cm32181: return zero after writing calibscale (git-fixes).\n- iio: light: gp2ap002: Disable regulators on resume failure (git-fixes).\n- iio: light: gp2ap002: re-enable irq if runtime suspend fails (git-fixes).\n- iio: light: isl29028: return zero in write_raw() on success (git-fixes).\n- iio: light: ltrf216a: fix runtime PM reference leak in error path (git-fixes).\n- iio: light: opt4001: Fix incompatible pointer type passed to div_u64_rem() (git-fixes).\n- iio: light: opt4001: Fix power down clearing bits of the wrong register (git-fixes).\n- iio: light: opt4001: Fix reversed GENMASK() arguments in fault count mask (git-fixes).\n- iio: light: opt4001: Reject integration times with a non-zero seconds part (git-fixes).\n- iio: light: tsl2583: return zero in write_raw() on success (git-fixes).\n- iio: light: tsl2772: fix ALS calibscale readback (git-fixes).\n- iio: orientation: hid-sensor-rotation: Avoid race between callback setup and device exposure (git-fixes).\n- iio: pressure: dps310: fix NULL pointer dereference on ACPI probe (git-fixes).\n- iio: pressure: mpl115: Fix runtime PM cleanup (git-fixes).\n- iio: srf04: fix pm_runtime handling on probe error path (git-fixes).\n- iio: temperature: hid-sensor-temperature: switch to non-devm iio_device_register() (git-fixes).\n- Input: atkbd - skip deactivate for HONOR ZQC-P (git-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Book Pro 14's internal keyboard (stable-fixes).\n- Input: cs40l50-vibra - validate custom data from user space (git-fixes).\n- Input: evdev - fix information leak in evdev_pass_values() (stable-fixes).\n- Input: evdev - sanitize event type index when fetching event masks (stable-fixes).\n- Input: focaltech - fix array out-of-bounds in focaltech_process_rel_packet (git-fixes).\n- Input: focaltech - use signed coordinates to prevent underflow (git-fixes).\n- Input: hynitron_cstxxx - validate touch count and finger IDs (git-fixes).\n- Input: iforce - validate input packet lengths (stable-fixes).\n- Input: iqs5xx - validate firmware record destination span (git-fixes).\n- Input: mms114 - fix Y-resolution configuration (git-fixes).\n- Input: psxpad-spi - set driver data before use (git-fixes).\n- Input: reject inhibit and uninhibit requests on unregistering devices (git-fixes).\n- Input: sur40 - fix input device registration ordering (stable-fixes).\n- Input: sur40 - fix V4L error path cleanup (stable-fixes).\n- Input: synaptics-rmi4 - block s_input when F54 queue is busy (git-fixes).\n- Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer (git-fixes).\n- Input: synaptics-rmi4 - fix F55 transmitter electrode count typo (git-fixes).\n- Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue (git-fixes).\n- Input: synaptics-rmi4 - zero report size on F54 work error (git-fixes).\n- Input: xpad - add support for ZENAIM LEVERLESS (stable-fixes).\n- interconnect: Fix use after free in icc_get() and of_icc_get_by_index() (git-fixes).\n- io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (git-fixes).\n- io_uring/net: Avoid msghdr on op_connect/op_bind async data (git-fixes).\n- iommu/arm-smmu-v3: Manage teardown with devm (stable-fixes).\n- ip_tunnel: Use ip_tunnel_info() helper instead of 'info + 1' (bsc#1274727).\n- ipmi: ipmb: validate write message length (git-fixes).\n- ipmi: si: Fix NULL pointer dereference after failed registration (git-fixes).\n- KVM: arm64: Ensure FFA ranges are page aligned (git-fixes).\n- KVM: arm64: Fix bounds checking in do_ffa_mem_reclaim() (git-fixes).\n- KVM: arm64: Fix sign-extension of MMIO loads (git-fixes).\n- KVM: arm64: vgic: Reset in_kernel on private IRQ allocation failure (git-fixes).\n- KVM: arm64: Zero out the stack initialized data in the FFA handler (git-fixes).\n- KVM: nSVM: Always inject a #GP if mapping VMCB12 fails on nested VMRUN (git-fixes).\n- KVM: nSVM: Remove a user-triggerable WARN on nested_svm_load_cr3() succeeding (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (git-fixes).\n- KVM: PPC: Book3S HV: Add support for compat CPU capabilities for KVM on PowerNV (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Validate arch_compat against host compatibility mode (bsc#1263864 ltc#217835).\n- KVM: PPC: Document KVM_PPC_GET_COMPAT_CAPS ioctl (bsc#1263864 ltc#217835).\n- KVM: PPC: Introduce KVM_CAP_PPC_COMPAT_CAPS and wire up ioctl (bsc#1263864 ltc#217835).\n- KVM: SEV: Use to_kvm_sev_info() for fetching kvm_sev_info struct (git-fixes).\n- KVM: SVM: Add support to initialize SEV/SNP functionality in KVM (bsc#1279887).\n- KVM: SVM: Explicitly mark vmcb01 dirty after modifying VMCB intercepts (git-fixes).\n- KVM: SVM: Serialize accesses to the owner and mirror list with separate lock (git-fixes).\n- KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active (git-fixes).\n- KVM: TDX: Account all non-transient page allocations for per-TD structures (git-fixes).\n- KVM: TDX: Fix x2APIC MSR handling in tdx_has_emulated_msr() (git-fixes).\n- KVM: VMX: Don't register posted interrupt wakeup handler if alloc_kvm_area() fails (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86/mmu: Recover TDP MMU NX huge pages using MMU read lock (bsc#1271050).\n- KVM: x86/mmu: Rename kvm_tdp_mmu_zap_sp() to better indicate its purpose (bsc#1271050).\n- KVM: x86/mmu: Track possible NX huge pages separately for TDP vs. Shadow MMU (bsc#1271050).\n- KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears because it was cleared from the PIC (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears when Xen emulation is enabled (git-fixes).\n- KVM: x86: Fix array_index_nospec() protection in kvm_vcpu_ioctl_x86_set_mce() (git-fixes).\n- KVM: x86: Fix emulated CPUID features being applied to wrong sub-leaf (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- leds: pca9532: Fix inverted GPIO output polarity (git-fixes).\n- leds: pca9532: Fix phantom device registration on missing hardware (git-fixes).\n- lib/string: fix memchr_inv() for large ranges (git-fixes).\n- lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen() (git-fixes).\n- mac802154: fix data race and NULL deref on local-\u003eassoc_dev (git-fixes).\n- mac802154: fix netdev use-after-free in beacon worker (git-fixes).\n- mac802154: fix use-after-free of sdata via queued RX frames (git-fixes).\n- mailbox: pcc: Fix command timeout due to missed interrupt (git-fixes).\n- mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler (git-fixes).\n- mailbox: qcom-cpucp: handle NULL data in send_data callback (git-fixes).\n- mailbox: qcom-ipcc: fix duplicate channel allocation across holes (git-fixes).\n- mailbox: rockchip: disable pclk on probe failure and unbind (git-fixes).\n- maple_tree: fix argument name in header (git-fixes).\n- md/raid1: create serial pool adding rdev to array with serialize_policy=1 (bsc#1272261).\n- media: airspy: Return queued buffers on start_streaming() failure (git-fixes).\n- media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref (git-fixes).\n- media: amphion: Remove obsolete frame_count check in venc_start_session (git-fixes).\n- media: bcm2835-unicam: Fix asc leaked in error/remove path (git-fixes).\n- media: cec-pin: Fix event FIFO ordering (git-fixes).\n- media: cec: disable delayed work before freeing an interrupted transmit (git-fixes).\n- media: cec: extron-da-hd-4k-plus: add sanity check (git-fixes).\n- media: cec: meson: ao-cec-g12a: name the CEC core regmap to avoid debugfs clash (git-fixes).\n- media: cec: Serialize exclusive follower delivery (git-fixes).\n- media: cec: stm32: prevent out-of-bounds write on RX overflow (git-fixes).\n- media: cedrus: clean up media device on probe failure (git-fixes).\n- media: cedrus: fix memory leak in cedrus_init_ctrls() (git-fixes).\n- media: chips-media: wave5: Guard bit depth check with initial_info_obtained (git-fixes).\n- media: chips-media: wave5: Move src_buf Removal to finish_encode (git-fixes).\n- media: cobalt: Avoid freeing ALSA private data twice (git-fixes).\n- media: cx231xx: fix devres lifetime (git-fixes).\n- media: cx231xx: reject geometry changes while the VBI queue is busy (git-fixes).\n- media: cx23885: add ioremap return check and cleanup (git-fixes).\n- media: cx23885: cancel NetUP CI work before teardown (git-fixes).\n- media: em28xx: defer audio-only extension registration (git-fixes).\n- media: em28xx: fix use-after-free of dev_next-\u003edevlist on disconnect (git-fixes).\n- media: go7007: defer the ALSA v4l2 put until card release (git-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: i2c: alvium: fix critical pointer access in alvium_ctrl_init (git-fixes).\n- media: i2c: alvium: Fix: Correct name of register in alvium_set_ctrl_auto_exposure (git-fixes).\n- media: i2c: imx219: Rename VTS to FRM_LENGTH (stable-fixes).\n- media: i2c: imx415: Return test pattern write errors (git-fixes).\n- media: i2c: ov02a10: fix endpoint parsing use-after-free (git-fixes).\n- media: i2c: ov7740: fix use-after-destroy in remove (git-fixes).\n- media: i2c: rdacm21: Fix missing media_entity_cleanup() (git-fixes).\n- media: imx219: Fix maximum frame length in lines (git-fixes).\n- media: intel/ipu6: fix async notifier cleanup leak on parse error (git-fixes).\n- media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges (git-fixes).\n- media: ipu6: Do not free aux device pdata after init (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_HAUPPAUGE_NEW keymap define (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_RC5_TV keymap define (git-fixes).\n- media: mc-entity: Add missing kerneldoc (git-fixes).\n- media: mediatek: vcodec: bound AV1 tile-start copy to the array capacity (git-fixes).\n- media: meson: vdec: Fix memory leak in error path of vdec_open (git-fixes).\n- media: meson: vdec: fix NULL pointer deref in vdec_try_fmt_common (git-fixes).\n- media: msi2500: Return queued buffers on start_streaming() failure (git-fixes).\n- media: nuvoton: npcm-video: fix error handling in npcm_video_init() (git-fixes).\n- media: nuvoton: npcm-video: fix memory leaks in probe and remove (git-fixes).\n- media: nxp: imx8-isi: Add missing v4l2_subdev_cleanup() in crossbar and pipe (git-fixes).\n- media: nxp: imx8-isi: Clean up already-initialized pipes on probe failure (git-fixes).\n- media: nxp: imx8-isi: Correct color map between V4L2 and ISI (git-fixes).\n- media: nxp: imx8-isi: Fix missing v4l2_subdev_cleanup() in pipe init error path (git-fixes).\n- media: nxp: imx8-isi: Fix potential out-of-bounds issues (git-fixes).\n- media: nxp: imx8-isi: Fix scale factor calculation for hardware rounding (git-fixes).\n- media: nxp: imx8-isi: Fix stream ID validation bypass in crossbar routing (git-fixes).\n- media: nxp: imx8-isi: Use BIT_ULL() for 64-bit stream masks (git-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: platform: mtk-mdp3: fix NULL deref on failed SCP lookup (git-fixes).\n- media: platform: mtk-mdp3: Fix SCP device refcounting (git-fixes).\n- media: pwc: Drain fill_buf on start_streaming() failure (git-fixes).\n- media: pwc: Return queued buffers on start_streaming() failure (git-fixes).\n- media: qcom: camss: Fix RDI streaming for CSID GEN2 (git-fixes).\n- media: radio-si476x: Unregister v4l2_device on probe failure (git-fixes).\n- media: rc: sunxi-cir: Unregister rc device on probe failure (git-fixes).\n- media: rtl2832: fix use-after-free in rtl2832_remove() (git-fixes).\n- media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: Return queued buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak (git-fixes).\n- media: s2255: bound JPEG frame size before copying into the buffer (git-fixes).\n- media: s2255: check firmware size before reading trailing marker (git-fixes).\n- media: saa7134: Fix a possible memory leak in saa7134_video_init1 (git-fixes).\n- media: saa7164: fix cleanup on resource allocation failure (git-fixes).\n- media: stm32: dcmi: unregister notifier on probe failure (git-fixes).\n- media: sun4i-csi: Return queued buffers on start_streaming() failure (git-fixes).\n- media: tda18250: fix possible integer overflow (git-fixes).\n- media: tegra-video: vi: fix invalid u32 return value in format lookup (git-fixes).\n- media: usbtv: keep device alive while ALSA card exists (git-fixes).\n- media: v4l2-async: avoid deleting unlinked ASC entry on link error (git-fixes).\n- media: v4l2-async: Unregister sub-device if asc_list is empty (git-fixes).\n- media: v4l2-ctrls-request: add NULL check in v4l2_ctrl_request_complete() (git-fixes).\n- media: v4l2-ctrls: Allow unknown HDR10 white point and luminance (git-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-fwnode: Fix fwnode leak in v4l2_fwnode_parse_link (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: v4l2-subdev: Fail {enable,disable}_streams and s_streaming nicely (git-fixes).\n- media: venus: fix payload size calculation in parse_raw_formats() (git-fixes).\n- media: venus: fix payload size returned by parse_caps() and parse_alloc_mode() (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer (git-fixes).\n- media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity (git-fixes).\n- media: vicodec: fix out-of-bounds write in FWHT encoder (git-fixes).\n- media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure (git-fixes).\n- media: vimc: fix pixel format lookup in enum_framesizes (git-fixes).\n- media: vivid: add vivid_update_reduced_fps() (git-fixes).\n- media: vivid: check for vb2_is_busy() when toggling caps (git-fixes).\n- media: vivid: fix cleanup bugs in vivid_init() (git-fixes).\n- media: zoran: Avoid freeing a registered video_device twice (git-fixes).\n- mei: pull kvfree out of spinlock (git-fixes).\n- mfd: iqs62x: Reject zero-length firmware records (git-fixes).\n- mfd: rave-sp: validate received frame payload lengths (git-fixes).\n- mfd: sm501: Fix potential memory leaks during remove (git-fixes).\n- misc: bcm-vk: Use acquire/release for msgq_inited (git-fixes).\n- misc: fastrpc: fix channel ctx ref leak when session alloc fails (git-fixes).\n- misc: fastrpc: fix memory leak in fastrpc_channel_ctx_free (git-fixes).\n- misc: fastrpc: Remove buffer from list prior to unmap operation (git-fixes).\n- misc: fastrpc: take fl-\u003elock when moving mmaps on interrupted invoke (git-fixes).\n- misc: nsm: bound the device-reported response length (git-fixes).\n- misc: rtsx: add missing write register handling (git-fixes).\n- misc: sgi-gru: remove interrupt-context page-table walks (git-fixes).\n- misc: vmc_vmci: Fix potential memory leak in vmci_event_subscribe() (git-fixes).\n- mkspec-dtb: Move DTS prefix into package list.\n- mkspec-dtb: Move provides-obsoletes to package list.\n- mkspec-dtb: Put per-architecture package lists into a hash.\n- mkspec-dtb: re-indent.\n- mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition (git-fixes).\n- mmc: omap_hsmmc: fix busy_timeout overflow in ns conversion on 32-bit (git-fixes).\n- mmc: sdhci: unmap the bounce buffer before device release (git-fixes).\n- mmc: via-sdmmc: stop card-detect handling on probe failure (git-fixes).\n- mtd: afs: validate v2 image info bounds (git-fixes).\n- mtd: fix double free and WARN_ON in add_mtd_device() error paths (git-fixes).\n- mtd: mtdoops: free page bitmap when the backing MTD is removed (git-fixes).\n- mtd: mtdswap: Avoid freeing registered blktrans device twice (git-fixes).\n- mtd: mtdswap: remove debugfs stats file on teardown (git-fixes).\n- mtd: nand: mtk-ecc: stop on ECC idle timeouts (git-fixes).\n- mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() (git-fixes).\n- mtd: rawnand: validate ONFI extended parameter page sections (git-fixes).\n- mtd: spinand: fix direct mapping creation sizes (stable-fixes).\n- mtd: spinand: repeat reading in regular mode if continuous reading fails (stable-fixes).\n- mtd: spinand: try a regular dirmap if creating a dirmap for continuous reading fails (stable-fixes).\n- mtd: ubi: Release device reference on busy detach (git-fixes).\n- mtd: ubi: skip programming unused bits in ubi headers (stable-fixes).\n- net: Add options as a flexible array to struct ip_tunnel_info (bsc#1274727).\n- net: mana: Add debug knob to skip TX timeout recovery reset (git-fixes).\n- net: mana: Add handler for sriov configure (bsc#1272756).\n- net: mana: Cap MSI-X vectors to the device MSI-X table size (git-fixes).\n- net: mana: Extend RX CQE coalescing up to 8 packets (git-fixes).\n- net: mana: Fall back to scattered pages for GDMA queues (git-fixes).\n- net: mana: force full-page RX buffers via ethtool private flag (bsc#1269792).\n- net: mana: refactor mana_get_strings() and mana_get_sset_count() to use switch (bsc#1269792).\n- net: mana: Route ring-buffer access through offset-based helpers (git-fixes).\n- net: tap: set skb-\u003edev before parsing virtio net header in tap_get_user_xdp() (git-fixes bsc#1274550).\n- net: thunderbolt: Count delivered packets in rx_packets and rx_bytes (git-fixes).\n- net: thunderbolt: Mark the connection down when bringing it up fails (git-fixes).\n- net: thunderbolt: Release the Rx HopID that was handed out on mismatch (git-fixes).\n- net: thunderbolt: Tear down DMA paths before stopping the rings (git-fixes).\n- net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup() (git-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: ipheth: fix carrier_work UAF on disconnect (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (git-fixes).\n- nfc: digital: clamp SENSF_RES length to the destination buffer (git-fixes).\n- nfc: digital: Do not dump a NULL response in command completion (git-fixes).\n- nfc: fdp: bound the device-reported read length and fix an skb leak (git-fixes).\n- nfc: llcp: avoid userspace overflow on invalid optlen (git-fixes).\n- nfc: llcp: bound SNL TLV parsing to the skb and add length checks (git-fixes).\n- nfc: llcp: bound the connect_sn TLV walk to the skb (git-fixes).\n- nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (git-fixes).\n- nfc: llcp: read llcp_sock-\u003elocal under the socket lock in getsockopt (git-fixes).\n- nfc: llcp: reject PDUs shorter than the LLCP header (git-fixes).\n- nfc: microread: validate target discovery payload lengths (git-fixes).\n- nfc: nci: fix double completion race in nci_data_exchange_complete (git-fixes).\n- nfc: nci: fix out-of-bounds write in nci_target_auto_activated() (git-fixes).\n- nfc: nci: fix uninit-value in the RF discover/activated NTF handlers (git-fixes).\n- nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing (git-fixes).\n- nfc: nci: free destination parameters when closing a connection (git-fixes).\n- nfc: pn533: hold a reference to the request skb during send_frame (git-fixes).\n- nfc: pn533: purge fragmented skbs during cleanup (git-fixes).\n- nfc: st21nfca: validate ATR_REQ length against the received frame (git-fixes).\n- nouveau/gem: reserve the bo in the info ioctl around the vma lookup (git-fixes).\n- nvme-tcp: fix usage of page_frag_cache (bsc#1267882).\n- nvmet-rdma: fix queue leak when connect backlog is exceeded (git-fixes).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- PCI/ASPM: Use pcie_capability_clear_and_set_word() for ASPM disable/restore (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (git-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (git-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI: Add ACS quirk for Pericom PI7C9X2G608 switches [12d8:2608] (git-fixes).\n- PCI: hv: Set irq_retrigger callback for the Hyper-V PCI MSI irqchip (git-fixes).\n- PCI: j721e: Fix incorrect max_lanes for J7200 (git-fixes).\n- PCI: meson: Fix GPIO state while requesting PERST# (git-fixes).\n- PCI: plda: Fix IRQ domain leaks in the error paths of plda_init_interrupts() (git-fixes).\n- PCI: plda: Fix use-after-free of event IRQs during teardown (git-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- pinctrl: bcm2835: Don't remove an unregistered GPIO chip (git-fixes).\n- pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip (git-fixes).\n- pinctrl: rockchip: Reset the pin count when recalculating SoC data (git-fixes).\n- platform/chrome: cros_ec_debugfs: Clean up console log on probe failure (git-fixes).\n- platform/chrome: cros_ec_debugfs: Unregister panic notifier (git-fixes).\n- platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count (git-fixes).\n- platform/chrome: sensorhub: Bound the EC-reported sensor number (git-fixes).\n- platform/chrome: sensorhub: Fix dropped timestamp events and log spam (git-fixes).\n- platform/chrome: sensorhub: Fix memory overread in ring handler (git-fixes).\n- platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL (git-fixes).\n- platform/surface: acpi-notify: Check ACPI companion before use (git-fixes).\n- platform/x86/amd/hsmp: Reject negative power cap writes in hwmon (git-fixes).\n- platform/x86: asus-wmi: fix resource leaks on probe failure (git-fixes).\n- platform/x86: dell-privacy: Fix race condition (git-fixes).\n- platform/x86: dell-wmi-base: Fix resource leak on module load failure (git-fixes).\n- platform/x86: dell-wmi-sysman: Don't hex dump attribute security buffer (git-fixes).\n- platform/x86: dell-wmi-sysman: Fix instance ID bounds (git-fixes).\n- platform/x86: hp-bioscfg: accept reduced ACPI packages from older HP BIOS (git-fixes).\n- platform/x86: hp-bioscfg: advance elem past consumed array elements (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store() (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read on empty password write (git-fixes).\n- platform/x86: hp-bioscfg: fix new_password_store() overwriting current_password (git-fixes).\n- platform/x86: hp-bioscfg: fix off-by-one write in hp_get_string_from_buffer() (git-fixes).\n- platform/x86: hp-bioscfg: fix ORD_LIST_ELEMENTS never being parsed (git-fixes).\n- platform/x86: hp-bioscfg: fix password encoding bounds check (git-fixes).\n- platform/x86: hp-bioscfg: warn on element type mismatch instead of failing (git-fixes).\n- platform/x86: ishtp_eclite: Fix ACPI device reference leak in probe error path (git-fixes).\n- platform/x86: ISST: Add a NULL check for sst_inst (git-fixes).\n- platform/x86: ISST: Just allow 2 bits for SST feature enable (git-fixes).\n- platform/x86: ISST: Return error during profile addition (git-fixes).\n- platform/x86: ISST: Use PP level enable mask (git-fixes).\n- platform/x86: ISST: Validate level in perf mask ioctls (git-fixes).\n- platform/x86: ISST: Validate logical CPU id and clos id (git-fixes).\n- platform/x86: ISST: Validate parameter for core power state (git-fixes).\n- platform/x86: ISST: Validate parameter for frequency and priority (git-fixes).\n- platform/x86: ISST: Validate socket ID in clos_assoc ioctl (git-fixes).\n- PM: hibernate: Fix memory leak in snapshot_write_next() error path (git-fixes).\n- PM: sleep: Fix off-by-one in wakelocks number limit check (git-fixes).\n- power: supply: bd99954: Drop bad register fields (git-fixes).\n- power: supply: bq27xxx: bq27z561: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq28z610: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq27520g4: fix REG_TTES address (git-fixes).\n- power: supply: bq256xx: drain usb_work before freeing the charger (git-fixes).\n- power: supply: bq24257: fix use-after-free on remove (git-fixes).\n- power: supply: bq25890: Fix power_supply reference leak (git-fixes).\n- power: supply: charger-manager: register regulators before exposing sysfs (git-fixes).\n- power: supply: cros_usbpd-charger: bound the EC-reported port count (git-fixes).\n- power: supply: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS (git-fixes).\n- power: supply: isp1704_charger: cancel work on remove (git-fixes).\n- power: supply: lp8727: fix use-after-free in lp8727_release_irq() (git-fixes).\n- power: supply: lp8788-charger: fix use-after-free on remove (git-fixes).\n- power: supply: max17040: drop incorrect I2C functionality check (git-fixes).\n- power: supply: max17040: propagate register read errors (git-fixes).\n- power: supply: max17040: synchronize work cancellation on suspend (git-fixes).\n- power: supply: qcom_battmgr: terminate the strings from firmware (git-fixes).\n- power: supply: rt9455: quiesce delayed work before teardown (git-fixes).\n- power: supply: sbs-battery: Use a per-device serial number buffer (git-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: twl4030_charger: cancel workers via devm (git-fixes).\n- power: supply: ucs1002: fix use-after-free on remove (git-fixes).\n- powercap: intel_rapl_tpmi: Handle PMU registration failure during probe (git-fixes).\n- powerpc/dt_cpu_ftrs: Set CPU_FTR_P11_PVR for Power11 and later processors (bsc#1263864 ltc#217835).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/pseries: Ensure vpa,slb_shadow \u0026 dtl are unregistered during crash (bsc#1271256).\n- powerpc/pseries: lparcfg - fix kbuf[] underflow (bsc#1274753 ltc#221289 bsc#1274754 ltc#221288 bsc#1274752\n  ltc#221290).\n- powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak (bsc#1274751 ltc#221105 bsc#1274750 ltc#221106).\n- powerpc/pseries: pci - logic bug (bsc#1274749 ltc#221282 bsc#1274755 ltc#221284 bsc#1274756 ltc#221283).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in non-uapi headers (bsc#1263864 ltc#217835).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in uapi headers (bsc#1263864 ltc#217835).\n- ppdev: prevent overflow when setting port timeout (git-fixes).\n- rapidio/tsi721: prevent a bad dereference in tsi721_db_dpc() (git-fixes).\n- rapidio: clear mport-\u003enet when rio_add_net() fails (git-fixes).\n- rapidio: mport_cdev: fix use-after-free in dma_req_free() (git-fixes).\n- RDMA/bnxt_re: Avoid displaying the kernel pointer (git-fixes).\n- RDMA/bnxt_re: Proper rollback if the ioremap fails (git-fixes).\n- RDMA/irdma: Remove redundant legacy_mode checks (git-fixes).\n- RDMA/mana_ib: drain QP references after partial table insertion (git-fixes).\n- RDMA/mana_ib: unify QP lookup table (git-fixes).\n- RDMA/mlx5: Fix integer overflow of user QP buffer size (git-fixes).\n- regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving dangling of_node pointer (git-fixes).\n- regulator: core: use system_freezable_wq for init complete work (git-fixes).\n- regulator: max8998_pmic_dt_parse_pdata: of_node_put on reg_np after ownership transferred to rdata (git-fixes).\n- regulator: qcom-refgen: correct the regulator type to CURRENT (git-fixes).\n- regulator: qcom-rpmh: Fix PMIC5 BOB bypass mode handling (git-fixes).\n- remoteproc: qcom: Fix glink-\u003enode reference leak in qcom_add_glink_subdev (git-fixes).\n- remoteproc: qcom_q6v5_adsp: Fix reference leak for device node (git-fixes).\n- remoteproc: scp: Fix device reference leak on failed lookup (git-fixes).\n- Revert \"drm/amdgpu: fix aperture mapping leak\" (git-fixes).\n- Revert \"media: v4l2-dev: fix error handling in __video_register_device()\" (git-fixes).\n- Revert \"net: thunderbolt: Enable end-to-end flow control also in transmit\" (git-fixes).\n- Revert \"thermal/drivers/hwmon: Cleanup coding style a bit\" (stable-fixes).\n- Revert \"wifi: mt76: Disable napi when removing device\" (git-fixes).\n- rpmsg: core: Fix incorrect return value documentation (git-fixes).\n- rpmsg: glink: smem: order FIFO read after availability check (git-fixes).\n- rtc: gamecube: check return value of devm_rtc_register_device() (git-fixes).\n- rtc: pcf8563: fix clock provider leak on unbind (git-fixes).\n- rtc: pcf85363: Add error checking to regmap calls in probe() (git-fixes).\n- rtc: rzn1: Disable alarm interrupt before reprogramming alarm registers (git-fixes).\n- rtc: rzn1: Fix weekday underflow when alarm crosses month boundary (git-fixes).\n- rtc: zynqmp: Return optional clock lookup errors (git-fixes).\n- s390/pkey: Check length in pkey_pckmo handler implementation (bsc#1270266).\n- s390/pkey: Check length in PKEY_VERIFYPROTK ioctl (bsc#1270267).\n- sched/psi: Create the psimon kthread outside of cgroup_mutex (bsc#1269134).\n- scsi: fnic: Abort timed-out NVMe LS requests (bsc#1236344).\n- scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths (bsc#1236344).\n- scsi: fnic: Add FDLS role handling for NVMe initiators (bsc#1236344).\n- scsi: fnic: Add the NVMe/FC transport path (bsc#1236344).\n- scsi: fnic: Advertise NVMe initiator service parameters (bsc#1236344).\n- scsi: fnic: Bump up version number (bsc#1236344).\n- scsi: fnic: Decode firmware role configuration (bsc#1236344).\n- scsi: fnic: Do not use GFP_ZERO for mempools (bsc#1236344).\n- scsi: fnic: Expose NVMe transport state in debugfs (bsc#1236344).\n- scsi: fnic: Handle NVMe LS frames in FDLS (bsc#1236344).\n- scsi: fnic: Make debug logging protocol independent (bsc#1236344).\n- scsi: fnic: Make fnic_queuecommand() easier to analyze (bsc#1236344).\n- scsi: fnic: Refactor in_remove flag and call to fnic_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Remove a useless struct mempool forward declaration (bsc#1236344).\n- scsi: fnic: Rename fnic_scsi_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Route completions and resets by initiator role (bsc#1236344).\n- scsi: fnic: Self-assignment of intr_time_type has no effect (bsc#1236344).\n- scsi: fnic: Send NVMe LS requests through FDLS (bsc#1236344).\n- scsi: fnic: Switch to use %ptSp (bsc#1236344).\n- scsi: fnic: Track NVMe transport statistics (bsc#1236344).\n- scsi: fnic: Use fnic_num for non-SCSI identifiers (bsc#1236344).\n- scsi: fnic: Use mempool for receive frames (bsc#1236344).\n- scsi: qla2xxx: Add support to report MPI FW state (bsc#1275737).\n- scsi: qla2xxx: Declare qla2xxx_mqueuecommand() static (bsc#1275737).\n- scsi: qla2xxx: Use nr_cpu_ids instead of NR_CPUS for qp_cpu_map allocation (bsc#1275737).\n- scsi: storvsc: Support manual scans for all Hyper-V targets (git-fixes).\n- sctp: avoid auth_enable sysctl UAF during netns teardown (git-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- serial: 8250_dma: Clear stale RX state on shutdown (git-fixes).\n- serial: amba-pl011: unprepare console clock on unregister (git-fixes).\n- serial: core: clear freed pointers on uart_register_driver() failure (git-fixes).\n- serial: imx: serialize imx_uart_ports lifetime (git-fixes).\n- serial: ma35d1: Fix OF node reference leaks in console init (git-fixes).\n- serial: qcom-geni: do not advance stale DMA completions (git-fixes).\n- serial: qcom-geni: fix TX DMA buffer flush (git-fixes).\n- serial: sc16is7xx: enable THRI before filling TX FIFO (git-fixes).\n- serial: sc16is7xx: rename EFR mutex with generic name (stable-fixes).\n- serial: sc16is7xx: use guards for simple mutex locks (stable-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb/client: handle overlapping allocated ranges in fallocate (bsc#1274902).\n- smb: client: harden POSIX SID length parsing (bsc#1273557).\n- smb: client: require net admin for CIFS SWN netlink (bsc#1273966).\n- smb: client: resolve SWN tcon from live registrations (bsc#1273872).\n- soc: fsl: qe: check platform_driver_register() in qe_ic_of_init() (git-fixes).\n- soc: qcom: rpmh-rsc: manage PM notifiers with devres (git-fixes).\n- soc: samsung: exynos-pmu: fix of_node refcount leak in exynos_get_pmu_regmap() (git-fixes).\n- software node: Fix software_node_get_reference_args() with index -1 (git-fixes).\n- soundwire: qcom: Fix port exhaustion check in stream_alloc_ports (git-fixes).\n- speakup: keyhelp: guard letter_offsets possible out-of-range indexing (git-fixes).\n- spi: bcm63xx-hsspi: disable clocks on resume failure (git-fixes).\n- spi: bcm63xx: disable clock on resume failure (git-fixes).\n- spi: bcmbca-hsspi: disable clocks on resume failure (git-fixes).\n- spi: davinci: switch to managed controller allocation (git-fixes).\n- spi: Fix DMA mapping ownership on partial map failure (git-fixes).\n- spi: img-spfi: don't disable runtime PM on DMA deferred probe (git-fixes).\n- spi: oc-tiny: switch to managed controller allocation (git-fixes).\n- spi: spi-cadence: enable SPI_CONTROLLER_MUST_TX (git-fixes).\n- spi: spi-cadence: Move TX FIFO full busy-wait into FIFO (git-fixes).\n- spi: spi-cadence: supports transmission with bits_per_word of 16 and 32 (stable-fixes).\n- spi: spi-fsl-dspi: Avoid setup_accel logic for DMA transfers (stable-fixes).\n- spi: sprd-adi: Fix probe succeeding without registering the controller (git-fixes).\n- staging: fbtft: Use sysfs_emit_at() to print to sysfs file (git-fixes).\n- staging: media: tegra-video: fix of_node_put() on VIP parse errors (git-fixes).\n- staging: media: tegra-video: vi: fix probe failure on skipped last port (git-fixes).\n- staging: octeon: add missing tasklet_kill in cvm_oct_tx_shutdown (git-fixes).\n- staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init() (git-fixes).\n- staging: rtl8723bs: fix missing shared-key auth challenge length check (git-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() (git-fixes).\n- staging: rtl8723bs: fix OOB read in WMM_param_handler() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: use kfree_sensitive() for key material (git-fixes).\n- staging: rtl8723bs: validate monitor transmit frame lengths (git-fixes).\n- staging: sm750fb: Add missing Kconfig dependency (git-fixes).\n- staging: sm750fb: gate dualview dataflow using g_dualview (git-fixes).\n- thermal/drivers/imx: Disable clock on runtime resume failure (git-fixes).\n- thermal/drivers/qoriq: Disable clock on resume failure (git-fixes).\n- thermal/drivers/rcar: Fix error checking in probe() (git-fixes).\n- thermal: intel: int3400: clean up ODVP on probe failures (git-fixes).\n- thermal: sysfs: switch to use scnprintf() to suppress truncation warning (git-fixes).\n- thunderbolt: Bound the DROM dual link port number before indexing sw-\u003eports (git-fixes).\n- thunderbolt: Fix bandwidth group reservation indexing (git-fixes).\n- thunderbolt: icm: Preserve USB4 proxy data-valid bit (git-fixes).\n- tlclk: if sscanf() fails, fall back to 0, not random value (git-fixes).\n- tpm: st33zp24: Return zero on status read failure (git-fixes).\n- tpm: st33zp24: Validate locality read result (git-fixes).\n- tpm: tpm_i2c_nuvoton: disable IRQ on wait timeout (git-fixes).\n- tty: clear cdev pointer after cdev_add() failure (git-fixes).\n- tty: hvc: restrict HVC_DCC to ARMv6+ and ARM64 (git-fixes).\n- tty: skip cdev_del() when no cdev is registered (git-fixes).\n- uio: Fix stale info pointer in failed registration path (git-fixes).\n- usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm() (git-fixes).\n- usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect (git-fixes).\n- usb: atm: usbatm: fix invalid ci_range initialization (git-fixes).\n- USB: c67x00: fix use-after-free in c67x00_add_iso_urb() (git-fixes).\n- usb: cdnsp: fix incorrect endian conversions for APB timeout register (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (git-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: core: sysfs: add lock to bos_descriptors_read() (stable-fixes).\n- usb: dwc2: add missing @remotewakeup kernel-doc parameter (git-fixes).\n- usb: dwc2: gadget: Exit partial power down state when changing USB pull-up (git-fixes).\n- usb: dwc3: clear forceRM when issuing EndTransfer (git-fixes).\n- usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: fix UAF when probe runs concurrent to dyn ID removal (git-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed (git-fixes).\n- usb: gadget: configfs: fix out-of-bounds read of qw_sign (git-fixes).\n- usb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths (git-fixes).\n- usb: gadget: f_fs: Prevent deadlock during ep0 read loop (git-fixes).\n- usb: gadget: f_midi: initialize work in f_midi_alloc() (git-fixes).\n- usb: gadget: f_ncm: Use unsigned int for ndp_index (git-fixes).\n- usb: gadget: f_tcm: fix deadlock in usbg_make_tpg() (git-fixes).\n- usb: gadget: f_uac1_legacy: remove broken string configfs attributes (git-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- USB: gadget: fsl-udc: fix dev_printk() device (git-fixes).\n- usb: gadget: midi2: Fix null-pointer dereference in f_midi2_free_ep_reqs (git-fixes).\n- usb: gadget: midi2: remove default configfs groups on teardown (git-fixes).\n- usb: gadget: pch_udc: remove excess kernel-doc member for registered (git-fixes).\n- usb: gadget: r8a66597: avoid double free of ep0_req in probe error path (git-fixes).\n- usb: gadget: snps_udc_plat: clean up PHY on probe deferral (git-fixes).\n- usb: gadget: u_audio: Fix use-after-free on sound card disconnect (git-fixes).\n- usb: gadget: uac: validate rate list length before storing (git-fixes).\n- USB: gadget: Use str_enable_disable-like helpers (stable-fixes).\n- usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and uvc_function_unbind() (git-fixes).\n- usb: ljca: bound bank_num in ljca_enumerate_gpio() (git-fixes).\n- usb: mtu3: allow system suspend during active gadget connection (git-fixes).\n- usb: musb: omap2430: clean up probe error handling (stable-fixes).\n- usb: musb: omap2430: Do not put borrowed of_node in probe (git-fixes).\n- usb: musb: omap2430: Fix use-after-free in omap2430_probe() (git-fixes).\n- USB: phy: fsl-usb: fix missing static keywords (git-fixes).\n- usb: renesas_usbhs: Fix power-off ordering on unbind (git-fixes).\n- USB: serial: digi_acceleport: fix port registration order (git-fixes).\n- USB: serial: ftdi_sio: add support for E+H FXA291 (stable-fixes).\n- USB: serial: option: add TDTECH MT5710-CN (stable-fixes).\n- USB: serial: option: fix slab OOB read in interrupt URB callback (git-fixes).\n- USB: serial: spcp8x5: drop broken carrier detect support (git-fixes).\n- USB: storage: add NO_ATA_1X quirk for Longmai USB Key (stable-fixes).\n- usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop (git-fixes).\n- usb: typec: qcom-pmic-typec: drain cc_debounce_dwork if port_start() fails (git-fixes).\n- usb: typec: qcom-pmic: cancel reset_work on stop (git-fixes).\n- usb: typec: tcpci: pass correct rx_type to tcpm_pd_receive() (git-fixes).\n- usb: typec: thunderbolt: Disable work before freeing tbt on remove (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: unregister debugfs entries on teardown (git-fixes).\n- usb: typec: ucsi: use UCSI_TIMEOUT_MS for sync command completion (git-fixes).\n- usb: usbfs: fix use-after-free of usb_device in usbdev_release() (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: xhci: Handle USB3 port events when there is one roothub (git-fixes).\n- vfs: Add a sysctl for automated deletion of dentry (bsc#1240890 bsc#1276586).\n- vt: add permission check for KDSKBMETA ioctl (stable-fixes).\n- vt: stabilize tty reference in kbd_keycode with tty_port_tty_get (stable-fixes).\n- w1: ds28e17: reject an oversize length on an I2C block read (git-fixes).\n- w1: ds2482: Fix signedness bug in ds2482_w1_triplet() (git-fixes).\n- watchdog: bd96801_wdt: Fix timeout for enabled WDG (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath6kl: avoid buffer overreads in WMI event handlers (git-fixes).\n- wifi: ath6kl: clamp assoc request/response lengths before subtracting IE offsets (git-fixes).\n- wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump (git-fixes).\n- wifi: ath11k: Avoid buffer overread in ath11k_wmi_tlv_op_rx() (git-fixes).\n- wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate (git-fixes).\n- wifi: ath11k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath12k: Avoid buffer overread in ath12k_wmi_op_rx() (git-fixes).\n- wifi: ath12k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: brcmfmac: Fix memory leak in brcmf_sdio_read_control() (git-fixes).\n- wifi: brcmfmac: fix P2P action frame handling without device vif (git-fixes).\n- wifi: brcmfmac: initialize SDIO data work before cleanup (git-fixes).\n- wifi: cfg80211: bound element ID read when checking non-inheritance (git-fixes).\n- wifi: cfg80211: cancel sched scan results work on unregister (git-fixes).\n- wifi: cfg80211: derive S1G beacon TSF from S1G fields (git-fixes).\n- wifi: cfg80211: reject unsupported PMSR FTM location requests (git-fixes).\n- wifi: cfg80211: validate PMSR FTM preamble range (git-fixes).\n- wifi: cfg80211: validate PMSR measurement type data (git-fixes).\n- wifi: ipw2100: fix potential memory leak in ipw2100_pci_init_one() (git-fixes).\n- wifi: iwlwifi: fix counter type in iwl_fwrt_dump_error_logs (git-fixes).\n- wifi: iwlwifi: guard against division by zero in iwl_dbg_tlv_alloc_fragments (git-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mei: pass correct argument to function (git-fixes).\n- wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser (git-fixes).\n- wifi: libertas: fix memory leak in helper_firmware_cb() (git-fixes).\n- wifi: mac80211: disconnect on CSA to channel 0 (git-fixes).\n- wifi: mac80211: fix fils_discovery double free on alloc failure (git-fixes).\n- wifi: mac80211: fix per-STA profile length in cross-link CSA parsing (git-fixes).\n- wifi: mac80211: fix unsol_bcast_probe_resp double free on alloc failure (git-fixes).\n- wifi: mac80211: free AP_VLAN bc_buf SKBs outside IRQ lock (git-fixes).\n- wifi: mac80211: send TWT teardown to peer after setup TX failure (git-fixes).\n- wifi: mac80211: skip default WMM setup for AP_VLAN links (git-fixes).\n- wifi: mac80211: skip unused probe response countdown offsets (git-fixes).\n- wifi: mt76: check txfree done event on the WED hw path (git-fixes).\n- wifi: mt76: fix 4th chain ACK RSSI bitmask in sta_poll (git-fixes).\n- wifi: mt76: fix ER-SU 106-tone RU check in RX rate decode (git-fixes).\n- wifi: mt76: fix HE DCM max-RU capability encoding (git-fixes).\n- wifi: mt76: fix non-AQL packet accounting for MLO stations (git-fixes).\n- wifi: mt76: fix stranded frames in mt76_txq_schedule_pending (git-fixes).\n- wifi: mt76: mt76x02: do not WARN on invalid rx descriptor length (git-fixes).\n- wifi: mt76: mt792x: Fix memory leak in SDIO TX path (git-fixes).\n- wifi: mt76: mt792x: fix use-after-free in mt76_rx_poll_complete (git-fixes).\n- wifi: mt76: mt7615: avoid waiting for mac work under the mt76 mutex (git-fixes).\n- wifi: mt76: mt7915: avoid nss underflow in mt7915_mcu_get_sta_nss (git-fixes).\n- wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear (git-fixes).\n- wifi: mt76: mt7915: fix double hif2 init on the non-WED path (git-fixes).\n- wifi: mt76: mt7915: fix ext PHY use-after-free on register error path (git-fixes).\n- wifi: mt76: mt7915: fix net_fill_forward_path for non-DBDC mt7986 (git-fixes).\n- wifi: mt76: mt7915: poll the correct SLP CTRL register for the second adie (git-fixes).\n- wifi: mt76: mt7915: release hif2 reference on probe IRQ failure (git-fixes).\n- wifi: mt76: mt7915: unlink TWT flow if the MCU rejects the agreement (git-fixes).\n- wifi: mt76: mt7915: unwind state on add_interface failure (git-fixes).\n- wifi: mt76: mt7915: use little-endian for bss_info_ra wire fields (git-fixes).\n- wifi: mt76: mt7915: write RX header translation bit to the correct register (git-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: mt7921: validate CLC firmware records (git-fixes).\n- wifi: mt76: mt7925: ensure tx headroom in usb_sdio_tx_prepare_skb (git-fixes).\n- wifi: mt76: mt7925: fix msg len mismatch between driver and firmware (git-fixes).\n- wifi: mt76: mt7925: update clc before setting sar power table (git-fixes).\n- wifi: mt76: mt7996: bound TLV walk in mt7996_mcu_get_chip_config (git-fixes).\n- wifi: mt76: mt7996: don't report a zero TX bitrate (git-fixes).\n- wifi: mt76: mt7996: fix capability of EHT-MCS 15 in MRU (git-fixes).\n- wifi: mt76: mt7996: fix reg addr remap when addr is 0 (git-fixes).\n- wifi: mt76: mt7996: reserve space for the CSA-abort countdown TLV (git-fixes).\n- wifi: mt76: mt7996: set MT76_MCU_RESET before waking MCU waiters on full reset (git-fixes).\n- wifi: mt76: mt7996: validate RX band_idx before dereferencing phys (git-fixes).\n- wifi: mt76: only consume the WO drop bit on WED v2 devices (git-fixes).\n- wifi: mt76: report data NSS for STBC frames in RX rate decode (git-fixes).\n- wifi: mwifiex: Detach sync cmd buffer on interrupted wait (git-fixes).\n- wifi: nl80211: free RNR data on MBSSID mismatch (git-fixes).\n- wifi: nl80211: validate nested MBSSID IE blobs (git-fixes).\n- wifi: p54: validate RX frame length in p54_rx_eeprom_readback() (git-fixes).\n- wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop (git-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtlwifi: pci: fix error path in rtl_pci_probe() (git-fixes).\n- wifi: rtlwifi: rtl8192du: check QoS TID before indexing tids (git-fixes).\n- wifi: rtlwifi: rtl8192du: Fix possible memory leak in rtl92du_init_sw_vars() (git-fixes).\n- wifi: rtw88: Fix potential memory leak in rtw_txq_push_skb() (git-fixes).\n- wifi: rtw88: pci: fix resource leak on failed NAPI setup (git-fixes).\n- wifi: rtw89: fix HE extended capability length check (git-fixes).\n- wifi: zd1211rw: reject secondary interfaces to prevent conflicts (git-fixes).\n- x86/virt/tdx: Print TDX module version during init (git-fixes).\n- x86/virt/tdx: Retrieve TDX module version (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_alloc_driver() failure (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_register_driver() failure (git-fixes).\n- xhci: fix lost bounce buffers on TDs spanning several ring segments (git-fixes).\n","status":"published","published":"2026-09-22T13:18:52Z","modified":"2026-09-30T18:23:11.183114716Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"SUSE-SU-2026:23887-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-68214: timers: Fix NULL function pointer race in timer_shutdown_sync() (bsc#1255225).\n- CVE-2025-68358: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() (bsc#1255531).\n- CVE-2025-68780: sched/deadline: only set free_cpus for online runqueues (bsc#1256671).\n- CVE-2025-71075: scsi: aic94xx: fix use-after-free in device removal path (bsc#1256629).\n- CVE-2026-23113: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (bsc#1258278).\n- CVE-2026-23306: scsi: pm8001: Fix use-after-free in pm8001_queue_command() (bsc#1260501).\n- CVE-2026-23348: cxl/mem: Clarify @host for devm_cxl_add_nvdimm() (bsc#1260577).\n- CVE-2026-31418: netfilter: ipset: drop logically empty buckets in mtype_del (bsc#1262073).\n- CVE-2026-31530: cxl/port: Fix use after free of parent_port in cxl_detach_ep() (bsc#1262756).\n- CVE-2026-31531: ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop() (bsc#1263004).\n- CVE-2026-43116: netfilter: ctnetlink: ensure safe access to master conntrack (bsc#1264619).\n- CVE-2026-43125: dlm: validate length in dlm_search_rsb_tree (bsc#1264541).\n- CVE-2026-43163: md/bitmap: fix GPF in write_page caused by resize race (bsc#1264335).\n- CVE-2026-43239: smb: client: prevent races in -\u003equery_interfaces() (bsc#1264444).\n- CVE-2026-43271: md-cluster: fix NULL pointer dereference in process_metadata_update (bsc#1264587).\n- CVE-2026-43299: btrfs: do not ASSERT() when the fs flips RO inside btrfs_repair_io_failure() (bsc#1264851).\n- CVE-2026-43331: x86/kexec: Disable KCOV instrumentation after load_segments() (bsc#1265132).\n- CVE-2026-43355: iio: light: bh1780: fix PM runtime leak on error path (bsc#1265036).\n- CVE-2026-43363: x86/apic: Disable x2apic on resume if the kernel expects so (bsc#1265068).\n- CVE-2026-43416: powerpc, perf: Check that current-\u003emm is alive before getting user callchain (bsc#1265121).\n- CVE-2026-43439: cgroup: fix race between task migration and iteration (bsc#1265141).\n- CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807).\n- CVE-2026-45860: netfilter: nf_conncount: increase the connection clean up limit to 64 (bsc#1266710).\n- CVE-2026-45897: netfilter: nft_counter: serialize reset with spinlock (bsc#1266897).\n- CVE-2026-45968: cpuidle: Skip governor when only one idle state is available (bsc#1267023).\n- CVE-2026-46007: hwmon: (powerz) Avoid cacheline sharing for DMA buffer (bsc#1267586).\n- CVE-2026-46070: md/raid5: validate payload size before accessing journal metadata (bsc#1267501).\n- CVE-2026-46107: dm-thin: fix metadata refcount underflow (bsc#1267612).\n- CVE-2026-46115: block: add pgmap check to biovec_phys_mergeable (bsc#1266874).\n- CVE-2026-46133: RDMA/rxe: Reject unknown opcodes before ICRC processing (bsc#1266928).\n- CVE-2026-46135: nvmet-tcp: remove redundant calls to nvmet_tcp_fatal_error() (bsc#1267373).\n- CVE-2026-46195: smb: client: validate dacloffset before building DACL pointers (bsc#1266860).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-52920: netfilter: xt_policy: fix strict mode inbound policy matching (bsc#1269013).\n- CVE-2026-52928: af_unix: Reject SIOCATMARK on non-stream sockets (bsc#1269010).\n- CVE-2026-52929: sctp: stream: fully roll back denied add-stream state (bsc#1269004).\n- CVE-2026-52935: xfrm: espintcp: do not reuse an in-progress partial send (bsc#1268979).\n- CVE-2026-52939: net/rds: fix NULL deref in rds_ib_send_cqe_handler() on masked atomic completion (bsc#1268972).\n- CVE-2026-52946: fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling (bsc#1269113).\n- CVE-2026-52977: futex: Prevent lockup in requeue-PI during signal/ timeout wakeup (bsc#1269242).\n- CVE-2026-52990: fsnotify: fix inode reference leak in fsnotify_recalc_mask() (bsc#1269108).\n- CVE-2026-52991: sched/psi: fix race between file release and pressure write (bsc#1269134).\n- CVE-2026-52994: vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting (bsc#1269126).\n- CVE-2026-53001: netfilter: xtables: restrict several matches to inet family (bsc#1269114).\n- CVE-2026-53031: bpf: Validate node_id in arena_alloc_pages() (bsc#1269380).\n- CVE-2026-53033: bpf, sockmap: Take state lock for af_unix iter (bsc#1269388).\n- CVE-2026-53034: bpf, sockmap: Fix af_unix null-ptr-deref in proto update (bsc#1269140).\n- CVE-2026-53048: gfs2: prevent NULL pointer dereference during unmount (bsc#1269162).\n- CVE-2026-53059: dm log: fix out-of-bounds write due to region_count overflow (bsc#1269655).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53076: bpf: Fix OOB in pcpu_init_value (bsc#1269695).\n- CVE-2026-53077: net/rds: Restrict use of RDS/IB to the initial network namespace (bsc#1269412).\n- CVE-2026-53089: bpf: Fix use-after-free in offloaded map/prog info fill (bsc#1269783).\n- CVE-2026-53091: net: account for encap headers in qdisc pkt len (bsc#1269530).\n- CVE-2026-53092: bpf: Fix linked reg delta tracking when src_reg == dst_reg (bsc#1269528).\n- CVE-2026-53094: bpf: Fix stale offload-\u003eprog pointer after constant blinding (bsc#1269965).\n- CVE-2026-53096: bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path (bsc#1269969).\n- CVE-2026-53109: powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy (bsc#1269417).\n- CVE-2026-53110: s390: always declare expoline thunks (bsc#1269985).\n- CVE-2026-53111: bpf: test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap (bsc#1269167).\n- CVE-2026-53114: perf: Extend the bit width of the arch-specific flag (bsc#1269999).\n- CVE-2026-53126: blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() (bsc#1269635).\n- CVE-2026-53129: fs/mbcache: cancel shrink work before destroying the cache (bsc#1269633).\n- CVE-2026-53142: drm/xe/display: fix oops in suspend/shutdown without display (bsc#1269402).\n- CVE-2026-53154: mm/hugetlb: restore reservation on error in hugetlb folio copy paths (bsc#1269665).\n- CVE-2026-53163: locking/rtmutex: Skip remove_waiter() when waiter is not enqueued (bsc#1269306).\n- CVE-2026-53180: timers/migration: Fix livelock in tmigr_handle_remote_up() (bsc#1269888).\n- CVE-2026-53207: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison (bsc#1269590).\n- CVE-2026-53219: netfilter: x_tables: avoid leaking percpu counter pointers (bsc#1269686).\n- CVE-2026-53220: netfilter: revalidate bridge ports (bsc#1269381).\n- CVE-2026-53223: net: guard timestamp cmsgs to real error queue skbs (bsc#1269301).\n- CVE-2026-53228: ipv6: sit: reload inner IPv6 header after GSO offloads (bsc#1269256).\n- CVE-2026-53238: netlabel: validate unlabeled address and mask attribute lengths (bsc#1269774).\n- CVE-2026-53264: net/sched: act_api: use RCU with deferred freeing for action lifecycle (bsc#1269238).\n- CVE-2026-53269: netfilter: synproxy: add mutex to guard hook reference counting (bsc#1269579).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53291: ALSA: hda/conexant: Fix missing error check for jack detection (bsc#1269697).\n- CVE-2026-53309: ocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison (bsc#1269815).\n- CVE-2026-53330: drm/amd/display: Fix out-of-bounds read in (bsc#1270090).\n- CVE-2026-53336: nvmem: layouts: onie-tlv: fix hang on unknown types (bsc#1270108).\n- CVE-2026-53337: net: bonding: fix NULL pointer dereference in bond_do_ioctl() (bsc#1270251).\n- CVE-2026-53341: fhandle: fix UAF due to unlocked -\u003emnt_ns read in may_decode_fh() (bsc#1270139).\n- CVE-2026-53353: hsr: Remove WARN_ONCE() in hsr_addr_is_self() (bsc#1270111).\n- CVE-2026-53365: vsock/virtio: fix zerocopy completion for multi-skb sends (bsc#1271365).\n- CVE-2026-63801: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (bsc#1272230).\n- CVE-2026-63803: hdlc_ppp: sync per-proto timers before freeing hdlc state (bsc#1272284).\n- CVE-2026-63804: gfs2: fix use-after-free in gfs2_qd_dealloc (bsc#1272287).\n- CVE-2026-63808: exfat: fix potential use-after-free in exfat_find_dir_entry() (bsc#1272260).\n- CVE-2026-63810: block: Avoid mounting the bdev pseudo-filesystem in userspace (bsc#1272297).\n- CVE-2026-63823: keys: Pin request_key_auth payload in instantiate paths (bsc#1272182).\n- CVE-2026-63828: apparmor: mediate the implicit connect of TCP fast open sendmsg (bsc#1272175).\n- CVE-2026-63860: RDMA/core: Prefer NLA_NUL_STRING (bsc#1272429).\n- CVE-2026-63865: bpf: Drop task_to_inode and inet_conn_established from lsm sleepable hooks (bsc#1272486).\n- CVE-2026-63868: net: garp: fix unsigned integer underflow in garp_pdu_parse_attr (bsc#1272497).\n- CVE-2026-63879: drm/amdgpu: fix amdgpu_hmm_range_get_pages (bsc#1272569).\n- CVE-2026-63887: scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf (bsc#1272385).\n- CVE-2026-63888: scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd() (bsc#1272390).\n- CVE-2026-63889: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (bsc#1272423).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63891: thunderbolt: property: Cap recursion depth in __tb_property_parse_dir() (bsc#1272641).\n- CVE-2026-63901: USB: serial: digi_acceleport: fix memory corruption with small endpoints (bsc#1272501).\n- CVE-2026-63917: ip6: vti: Use ip6_tnl.net in vti6_changelink() (bsc#1272904).\n- CVE-2026-63918: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname (bsc#1272905).\n- CVE-2026-63920: ipv6: validate extension header length before copying to cmsg (bsc#1272877).\n- CVE-2026-63921: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate() (bsc#1272918).\n- CVE-2026-63922,CVE-2026-63924: ipv6: exthdrs: refresh nh after handling HAO option (bsc#1272855).\n- CVE-2026-63925: macsec: fix replay protection at XPN lower-PN wrap (bsc#1273008).\n- CVE-2026-63926: bpf: sockmap: fix tail fragment offset in bpf_msg_push_data (bsc#1273019).\n- CVE-2026-63941: KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor (bsc#1272869).\n- CVE-2026-63969: ipv6: fix possible infinite loop in rt6_fill_node() (bsc#1272484).\n- CVE-2026-63970: vsock/virtio: bind uarg before filling zerocopy skb (bsc#1272673).\n- CVE-2026-63984: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() (bsc#1272865).\n- CVE-2026-63985: ethtool: eeprom: add more safeties to EEPROM Netlink fallback (bsc#1272963).\n- CVE-2026-63986: ethtool: tsinfo: don't pass ERR_PTR to genlmsg_cancel on prepare failure (bsc#1272969).\n- CVE-2026-63987: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (bsc#1272971).\n- CVE-2026-63990: bonding: refuse to enslave CAN devices (bsc#1273027).\n- CVE-2026-63992: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() (bsc#1272868).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-63995: ethtool: cmis: validate start_cmd_payload_size from module (bsc#1273033).\n- CVE-2026-63996: ethtool: cmis: require exact CDB reply length (bsc#1273032).\n- CVE-2026-63997: ethtool: module: avoid leaking a netdev ref on module flash errors (bsc#1273036).\n- CVE-2026-63998: ethtool: module: call ethnl_ops_complete() on module flash errors (bsc#1273037).\n- CVE-2026-63999: ethtool: rss: fix indir_table and hkey leak on get_rxfh failure (bsc#1273038).\n- CVE-2026-64000: net: hsr: fix potential OOB access in supervision frame handling (bsc#1273030).\n- CVE-2026-64002: ipv4: free net-\u003eipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (bsc#1273774).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64004: net/iucv: fix locking in .getsockopt (bsc#1273804).\n- CVE-2026-64005: net/smc: Do not re-initialize smc hashtables (bsc#1273831).\n- CVE-2026-64006: netfilter: nf_tables: fix dst corruption in same register operation (bsc#1273834).\n- CVE-2026-64007: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (bsc#1273105).\n- CVE-2026-64017: blk-mq: pop cached request if it is usable (bsc#1273770).\n- CVE-2026-64024: tcp: fix stale per-CPU tcp_tw_isn leak enabling ISN prediction (bsc#1273107).\n- CVE-2026-64033: RDMA/rtrs: Fix use-after-free in path file creation cleanup (bsc#1273134).\n- CVE-2026-64047: net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring (bsc#1273060).\n- CVE-2026-64048: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot (bsc#1273484).\n- CVE-2026-64052: block: bio-integrity: Fix null-ptr-deref in bio_integrity_map_user() (bsc#1272983).\n- CVE-2026-64053: block: don't overwrite bip_vcnt in bio_integrity_copy_user() (bsc#1272985).\n- CVE-2026-64054: net: shaper: reject duplicate leaves in GROUP request (bsc#1272894).\n- CVE-2026-64055: net: ethernet: cortina: Carry over frag counter (bsc#1272893).\n- CVE-2026-64056: net: ethernet: cortina: Make RX SKB per-port (bsc#1272502).\n- CVE-2026-64071: nvme-pci: fix use-after-free in nvme_free_host_mem() (bsc#1273486).\n- CVE-2026-64073: irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT (bsc#1273490).\n- CVE-2026-64088: batman-adv: tt: fix negative tt_buff_len (bsc#1273463).\n- CVE-2026-64089: batman-adv: tt: fix negative last_changeset_len (bsc#1272513).\n- CVE-2026-64093: batman-adv: tp_meter: directly shut down timer on cleanup (bsc#1273461).\n- CVE-2026-64099: drm/v3d: Fix use-after-free of CPU job query arrays on error path (bsc#1273465).\n- CVE-2026-64102: RDMA/siw: Reject MPA FPDU length underflow before signed receive math (bsc#1272516).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64109: af_unix: Fix UAF read of tail-\u003elen in unix_stream_data_wait() (bsc#1273748).\n- CVE-2026-64111: lsm: hold cred_guard_mutex for lsm_set_self_attr() (bsc#1273740).\n- CVE-2026-64112: rbd: eliminate a race in lock_dwork draining on unmap (bsc#1273741).\n- CVE-2026-64113: ixgbevf: fix use-after-free in VEPA multicast source pruning (bsc#1272262).\n- CVE-2026-64114: ipv4: raw: reject IP_HDRINCL packets with ihl \u003c 5 (bsc#1273742).\n- CVE-2026-64115: vsock/vmci: fix UAF when peer resets connection during handshake (bsc#1273745).\n- CVE-2026-64118: qed: fix double free in qed_cxt_tables_alloc() (bsc#1273749).\n- CVE-2026-64119: l2tp: use list_del_rcu in l2tp_session_unhash (bsc#1273746).\n- CVE-2026-64121: net: ifb: report ethtool stats over num_tx_queues (bsc#1273743).\n- CVE-2026-64125: net: bcmgenet: keep RBUF EEE/PM disabled (bsc#1272346).\n- CVE-2026-64131: mm/memory: fix spurious warning when unmapping device-private/exclusive pages (bsc#1274063).\n- CVE-2026-64146: erofs: fix metabuf leak in inode xattr initialization (bsc#1273681).\n- CVE-2026-64147: pds_core: fix debugfs_lookup dentry leak and error handling (bsc#1273119).\n- CVE-2026-64148: pds_core: fix error handling in pdsc_devcmd_wait (bsc#1273956).\n- CVE-2026-64162: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (bsc#1272366).\n- CVE-2026-64164: btrfs: tracepoints: fix sleep while in atomic context in btrfs_sync_file() (bsc#1273957).\n- CVE-2026-64177: phonet/pep: disable BH around forwarded sk_receive_skb() (bsc#1272148).\n- CVE-2026-64179: net: wwan: iosm: fix potential memory leaks in ipc_imem_init() (bsc#1272149).\n- CVE-2026-64180: mm/memory_hotplug: fix memory block reference leak on remove (bsc#1273679).\n- CVE-2026-64184: mm/damon/sysfs-schemes: call missing mem_cgroup_iter_break() (bsc#1272199).\n- CVE-2026-64185: sysfs: don't remove existing directory on update failure (bsc#1272200).\n- CVE-2026-64190: net: team: fix NULL pointer dereference in team_xmit during mode change (bsc#1272210).\n- CVE-2026-64192: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized (bsc#1272213).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64214: powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise()\n  (bsc#1272799).\n- CVE-2026-64217: netfs: Fix overrun check in netfs_extract_user_iter() (bsc#1272798).\n- CVE-2026-64222: octeontx2-pf: avoid double free of pool-\u003estack on AQ init failure (bsc#1272788).\n- CVE-2026-64224: octeontx2-pf: fix double free in rvu_rep_rsrc_init() (bsc#1272804).\n- CVE-2026-64225: octeontx2-af: CGX: add bounds check to cgx_speed_mbps index (bsc#1272786).\n- CVE-2026-64232: block: recompute nr_integrity_segments in blk_insert_cloned_request (bsc#1272791).\n- CVE-2026-64239: mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() (bsc#1273898).\n- CVE-2026-64244: drivers/base/memory: set mem-\u003ealtmap after successful device registration (bsc#1273812).\n- CVE-2026-64253: kernel/fork: clear PF_BLOCK_TS in copy_process() (bsc#1273904).\n- CVE-2026-64256: xfs: don't wrap around quota ids in dqiterate (bsc#1273271).\n- CVE-2026-64265: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req (bsc#1273947).\n- CVE-2026-64268: RDMA/siw: bound Read Response placement to the RREAD length (bsc#1273276).\n- CVE-2026-64269: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg (bsc#1273280).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64286: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU (bsc#1274058).\n- CVE-2026-64287: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU (bsc#1273325).\n- CVE-2026-64294: mm: do file ownership checks with the proper mount idmap (bsc#1273525).\n- CVE-2026-64296: exfat: bound uniname advance in exfat_find_dir_entry() (bsc#1273975).\n- CVE-2026-64298: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (bsc#1273550).\n- CVE-2026-64300: perf/aux: Fix page UAF in map_range() (bsc#1273852).\n- CVE-2026-64307: crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG) (bsc#1273567).\n- CVE-2026-64315: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1274028).\n- CVE-2026-64316: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1273598).\n- CVE-2026-64317: isofs: bound Rock Ridge symlink components to the SL record (bsc#1273936).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64321: nvme: target: rdma: fix ndev refcount leak on queue connect (bsc#1273864).\n- CVE-2026-64322: udf: validate sparing table length as an entry count, not a byte count (bsc#1273958).\n- CVE-2026-64323: udf: validate VAT header length against the VAT inode size (bsc#1273305).\n- CVE-2026-64326: block: skip sync_blockdev() on surprise removal in bdev_mark_dead() (bsc#1273312).\n- CVE-2026-64327: usb: gadget: f_fs: Initialize epfile-\u003ein early to fix endpoint direction checks (bsc#1273283).\n- CVE-2026-64354: bpf: Validate BTF repeated field counts before expansion (bsc#1274060).\n- CVE-2026-64355: bpf: Reject fragmented frames in devmap (bsc#1273422).\n- CVE-2026-64364: HID: multitouch: fix out-of-bounds bit access on mt_io_flags (bsc#1273495).\n- CVE-2026-64368: mm/slab: do not limit zeroing to orig_size when only red zoning is enabled (bsc#1273997).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64375: proc: protect ptrace_may_access() with exec_update_lock (FD links) (bsc#1273868).\n- CVE-2026-64378: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (bsc#1273603).\n- CVE-2026-64381: smb: client: Fix next buffer leak in receive_encrypted_standard() (bsc#1273860).\n- CVE-2026-64382: smb: client: fix double-free in SMB2_open() replay (bsc#1273291).\n- CVE-2026-64383: smb: client: fix double-free in SMB2_flush() replay (bsc#1273426).\n- CVE-2026-64384: smb: client: fix change notify replay double-free (bsc#1274541).\n- CVE-2026-64385: smb: client: fix double-free in SMB2_ioctl() replay (bsc#1274539).\n- CVE-2026-64386: smb: client: fix query_info() replay double-free (bsc#1274543).\n- CVE-2026-64387: smb: client: fix query directory replay double-free (bsc#1274545).\n- CVE-2026-64411: netfilter: ebtables: terminate table name before find_table_lock() (bsc#1274077).\n- CVE-2026-64412: netfilter: ebtables: module names must be null-terminated (bsc#1273780).\n- CVE-2026-64415: mm/swap: add cond_resched() in swap_reclaim_full_clusters to prevent softlockup (bsc#1273317).\n- CVE-2026-64416: mm: swap_cgroup: fix NULL deref in lookup_swap_cgroup_id on swapless host (bsc#1273286).\n- CVE-2026-64423: ipv4: igmp: remove multicast group from hash table on device destruction (bsc#1274274).\n- CVE-2026-64434: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref (bsc#1273880).\n- CVE-2026-64436: net: af_key: initialize alg_key_len for IPComp states (bsc#1274277).\n- CVE-2026-64450: tipc: fix out-of-bounds read in broadcast Gap ACK blocks (bsc#1273523).\n- CVE-2026-64452: 6lowpan: fix NHC entry use-after-free on error path (bsc#1273460).\n- CVE-2026-64458: mm/damon/ops-common: handle extreme intervals in damon_hot_score() (bsc#1273788).\n- CVE-2026-64463: usb: typec: tcpci_rt1711h: unregister TCPCI port with devres (bsc#1273273).\n- CVE-2026-64472: vfio/mlx5: Fix racy bitfields and tighten struct layout (bsc#1274075).\n- CVE-2026-64477: x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled (bsc#1274264).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64518: tcp: Fix out-of-bounds access for twsk in tcp_ao_established_key() (bsc#1273524).\n- CVE-2026-64519: NFSD: Fix infinite loop in layout state revocation (bsc#1274252).\n- CVE-2026-64526: ethtool: tsconfig: fix missing ethnl_ops_complete() (bsc#1274052).\n- CVE-2026-64534: nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error (bsc#1273803).\n- CVE-2026-64535: nvmet-tcp: Fix potential UAF when ddgst mismatch (bsc#1273809).\n- CVE-2026-64537: bridge: cfm: reject invalid CCM interval at configuration time (bsc#1273289).\n- CVE-2026-64538: ipv6: Fix null-ptr-deref in fib6_nh_mtu_change() (bsc#1273335).\n- CVE-2026-64541: net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket (bsc#1273303).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64543: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() (bsc#1273311).\n- CVE-2026-64545: net, bpf: check master for NULL in xdp_master_redirect() (bsc#1273318).\n- CVE-2026-64548: bpf, sockmap: reject overflowing copy + len in bpf_msg_push_data() (bsc#1273337).\n- CVE-2026-64551: sctp: validate STALE_COOKIE cause length before reading staleness (bsc#1273813).\n- CVE-2026-64552: virtio-net: fix len check in receive_big() (bsc#1273323).\n- CVE-2026-64553: net: psample: fix info leak in PSAMPLE_ATTR_DATA (bsc#1273336).\n- CVE-2026-64554: netfilter: bridge: fix stale prevhdr pointer in br_ip6_fragment() (bsc#1273340).\n- CVE-2026-64555: KVM: arm64: nv: Fix SPSR_EL2 restore in kvm_hyp_handle_mops() (bsc#1273331).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64563: rhashtable: clear stale iter-\u003ep on table restart (bsc#1273995).\n- CVE-2026-64567: btrfs: reject free space cache with more entries than pages (bsc#1274006).\n- CVE-2026-64569: mpls: fix NULL deref in mpls_valid_fib_dump_req() on CONFIG_INET=n (bsc#1274009).\n- CVE-2026-64572: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (bsc#1274014).\n- CVE-2026-64576: nexthop: initialize extack in nh_res_bucket_migrate() (bsc#1274030).\n- CVE-2026-64577: gtp: check skb_pull_data() return in gtp1u_send_echo_resp() (bsc#1274031).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64581: xfrm: fix sk_dst_cache double-free in xfrm_user_policy() (bsc#1274041).\n- CVE-2026-64582: RDMA/rxe: Fix a use-after-free problem in rxe_mmap (bsc#1274040).\n- CVE-2026-64586: wifi: brcmfmac: drain bus_reset work on device removal (bsc#1274492).\n- CVE-2026-68082: libceph: fix two unsafe bare decodes in decode_lockers() (bsc#1274581).\n- CVE-2026-68086: mm/khugepaged: write all dirty file folios when collapsing (bsc#1274713).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68105: drm/amdgpu: Fix kernel panic during driver load failure (bsc#1274849).\n- CVE-2026-68116: vxlan: mdb: Fix source list corruption on a failed replace (bsc#1274876).\n- CVE-2026-68117: tipc: clear sock-\u003esk on the failed-insert path in tipc_sk_create() (bsc#1274881).\n- CVE-2026-68120: rtase: Workaround for TX hang caused by hardware packet parsing (bsc#1274887).\n- CVE-2026-68121: pppoe: reload header pointer after dev_hard_header() (bsc#1274888).\n- CVE-2026-68123: openvswitch: fix GSO userspace truncation underflow (bsc#1275169).\n- CVE-2026-68124: mctp: serial: handle zero-length frames to prevent rx buffer overflow (bsc#1275192).\n- CVE-2026-68127: ila: reload IPv6 header after pskb_may_pull in checksum adjust (bsc#1275237).\n- CVE-2026-68128: ice: reject out-of-range ptype in ice_parser_profile_init (bsc#1275238).\n- CVE-2026-68129: gve: fix Rx queue stall on alloc failure (bsc#1275517).\n- CVE-2026-68132: super: fix emergency thaw deadlock on frozen block devices (bsc#1275553).\n- CVE-2026-68133: ice: fix PTP Call Trace during PTP release (bsc#1275555).\n- CVE-2026-68135: net: hip04: fix RX buffer leak on build_skb failure (bsc#1275557).\n- CVE-2026-68136: net: gro: fix double aggregation of flush-marked skbs (bsc#1275474).\n- CVE-2026-68138: net/sched: serialize qdisc_rtab_list against concurrent get/put (bsc#1274941).\n- CVE-2026-68139: net/mlx5e: Use sender devcom for MPV master-up (bsc#1275578).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68142: geneve: require CAP_NET_ADMIN in the device netns for changelink (bsc#1275582).\n- CVE-2026-68143: net: slip: serialize receive against buffer reallocation (bsc#1275583).\n- CVE-2026-68144: phonet: pep: fix use-after-free in pep_get_sb() (bsc#1275481).\n- CVE-2026-68145: iomap: fix out-of-bounds bitmap_set() with zero-length range (bsc#1275584).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68149: fs: preserve ACL_DONT_CACHE state in forget_cached_acl() (bsc#1275294).\n- CVE-2026-68152: amt: fix use-after-free in AMT delayed works (bsc#1275300).\n- CVE-2026-68153: libceph: remove debugfs files before client teardown (bsc#1275301).\n- CVE-2026-68154: libceph: reject zero bucket types in crush_decode (bsc#1275303).\n- CVE-2026-68155: libceph: Reject monmaps advertising zero monitors (bsc#1275304).\n- CVE-2026-68156: libceph: refresh auth-\u003eauthorizer_buf{,_len} after authorizer update (bsc#1275305).\n- CVE-2026-68157: libceph: guard missing CRUSH type name lookup (bsc#1275306).\n- CVE-2026-68158: libceph: Fix multiplication overflow in decode_new_up_state_weight() (bsc#1275307).\n- CVE-2026-68159: libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE (bsc#1275470).\n- CVE-2026-68161: sctp: close UDP tunnel sockets during netns teardown (bsc#1274892).\n- CVE-2026-68164: mm/damon/core: disallow overlapping input ranges for damon_set_regions() (bsc#1274955).\n- CVE-2026-68165: mm/damon/core: validate ranges in damon_set_regions() (bsc#1274927).\n- CVE-2026-68166: userfaultfd: prevent registration of special VMAs (bsc#1274930).\n- CVE-2026-68169: mptcp: pm: userspace: fix use-after-free in get_local_id (bsc#1274952).\n- CVE-2026-68183: firmware: stratix10-svc: fix memory leaks and list corruption bugs (bsc#1274957).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68205: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() (bsc#1274934).\n- CVE-2026-68238: drm/amdgpu: Release VFCT ACPI table reference (bsc#1275704).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68267: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists (bsc#1275139).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68284: bpf, sockmap: Fix cork use-after-free in tcp_bpf_sendmsg() (bsc#1275970).\n- CVE-2026-68286: drop_monitor: perform u64_stats updates under IRQ-disabled section (bsc#1275973).\n- CVE-2026-68288: net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD (bsc#1275975).\n- CVE-2026-68289: tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream() (bsc#1275976).\n- CVE-2026-68293: net/mlx5: Fix MCIA register buffer overflow on 32 dword reads (bsc#1275091).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68296: net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM (bsc#1275045).\n- CVE-2026-68297: tipc: fix u16 MTU truncation in media and bearer MTU validation (bsc#1275040).\n- CVE-2026-68299: vmxnet3: fix BUG_ON in vmxnet3_get_hdr_len() for Geneve packets (bsc#1275088).\n- CVE-2026-68300: sctp: auth: verify auth requirement when auth_chunk is NULL (bsc#1275083).\n- CVE-2026-68302: amt: re-read skb header pointers after every pull (bsc#1275081).\n- CVE-2026-68313: tipc: fix infinite loop in __tipc_nl_compat_dumpit (bsc#1274665).\n- CVE-2026-68315: sctp: validate stream count in sctp_process_strreset_inreq() (bsc#1274662).\n- CVE-2026-68319: pds_core: fix deadlock between reset thread and remove (bsc#1274657).\n- CVE-2026-68320: sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid (bsc#1274659).\n- CVE-2026-68321: net: txgbe: fix FDIR filter leak on remove (bsc#1274652).\n- CVE-2026-68322: rds: Fix inet6_addr_lst NULL dereference when IPv6 is disabled (bsc#1274656).\n- CVE-2026-68325: iommu/amd: Bound the early ACPI HID map (bsc#1274651).\n- CVE-2026-68328: nfp: Check resource mutex allocation (bsc#1274646).\n- CVE-2026-68329: iommu/amd: Wait for completion instead of returning early in iommu_completion_wait() (bsc#1274645).\n- CVE-2026-68331: dpaa2-eth: put MAC endpoint device on disconnect (bsc#1274642).\n- CVE-2026-68333: dpaa2-switch: put MAC endpoint device on disconnect (bsc#1274644).\n- CVE-2026-68335: rds: drop incoming messages that cross network namespace boundaries (bsc#1274640).\n- CVE-2026-68336: bonding: fix devconf_all NULL dereference when IPv6 is disabled (bsc#1274639).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68375: bnxt_en: Handle partially initialized auxiliary devices (bsc#1274835).\n- CVE-2026-68377: net/sched: act_tunnel_key: Defer dst_release to RCU callback (bsc#1274831).\n- CVE-2026-68386: bpf, sockmap: Reject unhashed UDP sockets on sockmap update (bsc#1274814).\n- CVE-2026-68393: Bluetooth: hci_sync: extend conn_hash lookup critical sections (bsc#1274904).\n- CVE-2026-68395: ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered (bsc#1274900).\n- CVE-2026-68397: net/iucv: take a reference on the socket found in afiucv_hs_rcv() (bsc#1274898).\n- CVE-2026-68398: ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF (bsc#1274908).\n- CVE-2026-68399: bpf: Fix UAF in sock clone early bailouts (bsc#1274897).\n- CVE-2026-68408: wifi: cfg80211: convert pmsr_free_wk to wiphy_work to fix deadlock (bsc#1274709).\n- CVE-2026-68417: RDMA/siw: publish QP after initialization (bsc#1274696).\n- CVE-2026-68418: RDMA/irdma: Prevent user-triggered null deref on QP create (bsc#1274690).\n- CVE-2026-68419: RDMA/irdma: Prevent rereg_mr for non-mem regions (bsc#1274698).\n- CVE-2026-68422: btrfs: fix root leak if its reloc root is unexpected in merge_reloc_roots() (bsc#1274706).\n- CVE-2026-68425: IB/mad: Drop unmatched RMPP responses before reassembly (bsc#1274700).\n- CVE-2026-68426: xfrm: fix stale skb-\u003eprev after async crypto steals a GSO segment (bsc#1274705).\n- CVE-2026-68432: vxlan: require CAP_NET_ADMIN in the device netns for changelink (bsc#1274800).\n- CVE-2026-68433: libceph: bound get_version reply decode to front len (bsc#1274801).\n- CVE-2026-68442: btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps (bsc#1274773).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68450: btrfs: free mapping node on duplicate reloc root insert (bsc#1274834).\n- CVE-2026-68470: wifi: mac80211: validate extension-frame layout before RX (bsc#1276500).\n- CVE-2026-68480: x86/bugs: Make Safe-RET robust against interrupt injection (bsc#1274208).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72020: ipvs: reset full ip_vs_seq structs in ip_vs_conn_new (bsc#1275506).\n- CVE-2026-72022: llc: fix SAP refcount leak in llc_ui_autobind() (bsc#1276785).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72032: net/mlx5: HWS, fix matcher leak on resize target setup failure (bsc#1276955).\n- CVE-2026-72034: fhandle: reject detached mounts in capable_wrt_mount() (bsc#1276957).\n- CVE-2026-72035: net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1276961).\n- CVE-2026-72036: net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1277034).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72046: gve: fix header buffer corruption with header-split and HW-GRO (bsc#1275519).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72069: locking/rt: Fix the incorrect RCU protection in rt_spin_unlock() (bsc#1275528).\n- CVE-2026-72072: net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete (bsc#1277155).\n- CVE-2026-72083: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE (bsc#1275535).\n- CVE-2026-72084: scsi: target: core: Generate correct identifiers for PR OUT transport IDs (bsc#1275540).\n- CVE-2026-72100: dm-integrity: fix a bug if the bio is out of limits (bsc#1277311).\n- CVE-2026-72101: dm-integrity: fix leaking uninitialized kernel memory (bsc#1276831).\n- CVE-2026-72103: dm: avoid leaking the caller's thread keyring via the table device file (bsc#1277315).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72132: NFS: Charge unstable writes by request size, not folio size (bsc#1277551).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72137: xfrm: nat_keepalive: avoid double free on send error (bsc#1275587).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72176: mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error (bsc#1277230).\n- CVE-2026-72177: mm/damon/sysfs-schemes: fix dir put orders in access_pattern_add_dirs() (bsc#1277227).\n- CVE-2026-72217: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing (bsc#1275655).\n- CVE-2026-72221: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (bsc#1275665).\n- CVE-2026-72222: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (bsc#1275669).\n- CVE-2026-72234: batman-adv: access unicast_ttvn skb-\u003edata only after skb realloc (bsc#1275672).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72251: netfilter: nf_nat_sip: reload possible stale data pointer (bsc#1275827).\n- CVE-2026-72254: netfilter: nft_fib: reject fib expression on the netdev egress hook (bsc#1277204).\n- CVE-2026-72280: KVM: arm64: nv: Drop bogus WARN for write to ZCR_EL2 (bsc#1277726).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72288: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling (bsc#1275886).\n- CVE-2026-72289: KVM: arm64: vgic: Check the interrupt is still ours before migrating it (bsc#1275905).\n- CVE-2026-72296: net: ife: require ETH_HLEN to be pullable in ife_decode() (bsc#1275923).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72307: mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace() (bsc#1277160).\n- CVE-2026-72308: mlxsw: fix refcount leak in mlxsw_sp_port_lag_join() (bsc#1277159).\n- CVE-2026-72317: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (bsc#1275925).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72337: Bluetooth: 6lowpan: avoid untracked enable work (bsc#1277773).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72341: net/mlx5e: Fix publication race for priv-\u003echannel_stats[] (bsc#1277660).\n- CVE-2026-72342: net/mlx5e: Fix HV VHCA stats agent registration race (bsc#1277775).\n- CVE-2026-72343: net/mlx5e: Fix HV VHCA stats zero-sized buffer allocation (bsc#1277776).\n- CVE-2026-72345: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback (bsc#1277782).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72366: netfs: Fix netfs_create_write_req() to handle async cache object creation (bsc#1276333).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72389: bridge: stp: Fix a potential use-after-free when deleting a bridge (bsc#1273869).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72414: net: dsa: sja1105: round up PTP perout pin duration (bsc#1278039).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72430: net/sched: act_ct: fix nf_connlabels leak on two error paths (bsc#1277118).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72464: xprtrdma: Post receive buffers after RPC completion (bsc#1277069).\n- CVE-2026-72466: xprtrdma: Fix bcall rep leak and unbounded peek (bsc#1277057).\n- CVE-2026-72467: xprtrdma: Check frwr_wp_create() during connect (bsc#1277059).\n- CVE-2026-72468: xprtrdma: Initialize re_id before removal registration (bsc#1277062).\n- CVE-2026-72469: xprtrdma: Fix ep kref imbalance on ADDR_CHANGE (bsc#1277047).\n- CVE-2026-72473: xprtrdma: Avoid 250 ms delay on backlog wakeup (bsc#1277037).\n- CVE-2026-72485: coresight: platform: defer connection counter increment until alloc succeeds (bsc#1276771).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-72494: RDMA/irdma: Replace waitqueue and flag with completion (bsc#1276941).\n- CVE-2026-72495: RDMA/bnxt_re: Avoid repeated requests to allocate WC pages (bsc#1276937).\n- CVE-2026-72497: RDMA/bnxt_re: Add a max slot check for SQ (bsc#1276913).\n- CVE-2026-72499: RDMA/bnxt_re: Free CQ toggle page after firmware teardown (bsc#1276551).\n- CVE-2026-72500: RDMA/bnxt_re: Free SRQ toggle page after firmware teardown (bsc#1276552).\n- CVE-2026-72501: RDMA/bnxt_re: Initialize dpi variable to zero (bsc#1276546).\n- CVE-2026-72502: tcp: ipv6: clamp default adverting MSS to avoid GSO_BY_FRAGS (0xFFFF) (bsc#1276542).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74269: bnxt: fix head underflow on XDP head-grow (bsc#1276507).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74286: net: pfcp: allocate per-cpu tstats for PFCP netdevs (bsc#1276471).\n- CVE-2026-74296: RDMA/mlx5: Release the HW-provided UAR index rather than the SW one (bsc#1276452).\n- CVE-2026-74297: RDMA/mlx5: Fix undefined shift of user RQ WQE size (bsc#1276446).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74316: NFSD: Handle layout stid in nfsd4_drop_revoked_stid() (bsc#1276870).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74318: btrfs: fix deadlock cloning inline extent when using flushoncommit (bsc#1276864).\n- CVE-2026-74321: btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() (bsc#1277202).\n- CVE-2026-74334: RDMA/nldev: Fix locking when accessing mr-\u003epd (bsc#1277095).\n- CVE-2026-74345: RDMA/siw: Fix endpoint/socket association handling (bsc#1277285).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74394: RDMA/srpt: fix integer overflow in immediate data length check (bsc#1277408).\n- CVE-2026-74395: RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference (bsc#1277077).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74474: vxlan: use pskb_network_may_pull() for transmit path header pulls (bsc#1276335).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74481: mm/page_reporting: use system_freezable_wq to fix UAF during suspend (bsc#1276355).\n- CVE-2026-74482: mm/huge_memory: unlock i_mmap_rwsem before releasing after-split folios (bsc#1276346).\n- CVE-2026-74495: igbvf: Fix leak in TX DMA error cleanup (bsc#1275864).\n- CVE-2026-74496: fou: Fix use-after-free in fou_create() (bsc#1275867).\n- CVE-2026-74510: Bluetooth: mgmt: fix UAF in pair command cancellation (bsc#1275950).\n- CVE-2026-74512: audit: fix potential use-after-free in audit_del_rule() (bsc#1275954).\n- CVE-2026-74513: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister (bsc#1275956).\n- CVE-2026-74517: KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs (bsc#1276258).\n- CVE-2026-74518: mm/hugetlb: fix list corruption in allocate_file_region_entries() (bsc#1275798).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74527: octeontx2-af: Block VFs from clobbering special CGX PKIND state (bsc#1275805).\n- CVE-2026-74533: Bluetooth: ISO: fix race of kfree vs kref_get_unless_zero (bsc#1275804).\n- CVE-2026-74534: Bluetooth: ISO: Fix data-race on iso_pi(sk) in socket and HCI event paths (bsc#1275801).\n- CVE-2026-74535: Bluetooth: ISO: avoid deadlocks in iso_sock_timeout (bsc#1275812).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74537: Bluetooth: ISO: hold sk properly in iso_conn_ready (bsc#1275687).\n- CVE-2026-74545: rtase: fix double free of multi-frag skb on DMA map failure (bsc#1275679).\n- CVE-2026-74548: forcedeth: fix UAF of txrx_stats in nv_remove (bsc#1275695).\n- CVE-2026-74550: net: do not send ICMP/NDISC Redirects when peer allocation fails (bsc#1275688).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74556: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer (bsc#1275696).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74563: rds: tcp: hold the RCU lock across ipv6_chk_addr() in rds_tcp_laddr_check() (bsc#1275574).\n- CVE-2026-74566: keys: make keyring key-chunk byte order agree with keyring_diff_objects() (bsc#1275566).\n- CVE-2026-74567: keys: fix out-of-bounds read in keyring_get_key_chunk() (bsc#1275569).\n- CVE-2026-74571: btrfs: skip global block reserve accounting for rescue mounts (bsc#1275561).\n- CVE-2026-74577: net: mpls: initialize rtm_tos in mpls_getroute() (bsc#1275572).\n- CVE-2026-74581: net: ipv6: clear suppressed fib6 rule result (bsc#1275782).\n- CVE-2026-74582: packet: use consistent hard_header_len in non-ring send paths (bsc#1275784).\n- CVE-2026-74584: RDMA/bnxt_re: zero shared page before exposing to userspace (bsc#1277066).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74610: tls: don't leave a full plaintext sk_msg ring unpushed (bsc#1277054).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74644: mm/damon/ops-common: putback folios on invalid migrate nid (bsc#1277033).\n- CVE-2026-74665: net: fix skb length accounting after generic XDP frag adjustment (bsc#1277407).\n- CVE-2026-74669: ipvs: clear IPv4 options after rebasing tunnel ICMP errors (bsc#1277391).\n- CVE-2026-74695: netfilter: nf_flow_table: drop existing skb dst before skb_dst_set_noref() (bsc#1276931).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74712: vdpa/mlx5: Fix buffer length in create_direct_keys() (bsc#1276577).\n- CVE-2026-74717: net/mlx5: fw_tracer, return NULL on create error (bsc#1276569).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74722: btrfs: fix memory leak in btrfs_do_encoded_write() (bsc#1276561).\n- CVE-2026-74723: btrfs: lzo: reject inline extents without valid headers (bsc#1276562).\n- CVE-2026-74730: NFS: Pin the 'struct nfs_server' during a FREE_STATEID call (bsc#1276566).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-80529: xfs: don't swallow dquot recovery verification errors (bsc#1277688).\n- CVE-2026-80530: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN (bsc#1277668).\n- CVE-2026-80531: xfs: avoid UAF on sc-\u003etempip in xrep_tempfile_create (bsc#1277680).\n- CVE-2026-80533: xfs: don't walk off the end of a null sc-\u003esa.agi_bp in AGI repair (bsc#1277636).\n- CVE-2026-80534: xfs: fix ilock leak on error in xfs_dq_get_next_id (bsc#1277022).\n- CVE-2026-80535: xfs: don't double-lock when deleting a self-referential directory (bsc#1277641).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80558: libceph: Avoid using invalid osd indices from primary_temp (bsc#1277485).\n- CVE-2026-80561: libceph: fix multiple unsafe decodes in decode_locker() (bsc#1277265).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80590: inet: frags: strip GSO state from fragments before reassembly (bsc#1277275).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80609: qede: fix out-of-bounds check for cqe-\u003elen_list (bsc#1278334).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80721: Bluetooth: ISO: ensure no dangling hcon references in iso_conn (bsc#1277845).\n- CVE-2026-80727: x86/mce: Set up the polling timer before CMCI discovery (bsc#1278703).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80813: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() (bsc#1279537).\n- CVE-2026-80838: vxlan: keep the last remote linked during FDB flush (bsc#1279842).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Limit firmware log name prints to field size (git-fixes).\n- accel/ivpu: Validate firmware log buffer metadata (git-fixes).\n- accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr (git-fixes).\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- accessibility: speakup: Fix incorrect string length computation in report_char_chartab_status() (git-fixes).\n- accessibility: speakup: unregister tty ldisc on later init failures (git-fixes).\n- ACPI: APEI: Fix ERST timeout unit conversion (git-fixes).\n- ACPI: battery: Adjust charging status validation check (git-fixes).\n- ACPI: EC: Avoid _REG disconnect on GPIO IRQ defer (git-fixes).\n- ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root (git-fixes).\n- ACPI: pfr_update: fix stack buffer overflow in query_capability() (git-fixes).\n- ACPI: processor: idle: Expand _LPI package sanity checks (git-fixes).\n- ACPI: processor: validate MADT IOAPIC entry bounds (git-fixes).\n- ACPI: processor_idle: Mark LPI enter functions as __cpuidle (git-fixes).\n- ACPI: scan: fix bus ID cleanup on device_add() failures (git-fixes).\n- ACPI: video: Release PCI device reference after lookup (git-fixes).\n- ALSA: 6fire: bound the MIDI event length from the device (git-fixes).\n- ALSA: 6fire: Fix UAF at error handling during probe (stable-fixes).\n- ALSA: bcd2000: clear the URB pointers on disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: control: Don't add invalid kcontrols to LED layer (git-fixes).\n- ALSA: core: Fix use-after-free in snd_card_do_free() (git-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Check card index validity at probe (stable-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/ext: preserve PPLCCTL bits when clearing reset (git-fixes).\n- ALSA: hda/realtek: Enable headset mic on F+ FLAPTOP r (stable-fixes).\n- ALSA: hda: Fix connection list comparison in proc output (git-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hpi: Check transport errors during HPI6000 adapter initialization (git-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcxhr: initialize mutexes before requesting threaded IRQ (git-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: scarlett2: Use a private URB for the notification endpoint (git-fixes).\n- ALSA: seq: Don't leak the extension cell pointer in the bounce payload (git-fixes).\n- ALSA: seq: midi: Optimize event_input locking with RCU (git-fixes).\n- ALSA: seq: midi: Serialize input teardown with event_input (git-fixes).\n- ALSA: ump: Fix corrupted data bytes at MIDI 1.0 SysEx to UMP conversion (git-fixes).\n- ALSA: usb-audio: Complete cleanup after system-resume errors (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_novation_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write on Type II inbound URBs (git-fixes).\n- ALSA: usb: Fix UAF at delayed release of MIDI2 EPs (git-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usbusx2y: validate URB actual_length in interrupt callback (git-fixes).\n- ALSA: usx2y: bound the hwdep mmap fault offset (git-fixes).\n- ALSA: via82xx: Remove unreachable branch in snd_via686_pcm_pointer() (git-fixes).\n- apparmor: advertise the tcp fast open fix is applied (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: adau1761: sort the register default table (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add DMI entry for MSI Thin A15 B7UC (git-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: apple: mca: increase SERDES reset delay (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses (git-fixes).\n- ASoC: cs35l33: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l34: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l41: sort the register default table (git-fixes).\n- ASoC: cs35l45: sort the register default table (git-fixes).\n- ASoC: cs4265: sort the register default table (git-fixes).\n- ASoC: cx2072x: sort the register default table (git-fixes).\n- ASoC: dapm: Fix off-by-one check on the second enum channel (git-fixes).\n- ASoC: fix unmet dependencies on PPC_BESTCOMM and SND_SOC_AC97_BUS (git-fixes).\n- ASoC: fsl-asoc-card: defer probe when the CPU DAI device is not ready (git-fixes).\n- ASoC: fsl: mpc5200-i2s: Free DMA resources on probe failure (git-fixes).\n- ASoC: fsl_audmix: rework runtime PM handling in probe (git-fixes).\n- ASoC: fsl_easrc: sort the register default table (git-fixes).\n- ASoC: hdac_hda: Fix hlink refcount leak on component registration failure (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: avs: Do not ignore -ENOENT when loading a topology (git-fixes).\n- ASoC: Intel: avs: Fix unbalanced module reference count (git-fixes).\n- AsoC: intel: sst: fix PCI device reference leak on probe failure (git-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: loongson: Fix error handling in ACPI property parsing (git-fixes).\n- ASoC: max9860: sort the register default table (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Shorten memif_data table using macros (stable-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Support \u003e32 bit DMA addresses (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: use local `dev` pointer in driver callbacks (stable-fixes).\n- ASoC: mediatek: mt8183: Check runtime resume during probe (git-fixes).\n- ASoC: mediatek: mt8192-afe-pcm: Simplify probe() with local dev variable (stable-fixes).\n- ASoC: mediatek: mt8192: Check runtime resume during probe (git-fixes).\n- ASoC: meson: Keep link pointers valid on realloc failure (git-fixes).\n- ASoC: ml26124: sort the register default table (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: pcm512x: sort the register default table (git-fixes).\n- ASoC: pxa: Use devm_clk_get_optional() for extclk clock (git-fixes).\n- ASoC: qcom: q6apm: keep the graph start count in sync with the DSP (git-fixes).\n- ASoC: rt274: sort the register default table (git-fixes).\n- ASoC: rt286: sort the register default table (git-fixes).\n- ASoC: rt298: sort the register default table (git-fixes).\n- ASoC: rt700-sdw: always drain jack work on remove (git-fixes).\n- ASoC: rt700: drop duplicate reg_default entry (git-fixes).\n- ASoC: rt700: sort the register default table (git-fixes).\n- ASoC: rt711-sdca: sort the register default tables (git-fixes).\n- ASoC: rt711: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-dmic: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt715-sdca: drop duplicate reg_default entries (git-fixes).\n- ASoC: rt715-sdca: sort the register default tables (git-fixes).\n- ASoC: rt715: sort the register default table (git-fixes).\n- ASoC: rt1017-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt1316-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318: sort the register default table (git-fixes).\n- ASoC: samsung: aries_audio_probe: double of_node_put due to direct assignment without of_node_get (git-fixes).\n- ASoC: sgtl5000: sort the register default table (git-fixes).\n- ASoC: SOF: sof-audio: Fix error path in sof_widget_setup_unlocked() (git-fixes).\n- ASoC: SOF: validate topology volume range before allocation (git-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti-sas: sort the register default table (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tas2552: sort the register default table (git-fixes).\n- ASoC: tas2764: sort the register default table (git-fixes).\n- ASoC: tas2780: sort the register default table (git-fixes).\n- ASoC: tegra210_i2s: sort the register default table (git-fixes).\n- ASoC: tegra210_mixer: sort the register default table (git-fixes).\n- ASoC: tegra: Fix the MIXER enable default value (git-fixes).\n- ASoC: tegra: Sort MBDRC register defaults (git-fixes).\n- ASoC: xilinx: formatter_pcm: fix stream_data leak on open error (git-fixes).\n- ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- batman-adv: bla: fix freeing of claims on meshif deletion (git-fixes).\n- batman-adv: bla: prevent CRC corruptions after claim flush (git-fixes).\n- batman-adv: dat: avoid unaligned fault in IP extraction (git-fixes).\n- batman-adv: fix stale receive device on merged fragments (git-fixes).\n- batman-adv: mcast: ensure unshared skb for multicast packets (git-fixes).\n- batman-adv: mcast: linearize skbuff for packet generation (git-fixes).\n- batman-adv: reject unrepresentable multicast TVLV offsets (git-fixes).\n- blk-mq: reinsert cached request to the list (bsc#1273770).\n- Bluetooth: btintel: bound firmware ID by TLV length (git-fixes).\n- Bluetooth: btintel: Fix diagnostics event detection (git-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btintel_pcie: Clear automask on spurious interrupts (git-fixes).\n- Bluetooth: btintel_pcie: fix tx_handle bounds off-by-one (git-fixes).\n- Bluetooth: btintel_pcie: validate packet_len before skb_put_data (git-fixes).\n- Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware (git-fixes).\n- Bluetooth: btmtk: Do not discard the subsystem reset timeout (git-fixes).\n- Bluetooth: btmtk: Fix short read errors in btmtk_usb_uhw_reg_read() (stable-fixes).\n- Bluetooth: btmtksdio: Fix out-of-bounds DMA read in the TX path (git-fixes).\n- Bluetooth: btmtksdio: Take exclusive ownership of the SKB before TX (git-fixes).\n- Bluetooth: btqca: Fix qca_set_bdaddr() waiting for wrong HCI event (git-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Fix BD_ADDR byte order in btusb_set_bdaddr_wcn6855() (git-fixes).\n- Bluetooth: btusb: Fix short read errors in btusb_qca_send_vendor_req() (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: do not leak an hci_conn when a second LE connect is rejected (git-fixes).\n- Bluetooth: eir: Fix OOB read in eir_get_service_data() (git-fixes).\n- Bluetooth: hci_aml: validate firmware segment lengths (git-fixes).\n- Bluetooth: hci_bcm4377: Ignore reserved PHY in ext adv reports on BCM4378 (git-fixes).\n- Bluetooth: hci_bcm: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_conn: fix the SCO setup context lifetime (git-fixes).\n- Bluetooth: hci_conn: hold conn reference in abort_conn_sync() (git-fixes).\n- Bluetooth: hci_conn: re-enable advertising only for peripheral role (git-fixes).\n- Bluetooth: hci_core: Fix race condition during device registration (git-fixes).\n- Bluetooth: hci_core: use skb_get() instead of skb_clone() for req_skb (git-fixes).\n- Bluetooth: hci_event: clear HCI_LE_ADV only on a created connection (git-fixes).\n- Bluetooth: hci_event: fix LE list UAF on reset (git-fixes).\n- Bluetooth: hci_event: validate LE Set CIG Parameters response (git-fixes).\n- Bluetooth: hci_h5: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_intel: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sync: Clear HCI_CMD_PENDING when dropping the last request (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: free the advertising instance on the failure and cancel paths (git-fixes).\n- Bluetooth: hci_sync: make hci_cmd_sync_run_once return -EEXIST if exists (stable-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del() (git-fixes).\n- Bluetooth: hci_uart: Fix false success return in hci_uart_setup() (git-fixes).\n- Bluetooth: ISO: do not force BT_LISTEN after a failed BIG sync (git-fixes).\n- Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect (git-fixes).\n- Bluetooth: mgmt: fix locking in unpair_device/disconnect_sync (git-fixes).\n- Bluetooth: MGMT: free the HCI command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: free the mesh send cancel command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: reject HCI_CMD_SYNC params_len above 255 (git-fixes).\n- Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update (git-fixes).\n- Bluetooth: MSFT: validate evt_prefix_len against the response length (git-fixes).\n- Bluetooth: qca: fix NVM tag length underflow in TLV parser (git-fixes).\n- Bluetooth: RFCOMM: serialize security confirmation handling (git-fixes).\n- Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept (git-fixes).\n- Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (git-fixes).\n- Bluetooth: virtio_bt: avoid OOB read of build info string (git-fixes).\n- bnxt_en: Check return value of bnxt_hwrm_vnic_cfg (jsc#PED-16798).\n- bnxt_en: Delay for 5 seconds after AER DPC for all chips (jsc#PED-16798).\n- bnxt_en: Don't assume XDP is never enabled in bnxt_init_dflt_ring_mode() (jsc#PED-16798).\n- bnxt_en: Drop pci_save_state() after pci_restore_state() (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction for V3_CMP (jsc#PED-16798).\n- bnxt_en: Move bnxt_rss_ext_op into header (jsc#PED-16798).\n- bnxt_en: Refactor some basic ring setup and adjustment logic (jsc#PED-16798).\n- bnxt_en: Restore default stat ctxs for ULP when resource is available (jsc#PED-16798).\n- bnxt_en: Set bp-\u003emax_tpa according to what the FW supports (jsc#PED-16798).\n- bnxt_en: Use absolute target ns from ptp_clock_request (jsc#PED-16798).\n- bnxt_en: use bnxt_xdp_buff for xdp context (jsc#PED-16798).\n- bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation (git-fixes).\n- bus: mhi: host: Fix controller cleanup on EDL sysfs failure (git-fixes).\n- bus: mhi: host: Flush the posted write after writing to MHI_SOC_RESET_REQ_OFFSET (git-fixes).\n- bus: ti-sysc: Fix /chosen node reference leak (git-fixes).\n- cacheinfo: don't propagate DT/ACPI error when arch supplies info (arm64) (git-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: use netdevice_tracker for j1939_{priv,session,ecu} tracking (stable-fixes).\n- char: xilinx_hwicap: unregister class on init errors (git-fixes).\n- cleanup: add a scoped version of CLASS() (stable-fixes).\n- cleanup: fix scoped_class() (git-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- cpufreq: intel_pstate: Add and use hybrid_get_cpu_type() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Avoid SMP calls to get cpu-type (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Fix hwp_get_cpu_scaling() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use correct scaling factor on Raptor Lake-E (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use CPPC to get scaling factors (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use HYBRID_SCALING_FACTOR_ADL for Bartlett Lake (bsc#1240957 bsc#1249104 bsc#1265220).\n- crypto: aspeed - Propagate platform_get_irq() errors (git-fixes).\n- crypto: atmel-sha204a - fix heap info leak on I2C transfer failure (git-fixes).\n- crypto: atmel-tdes - use scatterlist length before DMA mapping (git-fixes).\n- crypto: ccm - Set rfc4309 maxauthsize from child (git-fixes).\n- crypto: ccp - Abort doing SEV INIT if SNP INIT fails (stable-fixes).\n- crypto: ccp - Add new SEV/SNP platform shutdown API (stable-fixes).\n- crypto: ccp - Always pass in an error pointer to __sev_platform_shutdown_locked() (git-fixes).\n- crypto: ccp - Fix __sev_snp_shutdown_locked (git-fixes).\n- crypto: ccp - Fix dereferencing uninitialized error pointer (git-fixes).\n- crypto: ccp - Fix memory leak in SEV INIT_EX path (git-fixes).\n- crypto: ccp - Fix possible deadlock in SEV init failure path (git-fixes).\n- crypto: ccp - Fix SNP panic notifier unregistration (git-fixes).\n- crypto: ccp - Move dev_info/err messages for SEV/SNP init and shutdown (stable-fixes).\n- crypto: ccp - Move SEV/SNP Platform initialization to KVM (stable-fixes).\n- crypto: ccp - Register SNP panic notifier only if SNP is enabled (stable-fixes).\n- crypto: ccp - Reset TMR size at SNP Shutdown (stable-fixes).\n- crypto: doc - Remove extra parenthesis (git-fixes).\n- crypto: hisilicon/sec2 - fix CCM algorithm long packet failure (git-fixes).\n- crypto: keembay - Fix AEAD unregister count in error path (git-fixes).\n- crypto: keembay - Initialize completion before requesting IRQ (git-fixes).\n- crypto: keembay - publish OF module alias for OCS AES/SM4 (git-fixes).\n- crypto: lskcipher - propagate errors from unaligned crypt (git-fixes).\n- crypto: mxs-dcp - fix source scatterlist length access (git-fixes).\n- crypto: qat - cancel work on re-enable SR-IOV timeout (git-fixes).\n- crypto: qat - clear AES key schedule from stack (git-fixes).\n- crypto: qce - fix CCM AAD buffer underallocation (git-fixes).\n- crypto: qce - fix error path in devm_qce_register_algs (git-fixes).\n- crypto: qcom-rng - Allow zero as a random number (git-fixes).\n- crypto: qcom-rng - Enable clock in hwrng case (git-fixes).\n- crypto: rk3288 - fail ahash requests on HASH idle timeout (git-fixes).\n- crypto: sa2ul - stop probe if context pool creation fails (git-fixes).\n- crypto: sl3516 - drop invalid sg_dma_len checks before DMA mapping (git-fixes).\n- crypto: tegra - Don't touch bo refcount in host1x bo pin/unpin (stable-fixes).\n- crypto: tegra - fix rctx-\u003ecryptlen calculation in tegra_gcm_do_one_req() (git-fixes).\n- cxl/acpi: Fix CXL_ACPI and CXL_PMEM Kconfig tristate mismatch (git-fixes).\n- cxl: Adjust the startup priority of cxl_pmem to be higher (git-fixes).\n- default_gfp(): avoid using the \"newfangled\" __VA_OPT__ trick (bsc#1280139).\n- device property: fix infinite loop in fwnode_for_each_child_node() (git-fixes).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dma-mapping: add __dma_from_device_group_begin()/end() (bsc#1267586).\n- dmaengine: dw-edma: Clear stale requests on termination (git-fixes).\n- dmaengine: dw-edma: Complete descriptors before pausing (git-fixes).\n- dmaengine: dw-edma: Fix HDMA channel status register access (git-fixes).\n- dmaengine: dw-edma: Initialize IRQ data before requesting IRQs (git-fixes).\n- dmaengine: dw-edma: Serialize abort state updates (git-fixes).\n- dmaengine: dw-edma: Serialize channel state checks (git-fixes).\n- dmaengine: dw-edma: Terminate all descriptors without callbacks (git-fixes).\n- dmaengine: fsl-edma: tracing: no ptr dereference during log output (git-fixes).\n- dmaengine: hisilicon: Return -ENOMEM on dynamic memory allocation in probe (git-fixes).\n- dmaengine: mediatek: mtk-uart-apdma: Return -ENOMEM on memory allocation failure (git-fixes).\n- dmaengine: qcom-bam-dma: fix autosuspend cleanup during removal (git-fixes).\n- dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers (git-fixes).\n- dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout (git-fixes).\n- dmaengine: zynqmp_dma: fix kernel doc for zynqmp_dma_remove() (git-fixes).\n- driver core: soc: Unregister bus on early device registration failure (git-fixes).\n- drivers/virt: pkvm: Fix end calculation in mmio_guard_ioremap_hook() (git-fixes).\n- Drivers: hv: Use meaningful errnos for hypercall status codes (git-fixes).\n- drm/amd/display: Add AV mute wait frames to dce110_set_avmute (stable-fixes).\n- drm/amd/display: avoid divide-by-zero in __is_lut_linear() (git-fixes).\n- drm/amd/display: Check for tg ops in dce110_set_avmute (git-fixes).\n- drm/amd/display: dce100: skip non-DP stream encoders for DP MST (stable-fixes).\n- drm/amd/display: fix BT.2020 YCbCr limited output CSC matrix (git-fixes).\n- drm/amd/display: fix BT.2020 YCbCr output CSC matrices for DCE (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix NULL pointer dereference in amdgpu_dm_crtc_set_vblank() (git-fixes).\n- drm/amd/display: Increase HDMI AV mute wait from 2 to 3 frames (stable-fixes).\n- drm/amd/display: Remove unused-but-set variable hubp from (git-fixes).\n- drm/amd/display: validate plane degamma LUT size for private color prop (git-fixes).\n- drm/amd/pm: adjust the visibility of pp_table sysfs node (stable-fixes).\n- drm/amd/pm: fix gpu metrics energy accumulator for smu 13.0.0/13.0.7 (git-fixes).\n- drm/amd/pm: fix smu14 power limit range calculation (stable-fixes).\n- drm/amd/pm: make pp_features read-only when scpm is enabled (stable-fixes).\n- drm/amd/pm: Use same metric table for APU (stable-fixes).\n- drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read (git-fixes).\n- drm/amdgpu/gfx6: Fixup emit_cntxcntl() (git-fixes).\n- drm/amdgpu/gfx6: Fixup emitting SWITCH_BUFFER packets (git-fixes).\n- drm/amdgpu/gfx6: Use PFP on the compute queues too (git-fixes).\n- drm/amdgpu/gfx8: drop unecessary BUG_ON() (stable-fixes).\n- drm/amdgpu/gfx9.4.3: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx9: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx11: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx12: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in SMU7 lookup (git-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup (git-fixes).\n- drm/amdgpu/sdma4.4.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma6.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma7.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/uvd: Fix forcing MSG, FB BOs into VCPU segment when it isn't at 0 (v2) (stable-fixes).\n- drm/amdgpu/uvd: Place VCPU BO only in VRAM for UVD 4.x and older (stable-fixes).\n- drm/amdgpu/vce: fix integer overflow in image size (stable-fixes).\n- drm/amdgpu/vcn4: avoid rereading IB param length (stable-fixes).\n- drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check (git-fixes).\n- drm/amdgpu: cap GTT size to physical RAM on APUs (stable-fixes).\n- drm/amdgpu: check ASPM on the dGPU host link (git-fixes).\n- drm/amdgpu: disallow multiple FENCE chunks in one submit (git-fixes).\n- drm/amdgpu: fix aperture iounmap skipped on device removal (git-fixes).\n- drm/amdgpu: fix autosuspend cleanup during removal (git-fixes).\n- drm/amdgpu: fix bo-\u003epin leaking in amdgpu_bo_create_reserved (stable-fixes).\n- drm/amdgpu: fix division by zero with invalid uvd dimensions (stable-fixes).\n- drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid() (stable-fixes).\n- drm/amdgpu: fix nbif 6.3.1 l1 low power not functional (git-fixes).\n- drm/amdgpu: Fix UVD decode image min size calculation (stable-fixes).\n- drm/amdgpu: Fix UVD dpb min size calculation for H264 (stable-fixes).\n- drm/amdgpu: Fix UVD min buffer sizes (stable-fixes).\n- drm/amdgpu: Fix VCE 3 ring align_mask (git-fixes).\n- drm/amdgpu: Fix VFCT bus number matching with soft filter (stable-fixes).\n- drm/amdgpu: Implement insert_end for VCE 3 (git-fixes).\n- drm/amdgpu: invoke pm_genpd_remove() before freeing genpd (stable-fixes).\n- drm/amdgpu: move debug_vm handling to amdgpu_cs_parser_fini (git-fixes).\n- drm/amdgpu: read TRUNCATE_COORD_MODE on gfx12 (git-fixes).\n- drm/amdgpu: reject oversized IBs with per-ring packet limits (stable-fixes).\n- drm/amdgpu: Reject UVD message with dimensions above 4096 (stable-fixes).\n- drm/amdgpu: Reject UVD message with invalid number of h265 refs (stable-fixes).\n- drm/amdgpu: remove unused function parameter (stable-fixes).\n- drm/amdgpu: restore UMD profile pstate after runtime resume (stable-fixes).\n- drm/amdgpu: validate GEM_CREATE domain combinations (stable-fixes).\n- drm/amdkfd: Check bounds in allocate_event_notification_slot (stable-fixes).\n- drm/amdkfd: fix 32-bit overflow in CWSR total size calculation (stable-fixes).\n- drm/amdkfd: Fix missing authorization check in KFD_IOC_DBG_TRAP_DISABLE (stable-fixes).\n- drm/amdkfd: fix QID bit leak in pqm_create_queue() (stable-fixes).\n- drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore (git-fixes).\n- drm/amdkfd: Handle invalid event type in CRIU event restore (stable-fixes).\n- drm/amdkfd: Use kvcalloc to allocate arrays (stable-fixes).\n- drm/bridge: cdns-mhdp8546: Return an error pointer on allocation failure (git-fixes).\n- drm/bridge: dw-hdmi: fix i2c adapter leak on probe failure (git-fixes).\n- drm/bridge: ps8640: propagate AUX transfer register errors (git-fixes).\n- drm/bridge: tc358767: clamp the reported AUX read size to the request (git-fixes).\n- drm/connector/hdmi: Fix out of bounds memory read (git-fixes).\n- drm/connector: Fix epoch_counter docs to reflect reality (git-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/hibmc: Fix list of formats on the primary plane (git-fixes).\n- drm/hibmc: Use drm_atomic_helper_check_plane_state() (git-fixes).\n- drm/i915/hdcp: check streams bounds before overflow (git-fixes).\n- drm/i915/hdcp: Move to using intel_display in intel_hdcp (stable-fixes).\n- drm/i915/hdcp: require monotonically increasing seq_num_v (git-fixes).\n- drm/i915/hdcp: Skip inactive MST connectors when building stream list (stable-fixes).\n- drm/i915/vrr: Check HAS_VRR() first in intel_vrr_is_capable() (stable-fixes).\n- drm/i915/vrr: require valid min/max vfreq for VRR (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/lima: call drm_mm_init() with a valid allocation range (git-fixes).\n- drm/msm/a6xx: Fix RBBM_CLOCK_CNTL3_TP0 value in a730_hwcg (git-fixes).\n- drm/msm/a6xx: Fix stale rpmh votes after suspend (git-fixes).\n- drm/msm/dpu: Drop sneaky dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: Drop dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: round 6G byte clock rate to the PLL-achievable value (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau: unsubscribe the channel-kill event before the fence context (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/panel-edp: fix i2c adapter leak on probe failure (git-fixes).\n- drm/panel: samsung-s6d16d0: Power off on prepare failure (git-fixes).\n- drm/panthor: fix firmware control interface bounds checks (git-fixes).\n- drm/panthor: return PTR_ERR() from devm_drm_dev_alloc() (git-fixes).\n- drm/panthor: skip zero-sized firmware sections (git-fixes).\n- drm/radeon: fix autosuspend cleanup during teardown (git-fixes).\n- drm/radeon: fix r100_copy_blit for large BOs (stable-fixes).\n- drm/radeon: restore hardware polling in fence_is_signaled to fix performance regression (git-fixes).\n- drm/rockchip: vop2: Recognise 10-bit YUV422 as YUV format (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates for ssd132x (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates in ssd133x (git-fixes).\n- drm/sun4i: crtc: Propagate layer initialization error (git-fixes).\n- drm/sun4i: Drop node references while building component list (git-fixes).\n- drm/sun4i: dw-hdmi: Drop TCON TOP port reference (git-fixes).\n- drm/sun4i: fix refcount leak in sun4i_backend_init_sat() (git-fixes).\n- drm/sun4i: hdmi-phy: Fix H6 8-bit MPLL config at 594 MHz (git-fixes).\n- drm/sun4i: hdmi: Don't leak sync polarity bits into packet control (git-fixes).\n- drm/sun4i: tcon: Drop remote endpoint reference (git-fixes).\n- drm/sun4i: tcon: Drop TCON TOP device reference (git-fixes).\n- drm/sun4i: tcon: Set output mux for DSI and LVDS (git-fixes).\n- drm/sun4i: vi scaler: Fix coefficient selection (git-fixes).\n- drm/tegra: dsi: Re-add clear enable register if DSI was powered by bootloader (git-fixes).\n- drm/tegra: fbdev: Do not assign to struct drm_fb_helper.info (git-fixes).\n- drm/tve200: add OF module alias for autoloading (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/xe/oa: Check managed mutex initialization errors (git-fixes).\n- drm/xe/oa: Fix sync entry leak on OA config emit failure (git-fixes).\n- drm/xe/oa: Remove sysfs entry on idr_alloc failure in xe_oa_add_config_ioctl() (git-fixes).\n- drm/xe: Introduce xe_gt_dbg_printer() (stable-fixes).\n- drm/xe: Order ring writes before ring tail updates (git-fixes).\n- drm/xe: Stub out new pagefault layer (stable-fixes).\n- drm/xe: tests: fix error message in xe_migrate_sanity_test() (git-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: fix race between partial drm_dev_register() failure and ioctl (git-fixes).\n- drm: lcdif: Wait for vblank before disabling DMA (git-fixes).\n- drm: Remove unused header in drm_dumb_buffers.c (git-fixes).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- erspan: Initialize options_len before referencing options (bsc#1274727).\n- ethtool: rss: fix hkey leak when indir_size is 0 (git-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_cursor() (git-fixes).\n- fbdev: core: Fix pointer desynchronization in fb_io_read() (git-fixes).\n- fbdev: kyro: Validate overlay viewport coordinates (git-fixes).\n- fbdev: omapfb: panel-dsi-cm: initialize lock before registering display (git-fixes).\n- fbdev: tdfxfb: fix PCI enable cleanup with pcim_enable_device() (git-fixes).\n- fbdev: uvesafb: unregister connector callback on init failure (git-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Avoid IDR updates while cleaning channels (git-fixes).\n- firmware: arm_scmi: Clean up channels on setup failure (git-fixes).\n- firmware: arm_scmi: Drop handle on protocol bind failures (git-fixes).\n- firmware: arm_scmi: Fix requested device removal race (git-fixes).\n- firmware: arm_scmi: Free transport channel on IDR failure (git-fixes).\n- firmware: arm_scmi: Protect device request lookup with RCU (git-fixes).\n- firmware: arm_scmi: Publish channel state before callbacks (git-fixes).\n- firmware: arm_scmi: Quiesce notifications before teardown (git-fixes).\n- firmware: arm_scmi: Rate-limit queue-full warnings in IRQ context (git-fixes).\n- firmware: arm_scmi: Reject out of range DT protocol IDs (git-fixes).\n- firmware: arm_scmi: Roll back partial protocol table registration (git-fixes).\n- firmware: arm_scmi: Unregister device notifier before IDR teardown (git-fixes).\n- firmware: arm_scmi: Unrequest devices if driver registration fails (git-fixes).\n- firmware: arm_scmi: Unwind P2A receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Unwind TX receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Use channel ID for transport teardown (git-fixes).\n- firmware_loader: do not queue completed sysfs fallback requests (git-fixes).\n- fpga: altera-cvp: Avoid out-of-bounds read in trailing byte write (git-fixes).\n- fpga: dfl: fme: add error handling (git-fixes).\n- fpga: stratix10-soc: Fix SVC mailbox handling during reconfiguration (git-fixes).\n- fuse: fix race between interrupt and resend (git-fixes).\n- gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind (git-fixes).\n- gpu: host1x: Avoid stack over-read in debug output helpers (git-fixes).\n- gpu: host1x: Fix offset calculation in trace_write_gather (git-fixes).\n- gpu: host1x: Fix use-after-free in host1x_bo_clear_cached_mappings (stable-fixes).\n- HID: asus: fix missing hid_is_usb() check (git-fixes).\n- HID: asus: simplify RGB init sequence (stable-fixes).\n- HID: bpf: serialize device reference release in struct_ops destroy path (git-fixes).\n- HID: core: fix number/pointer type confusion on long items (git-fixes).\n- HID: core: fix OOB read of field-\u003eusage in hid_set_field() (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: hyperv: validate initial device info bounds (git-fixes).\n- HID: i2c-hid: Fix \"(null)\" output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: goodix: Disable VDD on VDDIO enable failure (git-fixes).\n- HID: lg4ff: validate report length before fixed offsets (git-fixes).\n- HID: logitech-dj: Fix maxfield check in DJ short report validation (git-fixes).\n- HID: logitech-dj: fix wrong detection of bad DJ_SHORT output report (git-fixes).\n- HID: logitech-dj: Prevent REPORT_ID_DJ_SHORT related user initiated OOB write (stable-fixes).\n- HID: logitech-dj: Standardise hid_report_enum variable nomenclature (stable-fixes).\n- HID: magicmouse: do not keep a stale msc-\u003einput if no input is claimed (git-fixes).\n- HID: magicmouse: fix battery reporting for Bluetooth Magic Trackpad USB-C (git-fixes).\n- HID: magicmouse: Prevent out-of-bounds (OOB) read during DOUBLE_REPORT_ID (stable-fixes).\n- HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() (git-fixes).\n- HID: magicmouse: re-enable multitouch after reset-resume (git-fixes).\n- HID: mcp2221: validate report size in mcp2221_raw_event() (git-fixes).\n- HID: multitouch: reclassify HTIX5288 to WIN_8_FORCE_MULTI_INPUT_NSMU (git-fixes).\n- HID: nintendo: Fix imu_timestamp_us double increment per report (git-fixes).\n- HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler() (git-fixes).\n- HID: nintendo: register input device after capabilities are set (git-fixes).\n- HID: nintendo: stop device IO before hid_hw_stop on probe failure (git-fixes).\n- HID: picolcd: clamp eeprom debugfs read to bytes actually received (git-fixes).\n- HID: pidff: Rework pidff_set_time() to fix warnings (stable-fixes).\n- HID: pidff: Use ARRAY_SIZE macro instead of sizeof (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: roccat: bound device-supplied profile index (git-fixes).\n- HID: roccat: free buffered reports when destroying device (git-fixes).\n- HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature (git-fixes).\n- HID: sensor: custom: Fix field sysfs group cleanup on failure (git-fixes).\n- HID: sensor: custom: Fix use-after-free in enable_sensor (git-fixes).\n- HID: synchronize input before cleaning up a failed probe (git-fixes).\n- HID: tmff: Use 64-bit arithmetic for force feedback scaling (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- hwmon: (ads7828) Fix external VREF regulator handling (git-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (chipcap2) fix channels in humidity alarm notifications (git-fixes).\n- hwmon: (coretemp) Fix core_data leak on CPUs without PTS (git-fixes).\n- hwmon: (corsair-cpro) Create debugfs entries after hwmon registration (git-fixes).\n- hwmon: (corsair-cpro) Remove debugfs entries when probe fails (git-fixes).\n- hwmon: (corsair-psu) fix possible out-of-bounds access on missing string termination (git-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (ina2xx) Add support for has_alerts configuration flag (stable-fixes).\n- hwmon: (ina2xx) Add support for INA234 (stable-fixes).\n- hwmon: (ina2xx) Add support for INA260 (stable-fixes).\n- hwmon: (ina2xx) Fix various overflow issues (git-fixes).\n- hwmon: (ina2xx) Make it easier to add more devices (stable-fixes).\n- hwmon: (ina2xx) Shift INA234 shunt and current registers (stable-fixes).\n- hwmon: (ina226) Add support for SY24655 (stable-fixes).\n- hwmon: (ltc4282) Avoid overflow in maximum power calculation (git-fixes).\n- hwmon: (ltc4282) Clamp negative current limits (git-fixes).\n- hwmon: (ltc4282) Fix parsing adi,current-limit-sense-microvolt (git-fixes).\n- hwmon: (ltc4282) Make sure clk_init_data is fully initialized (git-fixes).\n- hwmon: (max6621) fix negative temperature offset and crit readings (git-fixes).\n- hwmon: (max6621) fix temperature clamp range (git-fixes).\n- hwmon: (nzxt-smart2) Check return value of init_device() in probe (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficient calculations (git-fixes).\n- hwmon: Switch back to struct platform_driver::remove() (stable-fixes).\n- hwrng: ks-sa - Fix runtime PM cleanup on registration failure (git-fixes).\n- hwrng: omap - Fix probe error path cleanup (git-fixes).\n- hwtracing: hisi_ptt: Propagate DMA reset timeout in trace_start() (git-fixes).\n- i2c: core: fix debugfs UAF on adapter removal (git-fixes).\n- i2c: imx: fix locked bus on SMBus block-read of 0 (atomic) (git-fixes).\n- i2c: imx: separate atomic, dma and non-dma use case (stable-fixes).\n- i2c: mux: demux-pinctrl: fix OF node leak on kstrdup failure (git-fixes).\n- i2c: mux: Fix channel node leak on adapter add failure (git-fixes).\n- i2c: ocores: Disable clock on failed resume (git-fixes).\n- i3c: dw: avoid shift-out-of-bounds when DAA assigns no devices (git-fixes).\n- i3c: dw: rename \"pclk\" to \"apb\" to match dt-binding (git-fixes).\n- i3c: master: Fix device_register() error path (git-fixes).\n- i3c: master: Fix info leak and UAF in device unregister path (git-fixes).\n- i3c: master: Fix potential UAF in i3c_device_uevent() (git-fixes).\n- i3c: master: svc: bound IBI payload to the requested max_payload_len (git-fixes).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: dmard09: Implement IIO_CHAN_INFO_SCALE (git-fixes).\n- iio: adc: max34408: add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- iio: adc: pac1921: fix wrong channel used in trigger handler read (git-fixes).\n- iio: buffer: Fix potential use-after-free in anonymous buffer release (git-fixes).\n- iio: buffer: Make IIO DMA fence release RCU-safe (git-fixes).\n- iio: buffer: Tie IIO dma fence lock lifetime to the fence (git-fixes).\n- iio: chemical: atlas-sensor: fix PM reference leak in buffer postenable (git-fixes).\n- iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF (git-fixes).\n- iio: chemical: sgp30: Handle IAQ thread creation failure (git-fixes).\n- iio: dac: m62332: Fix regulator reference count imbalance (git-fixes).\n- iio: gyro: mpu3050: fix sign of raw angular velocity readings (git-fixes).\n- iio: light: cm32181: return zero after writing calibscale (git-fixes).\n- iio: light: gp2ap002: Disable regulators on resume failure (git-fixes).\n- iio: light: gp2ap002: re-enable irq if runtime suspend fails (git-fixes).\n- iio: light: isl29028: return zero in write_raw() on success (git-fixes).\n- iio: light: ltrf216a: fix runtime PM reference leak in error path (git-fixes).\n- iio: light: opt4001: Fix incompatible pointer type passed to div_u64_rem() (git-fixes).\n- iio: light: opt4001: Fix power down clearing bits of the wrong register (git-fixes).\n- iio: light: opt4001: Fix reversed GENMASK() arguments in fault count mask (git-fixes).\n- iio: light: opt4001: Reject integration times with a non-zero seconds part (git-fixes).\n- iio: light: tsl2583: return zero in write_raw() on success (git-fixes).\n- iio: light: tsl2772: fix ALS calibscale readback (git-fixes).\n- iio: orientation: hid-sensor-rotation: Avoid race between callback setup and device exposure (git-fixes).\n- iio: pressure: dps310: fix NULL pointer dereference on ACPI probe (git-fixes).\n- iio: pressure: mpl115: Fix runtime PM cleanup (git-fixes).\n- iio: srf04: fix pm_runtime handling on probe error path (git-fixes).\n- iio: temperature: hid-sensor-temperature: switch to non-devm iio_device_register() (git-fixes).\n- Input: atkbd - skip deactivate for HONOR ZQC-P (git-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Book Pro 14's internal keyboard (stable-fixes).\n- Input: cs40l50-vibra - validate custom data from user space (git-fixes).\n- Input: evdev - fix information leak in evdev_pass_values() (stable-fixes).\n- Input: evdev - sanitize event type index when fetching event masks (stable-fixes).\n- Input: focaltech - fix array out-of-bounds in focaltech_process_rel_packet (git-fixes).\n- Input: focaltech - use signed coordinates to prevent underflow (git-fixes).\n- Input: hynitron_cstxxx - validate touch count and finger IDs (git-fixes).\n- Input: iforce - validate input packet lengths (stable-fixes).\n- Input: iqs5xx - validate firmware record destination span (git-fixes).\n- Input: mms114 - fix Y-resolution configuration (git-fixes).\n- Input: psxpad-spi - set driver data before use (git-fixes).\n- Input: reject inhibit and uninhibit requests on unregistering devices (git-fixes).\n- Input: sur40 - fix input device registration ordering (stable-fixes).\n- Input: sur40 - fix V4L error path cleanup (stable-fixes).\n- Input: synaptics-rmi4 - block s_input when F54 queue is busy (git-fixes).\n- Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer (git-fixes).\n- Input: synaptics-rmi4 - fix F55 transmitter electrode count typo (git-fixes).\n- Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue (git-fixes).\n- Input: synaptics-rmi4 - zero report size on F54 work error (git-fixes).\n- Input: xpad - add support for ZENAIM LEVERLESS (stable-fixes).\n- interconnect: Fix use after free in icc_get() and of_icc_get_by_index() (git-fixes).\n- io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (git-fixes).\n- io_uring/net: Avoid msghdr on op_connect/op_bind async data (git-fixes).\n- iommu/arm-smmu-v3: Manage teardown with devm (stable-fixes).\n- ip_tunnel: Use ip_tunnel_info() helper instead of 'info + 1' (bsc#1274727).\n- ipmi: ipmb: validate write message length (git-fixes).\n- ipmi: si: Fix NULL pointer dereference after failed registration (git-fixes).\n- KVM: arm64: Ensure FFA ranges are page aligned (git-fixes).\n- KVM: arm64: Fix bounds checking in do_ffa_mem_reclaim() (git-fixes).\n- KVM: arm64: Fix sign-extension of MMIO loads (git-fixes).\n- KVM: arm64: vgic: Reset in_kernel on private IRQ allocation failure (git-fixes).\n- KVM: arm64: Zero out the stack initialized data in the FFA handler (git-fixes).\n- KVM: nSVM: Always inject a #GP if mapping VMCB12 fails on nested VMRUN (git-fixes).\n- KVM: nSVM: Remove a user-triggerable WARN on nested_svm_load_cr3() succeeding (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (git-fixes).\n- KVM: PPC: Book3S HV: Add support for compat CPU capabilities for KVM on PowerNV (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Validate arch_compat against host compatibility mode (bsc#1263864 ltc#217835).\n- KVM: PPC: Document KVM_PPC_GET_COMPAT_CAPS ioctl (bsc#1263864 ltc#217835).\n- KVM: PPC: Introduce KVM_CAP_PPC_COMPAT_CAPS and wire up ioctl (bsc#1263864 ltc#217835).\n- KVM: SEV: Use to_kvm_sev_info() for fetching kvm_sev_info struct (git-fixes).\n- KVM: SVM: Add support to initialize SEV/SNP functionality in KVM (bsc#1279887).\n- KVM: SVM: Explicitly mark vmcb01 dirty after modifying VMCB intercepts (git-fixes).\n- KVM: SVM: Serialize accesses to the owner and mirror list with separate lock (git-fixes).\n- KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active (git-fixes).\n- KVM: TDX: Account all non-transient page allocations for per-TD structures (git-fixes).\n- KVM: TDX: Fix x2APIC MSR handling in tdx_has_emulated_msr() (git-fixes).\n- KVM: VMX: Don't register posted interrupt wakeup handler if alloc_kvm_area() fails (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86/mmu: Recover TDP MMU NX huge pages using MMU read lock (bsc#1271050).\n- KVM: x86/mmu: Rename kvm_tdp_mmu_zap_sp() to better indicate its purpose (bsc#1271050).\n- KVM: x86/mmu: Track possible NX huge pages separately for TDP vs. Shadow MMU (bsc#1271050).\n- KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears because it was cleared from the PIC (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears when Xen emulation is enabled (git-fixes).\n- KVM: x86: Fix array_index_nospec() protection in kvm_vcpu_ioctl_x86_set_mce() (git-fixes).\n- KVM: x86: Fix emulated CPUID features being applied to wrong sub-leaf (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- leds: pca9532: Fix inverted GPIO output polarity (git-fixes).\n- leds: pca9532: Fix phantom device registration on missing hardware (git-fixes).\n- lib/string: fix memchr_inv() for large ranges (git-fixes).\n- lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen() (git-fixes).\n- mac802154: fix data race and NULL deref on local-\u003eassoc_dev (git-fixes).\n- mac802154: fix netdev use-after-free in beacon worker (git-fixes).\n- mac802154: fix use-after-free of sdata via queued RX frames (git-fixes).\n- mailbox: pcc: Fix command timeout due to missed interrupt (git-fixes).\n- mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler (git-fixes).\n- mailbox: qcom-cpucp: handle NULL data in send_data callback (git-fixes).\n- mailbox: qcom-ipcc: fix duplicate channel allocation across holes (git-fixes).\n- mailbox: rockchip: disable pclk on probe failure and unbind (git-fixes).\n- maple_tree: fix argument name in header (git-fixes).\n- md/raid1: create serial pool adding rdev to array with serialize_policy=1 (bsc#1272261).\n- media: airspy: Return queued buffers on start_streaming() failure (git-fixes).\n- media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref (git-fixes).\n- media: amphion: Remove obsolete frame_count check in venc_start_session (git-fixes).\n- media: bcm2835-unicam: Fix asc leaked in error/remove path (git-fixes).\n- media: cec-pin: Fix event FIFO ordering (git-fixes).\n- media: cec: disable delayed work before freeing an interrupted transmit (git-fixes).\n- media: cec: extron-da-hd-4k-plus: add sanity check (git-fixes).\n- media: cec: meson: ao-cec-g12a: name the CEC core regmap to avoid debugfs clash (git-fixes).\n- media: cec: Serialize exclusive follower delivery (git-fixes).\n- media: cec: stm32: prevent out-of-bounds write on RX overflow (git-fixes).\n- media: cedrus: clean up media device on probe failure (git-fixes).\n- media: cedrus: fix memory leak in cedrus_init_ctrls() (git-fixes).\n- media: chips-media: wave5: Guard bit depth check with initial_info_obtained (git-fixes).\n- media: chips-media: wave5: Move src_buf Removal to finish_encode (git-fixes).\n- media: cobalt: Avoid freeing ALSA private data twice (git-fixes).\n- media: cx231xx: fix devres lifetime (git-fixes).\n- media: cx231xx: reject geometry changes while the VBI queue is busy (git-fixes).\n- media: cx23885: add ioremap return check and cleanup (git-fixes).\n- media: cx23885: cancel NetUP CI work before teardown (git-fixes).\n- media: em28xx: defer audio-only extension registration (git-fixes).\n- media: em28xx: fix use-after-free of dev_next-\u003edevlist on disconnect (git-fixes).\n- media: go7007: defer the ALSA v4l2 put until card release (git-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: i2c: alvium: fix critical pointer access in alvium_ctrl_init (git-fixes).\n- media: i2c: alvium: Fix: Correct name of register in alvium_set_ctrl_auto_exposure (git-fixes).\n- media: i2c: imx219: Rename VTS to FRM_LENGTH (stable-fixes).\n- media: i2c: imx415: Return test pattern write errors (git-fixes).\n- media: i2c: ov02a10: fix endpoint parsing use-after-free (git-fixes).\n- media: i2c: ov7740: fix use-after-destroy in remove (git-fixes).\n- media: i2c: rdacm21: Fix missing media_entity_cleanup() (git-fixes).\n- media: imx219: Fix maximum frame length in lines (git-fixes).\n- media: intel/ipu6: fix async notifier cleanup leak on parse error (git-fixes).\n- media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges (git-fixes).\n- media: ipu6: Do not free aux device pdata after init (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_HAUPPAUGE_NEW keymap define (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_RC5_TV keymap define (git-fixes).\n- media: mc-entity: Add missing kerneldoc (git-fixes).\n- media: mediatek: vcodec: bound AV1 tile-start copy to the array capacity (git-fixes).\n- media: meson: vdec: Fix memory leak in error path of vdec_open (git-fixes).\n- media: meson: vdec: fix NULL pointer deref in vdec_try_fmt_common (git-fixes).\n- media: msi2500: Return queued buffers on start_streaming() failure (git-fixes).\n- media: nuvoton: npcm-video: fix error handling in npcm_video_init() (git-fixes).\n- media: nuvoton: npcm-video: fix memory leaks in probe and remove (git-fixes).\n- media: nxp: imx8-isi: Add missing v4l2_subdev_cleanup() in crossbar and pipe (git-fixes).\n- media: nxp: imx8-isi: Clean up already-initialized pipes on probe failure (git-fixes).\n- media: nxp: imx8-isi: Correct color map between V4L2 and ISI (git-fixes).\n- media: nxp: imx8-isi: Fix missing v4l2_subdev_cleanup() in pipe init error path (git-fixes).\n- media: nxp: imx8-isi: Fix potential out-of-bounds issues (git-fixes).\n- media: nxp: imx8-isi: Fix scale factor calculation for hardware rounding (git-fixes).\n- media: nxp: imx8-isi: Fix stream ID validation bypass in crossbar routing (git-fixes).\n- media: nxp: imx8-isi: Use BIT_ULL() for 64-bit stream masks (git-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: platform: mtk-mdp3: fix NULL deref on failed SCP lookup (git-fixes).\n- media: platform: mtk-mdp3: Fix SCP device refcounting (git-fixes).\n- media: pwc: Drain fill_buf on start_streaming() failure (git-fixes).\n- media: pwc: Return queued buffers on start_streaming() failure (git-fixes).\n- media: qcom: camss: Fix RDI streaming for CSID GEN2 (git-fixes).\n- media: radio-si476x: Unregister v4l2_device on probe failure (git-fixes).\n- media: rc: sunxi-cir: Unregister rc device on probe failure (git-fixes).\n- media: rtl2832: fix use-after-free in rtl2832_remove() (git-fixes).\n- media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: Return queued buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak (git-fixes).\n- media: s2255: bound JPEG frame size before copying into the buffer (git-fixes).\n- media: s2255: check firmware size before reading trailing marker (git-fixes).\n- media: saa7134: Fix a possible memory leak in saa7134_video_init1 (git-fixes).\n- media: saa7164: fix cleanup on resource allocation failure (git-fixes).\n- media: stm32: dcmi: unregister notifier on probe failure (git-fixes).\n- media: sun4i-csi: Return queued buffers on start_streaming() failure (git-fixes).\n- media: tda18250: fix possible integer overflow (git-fixes).\n- media: tegra-video: vi: fix invalid u32 return value in format lookup (git-fixes).\n- media: usbtv: keep device alive while ALSA card exists (git-fixes).\n- media: v4l2-async: avoid deleting unlinked ASC entry on link error (git-fixes).\n- media: v4l2-async: Unregister sub-device if asc_list is empty (git-fixes).\n- media: v4l2-ctrls-request: add NULL check in v4l2_ctrl_request_complete() (git-fixes).\n- media: v4l2-ctrls: Allow unknown HDR10 white point and luminance (git-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-fwnode: Fix fwnode leak in v4l2_fwnode_parse_link (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: v4l2-subdev: Fail {enable,disable}_streams and s_streaming nicely (git-fixes).\n- media: venus: fix payload size calculation in parse_raw_formats() (git-fixes).\n- media: venus: fix payload size returned by parse_caps() and parse_alloc_mode() (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer (git-fixes).\n- media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity (git-fixes).\n- media: vicodec: fix out-of-bounds write in FWHT encoder (git-fixes).\n- media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure (git-fixes).\n- media: vimc: fix pixel format lookup in enum_framesizes (git-fixes).\n- media: vivid: add vivid_update_reduced_fps() (git-fixes).\n- media: vivid: check for vb2_is_busy() when toggling caps (git-fixes).\n- media: vivid: fix cleanup bugs in vivid_init() (git-fixes).\n- media: zoran: Avoid freeing a registered video_device twice (git-fixes).\n- mei: pull kvfree out of spinlock (git-fixes).\n- mfd: iqs62x: Reject zero-length firmware records (git-fixes).\n- mfd: rave-sp: validate received frame payload lengths (git-fixes).\n- mfd: sm501: Fix potential memory leaks during remove (git-fixes).\n- misc: bcm-vk: Use acquire/release for msgq_inited (git-fixes).\n- misc: fastrpc: fix channel ctx ref leak when session alloc fails (git-fixes).\n- misc: fastrpc: fix memory leak in fastrpc_channel_ctx_free (git-fixes).\n- misc: fastrpc: Remove buffer from list prior to unmap operation (git-fixes).\n- misc: fastrpc: take fl-\u003elock when moving mmaps on interrupted invoke (git-fixes).\n- misc: nsm: bound the device-reported response length (git-fixes).\n- misc: rtsx: add missing write register handling (git-fixes).\n- misc: sgi-gru: remove interrupt-context page-table walks (git-fixes).\n- misc: vmc_vmci: Fix potential memory leak in vmci_event_subscribe() (git-fixes).\n- mkspec-dtb: Move DTS prefix into package list.\n- mkspec-dtb: Move provides-obsoletes to package list.\n- mkspec-dtb: Put per-architecture package lists into a hash.\n- mkspec-dtb: re-indent.\n- mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition (git-fixes).\n- mmc: omap_hsmmc: fix busy_timeout overflow in ns conversion on 32-bit (git-fixes).\n- mmc: sdhci: unmap the bounce buffer before device release (git-fixes).\n- mmc: via-sdmmc: stop card-detect handling on probe failure (git-fixes).\n- mtd: afs: validate v2 image info bounds (git-fixes).\n- mtd: fix double free and WARN_ON in add_mtd_device() error paths (git-fixes).\n- mtd: mtdoops: free page bitmap when the backing MTD is removed (git-fixes).\n- mtd: mtdswap: Avoid freeing registered blktrans device twice (git-fixes).\n- mtd: mtdswap: remove debugfs stats file on teardown (git-fixes).\n- mtd: nand: mtk-ecc: stop on ECC idle timeouts (git-fixes).\n- mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() (git-fixes).\n- mtd: rawnand: validate ONFI extended parameter page sections (git-fixes).\n- mtd: spinand: fix direct mapping creation sizes (stable-fixes).\n- mtd: spinand: repeat reading in regular mode if continuous reading fails (stable-fixes).\n- mtd: spinand: try a regular dirmap if creating a dirmap for continuous reading fails (stable-fixes).\n- mtd: ubi: Release device reference on busy detach (git-fixes).\n- mtd: ubi: skip programming unused bits in ubi headers (stable-fixes).\n- net: Add options as a flexible array to struct ip_tunnel_info (bsc#1274727).\n- net: mana: Add debug knob to skip TX timeout recovery reset (git-fixes).\n- net: mana: Add handler for sriov configure (bsc#1272756).\n- net: mana: Cap MSI-X vectors to the device MSI-X table size (git-fixes).\n- net: mana: Extend RX CQE coalescing up to 8 packets (git-fixes).\n- net: mana: Fall back to scattered pages for GDMA queues (git-fixes).\n- net: mana: force full-page RX buffers via ethtool private flag (bsc#1269792).\n- net: mana: refactor mana_get_strings() and mana_get_sset_count() to use switch (bsc#1269792).\n- net: mana: Route ring-buffer access through offset-based helpers (git-fixes).\n- net: tap: set skb-\u003edev before parsing virtio net header in tap_get_user_xdp() (git-fixes bsc#1274550).\n- net: thunderbolt: Count delivered packets in rx_packets and rx_bytes (git-fixes).\n- net: thunderbolt: Mark the connection down when bringing it up fails (git-fixes).\n- net: thunderbolt: Release the Rx HopID that was handed out on mismatch (git-fixes).\n- net: thunderbolt: Tear down DMA paths before stopping the rings (git-fixes).\n- net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup() (git-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: ipheth: fix carrier_work UAF on disconnect (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (git-fixes).\n- nfc: digital: clamp SENSF_RES length to the destination buffer (git-fixes).\n- nfc: digital: Do not dump a NULL response in command completion (git-fixes).\n- nfc: fdp: bound the device-reported read length and fix an skb leak (git-fixes).\n- nfc: llcp: avoid userspace overflow on invalid optlen (git-fixes).\n- nfc: llcp: bound SNL TLV parsing to the skb and add length checks (git-fixes).\n- nfc: llcp: bound the connect_sn TLV walk to the skb (git-fixes).\n- nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (git-fixes).\n- nfc: llcp: read llcp_sock-\u003elocal under the socket lock in getsockopt (git-fixes).\n- nfc: llcp: reject PDUs shorter than the LLCP header (git-fixes).\n- nfc: microread: validate target discovery payload lengths (git-fixes).\n- nfc: nci: fix double completion race in nci_data_exchange_complete (git-fixes).\n- nfc: nci: fix out-of-bounds write in nci_target_auto_activated() (git-fixes).\n- nfc: nci: fix uninit-value in the RF discover/activated NTF handlers (git-fixes).\n- nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing (git-fixes).\n- nfc: nci: free destination parameters when closing a connection (git-fixes).\n- nfc: pn533: hold a reference to the request skb during send_frame (git-fixes).\n- nfc: pn533: purge fragmented skbs during cleanup (git-fixes).\n- nfc: st21nfca: validate ATR_REQ length against the received frame (git-fixes).\n- nouveau/gem: reserve the bo in the info ioctl around the vma lookup (git-fixes).\n- nvme-tcp: fix usage of page_frag_cache (bsc#1267882).\n- nvmet-rdma: fix queue leak when connect backlog is exceeded (git-fixes).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- PCI/ASPM: Use pcie_capability_clear_and_set_word() for ASPM disable/restore (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (git-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (git-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI: Add ACS quirk for Pericom PI7C9X2G608 switches [12d8:2608] (git-fixes).\n- PCI: hv: Set irq_retrigger callback for the Hyper-V PCI MSI irqchip (git-fixes).\n- PCI: j721e: Fix incorrect max_lanes for J7200 (git-fixes).\n- PCI: meson: Fix GPIO state while requesting PERST# (git-fixes).\n- PCI: plda: Fix IRQ domain leaks in the error paths of plda_init_interrupts() (git-fixes).\n- PCI: plda: Fix use-after-free of event IRQs during teardown (git-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- pinctrl: bcm2835: Don't remove an unregistered GPIO chip (git-fixes).\n- pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip (git-fixes).\n- pinctrl: rockchip: Reset the pin count when recalculating SoC data (git-fixes).\n- platform/chrome: cros_ec_debugfs: Clean up console log on probe failure (git-fixes).\n- platform/chrome: cros_ec_debugfs: Unregister panic notifier (git-fixes).\n- platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count (git-fixes).\n- platform/chrome: sensorhub: Bound the EC-reported sensor number (git-fixes).\n- platform/chrome: sensorhub: Fix dropped timestamp events and log spam (git-fixes).\n- platform/chrome: sensorhub: Fix memory overread in ring handler (git-fixes).\n- platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL (git-fixes).\n- platform/surface: acpi-notify: Check ACPI companion before use (git-fixes).\n- platform/x86/amd/hsmp: Reject negative power cap writes in hwmon (git-fixes).\n- platform/x86: asus-wmi: fix resource leaks on probe failure (git-fixes).\n- platform/x86: dell-privacy: Fix race condition (git-fixes).\n- platform/x86: dell-wmi-base: Fix resource leak on module load failure (git-fixes).\n- platform/x86: dell-wmi-sysman: Don't hex dump attribute security buffer (git-fixes).\n- platform/x86: dell-wmi-sysman: Fix instance ID bounds (git-fixes).\n- platform/x86: hp-bioscfg: accept reduced ACPI packages from older HP BIOS (git-fixes).\n- platform/x86: hp-bioscfg: advance elem past consumed array elements (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store() (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read on empty password write (git-fixes).\n- platform/x86: hp-bioscfg: fix new_password_store() overwriting current_password (git-fixes).\n- platform/x86: hp-bioscfg: fix off-by-one write in hp_get_string_from_buffer() (git-fixes).\n- platform/x86: hp-bioscfg: fix ORD_LIST_ELEMENTS never being parsed (git-fixes).\n- platform/x86: hp-bioscfg: fix password encoding bounds check (git-fixes).\n- platform/x86: hp-bioscfg: warn on element type mismatch instead of failing (git-fixes).\n- platform/x86: ishtp_eclite: Fix ACPI device reference leak in probe error path (git-fixes).\n- platform/x86: ISST: Add a NULL check for sst_inst (git-fixes).\n- platform/x86: ISST: Just allow 2 bits for SST feature enable (git-fixes).\n- platform/x86: ISST: Return error during profile addition (git-fixes).\n- platform/x86: ISST: Use PP level enable mask (git-fixes).\n- platform/x86: ISST: Validate level in perf mask ioctls (git-fixes).\n- platform/x86: ISST: Validate logical CPU id and clos id (git-fixes).\n- platform/x86: ISST: Validate parameter for core power state (git-fixes).\n- platform/x86: ISST: Validate parameter for frequency and priority (git-fixes).\n- platform/x86: ISST: Validate socket ID in clos_assoc ioctl (git-fixes).\n- PM: hibernate: Fix memory leak in snapshot_write_next() error path (git-fixes).\n- PM: sleep: Fix off-by-one in wakelocks number limit check (git-fixes).\n- power: supply: bd99954: Drop bad register fields (git-fixes).\n- power: supply: bq27xxx: bq27z561: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq28z610: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq27520g4: fix REG_TTES address (git-fixes).\n- power: supply: bq256xx: drain usb_work before freeing the charger (git-fixes).\n- power: supply: bq24257: fix use-after-free on remove (git-fixes).\n- power: supply: bq25890: Fix power_supply reference leak (git-fixes).\n- power: supply: charger-manager: register regulators before exposing sysfs (git-fixes).\n- power: supply: cros_usbpd-charger: bound the EC-reported port count (git-fixes).\n- power: supply: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS (git-fixes).\n- power: supply: isp1704_charger: cancel work on remove (git-fixes).\n- power: supply: lp8727: fix use-after-free in lp8727_release_irq() (git-fixes).\n- power: supply: lp8788-charger: fix use-after-free on remove (git-fixes).\n- power: supply: max17040: drop incorrect I2C functionality check (git-fixes).\n- power: supply: max17040: propagate register read errors (git-fixes).\n- power: supply: max17040: synchronize work cancellation on suspend (git-fixes).\n- power: supply: qcom_battmgr: terminate the strings from firmware (git-fixes).\n- power: supply: rt9455: quiesce delayed work before teardown (git-fixes).\n- power: supply: sbs-battery: Use a per-device serial number buffer (git-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: twl4030_charger: cancel workers via devm (git-fixes).\n- power: supply: ucs1002: fix use-after-free on remove (git-fixes).\n- powercap: intel_rapl_tpmi: Handle PMU registration failure during probe (git-fixes).\n- powerpc/dt_cpu_ftrs: Set CPU_FTR_P11_PVR for Power11 and later processors (bsc#1263864 ltc#217835).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/pseries: Ensure vpa,slb_shadow \u0026 dtl are unregistered during crash (bsc#1271256).\n- powerpc/pseries: lparcfg - fix kbuf[] underflow (bsc#1274753 ltc#221289 bsc#1274754 ltc#221288 bsc#1274752\n  ltc#221290).\n- powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak (bsc#1274751 ltc#221105 bsc#1274750 ltc#221106).\n- powerpc/pseries: pci - logic bug (bsc#1274749 ltc#221282 bsc#1274755 ltc#221284 bsc#1274756 ltc#221283).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in non-uapi headers (bsc#1263864 ltc#217835).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in uapi headers (bsc#1263864 ltc#217835).\n- ppdev: prevent overflow when setting port timeout (git-fixes).\n- rapidio/tsi721: prevent a bad dereference in tsi721_db_dpc() (git-fixes).\n- rapidio: clear mport-\u003enet when rio_add_net() fails (git-fixes).\n- rapidio: mport_cdev: fix use-after-free in dma_req_free() (git-fixes).\n- RDMA/bnxt_re: Avoid displaying the kernel pointer (git-fixes).\n- RDMA/bnxt_re: Proper rollback if the ioremap fails (git-fixes).\n- RDMA/irdma: Remove redundant legacy_mode checks (git-fixes).\n- RDMA/mana_ib: drain QP references after partial table insertion (git-fixes).\n- RDMA/mana_ib: unify QP lookup table (git-fixes).\n- RDMA/mlx5: Fix integer overflow of user QP buffer size (git-fixes).\n- regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving dangling of_node pointer (git-fixes).\n- regulator: core: use system_freezable_wq for init complete work (git-fixes).\n- regulator: max8998_pmic_dt_parse_pdata: of_node_put on reg_np after ownership transferred to rdata (git-fixes).\n- regulator: qcom-refgen: correct the regulator type to CURRENT (git-fixes).\n- regulator: qcom-rpmh: Fix PMIC5 BOB bypass mode handling (git-fixes).\n- remoteproc: qcom: Fix glink-\u003enode reference leak in qcom_add_glink_subdev (git-fixes).\n- remoteproc: qcom_q6v5_adsp: Fix reference leak for device node (git-fixes).\n- remoteproc: scp: Fix device reference leak on failed lookup (git-fixes).\n- Revert \"drm/amdgpu: fix aperture mapping leak\" (git-fixes).\n- Revert \"media: v4l2-dev: fix error handling in __video_register_device()\" (git-fixes).\n- Revert \"net: thunderbolt: Enable end-to-end flow control also in transmit\" (git-fixes).\n- Revert \"thermal/drivers/hwmon: Cleanup coding style a bit\" (stable-fixes).\n- Revert \"wifi: mt76: Disable napi when removing device\" (git-fixes).\n- rpmsg: core: Fix incorrect return value documentation (git-fixes).\n- rpmsg: glink: smem: order FIFO read after availability check (git-fixes).\n- rtc: gamecube: check return value of devm_rtc_register_device() (git-fixes).\n- rtc: pcf8563: fix clock provider leak on unbind (git-fixes).\n- rtc: pcf85363: Add error checking to regmap calls in probe() (git-fixes).\n- rtc: rzn1: Disable alarm interrupt before reprogramming alarm registers (git-fixes).\n- rtc: rzn1: Fix weekday underflow when alarm crosses month boundary (git-fixes).\n- rtc: zynqmp: Return optional clock lookup errors (git-fixes).\n- s390/pkey: Check length in pkey_pckmo handler implementation (bsc#1270266).\n- s390/pkey: Check length in PKEY_VERIFYPROTK ioctl (bsc#1270267).\n- sched/psi: Create the psimon kthread outside of cgroup_mutex (bsc#1269134).\n- scsi: fnic: Abort timed-out NVMe LS requests (bsc#1236344).\n- scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths (bsc#1236344).\n- scsi: fnic: Add FDLS role handling for NVMe initiators (bsc#1236344).\n- scsi: fnic: Add the NVMe/FC transport path (bsc#1236344).\n- scsi: fnic: Advertise NVMe initiator service parameters (bsc#1236344).\n- scsi: fnic: Bump up version number (bsc#1236344).\n- scsi: fnic: Decode firmware role configuration (bsc#1236344).\n- scsi: fnic: Do not use GFP_ZERO for mempools (bsc#1236344).\n- scsi: fnic: Expose NVMe transport state in debugfs (bsc#1236344).\n- scsi: fnic: Handle NVMe LS frames in FDLS (bsc#1236344).\n- scsi: fnic: Make debug logging protocol independent (bsc#1236344).\n- scsi: fnic: Make fnic_queuecommand() easier to analyze (bsc#1236344).\n- scsi: fnic: Refactor in_remove flag and call to fnic_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Remove a useless struct mempool forward declaration (bsc#1236344).\n- scsi: fnic: Rename fnic_scsi_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Route completions and resets by initiator role (bsc#1236344).\n- scsi: fnic: Self-assignment of intr_time_type has no effect (bsc#1236344).\n- scsi: fnic: Send NVMe LS requests through FDLS (bsc#1236344).\n- scsi: fnic: Switch to use %ptSp (bsc#1236344).\n- scsi: fnic: Track NVMe transport statistics (bsc#1236344).\n- scsi: fnic: Use fnic_num for non-SCSI identifiers (bsc#1236344).\n- scsi: fnic: Use mempool for receive frames (bsc#1236344).\n- scsi: qla2xxx: Add support to report MPI FW state (bsc#1275737).\n- scsi: qla2xxx: Declare qla2xxx_mqueuecommand() static (bsc#1275737).\n- scsi: qla2xxx: Use nr_cpu_ids instead of NR_CPUS for qp_cpu_map allocation (bsc#1275737).\n- scsi: storvsc: Support manual scans for all Hyper-V targets (git-fixes).\n- sctp: avoid auth_enable sysctl UAF during netns teardown (git-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- serial: 8250_dma: Clear stale RX state on shutdown (git-fixes).\n- serial: amba-pl011: unprepare console clock on unregister (git-fixes).\n- serial: core: clear freed pointers on uart_register_driver() failure (git-fixes).\n- serial: imx: serialize imx_uart_ports lifetime (git-fixes).\n- serial: ma35d1: Fix OF node reference leaks in console init (git-fixes).\n- serial: qcom-geni: do not advance stale DMA completions (git-fixes).\n- serial: qcom-geni: fix TX DMA buffer flush (git-fixes).\n- serial: sc16is7xx: enable THRI before filling TX FIFO (git-fixes).\n- serial: sc16is7xx: rename EFR mutex with generic name (stable-fixes).\n- serial: sc16is7xx: use guards for simple mutex locks (stable-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb/client: handle overlapping allocated ranges in fallocate (bsc#1274902).\n- smb: client: harden POSIX SID length parsing (bsc#1273557).\n- smb: client: require net admin for CIFS SWN netlink (bsc#1273966).\n- smb: client: resolve SWN tcon from live registrations (bsc#1273872).\n- soc: fsl: qe: check platform_driver_register() in qe_ic_of_init() (git-fixes).\n- soc: qcom: rpmh-rsc: manage PM notifiers with devres (git-fixes).\n- soc: samsung: exynos-pmu: fix of_node refcount leak in exynos_get_pmu_regmap() (git-fixes).\n- software node: Fix software_node_get_reference_args() with index -1 (git-fixes).\n- soundwire: qcom: Fix port exhaustion check in stream_alloc_ports (git-fixes).\n- speakup: keyhelp: guard letter_offsets possible out-of-range indexing (git-fixes).\n- spi: bcm63xx-hsspi: disable clocks on resume failure (git-fixes).\n- spi: bcm63xx: disable clock on resume failure (git-fixes).\n- spi: bcmbca-hsspi: disable clocks on resume failure (git-fixes).\n- spi: davinci: switch to managed controller allocation (git-fixes).\n- spi: Fix DMA mapping ownership on partial map failure (git-fixes).\n- spi: img-spfi: don't disable runtime PM on DMA deferred probe (git-fixes).\n- spi: oc-tiny: switch to managed controller allocation (git-fixes).\n- spi: spi-cadence: enable SPI_CONTROLLER_MUST_TX (git-fixes).\n- spi: spi-cadence: Move TX FIFO full busy-wait into FIFO (git-fixes).\n- spi: spi-cadence: supports transmission with bits_per_word of 16 and 32 (stable-fixes).\n- spi: spi-fsl-dspi: Avoid setup_accel logic for DMA transfers (stable-fixes).\n- spi: sprd-adi: Fix probe succeeding without registering the controller (git-fixes).\n- staging: fbtft: Use sysfs_emit_at() to print to sysfs file (git-fixes).\n- staging: media: tegra-video: fix of_node_put() on VIP parse errors (git-fixes).\n- staging: media: tegra-video: vi: fix probe failure on skipped last port (git-fixes).\n- staging: octeon: add missing tasklet_kill in cvm_oct_tx_shutdown (git-fixes).\n- staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init() (git-fixes).\n- staging: rtl8723bs: fix missing shared-key auth challenge length check (git-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() (git-fixes).\n- staging: rtl8723bs: fix OOB read in WMM_param_handler() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: use kfree_sensitive() for key material (git-fixes).\n- staging: rtl8723bs: validate monitor transmit frame lengths (git-fixes).\n- staging: sm750fb: Add missing Kconfig dependency (git-fixes).\n- staging: sm750fb: gate dualview dataflow using g_dualview (git-fixes).\n- thermal/drivers/imx: Disable clock on runtime resume failure (git-fixes).\n- thermal/drivers/qoriq: Disable clock on resume failure (git-fixes).\n- thermal/drivers/rcar: Fix error checking in probe() (git-fixes).\n- thermal: intel: int3400: clean up ODVP on probe failures (git-fixes).\n- thermal: sysfs: switch to use scnprintf() to suppress truncation warning (git-fixes).\n- thunderbolt: Bound the DROM dual link port number before indexing sw-\u003eports (git-fixes).\n- thunderbolt: Fix bandwidth group reservation indexing (git-fixes).\n- thunderbolt: icm: Preserve USB4 proxy data-valid bit (git-fixes).\n- tlclk: if sscanf() fails, fall back to 0, not random value (git-fixes).\n- tpm: st33zp24: Return zero on status read failure (git-fixes).\n- tpm: st33zp24: Validate locality read result (git-fixes).\n- tpm: tpm_i2c_nuvoton: disable IRQ on wait timeout (git-fixes).\n- tty: clear cdev pointer after cdev_add() failure (git-fixes).\n- tty: hvc: restrict HVC_DCC to ARMv6+ and ARM64 (git-fixes).\n- tty: skip cdev_del() when no cdev is registered (git-fixes).\n- uio: Fix stale info pointer in failed registration path (git-fixes).\n- usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm() (git-fixes).\n- usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect (git-fixes).\n- usb: atm: usbatm: fix invalid ci_range initialization (git-fixes).\n- USB: c67x00: fix use-after-free in c67x00_add_iso_urb() (git-fixes).\n- usb: cdnsp: fix incorrect endian conversions for APB timeout register (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (git-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: core: sysfs: add lock to bos_descriptors_read() (stable-fixes).\n- usb: dwc2: add missing @remotewakeup kernel-doc parameter (git-fixes).\n- usb: dwc2: gadget: Exit partial power down state when changing USB pull-up (git-fixes).\n- usb: dwc3: clear forceRM when issuing EndTransfer (git-fixes).\n- usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: fix UAF when probe runs concurrent to dyn ID removal (git-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed (git-fixes).\n- usb: gadget: configfs: fix out-of-bounds read of qw_sign (git-fixes).\n- usb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths (git-fixes).\n- usb: gadget: f_fs: Prevent deadlock during ep0 read loop (git-fixes).\n- usb: gadget: f_midi: initialize work in f_midi_alloc() (git-fixes).\n- usb: gadget: f_ncm: Use unsigned int for ndp_index (git-fixes).\n- usb: gadget: f_tcm: fix deadlock in usbg_make_tpg() (git-fixes).\n- usb: gadget: f_uac1_legacy: remove broken string configfs attributes (git-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- USB: gadget: fsl-udc: fix dev_printk() device (git-fixes).\n- usb: gadget: midi2: Fix null-pointer dereference in f_midi2_free_ep_reqs (git-fixes).\n- usb: gadget: midi2: remove default configfs groups on teardown (git-fixes).\n- usb: gadget: pch_udc: remove excess kernel-doc member for registered (git-fixes).\n- usb: gadget: r8a66597: avoid double free of ep0_req in probe error path (git-fixes).\n- usb: gadget: snps_udc_plat: clean up PHY on probe deferral (git-fixes).\n- usb: gadget: u_audio: Fix use-after-free on sound card disconnect (git-fixes).\n- usb: gadget: uac: validate rate list length before storing (git-fixes).\n- USB: gadget: Use str_enable_disable-like helpers (stable-fixes).\n- usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and uvc_function_unbind() (git-fixes).\n- usb: ljca: bound bank_num in ljca_enumerate_gpio() (git-fixes).\n- usb: mtu3: allow system suspend during active gadget connection (git-fixes).\n- usb: musb: omap2430: clean up probe error handling (stable-fixes).\n- usb: musb: omap2430: Do not put borrowed of_node in probe (git-fixes).\n- usb: musb: omap2430: Fix use-after-free in omap2430_probe() (git-fixes).\n- USB: phy: fsl-usb: fix missing static keywords (git-fixes).\n- usb: renesas_usbhs: Fix power-off ordering on unbind (git-fixes).\n- USB: serial: digi_acceleport: fix port registration order (git-fixes).\n- USB: serial: ftdi_sio: add support for E+H FXA291 (stable-fixes).\n- USB: serial: option: add TDTECH MT5710-CN (stable-fixes).\n- USB: serial: option: fix slab OOB read in interrupt URB callback (git-fixes).\n- USB: serial: spcp8x5: drop broken carrier detect support (git-fixes).\n- USB: storage: add NO_ATA_1X quirk for Longmai USB Key (stable-fixes).\n- usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop (git-fixes).\n- usb: typec: qcom-pmic-typec: drain cc_debounce_dwork if port_start() fails (git-fixes).\n- usb: typec: qcom-pmic: cancel reset_work on stop (git-fixes).\n- usb: typec: tcpci: pass correct rx_type to tcpm_pd_receive() (git-fixes).\n- usb: typec: thunderbolt: Disable work before freeing tbt on remove (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: unregister debugfs entries on teardown (git-fixes).\n- usb: typec: ucsi: use UCSI_TIMEOUT_MS for sync command completion (git-fixes).\n- usb: usbfs: fix use-after-free of usb_device in usbdev_release() (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: xhci: Handle USB3 port events when there is one roothub (git-fixes).\n- vfs: Add a sysctl for automated deletion of dentry (bsc#1240890 bsc#1276586).\n- vt: add permission check for KDSKBMETA ioctl (stable-fixes).\n- vt: stabilize tty reference in kbd_keycode with tty_port_tty_get (stable-fixes).\n- w1: ds28e17: reject an oversize length on an I2C block read (git-fixes).\n- w1: ds2482: Fix signedness bug in ds2482_w1_triplet() (git-fixes).\n- watchdog: bd96801_wdt: Fix timeout for enabled WDG (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath6kl: avoid buffer overreads in WMI event handlers (git-fixes).\n- wifi: ath6kl: clamp assoc request/response lengths before subtracting IE offsets (git-fixes).\n- wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump (git-fixes).\n- wifi: ath11k: Avoid buffer overread in ath11k_wmi_tlv_op_rx() (git-fixes).\n- wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate (git-fixes).\n- wifi: ath11k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath12k: Avoid buffer overread in ath12k_wmi_op_rx() (git-fixes).\n- wifi: ath12k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: brcmfmac: Fix memory leak in brcmf_sdio_read_control() (git-fixes).\n- wifi: brcmfmac: fix P2P action frame handling without device vif (git-fixes).\n- wifi: brcmfmac: initialize SDIO data work before cleanup (git-fixes).\n- wifi: cfg80211: bound element ID read when checking non-inheritance (git-fixes).\n- wifi: cfg80211: cancel sched scan results work on unregister (git-fixes).\n- wifi: cfg80211: derive S1G beacon TSF from S1G fields (git-fixes).\n- wifi: cfg80211: reject unsupported PMSR FTM location requests (git-fixes).\n- wifi: cfg80211: validate PMSR FTM preamble range (git-fixes).\n- wifi: cfg80211: validate PMSR measurement type data (git-fixes).\n- wifi: ipw2100: fix potential memory leak in ipw2100_pci_init_one() (git-fixes).\n- wifi: iwlwifi: fix counter type in iwl_fwrt_dump_error_logs (git-fixes).\n- wifi: iwlwifi: guard against division by zero in iwl_dbg_tlv_alloc_fragments (git-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mei: pass correct argument to function (git-fixes).\n- wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser (git-fixes).\n- wifi: libertas: fix memory leak in helper_firmware_cb() (git-fixes).\n- wifi: mac80211: disconnect on CSA to channel 0 (git-fixes).\n- wifi: mac80211: fix fils_discovery double free on alloc failure (git-fixes).\n- wifi: mac80211: fix per-STA profile length in cross-link CSA parsing (git-fixes).\n- wifi: mac80211: fix unsol_bcast_probe_resp double free on alloc failure (git-fixes).\n- wifi: mac80211: free AP_VLAN bc_buf SKBs outside IRQ lock (git-fixes).\n- wifi: mac80211: send TWT teardown to peer after setup TX failure (git-fixes).\n- wifi: mac80211: skip default WMM setup for AP_VLAN links (git-fixes).\n- wifi: mac80211: skip unused probe response countdown offsets (git-fixes).\n- wifi: mt76: check txfree done event on the WED hw path (git-fixes).\n- wifi: mt76: fix 4th chain ACK RSSI bitmask in sta_poll (git-fixes).\n- wifi: mt76: fix ER-SU 106-tone RU check in RX rate decode (git-fixes).\n- wifi: mt76: fix HE DCM max-RU capability encoding (git-fixes).\n- wifi: mt76: fix non-AQL packet accounting for MLO stations (git-fixes).\n- wifi: mt76: fix stranded frames in mt76_txq_schedule_pending (git-fixes).\n- wifi: mt76: mt76x02: do not WARN on invalid rx descriptor length (git-fixes).\n- wifi: mt76: mt792x: Fix memory leak in SDIO TX path (git-fixes).\n- wifi: mt76: mt792x: fix use-after-free in mt76_rx_poll_complete (git-fixes).\n- wifi: mt76: mt7615: avoid waiting for mac work under the mt76 mutex (git-fixes).\n- wifi: mt76: mt7915: avoid nss underflow in mt7915_mcu_get_sta_nss (git-fixes).\n- wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear (git-fixes).\n- wifi: mt76: mt7915: fix double hif2 init on the non-WED path (git-fixes).\n- wifi: mt76: mt7915: fix ext PHY use-after-free on register error path (git-fixes).\n- wifi: mt76: mt7915: fix net_fill_forward_path for non-DBDC mt7986 (git-fixes).\n- wifi: mt76: mt7915: poll the correct SLP CTRL register for the second adie (git-fixes).\n- wifi: mt76: mt7915: release hif2 reference on probe IRQ failure (git-fixes).\n- wifi: mt76: mt7915: unlink TWT flow if the MCU rejects the agreement (git-fixes).\n- wifi: mt76: mt7915: unwind state on add_interface failure (git-fixes).\n- wifi: mt76: mt7915: use little-endian for bss_info_ra wire fields (git-fixes).\n- wifi: mt76: mt7915: write RX header translation bit to the correct register (git-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: mt7921: validate CLC firmware records (git-fixes).\n- wifi: mt76: mt7925: ensure tx headroom in usb_sdio_tx_prepare_skb (git-fixes).\n- wifi: mt76: mt7925: fix msg len mismatch between driver and firmware (git-fixes).\n- wifi: mt76: mt7925: update clc before setting sar power table (git-fixes).\n- wifi: mt76: mt7996: bound TLV walk in mt7996_mcu_get_chip_config (git-fixes).\n- wifi: mt76: mt7996: don't report a zero TX bitrate (git-fixes).\n- wifi: mt76: mt7996: fix capability of EHT-MCS 15 in MRU (git-fixes).\n- wifi: mt76: mt7996: fix reg addr remap when addr is 0 (git-fixes).\n- wifi: mt76: mt7996: reserve space for the CSA-abort countdown TLV (git-fixes).\n- wifi: mt76: mt7996: set MT76_MCU_RESET before waking MCU waiters on full reset (git-fixes).\n- wifi: mt76: mt7996: validate RX band_idx before dereferencing phys (git-fixes).\n- wifi: mt76: only consume the WO drop bit on WED v2 devices (git-fixes).\n- wifi: mt76: report data NSS for STBC frames in RX rate decode (git-fixes).\n- wifi: mwifiex: Detach sync cmd buffer on interrupted wait (git-fixes).\n- wifi: nl80211: free RNR data on MBSSID mismatch (git-fixes).\n- wifi: nl80211: validate nested MBSSID IE blobs (git-fixes).\n- wifi: p54: validate RX frame length in p54_rx_eeprom_readback() (git-fixes).\n- wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop (git-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtlwifi: pci: fix error path in rtl_pci_probe() (git-fixes).\n- wifi: rtlwifi: rtl8192du: check QoS TID before indexing tids (git-fixes).\n- wifi: rtlwifi: rtl8192du: Fix possible memory leak in rtl92du_init_sw_vars() (git-fixes).\n- wifi: rtw88: Fix potential memory leak in rtw_txq_push_skb() (git-fixes).\n- wifi: rtw88: pci: fix resource leak on failed NAPI setup (git-fixes).\n- wifi: rtw89: fix HE extended capability length check (git-fixes).\n- wifi: zd1211rw: reject secondary interfaces to prevent conflicts (git-fixes).\n- x86/virt/tdx: Print TDX module version during init (git-fixes).\n- x86/virt/tdx: Retrieve TDX module version (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_alloc_driver() failure (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_register_driver() failure (git-fixes).\n- xhci: fix lost bounce buffers on TDs spanning several ring segments (git-fixes).\n","status":"published","published":"2026-09-22T14:23:31Z","modified":"2026-09-30T18:23:11.253192518Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"SUSE-SU-2026:23897-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-68214: timers: Fix NULL function pointer race in timer_shutdown_sync() (bsc#1255225).\n- CVE-2025-68358: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() (bsc#1255531).\n- CVE-2025-68780: sched/deadline: only set free_cpus for online runqueues (bsc#1256671).\n- CVE-2025-71075: scsi: aic94xx: fix use-after-free in device removal path (bsc#1256629).\n- CVE-2026-23113: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (bsc#1258278).\n- CVE-2026-23306: scsi: pm8001: Fix use-after-free in pm8001_queue_command() (bsc#1260501).\n- CVE-2026-23348: cxl/mem: Clarify @host for devm_cxl_add_nvdimm() (bsc#1260577).\n- CVE-2026-31418: netfilter: ipset: drop logically empty buckets in mtype_del (bsc#1262073).\n- CVE-2026-31530: cxl/port: Fix use after free of parent_port in cxl_detach_ep() (bsc#1262756).\n- CVE-2026-31531: ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop() (bsc#1263004).\n- CVE-2026-43116: netfilter: ctnetlink: ensure safe access to master conntrack (bsc#1264619).\n- CVE-2026-43125: dlm: validate length in dlm_search_rsb_tree (bsc#1264541).\n- CVE-2026-43163: md/bitmap: fix GPF in write_page caused by resize race (bsc#1264335).\n- CVE-2026-43239: smb: client: prevent races in -\u003equery_interfaces() (bsc#1264444).\n- CVE-2026-43271: md-cluster: fix NULL pointer dereference in process_metadata_update (bsc#1264587).\n- CVE-2026-43299: btrfs: do not ASSERT() when the fs flips RO inside btrfs_repair_io_failure() (bsc#1264851).\n- CVE-2026-43331: x86/kexec: Disable KCOV instrumentation after load_segments() (bsc#1265132).\n- CVE-2026-43355: iio: light: bh1780: fix PM runtime leak on error path (bsc#1265036).\n- CVE-2026-43363: x86/apic: Disable x2apic on resume if the kernel expects so (bsc#1265068).\n- CVE-2026-43416: powerpc, perf: Check that current-\u003emm is alive before getting user callchain (bsc#1265121).\n- CVE-2026-43439: cgroup: fix race between task migration and iteration (bsc#1265141).\n- CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807).\n- CVE-2026-45860: netfilter: nf_conncount: increase the connection clean up limit to 64 (bsc#1266710).\n- CVE-2026-45897: netfilter: nft_counter: serialize reset with spinlock (bsc#1266897).\n- CVE-2026-45968: cpuidle: Skip governor when only one idle state is available (bsc#1267023).\n- CVE-2026-46007: hwmon: (powerz) Avoid cacheline sharing for DMA buffer (bsc#1267586).\n- CVE-2026-46070: md/raid5: validate payload size before accessing journal metadata (bsc#1267501).\n- CVE-2026-46107: dm-thin: fix metadata refcount underflow (bsc#1267612).\n- CVE-2026-46115: block: add pgmap check to biovec_phys_mergeable (bsc#1266874).\n- CVE-2026-46133: RDMA/rxe: Reject unknown opcodes before ICRC processing (bsc#1266928).\n- CVE-2026-46135: nvmet-tcp: remove redundant calls to nvmet_tcp_fatal_error() (bsc#1267373).\n- CVE-2026-46195: smb: client: validate dacloffset before building DACL pointers (bsc#1266860).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-52920: netfilter: xt_policy: fix strict mode inbound policy matching (bsc#1269013).\n- CVE-2026-52928: af_unix: Reject SIOCATMARK on non-stream sockets (bsc#1269010).\n- CVE-2026-52929: sctp: stream: fully roll back denied add-stream state (bsc#1269004).\n- CVE-2026-52935: xfrm: espintcp: do not reuse an in-progress partial send (bsc#1268979).\n- CVE-2026-52939: net/rds: fix NULL deref in rds_ib_send_cqe_handler() on masked atomic completion (bsc#1268972).\n- CVE-2026-52946: fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling (bsc#1269113).\n- CVE-2026-52977: futex: Prevent lockup in requeue-PI during signal/ timeout wakeup (bsc#1269242).\n- CVE-2026-52990: fsnotify: fix inode reference leak in fsnotify_recalc_mask() (bsc#1269108).\n- CVE-2026-52991: sched/psi: fix race between file release and pressure write (bsc#1269134).\n- CVE-2026-52994: vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting (bsc#1269126).\n- CVE-2026-53001: netfilter: xtables: restrict several matches to inet family (bsc#1269114).\n- CVE-2026-53031: bpf: Validate node_id in arena_alloc_pages() (bsc#1269380).\n- CVE-2026-53033: bpf, sockmap: Take state lock for af_unix iter (bsc#1269388).\n- CVE-2026-53034: bpf, sockmap: Fix af_unix null-ptr-deref in proto update (bsc#1269140).\n- CVE-2026-53048: gfs2: prevent NULL pointer dereference during unmount (bsc#1269162).\n- CVE-2026-53059: dm log: fix out-of-bounds write due to region_count overflow (bsc#1269655).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53076: bpf: Fix OOB in pcpu_init_value (bsc#1269695).\n- CVE-2026-53077: net/rds: Restrict use of RDS/IB to the initial network namespace (bsc#1269412).\n- CVE-2026-53089: bpf: Fix use-after-free in offloaded map/prog info fill (bsc#1269783).\n- CVE-2026-53091: net: account for encap headers in qdisc pkt len (bsc#1269530).\n- CVE-2026-53092: bpf: Fix linked reg delta tracking when src_reg == dst_reg (bsc#1269528).\n- CVE-2026-53094: bpf: Fix stale offload-\u003eprog pointer after constant blinding (bsc#1269965).\n- CVE-2026-53096: bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path (bsc#1269969).\n- CVE-2026-53109: powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy (bsc#1269417).\n- CVE-2026-53110: s390: always declare expoline thunks (bsc#1269985).\n- CVE-2026-53111: bpf: test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap (bsc#1269167).\n- CVE-2026-53114: perf: Extend the bit width of the arch-specific flag (bsc#1269999).\n- CVE-2026-53126: blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() (bsc#1269635).\n- CVE-2026-53129: fs/mbcache: cancel shrink work before destroying the cache (bsc#1269633).\n- CVE-2026-53142: drm/xe/display: fix oops in suspend/shutdown without display (bsc#1269402).\n- CVE-2026-53154: mm/hugetlb: restore reservation on error in hugetlb folio copy paths (bsc#1269665).\n- CVE-2026-53163: locking/rtmutex: Skip remove_waiter() when waiter is not enqueued (bsc#1269306).\n- CVE-2026-53180: timers/migration: Fix livelock in tmigr_handle_remote_up() (bsc#1269888).\n- CVE-2026-53207: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison (bsc#1269590).\n- CVE-2026-53219: netfilter: x_tables: avoid leaking percpu counter pointers (bsc#1269686).\n- CVE-2026-53220: netfilter: revalidate bridge ports (bsc#1269381).\n- CVE-2026-53223: net: guard timestamp cmsgs to real error queue skbs (bsc#1269301).\n- CVE-2026-53228: ipv6: sit: reload inner IPv6 header after GSO offloads (bsc#1269256).\n- CVE-2026-53238: netlabel: validate unlabeled address and mask attribute lengths (bsc#1269774).\n- CVE-2026-53264: net/sched: act_api: use RCU with deferred freeing for action lifecycle (bsc#1269238).\n- CVE-2026-53269: netfilter: synproxy: add mutex to guard hook reference counting (bsc#1269579).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53291: ALSA: hda/conexant: Fix missing error check for jack detection (bsc#1269697).\n- CVE-2026-53309: ocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison (bsc#1269815).\n- CVE-2026-53330: drm/amd/display: Fix out-of-bounds read in (bsc#1270090).\n- CVE-2026-53336: nvmem: layouts: onie-tlv: fix hang on unknown types (bsc#1270108).\n- CVE-2026-53337: net: bonding: fix NULL pointer dereference in bond_do_ioctl() (bsc#1270251).\n- CVE-2026-53341: fhandle: fix UAF due to unlocked -\u003emnt_ns read in may_decode_fh() (bsc#1270139).\n- CVE-2026-53353: hsr: Remove WARN_ONCE() in hsr_addr_is_self() (bsc#1270111).\n- CVE-2026-53365: vsock/virtio: fix zerocopy completion for multi-skb sends (bsc#1271365).\n- CVE-2026-63801: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (bsc#1272230).\n- CVE-2026-63803: hdlc_ppp: sync per-proto timers before freeing hdlc state (bsc#1272284).\n- CVE-2026-63804: gfs2: fix use-after-free in gfs2_qd_dealloc (bsc#1272287).\n- CVE-2026-63808: exfat: fix potential use-after-free in exfat_find_dir_entry() (bsc#1272260).\n- CVE-2026-63810: block: Avoid mounting the bdev pseudo-filesystem in userspace (bsc#1272297).\n- CVE-2026-63823: keys: Pin request_key_auth payload in instantiate paths (bsc#1272182).\n- CVE-2026-63828: apparmor: mediate the implicit connect of TCP fast open sendmsg (bsc#1272175).\n- CVE-2026-63860: RDMA/core: Prefer NLA_NUL_STRING (bsc#1272429).\n- CVE-2026-63865: bpf: Drop task_to_inode and inet_conn_established from lsm sleepable hooks (bsc#1272486).\n- CVE-2026-63868: net: garp: fix unsigned integer underflow in garp_pdu_parse_attr (bsc#1272497).\n- CVE-2026-63879: drm/amdgpu: fix amdgpu_hmm_range_get_pages (bsc#1272569).\n- CVE-2026-63887: scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf (bsc#1272385).\n- CVE-2026-63888: scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd() (bsc#1272390).\n- CVE-2026-63889: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (bsc#1272423).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63891: thunderbolt: property: Cap recursion depth in __tb_property_parse_dir() (bsc#1272641).\n- CVE-2026-63901: USB: serial: digi_acceleport: fix memory corruption with small endpoints (bsc#1272501).\n- CVE-2026-63917: ip6: vti: Use ip6_tnl.net in vti6_changelink() (bsc#1272904).\n- CVE-2026-63918: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname (bsc#1272905).\n- CVE-2026-63920: ipv6: validate extension header length before copying to cmsg (bsc#1272877).\n- CVE-2026-63921: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate() (bsc#1272918).\n- CVE-2026-63922,CVE-2026-63924: ipv6: exthdrs: refresh nh after handling HAO option (bsc#1272855).\n- CVE-2026-63925: macsec: fix replay protection at XPN lower-PN wrap (bsc#1273008).\n- CVE-2026-63926: bpf: sockmap: fix tail fragment offset in bpf_msg_push_data (bsc#1273019).\n- CVE-2026-63941: KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor (bsc#1272869).\n- CVE-2026-63969: ipv6: fix possible infinite loop in rt6_fill_node() (bsc#1272484).\n- CVE-2026-63970: vsock/virtio: bind uarg before filling zerocopy skb (bsc#1272673).\n- CVE-2026-63984: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() (bsc#1272865).\n- CVE-2026-63985: ethtool: eeprom: add more safeties to EEPROM Netlink fallback (bsc#1272963).\n- CVE-2026-63986: ethtool: tsinfo: don't pass ERR_PTR to genlmsg_cancel on prepare failure (bsc#1272969).\n- CVE-2026-63987: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (bsc#1272971).\n- CVE-2026-63990: bonding: refuse to enslave CAN devices (bsc#1273027).\n- CVE-2026-63992: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() (bsc#1272868).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-63995: ethtool: cmis: validate start_cmd_payload_size from module (bsc#1273033).\n- CVE-2026-63996: ethtool: cmis: require exact CDB reply length (bsc#1273032).\n- CVE-2026-63997: ethtool: module: avoid leaking a netdev ref on module flash errors (bsc#1273036).\n- CVE-2026-63998: ethtool: module: call ethnl_ops_complete() on module flash errors (bsc#1273037).\n- CVE-2026-63999: ethtool: rss: fix indir_table and hkey leak on get_rxfh failure (bsc#1273038).\n- CVE-2026-64000: net: hsr: fix potential OOB access in supervision frame handling (bsc#1273030).\n- CVE-2026-64002: ipv4: free net-\u003eipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (bsc#1273774).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64004: net/iucv: fix locking in .getsockopt (bsc#1273804).\n- CVE-2026-64005: net/smc: Do not re-initialize smc hashtables (bsc#1273831).\n- CVE-2026-64006: netfilter: nf_tables: fix dst corruption in same register operation (bsc#1273834).\n- CVE-2026-64007: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (bsc#1273105).\n- CVE-2026-64017: blk-mq: pop cached request if it is usable (bsc#1273770).\n- CVE-2026-64024: tcp: fix stale per-CPU tcp_tw_isn leak enabling ISN prediction (bsc#1273107).\n- CVE-2026-64033: RDMA/rtrs: Fix use-after-free in path file creation cleanup (bsc#1273134).\n- CVE-2026-64047: net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring (bsc#1273060).\n- CVE-2026-64048: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot (bsc#1273484).\n- CVE-2026-64052: block: bio-integrity: Fix null-ptr-deref in bio_integrity_map_user() (bsc#1272983).\n- CVE-2026-64053: block: don't overwrite bip_vcnt in bio_integrity_copy_user() (bsc#1272985).\n- CVE-2026-64054: net: shaper: reject duplicate leaves in GROUP request (bsc#1272894).\n- CVE-2026-64055: net: ethernet: cortina: Carry over frag counter (bsc#1272893).\n- CVE-2026-64056: net: ethernet: cortina: Make RX SKB per-port (bsc#1272502).\n- CVE-2026-64071: nvme-pci: fix use-after-free in nvme_free_host_mem() (bsc#1273486).\n- CVE-2026-64073: irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT (bsc#1273490).\n- CVE-2026-64088: batman-adv: tt: fix negative tt_buff_len (bsc#1273463).\n- CVE-2026-64089: batman-adv: tt: fix negative last_changeset_len (bsc#1272513).\n- CVE-2026-64093: batman-adv: tp_meter: directly shut down timer on cleanup (bsc#1273461).\n- CVE-2026-64099: drm/v3d: Fix use-after-free of CPU job query arrays on error path (bsc#1273465).\n- CVE-2026-64102: RDMA/siw: Reject MPA FPDU length underflow before signed receive math (bsc#1272516).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64109: af_unix: Fix UAF read of tail-\u003elen in unix_stream_data_wait() (bsc#1273748).\n- CVE-2026-64111: lsm: hold cred_guard_mutex for lsm_set_self_attr() (bsc#1273740).\n- CVE-2026-64112: rbd: eliminate a race in lock_dwork draining on unmap (bsc#1273741).\n- CVE-2026-64113: ixgbevf: fix use-after-free in VEPA multicast source pruning (bsc#1272262).\n- CVE-2026-64114: ipv4: raw: reject IP_HDRINCL packets with ihl \u003c 5 (bsc#1273742).\n- CVE-2026-64115: vsock/vmci: fix UAF when peer resets connection during handshake (bsc#1273745).\n- CVE-2026-64118: qed: fix double free in qed_cxt_tables_alloc() (bsc#1273749).\n- CVE-2026-64119: l2tp: use list_del_rcu in l2tp_session_unhash (bsc#1273746).\n- CVE-2026-64121: net: ifb: report ethtool stats over num_tx_queues (bsc#1273743).\n- CVE-2026-64125: net: bcmgenet: keep RBUF EEE/PM disabled (bsc#1272346).\n- CVE-2026-64131: mm/memory: fix spurious warning when unmapping device-private/exclusive pages (bsc#1274063).\n- CVE-2026-64146: erofs: fix metabuf leak in inode xattr initialization (bsc#1273681).\n- CVE-2026-64147: pds_core: fix debugfs_lookup dentry leak and error handling (bsc#1273119).\n- CVE-2026-64148: pds_core: fix error handling in pdsc_devcmd_wait (bsc#1273956).\n- CVE-2026-64162: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (bsc#1272366).\n- CVE-2026-64164: btrfs: tracepoints: fix sleep while in atomic context in btrfs_sync_file() (bsc#1273957).\n- CVE-2026-64177: phonet/pep: disable BH around forwarded sk_receive_skb() (bsc#1272148).\n- CVE-2026-64179: net: wwan: iosm: fix potential memory leaks in ipc_imem_init() (bsc#1272149).\n- CVE-2026-64180: mm/memory_hotplug: fix memory block reference leak on remove (bsc#1273679).\n- CVE-2026-64184: mm/damon/sysfs-schemes: call missing mem_cgroup_iter_break() (bsc#1272199).\n- CVE-2026-64185: sysfs: don't remove existing directory on update failure (bsc#1272200).\n- CVE-2026-64190: net: team: fix NULL pointer dereference in team_xmit during mode change (bsc#1272210).\n- CVE-2026-64192: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized (bsc#1272213).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64214: powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise()\n  (bsc#1272799).\n- CVE-2026-64217: netfs: Fix overrun check in netfs_extract_user_iter() (bsc#1272798).\n- CVE-2026-64222: octeontx2-pf: avoid double free of pool-\u003estack on AQ init failure (bsc#1272788).\n- CVE-2026-64224: octeontx2-pf: fix double free in rvu_rep_rsrc_init() (bsc#1272804).\n- CVE-2026-64225: octeontx2-af: CGX: add bounds check to cgx_speed_mbps index (bsc#1272786).\n- CVE-2026-64232: block: recompute nr_integrity_segments in blk_insert_cloned_request (bsc#1272791).\n- CVE-2026-64239: mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() (bsc#1273898).\n- CVE-2026-64244: drivers/base/memory: set mem-\u003ealtmap after successful device registration (bsc#1273812).\n- CVE-2026-64253: kernel/fork: clear PF_BLOCK_TS in copy_process() (bsc#1273904).\n- CVE-2026-64256: xfs: don't wrap around quota ids in dqiterate (bsc#1273271).\n- CVE-2026-64265: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req (bsc#1273947).\n- CVE-2026-64268: RDMA/siw: bound Read Response placement to the RREAD length (bsc#1273276).\n- CVE-2026-64269: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg (bsc#1273280).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64286: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU (bsc#1274058).\n- CVE-2026-64287: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU (bsc#1273325).\n- CVE-2026-64294: mm: do file ownership checks with the proper mount idmap (bsc#1273525).\n- CVE-2026-64296: exfat: bound uniname advance in exfat_find_dir_entry() (bsc#1273975).\n- CVE-2026-64298: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (bsc#1273550).\n- CVE-2026-64300: perf/aux: Fix page UAF in map_range() (bsc#1273852).\n- CVE-2026-64307: crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG) (bsc#1273567).\n- CVE-2026-64315: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1274028).\n- CVE-2026-64316: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1273598).\n- CVE-2026-64317: isofs: bound Rock Ridge symlink components to the SL record (bsc#1273936).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64321: nvme: target: rdma: fix ndev refcount leak on queue connect (bsc#1273864).\n- CVE-2026-64322: udf: validate sparing table length as an entry count, not a byte count (bsc#1273958).\n- CVE-2026-64323: udf: validate VAT header length against the VAT inode size (bsc#1273305).\n- CVE-2026-64326: block: skip sync_blockdev() on surprise removal in bdev_mark_dead() (bsc#1273312).\n- CVE-2026-64327: usb: gadget: f_fs: Initialize epfile-\u003ein early to fix endpoint direction checks (bsc#1273283).\n- CVE-2026-64354: bpf: Validate BTF repeated field counts before expansion (bsc#1274060).\n- CVE-2026-64355: bpf: Reject fragmented frames in devmap (bsc#1273422).\n- CVE-2026-64364: HID: multitouch: fix out-of-bounds bit access on mt_io_flags (bsc#1273495).\n- CVE-2026-64368: mm/slab: do not limit zeroing to orig_size when only red zoning is enabled (bsc#1273997).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64375: proc: protect ptrace_may_access() with exec_update_lock (FD links) (bsc#1273868).\n- CVE-2026-64378: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (bsc#1273603).\n- CVE-2026-64381: smb: client: Fix next buffer leak in receive_encrypted_standard() (bsc#1273860).\n- CVE-2026-64382: smb: client: fix double-free in SMB2_open() replay (bsc#1273291).\n- CVE-2026-64383: smb: client: fix double-free in SMB2_flush() replay (bsc#1273426).\n- CVE-2026-64384: smb: client: fix change notify replay double-free (bsc#1274541).\n- CVE-2026-64385: smb: client: fix double-free in SMB2_ioctl() replay (bsc#1274539).\n- CVE-2026-64386: smb: client: fix query_info() replay double-free (bsc#1274543).\n- CVE-2026-64387: smb: client: fix query directory replay double-free (bsc#1274545).\n- CVE-2026-64411: netfilter: ebtables: terminate table name before find_table_lock() (bsc#1274077).\n- CVE-2026-64412: netfilter: ebtables: module names must be null-terminated (bsc#1273780).\n- CVE-2026-64415: mm/swap: add cond_resched() in swap_reclaim_full_clusters to prevent softlockup (bsc#1273317).\n- CVE-2026-64416: mm: swap_cgroup: fix NULL deref in lookup_swap_cgroup_id on swapless host (bsc#1273286).\n- CVE-2026-64423: ipv4: igmp: remove multicast group from hash table on device destruction (bsc#1274274).\n- CVE-2026-64434: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref (bsc#1273880).\n- CVE-2026-64436: net: af_key: initialize alg_key_len for IPComp states (bsc#1274277).\n- CVE-2026-64450: tipc: fix out-of-bounds read in broadcast Gap ACK blocks (bsc#1273523).\n- CVE-2026-64452: 6lowpan: fix NHC entry use-after-free on error path (bsc#1273460).\n- CVE-2026-64458: mm/damon/ops-common: handle extreme intervals in damon_hot_score() (bsc#1273788).\n- CVE-2026-64463: usb: typec: tcpci_rt1711h: unregister TCPCI port with devres (bsc#1273273).\n- CVE-2026-64472: vfio/mlx5: Fix racy bitfields and tighten struct layout (bsc#1274075).\n- CVE-2026-64477: x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled (bsc#1274264).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64518: tcp: Fix out-of-bounds access for twsk in tcp_ao_established_key() (bsc#1273524).\n- CVE-2026-64519: NFSD: Fix infinite loop in layout state revocation (bsc#1274252).\n- CVE-2026-64526: ethtool: tsconfig: fix missing ethnl_ops_complete() (bsc#1274052).\n- CVE-2026-64534: nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error (bsc#1273803).\n- CVE-2026-64535: nvmet-tcp: Fix potential UAF when ddgst mismatch (bsc#1273809).\n- CVE-2026-64537: bridge: cfm: reject invalid CCM interval at configuration time (bsc#1273289).\n- CVE-2026-64538: ipv6: Fix null-ptr-deref in fib6_nh_mtu_change() (bsc#1273335).\n- CVE-2026-64541: net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket (bsc#1273303).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64543: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() (bsc#1273311).\n- CVE-2026-64545: net, bpf: check master for NULL in xdp_master_redirect() (bsc#1273318).\n- CVE-2026-64548: bpf, sockmap: reject overflowing copy + len in bpf_msg_push_data() (bsc#1273337).\n- CVE-2026-64551: sctp: validate STALE_COOKIE cause length before reading staleness (bsc#1273813).\n- CVE-2026-64552: virtio-net: fix len check in receive_big() (bsc#1273323).\n- CVE-2026-64553: net: psample: fix info leak in PSAMPLE_ATTR_DATA (bsc#1273336).\n- CVE-2026-64554: netfilter: bridge: fix stale prevhdr pointer in br_ip6_fragment() (bsc#1273340).\n- CVE-2026-64555: KVM: arm64: nv: Fix SPSR_EL2 restore in kvm_hyp_handle_mops() (bsc#1273331).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64563: rhashtable: clear stale iter-\u003ep on table restart (bsc#1273995).\n- CVE-2026-64567: btrfs: reject free space cache with more entries than pages (bsc#1274006).\n- CVE-2026-64569: mpls: fix NULL deref in mpls_valid_fib_dump_req() on CONFIG_INET=n (bsc#1274009).\n- CVE-2026-64572: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (bsc#1274014).\n- CVE-2026-64576: nexthop: initialize extack in nh_res_bucket_migrate() (bsc#1274030).\n- CVE-2026-64577: gtp: check skb_pull_data() return in gtp1u_send_echo_resp() (bsc#1274031).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64581: xfrm: fix sk_dst_cache double-free in xfrm_user_policy() (bsc#1274041).\n- CVE-2026-64582: RDMA/rxe: Fix a use-after-free problem in rxe_mmap (bsc#1274040).\n- CVE-2026-64586: wifi: brcmfmac: drain bus_reset work on device removal (bsc#1274492).\n- CVE-2026-68082: libceph: fix two unsafe bare decodes in decode_lockers() (bsc#1274581).\n- CVE-2026-68086: mm/khugepaged: write all dirty file folios when collapsing (bsc#1274713).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68105: drm/amdgpu: Fix kernel panic during driver load failure (bsc#1274849).\n- CVE-2026-68116: vxlan: mdb: Fix source list corruption on a failed replace (bsc#1274876).\n- CVE-2026-68117: tipc: clear sock-\u003esk on the failed-insert path in tipc_sk_create() (bsc#1274881).\n- CVE-2026-68120: rtase: Workaround for TX hang caused by hardware packet parsing (bsc#1274887).\n- CVE-2026-68121: pppoe: reload header pointer after dev_hard_header() (bsc#1274888).\n- CVE-2026-68123: openvswitch: fix GSO userspace truncation underflow (bsc#1275169).\n- CVE-2026-68124: mctp: serial: handle zero-length frames to prevent rx buffer overflow (bsc#1275192).\n- CVE-2026-68127: ila: reload IPv6 header after pskb_may_pull in checksum adjust (bsc#1275237).\n- CVE-2026-68128: ice: reject out-of-range ptype in ice_parser_profile_init (bsc#1275238).\n- CVE-2026-68129: gve: fix Rx queue stall on alloc failure (bsc#1275517).\n- CVE-2026-68132: super: fix emergency thaw deadlock on frozen block devices (bsc#1275553).\n- CVE-2026-68133: ice: fix PTP Call Trace during PTP release (bsc#1275555).\n- CVE-2026-68135: net: hip04: fix RX buffer leak on build_skb failure (bsc#1275557).\n- CVE-2026-68136: net: gro: fix double aggregation of flush-marked skbs (bsc#1275474).\n- CVE-2026-68138: net/sched: serialize qdisc_rtab_list against concurrent get/put (bsc#1274941).\n- CVE-2026-68139: net/mlx5e: Use sender devcom for MPV master-up (bsc#1275578).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68142: geneve: require CAP_NET_ADMIN in the device netns for changelink (bsc#1275582).\n- CVE-2026-68143: net: slip: serialize receive against buffer reallocation (bsc#1275583).\n- CVE-2026-68144: phonet: pep: fix use-after-free in pep_get_sb() (bsc#1275481).\n- CVE-2026-68145: iomap: fix out-of-bounds bitmap_set() with zero-length range (bsc#1275584).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68149: fs: preserve ACL_DONT_CACHE state in forget_cached_acl() (bsc#1275294).\n- CVE-2026-68152: amt: fix use-after-free in AMT delayed works (bsc#1275300).\n- CVE-2026-68153: libceph: remove debugfs files before client teardown (bsc#1275301).\n- CVE-2026-68154: libceph: reject zero bucket types in crush_decode (bsc#1275303).\n- CVE-2026-68155: libceph: Reject monmaps advertising zero monitors (bsc#1275304).\n- CVE-2026-68156: libceph: refresh auth-\u003eauthorizer_buf{,_len} after authorizer update (bsc#1275305).\n- CVE-2026-68157: libceph: guard missing CRUSH type name lookup (bsc#1275306).\n- CVE-2026-68158: libceph: Fix multiplication overflow in decode_new_up_state_weight() (bsc#1275307).\n- CVE-2026-68159: libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE (bsc#1275470).\n- CVE-2026-68161: sctp: close UDP tunnel sockets during netns teardown (bsc#1274892).\n- CVE-2026-68164: mm/damon/core: disallow overlapping input ranges for damon_set_regions() (bsc#1274955).\n- CVE-2026-68165: mm/damon/core: validate ranges in damon_set_regions() (bsc#1274927).\n- CVE-2026-68166: userfaultfd: prevent registration of special VMAs (bsc#1274930).\n- CVE-2026-68169: mptcp: pm: userspace: fix use-after-free in get_local_id (bsc#1274952).\n- CVE-2026-68183: firmware: stratix10-svc: fix memory leaks and list corruption bugs (bsc#1274957).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68205: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() (bsc#1274934).\n- CVE-2026-68238: drm/amdgpu: Release VFCT ACPI table reference (bsc#1275704).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68267: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists (bsc#1275139).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68284: bpf, sockmap: Fix cork use-after-free in tcp_bpf_sendmsg() (bsc#1275970).\n- CVE-2026-68286: drop_monitor: perform u64_stats updates under IRQ-disabled section (bsc#1275973).\n- CVE-2026-68288: net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD (bsc#1275975).\n- CVE-2026-68289: tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream() (bsc#1275976).\n- CVE-2026-68293: net/mlx5: Fix MCIA register buffer overflow on 32 dword reads (bsc#1275091).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68296: net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM (bsc#1275045).\n- CVE-2026-68297: tipc: fix u16 MTU truncation in media and bearer MTU validation (bsc#1275040).\n- CVE-2026-68299: vmxnet3: fix BUG_ON in vmxnet3_get_hdr_len() for Geneve packets (bsc#1275088).\n- CVE-2026-68300: sctp: auth: verify auth requirement when auth_chunk is NULL (bsc#1275083).\n- CVE-2026-68302: amt: re-read skb header pointers after every pull (bsc#1275081).\n- CVE-2026-68313: tipc: fix infinite loop in __tipc_nl_compat_dumpit (bsc#1274665).\n- CVE-2026-68315: sctp: validate stream count in sctp_process_strreset_inreq() (bsc#1274662).\n- CVE-2026-68319: pds_core: fix deadlock between reset thread and remove (bsc#1274657).\n- CVE-2026-68320: sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid (bsc#1274659).\n- CVE-2026-68321: net: txgbe: fix FDIR filter leak on remove (bsc#1274652).\n- CVE-2026-68322: rds: Fix inet6_addr_lst NULL dereference when IPv6 is disabled (bsc#1274656).\n- CVE-2026-68325: iommu/amd: Bound the early ACPI HID map (bsc#1274651).\n- CVE-2026-68328: nfp: Check resource mutex allocation (bsc#1274646).\n- CVE-2026-68329: iommu/amd: Wait for completion instead of returning early in iommu_completion_wait() (bsc#1274645).\n- CVE-2026-68331: dpaa2-eth: put MAC endpoint device on disconnect (bsc#1274642).\n- CVE-2026-68333: dpaa2-switch: put MAC endpoint device on disconnect (bsc#1274644).\n- CVE-2026-68335: rds: drop incoming messages that cross network namespace boundaries (bsc#1274640).\n- CVE-2026-68336: bonding: fix devconf_all NULL dereference when IPv6 is disabled (bsc#1274639).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68375: bnxt_en: Handle partially initialized auxiliary devices (bsc#1274835).\n- CVE-2026-68377: net/sched: act_tunnel_key: Defer dst_release to RCU callback (bsc#1274831).\n- CVE-2026-68386: bpf, sockmap: Reject unhashed UDP sockets on sockmap update (bsc#1274814).\n- CVE-2026-68393: Bluetooth: hci_sync: extend conn_hash lookup critical sections (bsc#1274904).\n- CVE-2026-68395: ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered (bsc#1274900).\n- CVE-2026-68397: net/iucv: take a reference on the socket found in afiucv_hs_rcv() (bsc#1274898).\n- CVE-2026-68398: ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF (bsc#1274908).\n- CVE-2026-68399: bpf: Fix UAF in sock clone early bailouts (bsc#1274897).\n- CVE-2026-68408: wifi: cfg80211: convert pmsr_free_wk to wiphy_work to fix deadlock (bsc#1274709).\n- CVE-2026-68417: RDMA/siw: publish QP after initialization (bsc#1274696).\n- CVE-2026-68418: RDMA/irdma: Prevent user-triggered null deref on QP create (bsc#1274690).\n- CVE-2026-68419: RDMA/irdma: Prevent rereg_mr for non-mem regions (bsc#1274698).\n- CVE-2026-68422: btrfs: fix root leak if its reloc root is unexpected in merge_reloc_roots() (bsc#1274706).\n- CVE-2026-68425: IB/mad: Drop unmatched RMPP responses before reassembly (bsc#1274700).\n- CVE-2026-68426: xfrm: fix stale skb-\u003eprev after async crypto steals a GSO segment (bsc#1274705).\n- CVE-2026-68432: vxlan: require CAP_NET_ADMIN in the device netns for changelink (bsc#1274800).\n- CVE-2026-68433: libceph: bound get_version reply decode to front len (bsc#1274801).\n- CVE-2026-68442: btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps (bsc#1274773).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68450: btrfs: free mapping node on duplicate reloc root insert (bsc#1274834).\n- CVE-2026-68470: wifi: mac80211: validate extension-frame layout before RX (bsc#1276500).\n- CVE-2026-68480: x86/bugs: Make Safe-RET robust against interrupt injection (bsc#1274208).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72020: ipvs: reset full ip_vs_seq structs in ip_vs_conn_new (bsc#1275506).\n- CVE-2026-72022: llc: fix SAP refcount leak in llc_ui_autobind() (bsc#1276785).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72032: net/mlx5: HWS, fix matcher leak on resize target setup failure (bsc#1276955).\n- CVE-2026-72034: fhandle: reject detached mounts in capable_wrt_mount() (bsc#1276957).\n- CVE-2026-72035: net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1276961).\n- CVE-2026-72036: net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1277034).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72046: gve: fix header buffer corruption with header-split and HW-GRO (bsc#1275519).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72069: locking/rt: Fix the incorrect RCU protection in rt_spin_unlock() (bsc#1275528).\n- CVE-2026-72072: net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete (bsc#1277155).\n- CVE-2026-72083: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE (bsc#1275535).\n- CVE-2026-72084: scsi: target: core: Generate correct identifiers for PR OUT transport IDs (bsc#1275540).\n- CVE-2026-72100: dm-integrity: fix a bug if the bio is out of limits (bsc#1277311).\n- CVE-2026-72101: dm-integrity: fix leaking uninitialized kernel memory (bsc#1276831).\n- CVE-2026-72103: dm: avoid leaking the caller's thread keyring via the table device file (bsc#1277315).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72132: NFS: Charge unstable writes by request size, not folio size (bsc#1277551).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72137: xfrm: nat_keepalive: avoid double free on send error (bsc#1275587).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72176: mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error (bsc#1277230).\n- CVE-2026-72177: mm/damon/sysfs-schemes: fix dir put orders in access_pattern_add_dirs() (bsc#1277227).\n- CVE-2026-72217: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing (bsc#1275655).\n- CVE-2026-72221: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (bsc#1275665).\n- CVE-2026-72222: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (bsc#1275669).\n- CVE-2026-72234: batman-adv: access unicast_ttvn skb-\u003edata only after skb realloc (bsc#1275672).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72251: netfilter: nf_nat_sip: reload possible stale data pointer (bsc#1275827).\n- CVE-2026-72254: netfilter: nft_fib: reject fib expression on the netdev egress hook (bsc#1277204).\n- CVE-2026-72280: KVM: arm64: nv: Drop bogus WARN for write to ZCR_EL2 (bsc#1277726).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72288: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling (bsc#1275886).\n- CVE-2026-72289: KVM: arm64: vgic: Check the interrupt is still ours before migrating it (bsc#1275905).\n- CVE-2026-72296: net: ife: require ETH_HLEN to be pullable in ife_decode() (bsc#1275923).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72307: mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace() (bsc#1277160).\n- CVE-2026-72308: mlxsw: fix refcount leak in mlxsw_sp_port_lag_join() (bsc#1277159).\n- CVE-2026-72317: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (bsc#1275925).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72337: Bluetooth: 6lowpan: avoid untracked enable work (bsc#1277773).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72341: net/mlx5e: Fix publication race for priv-\u003echannel_stats[] (bsc#1277660).\n- CVE-2026-72342: net/mlx5e: Fix HV VHCA stats agent registration race (bsc#1277775).\n- CVE-2026-72343: net/mlx5e: Fix HV VHCA stats zero-sized buffer allocation (bsc#1277776).\n- CVE-2026-72345: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback (bsc#1277782).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72366: netfs: Fix netfs_create_write_req() to handle async cache object creation (bsc#1276333).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72389: bridge: stp: Fix a potential use-after-free when deleting a bridge (bsc#1273869).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72414: net: dsa: sja1105: round up PTP perout pin duration (bsc#1278039).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72430: net/sched: act_ct: fix nf_connlabels leak on two error paths (bsc#1277118).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72464: xprtrdma: Post receive buffers after RPC completion (bsc#1277069).\n- CVE-2026-72466: xprtrdma: Fix bcall rep leak and unbounded peek (bsc#1277057).\n- CVE-2026-72467: xprtrdma: Check frwr_wp_create() during connect (bsc#1277059).\n- CVE-2026-72468: xprtrdma: Initialize re_id before removal registration (bsc#1277062).\n- CVE-2026-72469: xprtrdma: Fix ep kref imbalance on ADDR_CHANGE (bsc#1277047).\n- CVE-2026-72473: xprtrdma: Avoid 250 ms delay on backlog wakeup (bsc#1277037).\n- CVE-2026-72485: coresight: platform: defer connection counter increment until alloc succeeds (bsc#1276771).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-72494: RDMA/irdma: Replace waitqueue and flag with completion (bsc#1276941).\n- CVE-2026-72495: RDMA/bnxt_re: Avoid repeated requests to allocate WC pages (bsc#1276937).\n- CVE-2026-72497: RDMA/bnxt_re: Add a max slot check for SQ (bsc#1276913).\n- CVE-2026-72499: RDMA/bnxt_re: Free CQ toggle page after firmware teardown (bsc#1276551).\n- CVE-2026-72500: RDMA/bnxt_re: Free SRQ toggle page after firmware teardown (bsc#1276552).\n- CVE-2026-72501: RDMA/bnxt_re: Initialize dpi variable to zero (bsc#1276546).\n- CVE-2026-72502: tcp: ipv6: clamp default adverting MSS to avoid GSO_BY_FRAGS (0xFFFF) (bsc#1276542).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74269: bnxt: fix head underflow on XDP head-grow (bsc#1276507).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74286: net: pfcp: allocate per-cpu tstats for PFCP netdevs (bsc#1276471).\n- CVE-2026-74296: RDMA/mlx5: Release the HW-provided UAR index rather than the SW one (bsc#1276452).\n- CVE-2026-74297: RDMA/mlx5: Fix undefined shift of user RQ WQE size (bsc#1276446).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74316: NFSD: Handle layout stid in nfsd4_drop_revoked_stid() (bsc#1276870).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74318: btrfs: fix deadlock cloning inline extent when using flushoncommit (bsc#1276864).\n- CVE-2026-74321: btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() (bsc#1277202).\n- CVE-2026-74334: RDMA/nldev: Fix locking when accessing mr-\u003epd (bsc#1277095).\n- CVE-2026-74345: RDMA/siw: Fix endpoint/socket association handling (bsc#1277285).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74394: RDMA/srpt: fix integer overflow in immediate data length check (bsc#1277408).\n- CVE-2026-74395: RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference (bsc#1277077).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74474: vxlan: use pskb_network_may_pull() for transmit path header pulls (bsc#1276335).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74481: mm/page_reporting: use system_freezable_wq to fix UAF during suspend (bsc#1276355).\n- CVE-2026-74482: mm/huge_memory: unlock i_mmap_rwsem before releasing after-split folios (bsc#1276346).\n- CVE-2026-74495: igbvf: Fix leak in TX DMA error cleanup (bsc#1275864).\n- CVE-2026-74496: fou: Fix use-after-free in fou_create() (bsc#1275867).\n- CVE-2026-74510: Bluetooth: mgmt: fix UAF in pair command cancellation (bsc#1275950).\n- CVE-2026-74512: audit: fix potential use-after-free in audit_del_rule() (bsc#1275954).\n- CVE-2026-74513: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister (bsc#1275956).\n- CVE-2026-74517: KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs (bsc#1276258).\n- CVE-2026-74518: mm/hugetlb: fix list corruption in allocate_file_region_entries() (bsc#1275798).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74527: octeontx2-af: Block VFs from clobbering special CGX PKIND state (bsc#1275805).\n- CVE-2026-74533: Bluetooth: ISO: fix race of kfree vs kref_get_unless_zero (bsc#1275804).\n- CVE-2026-74534: Bluetooth: ISO: Fix data-race on iso_pi(sk) in socket and HCI event paths (bsc#1275801).\n- CVE-2026-74535: Bluetooth: ISO: avoid deadlocks in iso_sock_timeout (bsc#1275812).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74537: Bluetooth: ISO: hold sk properly in iso_conn_ready (bsc#1275687).\n- CVE-2026-74545: rtase: fix double free of multi-frag skb on DMA map failure (bsc#1275679).\n- CVE-2026-74548: forcedeth: fix UAF of txrx_stats in nv_remove (bsc#1275695).\n- CVE-2026-74550: net: do not send ICMP/NDISC Redirects when peer allocation fails (bsc#1275688).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74556: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer (bsc#1275696).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74563: rds: tcp: hold the RCU lock across ipv6_chk_addr() in rds_tcp_laddr_check() (bsc#1275574).\n- CVE-2026-74566: keys: make keyring key-chunk byte order agree with keyring_diff_objects() (bsc#1275566).\n- CVE-2026-74567: keys: fix out-of-bounds read in keyring_get_key_chunk() (bsc#1275569).\n- CVE-2026-74571: btrfs: skip global block reserve accounting for rescue mounts (bsc#1275561).\n- CVE-2026-74577: net: mpls: initialize rtm_tos in mpls_getroute() (bsc#1275572).\n- CVE-2026-74581: net: ipv6: clear suppressed fib6 rule result (bsc#1275782).\n- CVE-2026-74582: packet: use consistent hard_header_len in non-ring send paths (bsc#1275784).\n- CVE-2026-74584: RDMA/bnxt_re: zero shared page before exposing to userspace (bsc#1277066).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74610: tls: don't leave a full plaintext sk_msg ring unpushed (bsc#1277054).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74644: mm/damon/ops-common: putback folios on invalid migrate nid (bsc#1277033).\n- CVE-2026-74665: net: fix skb length accounting after generic XDP frag adjustment (bsc#1277407).\n- CVE-2026-74669: ipvs: clear IPv4 options after rebasing tunnel ICMP errors (bsc#1277391).\n- CVE-2026-74695: netfilter: nf_flow_table: drop existing skb dst before skb_dst_set_noref() (bsc#1276931).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74712: vdpa/mlx5: Fix buffer length in create_direct_keys() (bsc#1276577).\n- CVE-2026-74717: net/mlx5: fw_tracer, return NULL on create error (bsc#1276569).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74722: btrfs: fix memory leak in btrfs_do_encoded_write() (bsc#1276561).\n- CVE-2026-74723: btrfs: lzo: reject inline extents without valid headers (bsc#1276562).\n- CVE-2026-74730: NFS: Pin the 'struct nfs_server' during a FREE_STATEID call (bsc#1276566).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-80529: xfs: don't swallow dquot recovery verification errors (bsc#1277688).\n- CVE-2026-80530: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN (bsc#1277668).\n- CVE-2026-80531: xfs: avoid UAF on sc-\u003etempip in xrep_tempfile_create (bsc#1277680).\n- CVE-2026-80533: xfs: don't walk off the end of a null sc-\u003esa.agi_bp in AGI repair (bsc#1277636).\n- CVE-2026-80534: xfs: fix ilock leak on error in xfs_dq_get_next_id (bsc#1277022).\n- CVE-2026-80535: xfs: don't double-lock when deleting a self-referential directory (bsc#1277641).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80558: libceph: Avoid using invalid osd indices from primary_temp (bsc#1277485).\n- CVE-2026-80561: libceph: fix multiple unsafe decodes in decode_locker() (bsc#1277265).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80590: inet: frags: strip GSO state from fragments before reassembly (bsc#1277275).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80609: qede: fix out-of-bounds check for cqe-\u003elen_list (bsc#1278334).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80721: Bluetooth: ISO: ensure no dangling hcon references in iso_conn (bsc#1277845).\n- CVE-2026-80727: x86/mce: Set up the polling timer before CMCI discovery (bsc#1278703).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80813: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() (bsc#1279537).\n- CVE-2026-80838: vxlan: keep the last remote linked during FDB flush (bsc#1279842).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Limit firmware log name prints to field size (git-fixes).\n- accel/ivpu: Validate firmware log buffer metadata (git-fixes).\n- accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr (git-fixes).\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- accessibility: speakup: Fix incorrect string length computation in report_char_chartab_status() (git-fixes).\n- accessibility: speakup: unregister tty ldisc on later init failures (git-fixes).\n- ACPI: APEI: Fix ERST timeout unit conversion (git-fixes).\n- ACPI: battery: Adjust charging status validation check (git-fixes).\n- ACPI: EC: Avoid _REG disconnect on GPIO IRQ defer (git-fixes).\n- ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root (git-fixes).\n- ACPI: pfr_update: fix stack buffer overflow in query_capability() (git-fixes).\n- ACPI: processor: idle: Expand _LPI package sanity checks (git-fixes).\n- ACPI: processor: validate MADT IOAPIC entry bounds (git-fixes).\n- ACPI: processor_idle: Mark LPI enter functions as __cpuidle (git-fixes).\n- ACPI: scan: fix bus ID cleanup on device_add() failures (git-fixes).\n- ACPI: video: Release PCI device reference after lookup (git-fixes).\n- ALSA: 6fire: bound the MIDI event length from the device (git-fixes).\n- ALSA: 6fire: Fix UAF at error handling during probe (stable-fixes).\n- ALSA: bcd2000: clear the URB pointers on disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: control: Don't add invalid kcontrols to LED layer (git-fixes).\n- ALSA: core: Fix use-after-free in snd_card_do_free() (git-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Check card index validity at probe (stable-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/ext: preserve PPLCCTL bits when clearing reset (git-fixes).\n- ALSA: hda/realtek: Enable headset mic on F+ FLAPTOP r (stable-fixes).\n- ALSA: hda: Fix connection list comparison in proc output (git-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hpi: Check transport errors during HPI6000 adapter initialization (git-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcxhr: initialize mutexes before requesting threaded IRQ (git-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: scarlett2: Use a private URB for the notification endpoint (git-fixes).\n- ALSA: seq: Don't leak the extension cell pointer in the bounce payload (git-fixes).\n- ALSA: seq: midi: Optimize event_input locking with RCU (git-fixes).\n- ALSA: seq: midi: Serialize input teardown with event_input (git-fixes).\n- ALSA: ump: Fix corrupted data bytes at MIDI 1.0 SysEx to UMP conversion (git-fixes).\n- ALSA: usb-audio: Complete cleanup after system-resume errors (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_novation_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write on Type II inbound URBs (git-fixes).\n- ALSA: usb: Fix UAF at delayed release of MIDI2 EPs (git-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usbusx2y: validate URB actual_length in interrupt callback (git-fixes).\n- ALSA: usx2y: bound the hwdep mmap fault offset (git-fixes).\n- ALSA: via82xx: Remove unreachable branch in snd_via686_pcm_pointer() (git-fixes).\n- apparmor: advertise the tcp fast open fix is applied (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: adau1761: sort the register default table (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add DMI entry for MSI Thin A15 B7UC (git-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: apple: mca: increase SERDES reset delay (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses (git-fixes).\n- ASoC: cs35l33: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l34: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l41: sort the register default table (git-fixes).\n- ASoC: cs35l45: sort the register default table (git-fixes).\n- ASoC: cs4265: sort the register default table (git-fixes).\n- ASoC: cx2072x: sort the register default table (git-fixes).\n- ASoC: dapm: Fix off-by-one check on the second enum channel (git-fixes).\n- ASoC: fix unmet dependencies on PPC_BESTCOMM and SND_SOC_AC97_BUS (git-fixes).\n- ASoC: fsl-asoc-card: defer probe when the CPU DAI device is not ready (git-fixes).\n- ASoC: fsl: mpc5200-i2s: Free DMA resources on probe failure (git-fixes).\n- ASoC: fsl_audmix: rework runtime PM handling in probe (git-fixes).\n- ASoC: fsl_easrc: sort the register default table (git-fixes).\n- ASoC: hdac_hda: Fix hlink refcount leak on component registration failure (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: avs: Do not ignore -ENOENT when loading a topology (git-fixes).\n- ASoC: Intel: avs: Fix unbalanced module reference count (git-fixes).\n- AsoC: intel: sst: fix PCI device reference leak on probe failure (git-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: loongson: Fix error handling in ACPI property parsing (git-fixes).\n- ASoC: max9860: sort the register default table (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Shorten memif_data table using macros (stable-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Support \u003e32 bit DMA addresses (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: use local `dev` pointer in driver callbacks (stable-fixes).\n- ASoC: mediatek: mt8183: Check runtime resume during probe (git-fixes).\n- ASoC: mediatek: mt8192-afe-pcm: Simplify probe() with local dev variable (stable-fixes).\n- ASoC: mediatek: mt8192: Check runtime resume during probe (git-fixes).\n- ASoC: meson: Keep link pointers valid on realloc failure (git-fixes).\n- ASoC: ml26124: sort the register default table (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: pcm512x: sort the register default table (git-fixes).\n- ASoC: pxa: Use devm_clk_get_optional() for extclk clock (git-fixes).\n- ASoC: qcom: q6apm: keep the graph start count in sync with the DSP (git-fixes).\n- ASoC: rt274: sort the register default table (git-fixes).\n- ASoC: rt286: sort the register default table (git-fixes).\n- ASoC: rt298: sort the register default table (git-fixes).\n- ASoC: rt700-sdw: always drain jack work on remove (git-fixes).\n- ASoC: rt700: drop duplicate reg_default entry (git-fixes).\n- ASoC: rt700: sort the register default table (git-fixes).\n- ASoC: rt711-sdca: sort the register default tables (git-fixes).\n- ASoC: rt711: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-dmic: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt715-sdca: drop duplicate reg_default entries (git-fixes).\n- ASoC: rt715-sdca: sort the register default tables (git-fixes).\n- ASoC: rt715: sort the register default table (git-fixes).\n- ASoC: rt1017-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt1316-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318: sort the register default table (git-fixes).\n- ASoC: samsung: aries_audio_probe: double of_node_put due to direct assignment without of_node_get (git-fixes).\n- ASoC: sgtl5000: sort the register default table (git-fixes).\n- ASoC: SOF: sof-audio: Fix error path in sof_widget_setup_unlocked() (git-fixes).\n- ASoC: SOF: validate topology volume range before allocation (git-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti-sas: sort the register default table (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tas2552: sort the register default table (git-fixes).\n- ASoC: tas2764: sort the register default table (git-fixes).\n- ASoC: tas2780: sort the register default table (git-fixes).\n- ASoC: tegra210_i2s: sort the register default table (git-fixes).\n- ASoC: tegra210_mixer: sort the register default table (git-fixes).\n- ASoC: tegra: Fix the MIXER enable default value (git-fixes).\n- ASoC: tegra: Sort MBDRC register defaults (git-fixes).\n- ASoC: xilinx: formatter_pcm: fix stream_data leak on open error (git-fixes).\n- ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- batman-adv: bla: fix freeing of claims on meshif deletion (git-fixes).\n- batman-adv: bla: prevent CRC corruptions after claim flush (git-fixes).\n- batman-adv: dat: avoid unaligned fault in IP extraction (git-fixes).\n- batman-adv: fix stale receive device on merged fragments (git-fixes).\n- batman-adv: mcast: ensure unshared skb for multicast packets (git-fixes).\n- batman-adv: mcast: linearize skbuff for packet generation (git-fixes).\n- batman-adv: reject unrepresentable multicast TVLV offsets (git-fixes).\n- blk-mq: reinsert cached request to the list (bsc#1273770).\n- Bluetooth: btintel: bound firmware ID by TLV length (git-fixes).\n- Bluetooth: btintel: Fix diagnostics event detection (git-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btintel_pcie: Clear automask on spurious interrupts (git-fixes).\n- Bluetooth: btintel_pcie: fix tx_handle bounds off-by-one (git-fixes).\n- Bluetooth: btintel_pcie: validate packet_len before skb_put_data (git-fixes).\n- Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware (git-fixes).\n- Bluetooth: btmtk: Do not discard the subsystem reset timeout (git-fixes).\n- Bluetooth: btmtk: Fix short read errors in btmtk_usb_uhw_reg_read() (stable-fixes).\n- Bluetooth: btmtksdio: Fix out-of-bounds DMA read in the TX path (git-fixes).\n- Bluetooth: btmtksdio: Take exclusive ownership of the SKB before TX (git-fixes).\n- Bluetooth: btqca: Fix qca_set_bdaddr() waiting for wrong HCI event (git-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Fix BD_ADDR byte order in btusb_set_bdaddr_wcn6855() (git-fixes).\n- Bluetooth: btusb: Fix short read errors in btusb_qca_send_vendor_req() (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: do not leak an hci_conn when a second LE connect is rejected (git-fixes).\n- Bluetooth: eir: Fix OOB read in eir_get_service_data() (git-fixes).\n- Bluetooth: hci_aml: validate firmware segment lengths (git-fixes).\n- Bluetooth: hci_bcm4377: Ignore reserved PHY in ext adv reports on BCM4378 (git-fixes).\n- Bluetooth: hci_bcm: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_conn: fix the SCO setup context lifetime (git-fixes).\n- Bluetooth: hci_conn: hold conn reference in abort_conn_sync() (git-fixes).\n- Bluetooth: hci_conn: re-enable advertising only for peripheral role (git-fixes).\n- Bluetooth: hci_core: Fix race condition during device registration (git-fixes).\n- Bluetooth: hci_core: use skb_get() instead of skb_clone() for req_skb (git-fixes).\n- Bluetooth: hci_event: clear HCI_LE_ADV only on a created connection (git-fixes).\n- Bluetooth: hci_event: fix LE list UAF on reset (git-fixes).\n- Bluetooth: hci_event: validate LE Set CIG Parameters response (git-fixes).\n- Bluetooth: hci_h5: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_intel: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sync: Clear HCI_CMD_PENDING when dropping the last request (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: free the advertising instance on the failure and cancel paths (git-fixes).\n- Bluetooth: hci_sync: make hci_cmd_sync_run_once return -EEXIST if exists (stable-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del() (git-fixes).\n- Bluetooth: hci_uart: Fix false success return in hci_uart_setup() (git-fixes).\n- Bluetooth: ISO: do not force BT_LISTEN after a failed BIG sync (git-fixes).\n- Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect (git-fixes).\n- Bluetooth: mgmt: fix locking in unpair_device/disconnect_sync (git-fixes).\n- Bluetooth: MGMT: free the HCI command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: free the mesh send cancel command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: reject HCI_CMD_SYNC params_len above 255 (git-fixes).\n- Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update (git-fixes).\n- Bluetooth: MSFT: validate evt_prefix_len against the response length (git-fixes).\n- Bluetooth: qca: fix NVM tag length underflow in TLV parser (git-fixes).\n- Bluetooth: RFCOMM: serialize security confirmation handling (git-fixes).\n- Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept (git-fixes).\n- Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (git-fixes).\n- Bluetooth: virtio_bt: avoid OOB read of build info string (git-fixes).\n- bnxt_en: Check return value of bnxt_hwrm_vnic_cfg (jsc#PED-16798).\n- bnxt_en: Delay for 5 seconds after AER DPC for all chips (jsc#PED-16798).\n- bnxt_en: Don't assume XDP is never enabled in bnxt_init_dflt_ring_mode() (jsc#PED-16798).\n- bnxt_en: Drop pci_save_state() after pci_restore_state() (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction for V3_CMP (jsc#PED-16798).\n- bnxt_en: Move bnxt_rss_ext_op into header (jsc#PED-16798).\n- bnxt_en: Refactor some basic ring setup and adjustment logic (jsc#PED-16798).\n- bnxt_en: Restore default stat ctxs for ULP when resource is available (jsc#PED-16798).\n- bnxt_en: Set bp-\u003emax_tpa according to what the FW supports (jsc#PED-16798).\n- bnxt_en: Use absolute target ns from ptp_clock_request (jsc#PED-16798).\n- bnxt_en: use bnxt_xdp_buff for xdp context (jsc#PED-16798).\n- bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation (git-fixes).\n- bus: mhi: host: Fix controller cleanup on EDL sysfs failure (git-fixes).\n- bus: mhi: host: Flush the posted write after writing to MHI_SOC_RESET_REQ_OFFSET (git-fixes).\n- bus: ti-sysc: Fix /chosen node reference leak (git-fixes).\n- cacheinfo: don't propagate DT/ACPI error when arch supplies info (arm64) (git-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: use netdevice_tracker for j1939_{priv,session,ecu} tracking (stable-fixes).\n- char: xilinx_hwicap: unregister class on init errors (git-fixes).\n- cleanup: add a scoped version of CLASS() (stable-fixes).\n- cleanup: fix scoped_class() (git-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- cpufreq: intel_pstate: Add and use hybrid_get_cpu_type() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Avoid SMP calls to get cpu-type (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Fix hwp_get_cpu_scaling() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use correct scaling factor on Raptor Lake-E (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use CPPC to get scaling factors (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use HYBRID_SCALING_FACTOR_ADL for Bartlett Lake (bsc#1240957 bsc#1249104 bsc#1265220).\n- crypto: aspeed - Propagate platform_get_irq() errors (git-fixes).\n- crypto: atmel-sha204a - fix heap info leak on I2C transfer failure (git-fixes).\n- crypto: atmel-tdes - use scatterlist length before DMA mapping (git-fixes).\n- crypto: ccm - Set rfc4309 maxauthsize from child (git-fixes).\n- crypto: ccp - Abort doing SEV INIT if SNP INIT fails (stable-fixes).\n- crypto: ccp - Add new SEV/SNP platform shutdown API (stable-fixes).\n- crypto: ccp - Always pass in an error pointer to __sev_platform_shutdown_locked() (git-fixes).\n- crypto: ccp - Fix __sev_snp_shutdown_locked (git-fixes).\n- crypto: ccp - Fix dereferencing uninitialized error pointer (git-fixes).\n- crypto: ccp - Fix memory leak in SEV INIT_EX path (git-fixes).\n- crypto: ccp - Fix possible deadlock in SEV init failure path (git-fixes).\n- crypto: ccp - Fix SNP panic notifier unregistration (git-fixes).\n- crypto: ccp - Move dev_info/err messages for SEV/SNP init and shutdown (stable-fixes).\n- crypto: ccp - Move SEV/SNP Platform initialization to KVM (stable-fixes).\n- crypto: ccp - Register SNP panic notifier only if SNP is enabled (stable-fixes).\n- crypto: ccp - Reset TMR size at SNP Shutdown (stable-fixes).\n- crypto: doc - Remove extra parenthesis (git-fixes).\n- crypto: hisilicon/sec2 - fix CCM algorithm long packet failure (git-fixes).\n- crypto: keembay - Fix AEAD unregister count in error path (git-fixes).\n- crypto: keembay - Initialize completion before requesting IRQ (git-fixes).\n- crypto: keembay - publish OF module alias for OCS AES/SM4 (git-fixes).\n- crypto: lskcipher - propagate errors from unaligned crypt (git-fixes).\n- crypto: mxs-dcp - fix source scatterlist length access (git-fixes).\n- crypto: qat - cancel work on re-enable SR-IOV timeout (git-fixes).\n- crypto: qat - clear AES key schedule from stack (git-fixes).\n- crypto: qce - fix CCM AAD buffer underallocation (git-fixes).\n- crypto: qce - fix error path in devm_qce_register_algs (git-fixes).\n- crypto: qcom-rng - Allow zero as a random number (git-fixes).\n- crypto: qcom-rng - Enable clock in hwrng case (git-fixes).\n- crypto: rk3288 - fail ahash requests on HASH idle timeout (git-fixes).\n- crypto: sa2ul - stop probe if context pool creation fails (git-fixes).\n- crypto: sl3516 - drop invalid sg_dma_len checks before DMA mapping (git-fixes).\n- crypto: tegra - Don't touch bo refcount in host1x bo pin/unpin (stable-fixes).\n- crypto: tegra - fix rctx-\u003ecryptlen calculation in tegra_gcm_do_one_req() (git-fixes).\n- cxl/acpi: Fix CXL_ACPI and CXL_PMEM Kconfig tristate mismatch (git-fixes).\n- cxl: Adjust the startup priority of cxl_pmem to be higher (git-fixes).\n- default_gfp(): avoid using the \"newfangled\" __VA_OPT__ trick (bsc#1280139).\n- device property: fix infinite loop in fwnode_for_each_child_node() (git-fixes).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dma-mapping: add __dma_from_device_group_begin()/end() (bsc#1267586).\n- dmaengine: dw-edma: Clear stale requests on termination (git-fixes).\n- dmaengine: dw-edma: Complete descriptors before pausing (git-fixes).\n- dmaengine: dw-edma: Fix HDMA channel status register access (git-fixes).\n- dmaengine: dw-edma: Initialize IRQ data before requesting IRQs (git-fixes).\n- dmaengine: dw-edma: Serialize abort state updates (git-fixes).\n- dmaengine: dw-edma: Serialize channel state checks (git-fixes).\n- dmaengine: dw-edma: Terminate all descriptors without callbacks (git-fixes).\n- dmaengine: fsl-edma: tracing: no ptr dereference during log output (git-fixes).\n- dmaengine: hisilicon: Return -ENOMEM on dynamic memory allocation in probe (git-fixes).\n- dmaengine: mediatek: mtk-uart-apdma: Return -ENOMEM on memory allocation failure (git-fixes).\n- dmaengine: qcom-bam-dma: fix autosuspend cleanup during removal (git-fixes).\n- dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers (git-fixes).\n- dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout (git-fixes).\n- dmaengine: zynqmp_dma: fix kernel doc for zynqmp_dma_remove() (git-fixes).\n- driver core: soc: Unregister bus on early device registration failure (git-fixes).\n- drivers/virt: pkvm: Fix end calculation in mmio_guard_ioremap_hook() (git-fixes).\n- Drivers: hv: Use meaningful errnos for hypercall status codes (git-fixes).\n- drm/amd/display: Add AV mute wait frames to dce110_set_avmute (stable-fixes).\n- drm/amd/display: avoid divide-by-zero in __is_lut_linear() (git-fixes).\n- drm/amd/display: Check for tg ops in dce110_set_avmute (git-fixes).\n- drm/amd/display: dce100: skip non-DP stream encoders for DP MST (stable-fixes).\n- drm/amd/display: fix BT.2020 YCbCr limited output CSC matrix (git-fixes).\n- drm/amd/display: fix BT.2020 YCbCr output CSC matrices for DCE (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix NULL pointer dereference in amdgpu_dm_crtc_set_vblank() (git-fixes).\n- drm/amd/display: Increase HDMI AV mute wait from 2 to 3 frames (stable-fixes).\n- drm/amd/display: Remove unused-but-set variable hubp from (git-fixes).\n- drm/amd/display: validate plane degamma LUT size for private color prop (git-fixes).\n- drm/amd/pm: adjust the visibility of pp_table sysfs node (stable-fixes).\n- drm/amd/pm: fix gpu metrics energy accumulator for smu 13.0.0/13.0.7 (git-fixes).\n- drm/amd/pm: fix smu14 power limit range calculation (stable-fixes).\n- drm/amd/pm: make pp_features read-only when scpm is enabled (stable-fixes).\n- drm/amd/pm: Use same metric table for APU (stable-fixes).\n- drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read (git-fixes).\n- drm/amdgpu/gfx6: Fixup emit_cntxcntl() (git-fixes).\n- drm/amdgpu/gfx6: Fixup emitting SWITCH_BUFFER packets (git-fixes).\n- drm/amdgpu/gfx6: Use PFP on the compute queues too (git-fixes).\n- drm/amdgpu/gfx8: drop unecessary BUG_ON() (stable-fixes).\n- drm/amdgpu/gfx9.4.3: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx9: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx11: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx12: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in SMU7 lookup (git-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup (git-fixes).\n- drm/amdgpu/sdma4.4.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma6.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma7.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/uvd: Fix forcing MSG, FB BOs into VCPU segment when it isn't at 0 (v2) (stable-fixes).\n- drm/amdgpu/uvd: Place VCPU BO only in VRAM for UVD 4.x and older (stable-fixes).\n- drm/amdgpu/vce: fix integer overflow in image size (stable-fixes).\n- drm/amdgpu/vcn4: avoid rereading IB param length (stable-fixes).\n- drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check (git-fixes).\n- drm/amdgpu: cap GTT size to physical RAM on APUs (stable-fixes).\n- drm/amdgpu: check ASPM on the dGPU host link (git-fixes).\n- drm/amdgpu: disallow multiple FENCE chunks in one submit (git-fixes).\n- drm/amdgpu: fix aperture iounmap skipped on device removal (git-fixes).\n- drm/amdgpu: fix autosuspend cleanup during removal (git-fixes).\n- drm/amdgpu: fix bo-\u003epin leaking in amdgpu_bo_create_reserved (stable-fixes).\n- drm/amdgpu: fix division by zero with invalid uvd dimensions (stable-fixes).\n- drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid() (stable-fixes).\n- drm/amdgpu: fix nbif 6.3.1 l1 low power not functional (git-fixes).\n- drm/amdgpu: Fix UVD decode image min size calculation (stable-fixes).\n- drm/amdgpu: Fix UVD dpb min size calculation for H264 (stable-fixes).\n- drm/amdgpu: Fix UVD min buffer sizes (stable-fixes).\n- drm/amdgpu: Fix VCE 3 ring align_mask (git-fixes).\n- drm/amdgpu: Fix VFCT bus number matching with soft filter (stable-fixes).\n- drm/amdgpu: Implement insert_end for VCE 3 (git-fixes).\n- drm/amdgpu: invoke pm_genpd_remove() before freeing genpd (stable-fixes).\n- drm/amdgpu: move debug_vm handling to amdgpu_cs_parser_fini (git-fixes).\n- drm/amdgpu: read TRUNCATE_COORD_MODE on gfx12 (git-fixes).\n- drm/amdgpu: reject oversized IBs with per-ring packet limits (stable-fixes).\n- drm/amdgpu: Reject UVD message with dimensions above 4096 (stable-fixes).\n- drm/amdgpu: Reject UVD message with invalid number of h265 refs (stable-fixes).\n- drm/amdgpu: remove unused function parameter (stable-fixes).\n- drm/amdgpu: restore UMD profile pstate after runtime resume (stable-fixes).\n- drm/amdgpu: validate GEM_CREATE domain combinations (stable-fixes).\n- drm/amdkfd: Check bounds in allocate_event_notification_slot (stable-fixes).\n- drm/amdkfd: fix 32-bit overflow in CWSR total size calculation (stable-fixes).\n- drm/amdkfd: Fix missing authorization check in KFD_IOC_DBG_TRAP_DISABLE (stable-fixes).\n- drm/amdkfd: fix QID bit leak in pqm_create_queue() (stable-fixes).\n- drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore (git-fixes).\n- drm/amdkfd: Handle invalid event type in CRIU event restore (stable-fixes).\n- drm/amdkfd: Use kvcalloc to allocate arrays (stable-fixes).\n- drm/bridge: cdns-mhdp8546: Return an error pointer on allocation failure (git-fixes).\n- drm/bridge: dw-hdmi: fix i2c adapter leak on probe failure (git-fixes).\n- drm/bridge: ps8640: propagate AUX transfer register errors (git-fixes).\n- drm/bridge: tc358767: clamp the reported AUX read size to the request (git-fixes).\n- drm/connector/hdmi: Fix out of bounds memory read (git-fixes).\n- drm/connector: Fix epoch_counter docs to reflect reality (git-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/hibmc: Fix list of formats on the primary plane (git-fixes).\n- drm/hibmc: Use drm_atomic_helper_check_plane_state() (git-fixes).\n- drm/i915/hdcp: check streams bounds before overflow (git-fixes).\n- drm/i915/hdcp: Move to using intel_display in intel_hdcp (stable-fixes).\n- drm/i915/hdcp: require monotonically increasing seq_num_v (git-fixes).\n- drm/i915/hdcp: Skip inactive MST connectors when building stream list (stable-fixes).\n- drm/i915/vrr: Check HAS_VRR() first in intel_vrr_is_capable() (stable-fixes).\n- drm/i915/vrr: require valid min/max vfreq for VRR (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/lima: call drm_mm_init() with a valid allocation range (git-fixes).\n- drm/msm/a6xx: Fix RBBM_CLOCK_CNTL3_TP0 value in a730_hwcg (git-fixes).\n- drm/msm/a6xx: Fix stale rpmh votes after suspend (git-fixes).\n- drm/msm/dpu: Drop sneaky dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: Drop dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: round 6G byte clock rate to the PLL-achievable value (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau: unsubscribe the channel-kill event before the fence context (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/panel-edp: fix i2c adapter leak on probe failure (git-fixes).\n- drm/panel: samsung-s6d16d0: Power off on prepare failure (git-fixes).\n- drm/panthor: fix firmware control interface bounds checks (git-fixes).\n- drm/panthor: return PTR_ERR() from devm_drm_dev_alloc() (git-fixes).\n- drm/panthor: skip zero-sized firmware sections (git-fixes).\n- drm/radeon: fix autosuspend cleanup during teardown (git-fixes).\n- drm/radeon: fix r100_copy_blit for large BOs (stable-fixes).\n- drm/radeon: restore hardware polling in fence_is_signaled to fix performance regression (git-fixes).\n- drm/rockchip: vop2: Recognise 10-bit YUV422 as YUV format (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates for ssd132x (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates in ssd133x (git-fixes).\n- drm/sun4i: crtc: Propagate layer initialization error (git-fixes).\n- drm/sun4i: Drop node references while building component list (git-fixes).\n- drm/sun4i: dw-hdmi: Drop TCON TOP port reference (git-fixes).\n- drm/sun4i: fix refcount leak in sun4i_backend_init_sat() (git-fixes).\n- drm/sun4i: hdmi-phy: Fix H6 8-bit MPLL config at 594 MHz (git-fixes).\n- drm/sun4i: hdmi: Don't leak sync polarity bits into packet control (git-fixes).\n- drm/sun4i: tcon: Drop remote endpoint reference (git-fixes).\n- drm/sun4i: tcon: Drop TCON TOP device reference (git-fixes).\n- drm/sun4i: tcon: Set output mux for DSI and LVDS (git-fixes).\n- drm/sun4i: vi scaler: Fix coefficient selection (git-fixes).\n- drm/tegra: dsi: Re-add clear enable register if DSI was powered by bootloader (git-fixes).\n- drm/tegra: fbdev: Do not assign to struct drm_fb_helper.info (git-fixes).\n- drm/tve200: add OF module alias for autoloading (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/xe/oa: Check managed mutex initialization errors (git-fixes).\n- drm/xe/oa: Fix sync entry leak on OA config emit failure (git-fixes).\n- drm/xe/oa: Remove sysfs entry on idr_alloc failure in xe_oa_add_config_ioctl() (git-fixes).\n- drm/xe: Introduce xe_gt_dbg_printer() (stable-fixes).\n- drm/xe: Order ring writes before ring tail updates (git-fixes).\n- drm/xe: Stub out new pagefault layer (stable-fixes).\n- drm/xe: tests: fix error message in xe_migrate_sanity_test() (git-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: fix race between partial drm_dev_register() failure and ioctl (git-fixes).\n- drm: lcdif: Wait for vblank before disabling DMA (git-fixes).\n- drm: Remove unused header in drm_dumb_buffers.c (git-fixes).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- erspan: Initialize options_len before referencing options (bsc#1274727).\n- ethtool: rss: fix hkey leak when indir_size is 0 (git-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_cursor() (git-fixes).\n- fbdev: core: Fix pointer desynchronization in fb_io_read() (git-fixes).\n- fbdev: kyro: Validate overlay viewport coordinates (git-fixes).\n- fbdev: omapfb: panel-dsi-cm: initialize lock before registering display (git-fixes).\n- fbdev: tdfxfb: fix PCI enable cleanup with pcim_enable_device() (git-fixes).\n- fbdev: uvesafb: unregister connector callback on init failure (git-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Avoid IDR updates while cleaning channels (git-fixes).\n- firmware: arm_scmi: Clean up channels on setup failure (git-fixes).\n- firmware: arm_scmi: Drop handle on protocol bind failures (git-fixes).\n- firmware: arm_scmi: Fix requested device removal race (git-fixes).\n- firmware: arm_scmi: Free transport channel on IDR failure (git-fixes).\n- firmware: arm_scmi: Protect device request lookup with RCU (git-fixes).\n- firmware: arm_scmi: Publish channel state before callbacks (git-fixes).\n- firmware: arm_scmi: Quiesce notifications before teardown (git-fixes).\n- firmware: arm_scmi: Rate-limit queue-full warnings in IRQ context (git-fixes).\n- firmware: arm_scmi: Reject out of range DT protocol IDs (git-fixes).\n- firmware: arm_scmi: Roll back partial protocol table registration (git-fixes).\n- firmware: arm_scmi: Unregister device notifier before IDR teardown (git-fixes).\n- firmware: arm_scmi: Unrequest devices if driver registration fails (git-fixes).\n- firmware: arm_scmi: Unwind P2A receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Unwind TX receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Use channel ID for transport teardown (git-fixes).\n- firmware_loader: do not queue completed sysfs fallback requests (git-fixes).\n- fpga: altera-cvp: Avoid out-of-bounds read in trailing byte write (git-fixes).\n- fpga: dfl: fme: add error handling (git-fixes).\n- fpga: stratix10-soc: Fix SVC mailbox handling during reconfiguration (git-fixes).\n- fuse: fix race between interrupt and resend (git-fixes).\n- gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind (git-fixes).\n- gpu: host1x: Avoid stack over-read in debug output helpers (git-fixes).\n- gpu: host1x: Fix offset calculation in trace_write_gather (git-fixes).\n- gpu: host1x: Fix use-after-free in host1x_bo_clear_cached_mappings (stable-fixes).\n- HID: asus: fix missing hid_is_usb() check (git-fixes).\n- HID: asus: simplify RGB init sequence (stable-fixes).\n- HID: bpf: serialize device reference release in struct_ops destroy path (git-fixes).\n- HID: core: fix number/pointer type confusion on long items (git-fixes).\n- HID: core: fix OOB read of field-\u003eusage in hid_set_field() (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: hyperv: validate initial device info bounds (git-fixes).\n- HID: i2c-hid: Fix \"(null)\" output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: goodix: Disable VDD on VDDIO enable failure (git-fixes).\n- HID: lg4ff: validate report length before fixed offsets (git-fixes).\n- HID: logitech-dj: Fix maxfield check in DJ short report validation (git-fixes).\n- HID: logitech-dj: fix wrong detection of bad DJ_SHORT output report (git-fixes).\n- HID: logitech-dj: Prevent REPORT_ID_DJ_SHORT related user initiated OOB write (stable-fixes).\n- HID: logitech-dj: Standardise hid_report_enum variable nomenclature (stable-fixes).\n- HID: magicmouse: do not keep a stale msc-\u003einput if no input is claimed (git-fixes).\n- HID: magicmouse: fix battery reporting for Bluetooth Magic Trackpad USB-C (git-fixes).\n- HID: magicmouse: Prevent out-of-bounds (OOB) read during DOUBLE_REPORT_ID (stable-fixes).\n- HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() (git-fixes).\n- HID: magicmouse: re-enable multitouch after reset-resume (git-fixes).\n- HID: mcp2221: validate report size in mcp2221_raw_event() (git-fixes).\n- HID: multitouch: reclassify HTIX5288 to WIN_8_FORCE_MULTI_INPUT_NSMU (git-fixes).\n- HID: nintendo: Fix imu_timestamp_us double increment per report (git-fixes).\n- HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler() (git-fixes).\n- HID: nintendo: register input device after capabilities are set (git-fixes).\n- HID: nintendo: stop device IO before hid_hw_stop on probe failure (git-fixes).\n- HID: picolcd: clamp eeprom debugfs read to bytes actually received (git-fixes).\n- HID: pidff: Rework pidff_set_time() to fix warnings (stable-fixes).\n- HID: pidff: Use ARRAY_SIZE macro instead of sizeof (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: roccat: bound device-supplied profile index (git-fixes).\n- HID: roccat: free buffered reports when destroying device (git-fixes).\n- HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature (git-fixes).\n- HID: sensor: custom: Fix field sysfs group cleanup on failure (git-fixes).\n- HID: sensor: custom: Fix use-after-free in enable_sensor (git-fixes).\n- HID: synchronize input before cleaning up a failed probe (git-fixes).\n- HID: tmff: Use 64-bit arithmetic for force feedback scaling (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- hwmon: (ads7828) Fix external VREF regulator handling (git-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (chipcap2) fix channels in humidity alarm notifications (git-fixes).\n- hwmon: (coretemp) Fix core_data leak on CPUs without PTS (git-fixes).\n- hwmon: (corsair-cpro) Create debugfs entries after hwmon registration (git-fixes).\n- hwmon: (corsair-cpro) Remove debugfs entries when probe fails (git-fixes).\n- hwmon: (corsair-psu) fix possible out-of-bounds access on missing string termination (git-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (ina2xx) Add support for has_alerts configuration flag (stable-fixes).\n- hwmon: (ina2xx) Add support for INA234 (stable-fixes).\n- hwmon: (ina2xx) Add support for INA260 (stable-fixes).\n- hwmon: (ina2xx) Fix various overflow issues (git-fixes).\n- hwmon: (ina2xx) Make it easier to add more devices (stable-fixes).\n- hwmon: (ina2xx) Shift INA234 shunt and current registers (stable-fixes).\n- hwmon: (ina226) Add support for SY24655 (stable-fixes).\n- hwmon: (ltc4282) Avoid overflow in maximum power calculation (git-fixes).\n- hwmon: (ltc4282) Clamp negative current limits (git-fixes).\n- hwmon: (ltc4282) Fix parsing adi,current-limit-sense-microvolt (git-fixes).\n- hwmon: (ltc4282) Make sure clk_init_data is fully initialized (git-fixes).\n- hwmon: (max6621) fix negative temperature offset and crit readings (git-fixes).\n- hwmon: (max6621) fix temperature clamp range (git-fixes).\n- hwmon: (nzxt-smart2) Check return value of init_device() in probe (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficient calculations (git-fixes).\n- hwmon: Switch back to struct platform_driver::remove() (stable-fixes).\n- hwrng: ks-sa - Fix runtime PM cleanup on registration failure (git-fixes).\n- hwrng: omap - Fix probe error path cleanup (git-fixes).\n- hwtracing: hisi_ptt: Propagate DMA reset timeout in trace_start() (git-fixes).\n- i2c: core: fix debugfs UAF on adapter removal (git-fixes).\n- i2c: imx: fix locked bus on SMBus block-read of 0 (atomic) (git-fixes).\n- i2c: imx: separate atomic, dma and non-dma use case (stable-fixes).\n- i2c: mux: demux-pinctrl: fix OF node leak on kstrdup failure (git-fixes).\n- i2c: mux: Fix channel node leak on adapter add failure (git-fixes).\n- i2c: ocores: Disable clock on failed resume (git-fixes).\n- i3c: dw: avoid shift-out-of-bounds when DAA assigns no devices (git-fixes).\n- i3c: dw: rename \"pclk\" to \"apb\" to match dt-binding (git-fixes).\n- i3c: master: Fix device_register() error path (git-fixes).\n- i3c: master: Fix info leak and UAF in device unregister path (git-fixes).\n- i3c: master: Fix potential UAF in i3c_device_uevent() (git-fixes).\n- i3c: master: svc: bound IBI payload to the requested max_payload_len (git-fixes).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: dmard09: Implement IIO_CHAN_INFO_SCALE (git-fixes).\n- iio: adc: max34408: add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- iio: adc: pac1921: fix wrong channel used in trigger handler read (git-fixes).\n- iio: buffer: Fix potential use-after-free in anonymous buffer release (git-fixes).\n- iio: buffer: Make IIO DMA fence release RCU-safe (git-fixes).\n- iio: buffer: Tie IIO dma fence lock lifetime to the fence (git-fixes).\n- iio: chemical: atlas-sensor: fix PM reference leak in buffer postenable (git-fixes).\n- iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF (git-fixes).\n- iio: chemical: sgp30: Handle IAQ thread creation failure (git-fixes).\n- iio: dac: m62332: Fix regulator reference count imbalance (git-fixes).\n- iio: gyro: mpu3050: fix sign of raw angular velocity readings (git-fixes).\n- iio: light: cm32181: return zero after writing calibscale (git-fixes).\n- iio: light: gp2ap002: Disable regulators on resume failure (git-fixes).\n- iio: light: gp2ap002: re-enable irq if runtime suspend fails (git-fixes).\n- iio: light: isl29028: return zero in write_raw() on success (git-fixes).\n- iio: light: ltrf216a: fix runtime PM reference leak in error path (git-fixes).\n- iio: light: opt4001: Fix incompatible pointer type passed to div_u64_rem() (git-fixes).\n- iio: light: opt4001: Fix power down clearing bits of the wrong register (git-fixes).\n- iio: light: opt4001: Fix reversed GENMASK() arguments in fault count mask (git-fixes).\n- iio: light: opt4001: Reject integration times with a non-zero seconds part (git-fixes).\n- iio: light: tsl2583: return zero in write_raw() on success (git-fixes).\n- iio: light: tsl2772: fix ALS calibscale readback (git-fixes).\n- iio: orientation: hid-sensor-rotation: Avoid race between callback setup and device exposure (git-fixes).\n- iio: pressure: dps310: fix NULL pointer dereference on ACPI probe (git-fixes).\n- iio: pressure: mpl115: Fix runtime PM cleanup (git-fixes).\n- iio: srf04: fix pm_runtime handling on probe error path (git-fixes).\n- iio: temperature: hid-sensor-temperature: switch to non-devm iio_device_register() (git-fixes).\n- Input: atkbd - skip deactivate for HONOR ZQC-P (git-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Book Pro 14's internal keyboard (stable-fixes).\n- Input: cs40l50-vibra - validate custom data from user space (git-fixes).\n- Input: evdev - fix information leak in evdev_pass_values() (stable-fixes).\n- Input: evdev - sanitize event type index when fetching event masks (stable-fixes).\n- Input: focaltech - fix array out-of-bounds in focaltech_process_rel_packet (git-fixes).\n- Input: focaltech - use signed coordinates to prevent underflow (git-fixes).\n- Input: hynitron_cstxxx - validate touch count and finger IDs (git-fixes).\n- Input: iforce - validate input packet lengths (stable-fixes).\n- Input: iqs5xx - validate firmware record destination span (git-fixes).\n- Input: mms114 - fix Y-resolution configuration (git-fixes).\n- Input: psxpad-spi - set driver data before use (git-fixes).\n- Input: reject inhibit and uninhibit requests on unregistering devices (git-fixes).\n- Input: sur40 - fix input device registration ordering (stable-fixes).\n- Input: sur40 - fix V4L error path cleanup (stable-fixes).\n- Input: synaptics-rmi4 - block s_input when F54 queue is busy (git-fixes).\n- Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer (git-fixes).\n- Input: synaptics-rmi4 - fix F55 transmitter electrode count typo (git-fixes).\n- Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue (git-fixes).\n- Input: synaptics-rmi4 - zero report size on F54 work error (git-fixes).\n- Input: xpad - add support for ZENAIM LEVERLESS (stable-fixes).\n- interconnect: Fix use after free in icc_get() and of_icc_get_by_index() (git-fixes).\n- io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (git-fixes).\n- io_uring/net: Avoid msghdr on op_connect/op_bind async data (git-fixes).\n- iommu/arm-smmu-v3: Manage teardown with devm (stable-fixes).\n- ip_tunnel: Use ip_tunnel_info() helper instead of 'info + 1' (bsc#1274727).\n- ipmi: ipmb: validate write message length (git-fixes).\n- ipmi: si: Fix NULL pointer dereference after failed registration (git-fixes).\n- KVM: arm64: Ensure FFA ranges are page aligned (git-fixes).\n- KVM: arm64: Fix bounds checking in do_ffa_mem_reclaim() (git-fixes).\n- KVM: arm64: Fix sign-extension of MMIO loads (git-fixes).\n- KVM: arm64: vgic: Reset in_kernel on private IRQ allocation failure (git-fixes).\n- KVM: arm64: Zero out the stack initialized data in the FFA handler (git-fixes).\n- KVM: nSVM: Always inject a #GP if mapping VMCB12 fails on nested VMRUN (git-fixes).\n- KVM: nSVM: Remove a user-triggerable WARN on nested_svm_load_cr3() succeeding (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (git-fixes).\n- KVM: PPC: Book3S HV: Add support for compat CPU capabilities for KVM on PowerNV (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Validate arch_compat against host compatibility mode (bsc#1263864 ltc#217835).\n- KVM: PPC: Document KVM_PPC_GET_COMPAT_CAPS ioctl (bsc#1263864 ltc#217835).\n- KVM: PPC: Introduce KVM_CAP_PPC_COMPAT_CAPS and wire up ioctl (bsc#1263864 ltc#217835).\n- KVM: SEV: Use to_kvm_sev_info() for fetching kvm_sev_info struct (git-fixes).\n- KVM: SVM: Add support to initialize SEV/SNP functionality in KVM (bsc#1279887).\n- KVM: SVM: Explicitly mark vmcb01 dirty after modifying VMCB intercepts (git-fixes).\n- KVM: SVM: Serialize accesses to the owner and mirror list with separate lock (git-fixes).\n- KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active (git-fixes).\n- KVM: TDX: Account all non-transient page allocations for per-TD structures (git-fixes).\n- KVM: TDX: Fix x2APIC MSR handling in tdx_has_emulated_msr() (git-fixes).\n- KVM: VMX: Don't register posted interrupt wakeup handler if alloc_kvm_area() fails (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86/mmu: Recover TDP MMU NX huge pages using MMU read lock (bsc#1271050).\n- KVM: x86/mmu: Rename kvm_tdp_mmu_zap_sp() to better indicate its purpose (bsc#1271050).\n- KVM: x86/mmu: Track possible NX huge pages separately for TDP vs. Shadow MMU (bsc#1271050).\n- KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears because it was cleared from the PIC (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears when Xen emulation is enabled (git-fixes).\n- KVM: x86: Fix array_index_nospec() protection in kvm_vcpu_ioctl_x86_set_mce() (git-fixes).\n- KVM: x86: Fix emulated CPUID features being applied to wrong sub-leaf (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- leds: pca9532: Fix inverted GPIO output polarity (git-fixes).\n- leds: pca9532: Fix phantom device registration on missing hardware (git-fixes).\n- lib/string: fix memchr_inv() for large ranges (git-fixes).\n- lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen() (git-fixes).\n- mac802154: fix data race and NULL deref on local-\u003eassoc_dev (git-fixes).\n- mac802154: fix netdev use-after-free in beacon worker (git-fixes).\n- mac802154: fix use-after-free of sdata via queued RX frames (git-fixes).\n- mailbox: pcc: Fix command timeout due to missed interrupt (git-fixes).\n- mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler (git-fixes).\n- mailbox: qcom-cpucp: handle NULL data in send_data callback (git-fixes).\n- mailbox: qcom-ipcc: fix duplicate channel allocation across holes (git-fixes).\n- mailbox: rockchip: disable pclk on probe failure and unbind (git-fixes).\n- maple_tree: fix argument name in header (git-fixes).\n- md/raid1: create serial pool adding rdev to array with serialize_policy=1 (bsc#1272261).\n- media: airspy: Return queued buffers on start_streaming() failure (git-fixes).\n- media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref (git-fixes).\n- media: amphion: Remove obsolete frame_count check in venc_start_session (git-fixes).\n- media: bcm2835-unicam: Fix asc leaked in error/remove path (git-fixes).\n- media: cec-pin: Fix event FIFO ordering (git-fixes).\n- media: cec: disable delayed work before freeing an interrupted transmit (git-fixes).\n- media: cec: extron-da-hd-4k-plus: add sanity check (git-fixes).\n- media: cec: meson: ao-cec-g12a: name the CEC core regmap to avoid debugfs clash (git-fixes).\n- media: cec: Serialize exclusive follower delivery (git-fixes).\n- media: cec: stm32: prevent out-of-bounds write on RX overflow (git-fixes).\n- media: cedrus: clean up media device on probe failure (git-fixes).\n- media: cedrus: fix memory leak in cedrus_init_ctrls() (git-fixes).\n- media: chips-media: wave5: Guard bit depth check with initial_info_obtained (git-fixes).\n- media: chips-media: wave5: Move src_buf Removal to finish_encode (git-fixes).\n- media: cobalt: Avoid freeing ALSA private data twice (git-fixes).\n- media: cx231xx: fix devres lifetime (git-fixes).\n- media: cx231xx: reject geometry changes while the VBI queue is busy (git-fixes).\n- media: cx23885: add ioremap return check and cleanup (git-fixes).\n- media: cx23885: cancel NetUP CI work before teardown (git-fixes).\n- media: em28xx: defer audio-only extension registration (git-fixes).\n- media: em28xx: fix use-after-free of dev_next-\u003edevlist on disconnect (git-fixes).\n- media: go7007: defer the ALSA v4l2 put until card release (git-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: i2c: alvium: fix critical pointer access in alvium_ctrl_init (git-fixes).\n- media: i2c: alvium: Fix: Correct name of register in alvium_set_ctrl_auto_exposure (git-fixes).\n- media: i2c: imx219: Rename VTS to FRM_LENGTH (stable-fixes).\n- media: i2c: imx415: Return test pattern write errors (git-fixes).\n- media: i2c: ov02a10: fix endpoint parsing use-after-free (git-fixes).\n- media: i2c: ov7740: fix use-after-destroy in remove (git-fixes).\n- media: i2c: rdacm21: Fix missing media_entity_cleanup() (git-fixes).\n- media: imx219: Fix maximum frame length in lines (git-fixes).\n- media: intel/ipu6: fix async notifier cleanup leak on parse error (git-fixes).\n- media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges (git-fixes).\n- media: ipu6: Do not free aux device pdata after init (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_HAUPPAUGE_NEW keymap define (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_RC5_TV keymap define (git-fixes).\n- media: mc-entity: Add missing kerneldoc (git-fixes).\n- media: mediatek: vcodec: bound AV1 tile-start copy to the array capacity (git-fixes).\n- media: meson: vdec: Fix memory leak in error path of vdec_open (git-fixes).\n- media: meson: vdec: fix NULL pointer deref in vdec_try_fmt_common (git-fixes).\n- media: msi2500: Return queued buffers on start_streaming() failure (git-fixes).\n- media: nuvoton: npcm-video: fix error handling in npcm_video_init() (git-fixes).\n- media: nuvoton: npcm-video: fix memory leaks in probe and remove (git-fixes).\n- media: nxp: imx8-isi: Add missing v4l2_subdev_cleanup() in crossbar and pipe (git-fixes).\n- media: nxp: imx8-isi: Clean up already-initialized pipes on probe failure (git-fixes).\n- media: nxp: imx8-isi: Correct color map between V4L2 and ISI (git-fixes).\n- media: nxp: imx8-isi: Fix missing v4l2_subdev_cleanup() in pipe init error path (git-fixes).\n- media: nxp: imx8-isi: Fix potential out-of-bounds issues (git-fixes).\n- media: nxp: imx8-isi: Fix scale factor calculation for hardware rounding (git-fixes).\n- media: nxp: imx8-isi: Fix stream ID validation bypass in crossbar routing (git-fixes).\n- media: nxp: imx8-isi: Use BIT_ULL() for 64-bit stream masks (git-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: platform: mtk-mdp3: fix NULL deref on failed SCP lookup (git-fixes).\n- media: platform: mtk-mdp3: Fix SCP device refcounting (git-fixes).\n- media: pwc: Drain fill_buf on start_streaming() failure (git-fixes).\n- media: pwc: Return queued buffers on start_streaming() failure (git-fixes).\n- media: qcom: camss: Fix RDI streaming for CSID GEN2 (git-fixes).\n- media: radio-si476x: Unregister v4l2_device on probe failure (git-fixes).\n- media: rc: sunxi-cir: Unregister rc device on probe failure (git-fixes).\n- media: rtl2832: fix use-after-free in rtl2832_remove() (git-fixes).\n- media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: Return queued buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak (git-fixes).\n- media: s2255: bound JPEG frame size before copying into the buffer (git-fixes).\n- media: s2255: check firmware size before reading trailing marker (git-fixes).\n- media: saa7134: Fix a possible memory leak in saa7134_video_init1 (git-fixes).\n- media: saa7164: fix cleanup on resource allocation failure (git-fixes).\n- media: stm32: dcmi: unregister notifier on probe failure (git-fixes).\n- media: sun4i-csi: Return queued buffers on start_streaming() failure (git-fixes).\n- media: tda18250: fix possible integer overflow (git-fixes).\n- media: tegra-video: vi: fix invalid u32 return value in format lookup (git-fixes).\n- media: usbtv: keep device alive while ALSA card exists (git-fixes).\n- media: v4l2-async: avoid deleting unlinked ASC entry on link error (git-fixes).\n- media: v4l2-async: Unregister sub-device if asc_list is empty (git-fixes).\n- media: v4l2-ctrls-request: add NULL check in v4l2_ctrl_request_complete() (git-fixes).\n- media: v4l2-ctrls: Allow unknown HDR10 white point and luminance (git-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-fwnode: Fix fwnode leak in v4l2_fwnode_parse_link (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: v4l2-subdev: Fail {enable,disable}_streams and s_streaming nicely (git-fixes).\n- media: venus: fix payload size calculation in parse_raw_formats() (git-fixes).\n- media: venus: fix payload size returned by parse_caps() and parse_alloc_mode() (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer (git-fixes).\n- media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity (git-fixes).\n- media: vicodec: fix out-of-bounds write in FWHT encoder (git-fixes).\n- media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure (git-fixes).\n- media: vimc: fix pixel format lookup in enum_framesizes (git-fixes).\n- media: vivid: add vivid_update_reduced_fps() (git-fixes).\n- media: vivid: check for vb2_is_busy() when toggling caps (git-fixes).\n- media: vivid: fix cleanup bugs in vivid_init() (git-fixes).\n- media: zoran: Avoid freeing a registered video_device twice (git-fixes).\n- mei: pull kvfree out of spinlock (git-fixes).\n- mfd: iqs62x: Reject zero-length firmware records (git-fixes).\n- mfd: rave-sp: validate received frame payload lengths (git-fixes).\n- mfd: sm501: Fix potential memory leaks during remove (git-fixes).\n- misc: bcm-vk: Use acquire/release for msgq_inited (git-fixes).\n- misc: fastrpc: fix channel ctx ref leak when session alloc fails (git-fixes).\n- misc: fastrpc: fix memory leak in fastrpc_channel_ctx_free (git-fixes).\n- misc: fastrpc: Remove buffer from list prior to unmap operation (git-fixes).\n- misc: fastrpc: take fl-\u003elock when moving mmaps on interrupted invoke (git-fixes).\n- misc: nsm: bound the device-reported response length (git-fixes).\n- misc: rtsx: add missing write register handling (git-fixes).\n- misc: sgi-gru: remove interrupt-context page-table walks (git-fixes).\n- misc: vmc_vmci: Fix potential memory leak in vmci_event_subscribe() (git-fixes).\n- mkspec-dtb: Move DTS prefix into package list.\n- mkspec-dtb: Move provides-obsoletes to package list.\n- mkspec-dtb: Put per-architecture package lists into a hash.\n- mkspec-dtb: re-indent.\n- mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition (git-fixes).\n- mmc: omap_hsmmc: fix busy_timeout overflow in ns conversion on 32-bit (git-fixes).\n- mmc: sdhci: unmap the bounce buffer before device release (git-fixes).\n- mmc: via-sdmmc: stop card-detect handling on probe failure (git-fixes).\n- mtd: afs: validate v2 image info bounds (git-fixes).\n- mtd: fix double free and WARN_ON in add_mtd_device() error paths (git-fixes).\n- mtd: mtdoops: free page bitmap when the backing MTD is removed (git-fixes).\n- mtd: mtdswap: Avoid freeing registered blktrans device twice (git-fixes).\n- mtd: mtdswap: remove debugfs stats file on teardown (git-fixes).\n- mtd: nand: mtk-ecc: stop on ECC idle timeouts (git-fixes).\n- mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() (git-fixes).\n- mtd: rawnand: validate ONFI extended parameter page sections (git-fixes).\n- mtd: spinand: fix direct mapping creation sizes (stable-fixes).\n- mtd: spinand: repeat reading in regular mode if continuous reading fails (stable-fixes).\n- mtd: spinand: try a regular dirmap if creating a dirmap for continuous reading fails (stable-fixes).\n- mtd: ubi: Release device reference on busy detach (git-fixes).\n- mtd: ubi: skip programming unused bits in ubi headers (stable-fixes).\n- net: Add options as a flexible array to struct ip_tunnel_info (bsc#1274727).\n- net: mana: Add debug knob to skip TX timeout recovery reset (git-fixes).\n- net: mana: Add handler for sriov configure (bsc#1272756).\n- net: mana: Cap MSI-X vectors to the device MSI-X table size (git-fixes).\n- net: mana: Extend RX CQE coalescing up to 8 packets (git-fixes).\n- net: mana: Fall back to scattered pages for GDMA queues (git-fixes).\n- net: mana: force full-page RX buffers via ethtool private flag (bsc#1269792).\n- net: mana: refactor mana_get_strings() and mana_get_sset_count() to use switch (bsc#1269792).\n- net: mana: Route ring-buffer access through offset-based helpers (git-fixes).\n- net: tap: set skb-\u003edev before parsing virtio net header in tap_get_user_xdp() (git-fixes bsc#1274550).\n- net: thunderbolt: Count delivered packets in rx_packets and rx_bytes (git-fixes).\n- net: thunderbolt: Mark the connection down when bringing it up fails (git-fixes).\n- net: thunderbolt: Release the Rx HopID that was handed out on mismatch (git-fixes).\n- net: thunderbolt: Tear down DMA paths before stopping the rings (git-fixes).\n- net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup() (git-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: ipheth: fix carrier_work UAF on disconnect (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (git-fixes).\n- nfc: digital: clamp SENSF_RES length to the destination buffer (git-fixes).\n- nfc: digital: Do not dump a NULL response in command completion (git-fixes).\n- nfc: fdp: bound the device-reported read length and fix an skb leak (git-fixes).\n- nfc: llcp: avoid userspace overflow on invalid optlen (git-fixes).\n- nfc: llcp: bound SNL TLV parsing to the skb and add length checks (git-fixes).\n- nfc: llcp: bound the connect_sn TLV walk to the skb (git-fixes).\n- nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (git-fixes).\n- nfc: llcp: read llcp_sock-\u003elocal under the socket lock in getsockopt (git-fixes).\n- nfc: llcp: reject PDUs shorter than the LLCP header (git-fixes).\n- nfc: microread: validate target discovery payload lengths (git-fixes).\n- nfc: nci: fix double completion race in nci_data_exchange_complete (git-fixes).\n- nfc: nci: fix out-of-bounds write in nci_target_auto_activated() (git-fixes).\n- nfc: nci: fix uninit-value in the RF discover/activated NTF handlers (git-fixes).\n- nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing (git-fixes).\n- nfc: nci: free destination parameters when closing a connection (git-fixes).\n- nfc: pn533: hold a reference to the request skb during send_frame (git-fixes).\n- nfc: pn533: purge fragmented skbs during cleanup (git-fixes).\n- nfc: st21nfca: validate ATR_REQ length against the received frame (git-fixes).\n- nouveau/gem: reserve the bo in the info ioctl around the vma lookup (git-fixes).\n- nvme-tcp: fix usage of page_frag_cache (bsc#1267882).\n- nvmet-rdma: fix queue leak when connect backlog is exceeded (git-fixes).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- PCI/ASPM: Use pcie_capability_clear_and_set_word() for ASPM disable/restore (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (git-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (git-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI: Add ACS quirk for Pericom PI7C9X2G608 switches [12d8:2608] (git-fixes).\n- PCI: hv: Set irq_retrigger callback for the Hyper-V PCI MSI irqchip (git-fixes).\n- PCI: j721e: Fix incorrect max_lanes for J7200 (git-fixes).\n- PCI: meson: Fix GPIO state while requesting PERST# (git-fixes).\n- PCI: plda: Fix IRQ domain leaks in the error paths of plda_init_interrupts() (git-fixes).\n- PCI: plda: Fix use-after-free of event IRQs during teardown (git-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- pinctrl: bcm2835: Don't remove an unregistered GPIO chip (git-fixes).\n- pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip (git-fixes).\n- pinctrl: rockchip: Reset the pin count when recalculating SoC data (git-fixes).\n- platform/chrome: cros_ec_debugfs: Clean up console log on probe failure (git-fixes).\n- platform/chrome: cros_ec_debugfs: Unregister panic notifier (git-fixes).\n- platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count (git-fixes).\n- platform/chrome: sensorhub: Bound the EC-reported sensor number (git-fixes).\n- platform/chrome: sensorhub: Fix dropped timestamp events and log spam (git-fixes).\n- platform/chrome: sensorhub: Fix memory overread in ring handler (git-fixes).\n- platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL (git-fixes).\n- platform/surface: acpi-notify: Check ACPI companion before use (git-fixes).\n- platform/x86/amd/hsmp: Reject negative power cap writes in hwmon (git-fixes).\n- platform/x86: asus-wmi: fix resource leaks on probe failure (git-fixes).\n- platform/x86: dell-privacy: Fix race condition (git-fixes).\n- platform/x86: dell-wmi-base: Fix resource leak on module load failure (git-fixes).\n- platform/x86: dell-wmi-sysman: Don't hex dump attribute security buffer (git-fixes).\n- platform/x86: dell-wmi-sysman: Fix instance ID bounds (git-fixes).\n- platform/x86: hp-bioscfg: accept reduced ACPI packages from older HP BIOS (git-fixes).\n- platform/x86: hp-bioscfg: advance elem past consumed array elements (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store() (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read on empty password write (git-fixes).\n- platform/x86: hp-bioscfg: fix new_password_store() overwriting current_password (git-fixes).\n- platform/x86: hp-bioscfg: fix off-by-one write in hp_get_string_from_buffer() (git-fixes).\n- platform/x86: hp-bioscfg: fix ORD_LIST_ELEMENTS never being parsed (git-fixes).\n- platform/x86: hp-bioscfg: fix password encoding bounds check (git-fixes).\n- platform/x86: hp-bioscfg: warn on element type mismatch instead of failing (git-fixes).\n- platform/x86: ishtp_eclite: Fix ACPI device reference leak in probe error path (git-fixes).\n- platform/x86: ISST: Add a NULL check for sst_inst (git-fixes).\n- platform/x86: ISST: Just allow 2 bits for SST feature enable (git-fixes).\n- platform/x86: ISST: Return error during profile addition (git-fixes).\n- platform/x86: ISST: Use PP level enable mask (git-fixes).\n- platform/x86: ISST: Validate level in perf mask ioctls (git-fixes).\n- platform/x86: ISST: Validate logical CPU id and clos id (git-fixes).\n- platform/x86: ISST: Validate parameter for core power state (git-fixes).\n- platform/x86: ISST: Validate parameter for frequency and priority (git-fixes).\n- platform/x86: ISST: Validate socket ID in clos_assoc ioctl (git-fixes).\n- PM: hibernate: Fix memory leak in snapshot_write_next() error path (git-fixes).\n- PM: sleep: Fix off-by-one in wakelocks number limit check (git-fixes).\n- power: supply: bd99954: Drop bad register fields (git-fixes).\n- power: supply: bq27xxx: bq27z561: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq28z610: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq27520g4: fix REG_TTES address (git-fixes).\n- power: supply: bq256xx: drain usb_work before freeing the charger (git-fixes).\n- power: supply: bq24257: fix use-after-free on remove (git-fixes).\n- power: supply: bq25890: Fix power_supply reference leak (git-fixes).\n- power: supply: charger-manager: register regulators before exposing sysfs (git-fixes).\n- power: supply: cros_usbpd-charger: bound the EC-reported port count (git-fixes).\n- power: supply: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS (git-fixes).\n- power: supply: isp1704_charger: cancel work on remove (git-fixes).\n- power: supply: lp8727: fix use-after-free in lp8727_release_irq() (git-fixes).\n- power: supply: lp8788-charger: fix use-after-free on remove (git-fixes).\n- power: supply: max17040: drop incorrect I2C functionality check (git-fixes).\n- power: supply: max17040: propagate register read errors (git-fixes).\n- power: supply: max17040: synchronize work cancellation on suspend (git-fixes).\n- power: supply: qcom_battmgr: terminate the strings from firmware (git-fixes).\n- power: supply: rt9455: quiesce delayed work before teardown (git-fixes).\n- power: supply: sbs-battery: Use a per-device serial number buffer (git-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: twl4030_charger: cancel workers via devm (git-fixes).\n- power: supply: ucs1002: fix use-after-free on remove (git-fixes).\n- powercap: intel_rapl_tpmi: Handle PMU registration failure during probe (git-fixes).\n- powerpc/dt_cpu_ftrs: Set CPU_FTR_P11_PVR for Power11 and later processors (bsc#1263864 ltc#217835).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/pseries: Ensure vpa,slb_shadow \u0026 dtl are unregistered during crash (bsc#1271256).\n- powerpc/pseries: lparcfg - fix kbuf[] underflow (bsc#1274753 ltc#221289 bsc#1274754 ltc#221288 bsc#1274752\n  ltc#221290).\n- powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak (bsc#1274751 ltc#221105 bsc#1274750 ltc#221106).\n- powerpc/pseries: pci - logic bug (bsc#1274749 ltc#221282 bsc#1274755 ltc#221284 bsc#1274756 ltc#221283).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in non-uapi headers (bsc#1263864 ltc#217835).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in uapi headers (bsc#1263864 ltc#217835).\n- ppdev: prevent overflow when setting port timeout (git-fixes).\n- rapidio/tsi721: prevent a bad dereference in tsi721_db_dpc() (git-fixes).\n- rapidio: clear mport-\u003enet when rio_add_net() fails (git-fixes).\n- rapidio: mport_cdev: fix use-after-free in dma_req_free() (git-fixes).\n- RDMA/bnxt_re: Avoid displaying the kernel pointer (git-fixes).\n- RDMA/bnxt_re: Proper rollback if the ioremap fails (git-fixes).\n- RDMA/irdma: Remove redundant legacy_mode checks (git-fixes).\n- RDMA/mana_ib: drain QP references after partial table insertion (git-fixes).\n- RDMA/mana_ib: unify QP lookup table (git-fixes).\n- RDMA/mlx5: Fix integer overflow of user QP buffer size (git-fixes).\n- regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving dangling of_node pointer (git-fixes).\n- regulator: core: use system_freezable_wq for init complete work (git-fixes).\n- regulator: max8998_pmic_dt_parse_pdata: of_node_put on reg_np after ownership transferred to rdata (git-fixes).\n- regulator: qcom-refgen: correct the regulator type to CURRENT (git-fixes).\n- regulator: qcom-rpmh: Fix PMIC5 BOB bypass mode handling (git-fixes).\n- remoteproc: qcom: Fix glink-\u003enode reference leak in qcom_add_glink_subdev (git-fixes).\n- remoteproc: qcom_q6v5_adsp: Fix reference leak for device node (git-fixes).\n- remoteproc: scp: Fix device reference leak on failed lookup (git-fixes).\n- Revert \"drm/amdgpu: fix aperture mapping leak\" (git-fixes).\n- Revert \"media: v4l2-dev: fix error handling in __video_register_device()\" (git-fixes).\n- Revert \"net: thunderbolt: Enable end-to-end flow control also in transmit\" (git-fixes).\n- Revert \"thermal/drivers/hwmon: Cleanup coding style a bit\" (stable-fixes).\n- Revert \"wifi: mt76: Disable napi when removing device\" (git-fixes).\n- rpmsg: core: Fix incorrect return value documentation (git-fixes).\n- rpmsg: glink: smem: order FIFO read after availability check (git-fixes).\n- rtc: gamecube: check return value of devm_rtc_register_device() (git-fixes).\n- rtc: pcf8563: fix clock provider leak on unbind (git-fixes).\n- rtc: pcf85363: Add error checking to regmap calls in probe() (git-fixes).\n- rtc: rzn1: Disable alarm interrupt before reprogramming alarm registers (git-fixes).\n- rtc: rzn1: Fix weekday underflow when alarm crosses month boundary (git-fixes).\n- rtc: zynqmp: Return optional clock lookup errors (git-fixes).\n- s390/pkey: Check length in pkey_pckmo handler implementation (bsc#1270266).\n- s390/pkey: Check length in PKEY_VERIFYPROTK ioctl (bsc#1270267).\n- sched/psi: Create the psimon kthread outside of cgroup_mutex (bsc#1269134).\n- scsi: fnic: Abort timed-out NVMe LS requests (bsc#1236344).\n- scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths (bsc#1236344).\n- scsi: fnic: Add FDLS role handling for NVMe initiators (bsc#1236344).\n- scsi: fnic: Add the NVMe/FC transport path (bsc#1236344).\n- scsi: fnic: Advertise NVMe initiator service parameters (bsc#1236344).\n- scsi: fnic: Bump up version number (bsc#1236344).\n- scsi: fnic: Decode firmware role configuration (bsc#1236344).\n- scsi: fnic: Do not use GFP_ZERO for mempools (bsc#1236344).\n- scsi: fnic: Expose NVMe transport state in debugfs (bsc#1236344).\n- scsi: fnic: Handle NVMe LS frames in FDLS (bsc#1236344).\n- scsi: fnic: Make debug logging protocol independent (bsc#1236344).\n- scsi: fnic: Make fnic_queuecommand() easier to analyze (bsc#1236344).\n- scsi: fnic: Refactor in_remove flag and call to fnic_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Remove a useless struct mempool forward declaration (bsc#1236344).\n- scsi: fnic: Rename fnic_scsi_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Route completions and resets by initiator role (bsc#1236344).\n- scsi: fnic: Self-assignment of intr_time_type has no effect (bsc#1236344).\n- scsi: fnic: Send NVMe LS requests through FDLS (bsc#1236344).\n- scsi: fnic: Switch to use %ptSp (bsc#1236344).\n- scsi: fnic: Track NVMe transport statistics (bsc#1236344).\n- scsi: fnic: Use fnic_num for non-SCSI identifiers (bsc#1236344).\n- scsi: fnic: Use mempool for receive frames (bsc#1236344).\n- scsi: qla2xxx: Add support to report MPI FW state (bsc#1275737).\n- scsi: qla2xxx: Declare qla2xxx_mqueuecommand() static (bsc#1275737).\n- scsi: qla2xxx: Use nr_cpu_ids instead of NR_CPUS for qp_cpu_map allocation (bsc#1275737).\n- scsi: storvsc: Support manual scans for all Hyper-V targets (git-fixes).\n- sctp: avoid auth_enable sysctl UAF during netns teardown (git-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- serial: 8250_dma: Clear stale RX state on shutdown (git-fixes).\n- serial: amba-pl011: unprepare console clock on unregister (git-fixes).\n- serial: core: clear freed pointers on uart_register_driver() failure (git-fixes).\n- serial: imx: serialize imx_uart_ports lifetime (git-fixes).\n- serial: ma35d1: Fix OF node reference leaks in console init (git-fixes).\n- serial: qcom-geni: do not advance stale DMA completions (git-fixes).\n- serial: qcom-geni: fix TX DMA buffer flush (git-fixes).\n- serial: sc16is7xx: enable THRI before filling TX FIFO (git-fixes).\n- serial: sc16is7xx: rename EFR mutex with generic name (stable-fixes).\n- serial: sc16is7xx: use guards for simple mutex locks (stable-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb/client: handle overlapping allocated ranges in fallocate (bsc#1274902).\n- smb: client: harden POSIX SID length parsing (bsc#1273557).\n- smb: client: require net admin for CIFS SWN netlink (bsc#1273966).\n- smb: client: resolve SWN tcon from live registrations (bsc#1273872).\n- soc: fsl: qe: check platform_driver_register() in qe_ic_of_init() (git-fixes).\n- soc: qcom: rpmh-rsc: manage PM notifiers with devres (git-fixes).\n- soc: samsung: exynos-pmu: fix of_node refcount leak in exynos_get_pmu_regmap() (git-fixes).\n- software node: Fix software_node_get_reference_args() with index -1 (git-fixes).\n- soundwire: qcom: Fix port exhaustion check in stream_alloc_ports (git-fixes).\n- speakup: keyhelp: guard letter_offsets possible out-of-range indexing (git-fixes).\n- spi: bcm63xx-hsspi: disable clocks on resume failure (git-fixes).\n- spi: bcm63xx: disable clock on resume failure (git-fixes).\n- spi: bcmbca-hsspi: disable clocks on resume failure (git-fixes).\n- spi: davinci: switch to managed controller allocation (git-fixes).\n- spi: Fix DMA mapping ownership on partial map failure (git-fixes).\n- spi: img-spfi: don't disable runtime PM on DMA deferred probe (git-fixes).\n- spi: oc-tiny: switch to managed controller allocation (git-fixes).\n- spi: spi-cadence: enable SPI_CONTROLLER_MUST_TX (git-fixes).\n- spi: spi-cadence: Move TX FIFO full busy-wait into FIFO (git-fixes).\n- spi: spi-cadence: supports transmission with bits_per_word of 16 and 32 (stable-fixes).\n- spi: spi-fsl-dspi: Avoid setup_accel logic for DMA transfers (stable-fixes).\n- spi: sprd-adi: Fix probe succeeding without registering the controller (git-fixes).\n- staging: fbtft: Use sysfs_emit_at() to print to sysfs file (git-fixes).\n- staging: media: tegra-video: fix of_node_put() on VIP parse errors (git-fixes).\n- staging: media: tegra-video: vi: fix probe failure on skipped last port (git-fixes).\n- staging: octeon: add missing tasklet_kill in cvm_oct_tx_shutdown (git-fixes).\n- staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init() (git-fixes).\n- staging: rtl8723bs: fix missing shared-key auth challenge length check (git-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() (git-fixes).\n- staging: rtl8723bs: fix OOB read in WMM_param_handler() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: use kfree_sensitive() for key material (git-fixes).\n- staging: rtl8723bs: validate monitor transmit frame lengths (git-fixes).\n- staging: sm750fb: Add missing Kconfig dependency (git-fixes).\n- staging: sm750fb: gate dualview dataflow using g_dualview (git-fixes).\n- thermal/drivers/imx: Disable clock on runtime resume failure (git-fixes).\n- thermal/drivers/qoriq: Disable clock on resume failure (git-fixes).\n- thermal/drivers/rcar: Fix error checking in probe() (git-fixes).\n- thermal: intel: int3400: clean up ODVP on probe failures (git-fixes).\n- thermal: sysfs: switch to use scnprintf() to suppress truncation warning (git-fixes).\n- thunderbolt: Bound the DROM dual link port number before indexing sw-\u003eports (git-fixes).\n- thunderbolt: Fix bandwidth group reservation indexing (git-fixes).\n- thunderbolt: icm: Preserve USB4 proxy data-valid bit (git-fixes).\n- tlclk: if sscanf() fails, fall back to 0, not random value (git-fixes).\n- tpm: st33zp24: Return zero on status read failure (git-fixes).\n- tpm: st33zp24: Validate locality read result (git-fixes).\n- tpm: tpm_i2c_nuvoton: disable IRQ on wait timeout (git-fixes).\n- tty: clear cdev pointer after cdev_add() failure (git-fixes).\n- tty: hvc: restrict HVC_DCC to ARMv6+ and ARM64 (git-fixes).\n- tty: skip cdev_del() when no cdev is registered (git-fixes).\n- uio: Fix stale info pointer in failed registration path (git-fixes).\n- usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm() (git-fixes).\n- usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect (git-fixes).\n- usb: atm: usbatm: fix invalid ci_range initialization (git-fixes).\n- USB: c67x00: fix use-after-free in c67x00_add_iso_urb() (git-fixes).\n- usb: cdnsp: fix incorrect endian conversions for APB timeout register (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (git-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: core: sysfs: add lock to bos_descriptors_read() (stable-fixes).\n- usb: dwc2: add missing @remotewakeup kernel-doc parameter (git-fixes).\n- usb: dwc2: gadget: Exit partial power down state when changing USB pull-up (git-fixes).\n- usb: dwc3: clear forceRM when issuing EndTransfer (git-fixes).\n- usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: fix UAF when probe runs concurrent to dyn ID removal (git-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed (git-fixes).\n- usb: gadget: configfs: fix out-of-bounds read of qw_sign (git-fixes).\n- usb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths (git-fixes).\n- usb: gadget: f_fs: Prevent deadlock during ep0 read loop (git-fixes).\n- usb: gadget: f_midi: initialize work in f_midi_alloc() (git-fixes).\n- usb: gadget: f_ncm: Use unsigned int for ndp_index (git-fixes).\n- usb: gadget: f_tcm: fix deadlock in usbg_make_tpg() (git-fixes).\n- usb: gadget: f_uac1_legacy: remove broken string configfs attributes (git-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- USB: gadget: fsl-udc: fix dev_printk() device (git-fixes).\n- usb: gadget: midi2: Fix null-pointer dereference in f_midi2_free_ep_reqs (git-fixes).\n- usb: gadget: midi2: remove default configfs groups on teardown (git-fixes).\n- usb: gadget: pch_udc: remove excess kernel-doc member for registered (git-fixes).\n- usb: gadget: r8a66597: avoid double free of ep0_req in probe error path (git-fixes).\n- usb: gadget: snps_udc_plat: clean up PHY on probe deferral (git-fixes).\n- usb: gadget: u_audio: Fix use-after-free on sound card disconnect (git-fixes).\n- usb: gadget: uac: validate rate list length before storing (git-fixes).\n- USB: gadget: Use str_enable_disable-like helpers (stable-fixes).\n- usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and uvc_function_unbind() (git-fixes).\n- usb: ljca: bound bank_num in ljca_enumerate_gpio() (git-fixes).\n- usb: mtu3: allow system suspend during active gadget connection (git-fixes).\n- usb: musb: omap2430: clean up probe error handling (stable-fixes).\n- usb: musb: omap2430: Do not put borrowed of_node in probe (git-fixes).\n- usb: musb: omap2430: Fix use-after-free in omap2430_probe() (git-fixes).\n- USB: phy: fsl-usb: fix missing static keywords (git-fixes).\n- usb: renesas_usbhs: Fix power-off ordering on unbind (git-fixes).\n- USB: serial: digi_acceleport: fix port registration order (git-fixes).\n- USB: serial: ftdi_sio: add support for E+H FXA291 (stable-fixes).\n- USB: serial: option: add TDTECH MT5710-CN (stable-fixes).\n- USB: serial: option: fix slab OOB read in interrupt URB callback (git-fixes).\n- USB: serial: spcp8x5: drop broken carrier detect support (git-fixes).\n- USB: storage: add NO_ATA_1X quirk for Longmai USB Key (stable-fixes).\n- usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop (git-fixes).\n- usb: typec: qcom-pmic-typec: drain cc_debounce_dwork if port_start() fails (git-fixes).\n- usb: typec: qcom-pmic: cancel reset_work on stop (git-fixes).\n- usb: typec: tcpci: pass correct rx_type to tcpm_pd_receive() (git-fixes).\n- usb: typec: thunderbolt: Disable work before freeing tbt on remove (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: unregister debugfs entries on teardown (git-fixes).\n- usb: typec: ucsi: use UCSI_TIMEOUT_MS for sync command completion (git-fixes).\n- usb: usbfs: fix use-after-free of usb_device in usbdev_release() (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: xhci: Handle USB3 port events when there is one roothub (git-fixes).\n- vfs: Add a sysctl for automated deletion of dentry (bsc#1240890 bsc#1276586).\n- vt: add permission check for KDSKBMETA ioctl (stable-fixes).\n- vt: stabilize tty reference in kbd_keycode with tty_port_tty_get (stable-fixes).\n- w1: ds28e17: reject an oversize length on an I2C block read (git-fixes).\n- w1: ds2482: Fix signedness bug in ds2482_w1_triplet() (git-fixes).\n- watchdog: bd96801_wdt: Fix timeout for enabled WDG (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath6kl: avoid buffer overreads in WMI event handlers (git-fixes).\n- wifi: ath6kl: clamp assoc request/response lengths before subtracting IE offsets (git-fixes).\n- wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump (git-fixes).\n- wifi: ath11k: Avoid buffer overread in ath11k_wmi_tlv_op_rx() (git-fixes).\n- wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate (git-fixes).\n- wifi: ath11k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath12k: Avoid buffer overread in ath12k_wmi_op_rx() (git-fixes).\n- wifi: ath12k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: brcmfmac: Fix memory leak in brcmf_sdio_read_control() (git-fixes).\n- wifi: brcmfmac: fix P2P action frame handling without device vif (git-fixes).\n- wifi: brcmfmac: initialize SDIO data work before cleanup (git-fixes).\n- wifi: cfg80211: bound element ID read when checking non-inheritance (git-fixes).\n- wifi: cfg80211: cancel sched scan results work on unregister (git-fixes).\n- wifi: cfg80211: derive S1G beacon TSF from S1G fields (git-fixes).\n- wifi: cfg80211: reject unsupported PMSR FTM location requests (git-fixes).\n- wifi: cfg80211: validate PMSR FTM preamble range (git-fixes).\n- wifi: cfg80211: validate PMSR measurement type data (git-fixes).\n- wifi: ipw2100: fix potential memory leak in ipw2100_pci_init_one() (git-fixes).\n- wifi: iwlwifi: fix counter type in iwl_fwrt_dump_error_logs (git-fixes).\n- wifi: iwlwifi: guard against division by zero in iwl_dbg_tlv_alloc_fragments (git-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mei: pass correct argument to function (git-fixes).\n- wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser (git-fixes).\n- wifi: libertas: fix memory leak in helper_firmware_cb() (git-fixes).\n- wifi: mac80211: disconnect on CSA to channel 0 (git-fixes).\n- wifi: mac80211: fix fils_discovery double free on alloc failure (git-fixes).\n- wifi: mac80211: fix per-STA profile length in cross-link CSA parsing (git-fixes).\n- wifi: mac80211: fix unsol_bcast_probe_resp double free on alloc failure (git-fixes).\n- wifi: mac80211: free AP_VLAN bc_buf SKBs outside IRQ lock (git-fixes).\n- wifi: mac80211: send TWT teardown to peer after setup TX failure (git-fixes).\n- wifi: mac80211: skip default WMM setup for AP_VLAN links (git-fixes).\n- wifi: mac80211: skip unused probe response countdown offsets (git-fixes).\n- wifi: mt76: check txfree done event on the WED hw path (git-fixes).\n- wifi: mt76: fix 4th chain ACK RSSI bitmask in sta_poll (git-fixes).\n- wifi: mt76: fix ER-SU 106-tone RU check in RX rate decode (git-fixes).\n- wifi: mt76: fix HE DCM max-RU capability encoding (git-fixes).\n- wifi: mt76: fix non-AQL packet accounting for MLO stations (git-fixes).\n- wifi: mt76: fix stranded frames in mt76_txq_schedule_pending (git-fixes).\n- wifi: mt76: mt76x02: do not WARN on invalid rx descriptor length (git-fixes).\n- wifi: mt76: mt792x: Fix memory leak in SDIO TX path (git-fixes).\n- wifi: mt76: mt792x: fix use-after-free in mt76_rx_poll_complete (git-fixes).\n- wifi: mt76: mt7615: avoid waiting for mac work under the mt76 mutex (git-fixes).\n- wifi: mt76: mt7915: avoid nss underflow in mt7915_mcu_get_sta_nss (git-fixes).\n- wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear (git-fixes).\n- wifi: mt76: mt7915: fix double hif2 init on the non-WED path (git-fixes).\n- wifi: mt76: mt7915: fix ext PHY use-after-free on register error path (git-fixes).\n- wifi: mt76: mt7915: fix net_fill_forward_path for non-DBDC mt7986 (git-fixes).\n- wifi: mt76: mt7915: poll the correct SLP CTRL register for the second adie (git-fixes).\n- wifi: mt76: mt7915: release hif2 reference on probe IRQ failure (git-fixes).\n- wifi: mt76: mt7915: unlink TWT flow if the MCU rejects the agreement (git-fixes).\n- wifi: mt76: mt7915: unwind state on add_interface failure (git-fixes).\n- wifi: mt76: mt7915: use little-endian for bss_info_ra wire fields (git-fixes).\n- wifi: mt76: mt7915: write RX header translation bit to the correct register (git-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: mt7921: validate CLC firmware records (git-fixes).\n- wifi: mt76: mt7925: ensure tx headroom in usb_sdio_tx_prepare_skb (git-fixes).\n- wifi: mt76: mt7925: fix msg len mismatch between driver and firmware (git-fixes).\n- wifi: mt76: mt7925: update clc before setting sar power table (git-fixes).\n- wifi: mt76: mt7996: bound TLV walk in mt7996_mcu_get_chip_config (git-fixes).\n- wifi: mt76: mt7996: don't report a zero TX bitrate (git-fixes).\n- wifi: mt76: mt7996: fix capability of EHT-MCS 15 in MRU (git-fixes).\n- wifi: mt76: mt7996: fix reg addr remap when addr is 0 (git-fixes).\n- wifi: mt76: mt7996: reserve space for the CSA-abort countdown TLV (git-fixes).\n- wifi: mt76: mt7996: set MT76_MCU_RESET before waking MCU waiters on full reset (git-fixes).\n- wifi: mt76: mt7996: validate RX band_idx before dereferencing phys (git-fixes).\n- wifi: mt76: only consume the WO drop bit on WED v2 devices (git-fixes).\n- wifi: mt76: report data NSS for STBC frames in RX rate decode (git-fixes).\n- wifi: mwifiex: Detach sync cmd buffer on interrupted wait (git-fixes).\n- wifi: nl80211: free RNR data on MBSSID mismatch (git-fixes).\n- wifi: nl80211: validate nested MBSSID IE blobs (git-fixes).\n- wifi: p54: validate RX frame length in p54_rx_eeprom_readback() (git-fixes).\n- wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop (git-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtlwifi: pci: fix error path in rtl_pci_probe() (git-fixes).\n- wifi: rtlwifi: rtl8192du: check QoS TID before indexing tids (git-fixes).\n- wifi: rtlwifi: rtl8192du: Fix possible memory leak in rtl92du_init_sw_vars() (git-fixes).\n- wifi: rtw88: Fix potential memory leak in rtw_txq_push_skb() (git-fixes).\n- wifi: rtw88: pci: fix resource leak on failed NAPI setup (git-fixes).\n- wifi: rtw89: fix HE extended capability length check (git-fixes).\n- wifi: zd1211rw: reject secondary interfaces to prevent conflicts (git-fixes).\n- x86/virt/tdx: Print TDX module version during init (git-fixes).\n- x86/virt/tdx: Retrieve TDX module version (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_alloc_driver() failure (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_register_driver() failure (git-fixes).\n- xhci: fix lost bounce buffers on TDs spanning several ring segments (git-fixes).\n","status":"published","published":"2026-09-22T13:58:11Z","modified":"2026-09-30T18:23:11.377740347Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"SUSE-SU-2026:23902-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-68214: timers: Fix NULL function pointer race in timer_shutdown_sync() (bsc#1255225).\n- CVE-2025-68358: btrfs: fix racy bitfield write in btrfs_clear_space_info_full() (bsc#1255531).\n- CVE-2025-68780: sched/deadline: only set free_cpus for online runqueues (bsc#1256671).\n- CVE-2025-71075: scsi: aic94xx: fix use-after-free in device removal path (bsc#1256629).\n- CVE-2026-23113: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (bsc#1258278).\n- CVE-2026-23306: scsi: pm8001: Fix use-after-free in pm8001_queue_command() (bsc#1260501).\n- CVE-2026-23348: cxl/mem: Clarify @host for devm_cxl_add_nvdimm() (bsc#1260577).\n- CVE-2026-31418: netfilter: ipset: drop logically empty buckets in mtype_del (bsc#1262073).\n- CVE-2026-31530: cxl/port: Fix use after free of parent_port in cxl_detach_ep() (bsc#1262756).\n- CVE-2026-31531: ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop() (bsc#1263004).\n- CVE-2026-43116: netfilter: ctnetlink: ensure safe access to master conntrack (bsc#1264619).\n- CVE-2026-43125: dlm: validate length in dlm_search_rsb_tree (bsc#1264541).\n- CVE-2026-43163: md/bitmap: fix GPF in write_page caused by resize race (bsc#1264335).\n- CVE-2026-43239: smb: client: prevent races in -\u003equery_interfaces() (bsc#1264444).\n- CVE-2026-43271: md-cluster: fix NULL pointer dereference in process_metadata_update (bsc#1264587).\n- CVE-2026-43299: btrfs: do not ASSERT() when the fs flips RO inside btrfs_repair_io_failure() (bsc#1264851).\n- CVE-2026-43331: x86/kexec: Disable KCOV instrumentation after load_segments() (bsc#1265132).\n- CVE-2026-43355: iio: light: bh1780: fix PM runtime leak on error path (bsc#1265036).\n- CVE-2026-43363: x86/apic: Disable x2apic on resume if the kernel expects so (bsc#1265068).\n- CVE-2026-43416: powerpc, perf: Check that current-\u003emm is alive before getting user callchain (bsc#1265121).\n- CVE-2026-43439: cgroup: fix race between task migration and iteration (bsc#1265141).\n- CVE-2026-43448: nvme-pci: Fix race bug in nvme_poll_irqdisable() (bsc#1264807).\n- CVE-2026-45860: netfilter: nf_conncount: increase the connection clean up limit to 64 (bsc#1266710).\n- CVE-2026-45897: netfilter: nft_counter: serialize reset with spinlock (bsc#1266897).\n- CVE-2026-45968: cpuidle: Skip governor when only one idle state is available (bsc#1267023).\n- CVE-2026-46007: hwmon: (powerz) Avoid cacheline sharing for DMA buffer (bsc#1267586).\n- CVE-2026-46070: md/raid5: validate payload size before accessing journal metadata (bsc#1267501).\n- CVE-2026-46107: dm-thin: fix metadata refcount underflow (bsc#1267612).\n- CVE-2026-46115: block: add pgmap check to biovec_phys_mergeable (bsc#1266874).\n- CVE-2026-46133: RDMA/rxe: Reject unknown opcodes before ICRC processing (bsc#1266928).\n- CVE-2026-46135: nvmet-tcp: remove redundant calls to nvmet_tcp_fatal_error() (bsc#1267373).\n- CVE-2026-46195: smb: client: validate dacloffset before building DACL pointers (bsc#1266860).\n- CVE-2026-46304: nvmet: avoid recursive nvmet-wq flush in nvmet_ctrl_free (bsc#1267985).\n- CVE-2026-52912: netfilter: nf_queue: hold bridge skb-\u003edev while queued (bsc#1269000).\n- CVE-2026-52920: netfilter: xt_policy: fix strict mode inbound policy matching (bsc#1269013).\n- CVE-2026-52928: af_unix: Reject SIOCATMARK on non-stream sockets (bsc#1269010).\n- CVE-2026-52929: sctp: stream: fully roll back denied add-stream state (bsc#1269004).\n- CVE-2026-52935: xfrm: espintcp: do not reuse an in-progress partial send (bsc#1268979).\n- CVE-2026-52939: net/rds: fix NULL deref in rds_ib_send_cqe_handler() on masked atomic completion (bsc#1268972).\n- CVE-2026-52946: fs/fcntl: fix SOFTIRQ-unsafe lock order in fasync signaling (bsc#1269113).\n- CVE-2026-52977: futex: Prevent lockup in requeue-PI during signal/ timeout wakeup (bsc#1269242).\n- CVE-2026-52990: fsnotify: fix inode reference leak in fsnotify_recalc_mask() (bsc#1269108).\n- CVE-2026-52991: sched/psi: fix race between file release and pressure write (bsc#1269134).\n- CVE-2026-52994: vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting (bsc#1269126).\n- CVE-2026-53001: netfilter: xtables: restrict several matches to inet family (bsc#1269114).\n- CVE-2026-53031: bpf: Validate node_id in arena_alloc_pages() (bsc#1269380).\n- CVE-2026-53033: bpf, sockmap: Take state lock for af_unix iter (bsc#1269388).\n- CVE-2026-53034: bpf, sockmap: Fix af_unix null-ptr-deref in proto update (bsc#1269140).\n- CVE-2026-53048: gfs2: prevent NULL pointer dereference during unmount (bsc#1269162).\n- CVE-2026-53059: dm log: fix out-of-bounds write due to region_count overflow (bsc#1269655).\n- CVE-2026-53061: dm cache: fix dirty mapping checking in passthrough mode switching (bsc#1269685).\n- CVE-2026-53076: bpf: Fix OOB in pcpu_init_value (bsc#1269695).\n- CVE-2026-53077: net/rds: Restrict use of RDS/IB to the initial network namespace (bsc#1269412).\n- CVE-2026-53089: bpf: Fix use-after-free in offloaded map/prog info fill (bsc#1269783).\n- CVE-2026-53091: net: account for encap headers in qdisc pkt len (bsc#1269530).\n- CVE-2026-53092: bpf: Fix linked reg delta tracking when src_reg == dst_reg (bsc#1269528).\n- CVE-2026-53094: bpf: Fix stale offload-\u003eprog pointer after constant blinding (bsc#1269965).\n- CVE-2026-53096: bpf: Use RCU-safe iteration in dev_map_redirect_multi() SKB path (bsc#1269969).\n- CVE-2026-53109: powerpc/pgtable-frag: Fix bad page state in pte_frag_destroy (bsc#1269417).\n- CVE-2026-53110: s390: always declare expoline thunks (bsc#1269985).\n- CVE-2026-53111: bpf: test_run: Fix the null pointer dereference issue in bpf_lwt_xmit_push_encap (bsc#1269167).\n- CVE-2026-53114: perf: Extend the bit width of the arch-specific flag (bsc#1269999).\n- CVE-2026-53126: blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() (bsc#1269635).\n- CVE-2026-53129: fs/mbcache: cancel shrink work before destroying the cache (bsc#1269633).\n- CVE-2026-53142: drm/xe/display: fix oops in suspend/shutdown without display (bsc#1269402).\n- CVE-2026-53154: mm/hugetlb: restore reservation on error in hugetlb folio copy paths (bsc#1269665).\n- CVE-2026-53163: locking/rtmutex: Skip remove_waiter() when waiter is not enqueued (bsc#1269306).\n- CVE-2026-53180: timers/migration: Fix livelock in tmigr_handle_remote_up() (bsc#1269888).\n- CVE-2026-53207: mm/memory-failure: fix hugetlb_lock AA deadlock in get_huge_page_for_hwpoison (bsc#1269590).\n- CVE-2026-53219: netfilter: x_tables: avoid leaking percpu counter pointers (bsc#1269686).\n- CVE-2026-53220: netfilter: revalidate bridge ports (bsc#1269381).\n- CVE-2026-53223: net: guard timestamp cmsgs to real error queue skbs (bsc#1269301).\n- CVE-2026-53228: ipv6: sit: reload inner IPv6 header after GSO offloads (bsc#1269256).\n- CVE-2026-53238: netlabel: validate unlabeled address and mask attribute lengths (bsc#1269774).\n- CVE-2026-53264: net/sched: act_api: use RCU with deferred freeing for action lifecycle (bsc#1269238).\n- CVE-2026-53269: netfilter: synproxy: add mutex to guard hook reference counting (bsc#1269579).\n- CVE-2026-53284: btrfs: only release the dirty pages io tree after successful writes (bsc#1269816).\n- CVE-2026-53291: ALSA: hda/conexant: Fix missing error check for jack detection (bsc#1269697).\n- CVE-2026-53309: ocfs2/dlm: fix off-by-one in dlm_match_regions() region comparison (bsc#1269815).\n- CVE-2026-53330: drm/amd/display: Fix out-of-bounds read in (bsc#1270090).\n- CVE-2026-53336: nvmem: layouts: onie-tlv: fix hang on unknown types (bsc#1270108).\n- CVE-2026-53337: net: bonding: fix NULL pointer dereference in bond_do_ioctl() (bsc#1270251).\n- CVE-2026-53341: fhandle: fix UAF due to unlocked -\u003emnt_ns read in may_decode_fh() (bsc#1270139).\n- CVE-2026-53353: hsr: Remove WARN_ONCE() in hsr_addr_is_self() (bsc#1270111).\n- CVE-2026-53365: vsock/virtio: fix zerocopy completion for multi-skb sends (bsc#1271365).\n- CVE-2026-63801: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (bsc#1272230).\n- CVE-2026-63803: hdlc_ppp: sync per-proto timers before freeing hdlc state (bsc#1272284).\n- CVE-2026-63804: gfs2: fix use-after-free in gfs2_qd_dealloc (bsc#1272287).\n- CVE-2026-63808: exfat: fix potential use-after-free in exfat_find_dir_entry() (bsc#1272260).\n- CVE-2026-63810: block: Avoid mounting the bdev pseudo-filesystem in userspace (bsc#1272297).\n- CVE-2026-63823: keys: Pin request_key_auth payload in instantiate paths (bsc#1272182).\n- CVE-2026-63828: apparmor: mediate the implicit connect of TCP fast open sendmsg (bsc#1272175).\n- CVE-2026-63860: RDMA/core: Prefer NLA_NUL_STRING (bsc#1272429).\n- CVE-2026-63865: bpf: Drop task_to_inode and inet_conn_established from lsm sleepable hooks (bsc#1272486).\n- CVE-2026-63868: net: garp: fix unsigned integer underflow in garp_pdu_parse_attr (bsc#1272497).\n- CVE-2026-63879: drm/amdgpu: fix amdgpu_hmm_range_get_pages (bsc#1272569).\n- CVE-2026-63887: scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf (bsc#1272385).\n- CVE-2026-63888: scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd() (bsc#1272390).\n- CVE-2026-63889: scsi: scsi_transport_fc: Widen FPIN pname walker counter to u32 (bsc#1272423).\n- CVE-2026-63890: scsi: fcoe: Reject FIP descriptors with zero fip_dlen in CVL walker (bsc#1272426).\n- CVE-2026-63891: thunderbolt: property: Cap recursion depth in __tb_property_parse_dir() (bsc#1272641).\n- CVE-2026-63901: USB: serial: digi_acceleport: fix memory corruption with small endpoints (bsc#1272501).\n- CVE-2026-63917: ip6: vti: Use ip6_tnl.net in vti6_changelink() (bsc#1272904).\n- CVE-2026-63918: l2tp: use refcount_inc_not_zero in l2tp_session_get_by_ifname (bsc#1272905).\n- CVE-2026-63920: ipv6: validate extension header length before copying to cmsg (bsc#1272877).\n- CVE-2026-63921: ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate() (bsc#1272918).\n- CVE-2026-63922,CVE-2026-63924: ipv6: exthdrs: refresh nh after handling HAO option (bsc#1272855).\n- CVE-2026-63925: macsec: fix replay protection at XPN lower-PN wrap (bsc#1273008).\n- CVE-2026-63926: bpf: sockmap: fix tail fragment offset in bpf_msg_push_data (bsc#1273019).\n- CVE-2026-63941: KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor (bsc#1272869).\n- CVE-2026-63969: ipv6: fix possible infinite loop in rt6_fill_node() (bsc#1272484).\n- CVE-2026-63970: vsock/virtio: bind uarg before filling zerocopy skb (bsc#1272673).\n- CVE-2026-63984: ipv6: rpl: fix hdrlen overflow in ipv6_rpl_srh_decompress() (bsc#1272865).\n- CVE-2026-63985: ethtool: eeprom: add more safeties to EEPROM Netlink fallback (bsc#1272963).\n- CVE-2026-63986: ethtool: tsinfo: don't pass ERR_PTR to genlmsg_cancel on prepare failure (bsc#1272969).\n- CVE-2026-63987: ethtool: coalesce: cap profile updates at NET_DIM_PARAMS_NUM_PROFILES (bsc#1272971).\n- CVE-2026-63990: bonding: refuse to enslave CAN devices (bsc#1273027).\n- CVE-2026-63992: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() (bsc#1272868).\n- CVE-2026-63993: vxlan: do not reuse cached ip_hdr() value after skb_tunnel_check_pmtu() (bsc#1279847).\n- CVE-2026-63995: ethtool: cmis: validate start_cmd_payload_size from module (bsc#1273033).\n- CVE-2026-63996: ethtool: cmis: require exact CDB reply length (bsc#1273032).\n- CVE-2026-63997: ethtool: module: avoid leaking a netdev ref on module flash errors (bsc#1273036).\n- CVE-2026-63998: ethtool: module: call ethnl_ops_complete() on module flash errors (bsc#1273037).\n- CVE-2026-63999: ethtool: rss: fix indir_table and hkey leak on get_rxfh failure (bsc#1273038).\n- CVE-2026-64000: net: hsr: fix potential OOB access in supervision frame handling (bsc#1273030).\n- CVE-2026-64002: ipv4: free net-\u003eipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table() (bsc#1273774).\n- CVE-2026-64003: scsi: core: Run queues for all non-SDEV_DEL devices from scsi_run_host_queues (bsc#1273782).\n- CVE-2026-64004: net/iucv: fix locking in .getsockopt (bsc#1273804).\n- CVE-2026-64005: net/smc: Do not re-initialize smc hashtables (bsc#1273831).\n- CVE-2026-64006: netfilter: nf_tables: fix dst corruption in same register operation (bsc#1273834).\n- CVE-2026-64007: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (bsc#1273105).\n- CVE-2026-64017: blk-mq: pop cached request if it is usable (bsc#1273770).\n- CVE-2026-64024: tcp: fix stale per-CPU tcp_tw_isn leak enabling ISN prediction (bsc#1273107).\n- CVE-2026-64033: RDMA/rtrs: Fix use-after-free in path file creation cleanup (bsc#1273134).\n- CVE-2026-64047: net: tls: fix off-by-one in sg_chain entry count for wrapped sk_msg ring (bsc#1273060).\n- CVE-2026-64048: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot (bsc#1273484).\n- CVE-2026-64052: block: bio-integrity: Fix null-ptr-deref in bio_integrity_map_user() (bsc#1272983).\n- CVE-2026-64053: block: don't overwrite bip_vcnt in bio_integrity_copy_user() (bsc#1272985).\n- CVE-2026-64054: net: shaper: reject duplicate leaves in GROUP request (bsc#1272894).\n- CVE-2026-64055: net: ethernet: cortina: Carry over frag counter (bsc#1272893).\n- CVE-2026-64056: net: ethernet: cortina: Make RX SKB per-port (bsc#1272502).\n- CVE-2026-64071: nvme-pci: fix use-after-free in nvme_free_host_mem() (bsc#1273486).\n- CVE-2026-64073: irq_work: Fix use-after-free in irq_work_single() on PREEMPT_RT (bsc#1273490).\n- CVE-2026-64088: batman-adv: tt: fix negative tt_buff_len (bsc#1273463).\n- CVE-2026-64089: batman-adv: tt: fix negative last_changeset_len (bsc#1272513).\n- CVE-2026-64093: batman-adv: tp_meter: directly shut down timer on cleanup (bsc#1273461).\n- CVE-2026-64099: drm/v3d: Fix use-after-free of CPU job query arrays on error path (bsc#1273465).\n- CVE-2026-64102: RDMA/siw: Reject MPA FPDU length underflow before signed receive math (bsc#1272516).\n- CVE-2026-64103: scsi: isci: Fix use-after-free in device removal path (bsc#1273759).\n- CVE-2026-64109: af_unix: Fix UAF read of tail-\u003elen in unix_stream_data_wait() (bsc#1273748).\n- CVE-2026-64111: lsm: hold cred_guard_mutex for lsm_set_self_attr() (bsc#1273740).\n- CVE-2026-64112: rbd: eliminate a race in lock_dwork draining on unmap (bsc#1273741).\n- CVE-2026-64113: ixgbevf: fix use-after-free in VEPA multicast source pruning (bsc#1272262).\n- CVE-2026-64114: ipv4: raw: reject IP_HDRINCL packets with ihl \u003c 5 (bsc#1273742).\n- CVE-2026-64115: vsock/vmci: fix UAF when peer resets connection during handshake (bsc#1273745).\n- CVE-2026-64118: qed: fix double free in qed_cxt_tables_alloc() (bsc#1273749).\n- CVE-2026-64119: l2tp: use list_del_rcu in l2tp_session_unhash (bsc#1273746).\n- CVE-2026-64121: net: ifb: report ethtool stats over num_tx_queues (bsc#1273743).\n- CVE-2026-64125: net: bcmgenet: keep RBUF EEE/PM disabled (bsc#1272346).\n- CVE-2026-64131: mm/memory: fix spurious warning when unmapping device-private/exclusive pages (bsc#1274063).\n- CVE-2026-64146: erofs: fix metabuf leak in inode xattr initialization (bsc#1273681).\n- CVE-2026-64147: pds_core: fix debugfs_lookup dentry leak and error handling (bsc#1273119).\n- CVE-2026-64148: pds_core: fix error handling in pdsc_devcmd_wait (bsc#1273956).\n- CVE-2026-64162: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (bsc#1272366).\n- CVE-2026-64164: btrfs: tracepoints: fix sleep while in atomic context in btrfs_sync_file() (bsc#1273957).\n- CVE-2026-64177: phonet/pep: disable BH around forwarded sk_receive_skb() (bsc#1272148).\n- CVE-2026-64179: net: wwan: iosm: fix potential memory leaks in ipc_imem_init() (bsc#1272149).\n- CVE-2026-64180: mm/memory_hotplug: fix memory block reference leak on remove (bsc#1273679).\n- CVE-2026-64184: mm/damon/sysfs-schemes: call missing mem_cgroup_iter_break() (bsc#1272199).\n- CVE-2026-64185: sysfs: don't remove existing directory on update failure (bsc#1272200).\n- CVE-2026-64190: net: team: fix NULL pointer dereference in team_xmit during mode change (bsc#1272210).\n- CVE-2026-64192: bpf: Reject BPF_MAP_TYPE_INODE_STORAGE creation if BPF LSM is uninitialized (bsc#1272213).\n- CVE-2026-64210: net/mlx5e: xsk: Fix unlocked writing to ICOSQ (bsc#1273899).\n- CVE-2026-64214: powerpc/time: Remove redundant preempt_disable|enable() calls from arch_irq_work_raise()\n  (bsc#1272799).\n- CVE-2026-64217: netfs: Fix overrun check in netfs_extract_user_iter() (bsc#1272798).\n- CVE-2026-64222: octeontx2-pf: avoid double free of pool-\u003estack on AQ init failure (bsc#1272788).\n- CVE-2026-64224: octeontx2-pf: fix double free in rvu_rep_rsrc_init() (bsc#1272804).\n- CVE-2026-64225: octeontx2-af: CGX: add bounds check to cgx_speed_mbps index (bsc#1272786).\n- CVE-2026-64232: block: recompute nr_integrity_segments in blk_insert_cloned_request (bsc#1272791).\n- CVE-2026-64239: mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() (bsc#1273898).\n- CVE-2026-64244: drivers/base/memory: set mem-\u003ealtmap after successful device registration (bsc#1273812).\n- CVE-2026-64253: kernel/fork: clear PF_BLOCK_TS in copy_process() (bsc#1273904).\n- CVE-2026-64256: xfs: don't wrap around quota ids in dqiterate (bsc#1273271).\n- CVE-2026-64265: fuse: clear intr_entry in fuse_resend and fuse_remove_pending_req (bsc#1273947).\n- CVE-2026-64268: RDMA/siw: bound Read Response placement to the RREAD length (bsc#1273276).\n- CVE-2026-64269: RDMA/rtrs-srv: Bound RDMA-Write length to chunk size in rdma_write_sg (bsc#1273280).\n- CVE-2026-64283: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values (bsc#1273870).\n- CVE-2026-64286: KVM: arm64: Clear __hyp_running_vcpu when flushing the pKVM hyp vCPU (bsc#1274058).\n- CVE-2026-64287: KVM: arm64: Bound used_lrs when flushing the pKVM hyp vCPU (bsc#1273325).\n- CVE-2026-64294: mm: do file ownership checks with the proper mount idmap (bsc#1273525).\n- CVE-2026-64296: exfat: bound uniname advance in exfat_find_dir_entry() (bsc#1273975).\n- CVE-2026-64298: NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (bsc#1273550).\n- CVE-2026-64300: perf/aux: Fix page UAF in map_range() (bsc#1273852).\n- CVE-2026-64307: crypto: ccp - Do not initialize SNP for ioctl(SNP_CONFIG) (bsc#1273567).\n- CVE-2026-64315: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1274028).\n- CVE-2026-64316: crypto: caam - use print_hex_dump_devel to guard key hex dumps (bsc#1273598).\n- CVE-2026-64317: isofs: bound Rock Ridge symlink components to the SL record (bsc#1273936).\n- CVE-2026-64319: nvmet-auth: validate reply message payload bounds against transfer length (bsc#1273339).\n- CVE-2026-64320: nvmet: fix pre-auth out-of-bounds heap read in Discovery Get Log Page (bsc#1273420).\n- CVE-2026-64321: nvme: target: rdma: fix ndev refcount leak on queue connect (bsc#1273864).\n- CVE-2026-64322: udf: validate sparing table length as an entry count, not a byte count (bsc#1273958).\n- CVE-2026-64323: udf: validate VAT header length against the VAT inode size (bsc#1273305).\n- CVE-2026-64326: block: skip sync_blockdev() on surprise removal in bdev_mark_dead() (bsc#1273312).\n- CVE-2026-64327: usb: gadget: f_fs: Initialize epfile-\u003ein early to fix endpoint direction checks (bsc#1273283).\n- CVE-2026-64354: bpf: Validate BTF repeated field counts before expansion (bsc#1274060).\n- CVE-2026-64355: bpf: Reject fragmented frames in devmap (bsc#1273422).\n- CVE-2026-64364: HID: multitouch: fix out-of-bounds bit access on mt_io_flags (bsc#1273495).\n- CVE-2026-64368: mm/slab: do not limit zeroing to orig_size when only red zoning is enabled (bsc#1273997).\n- CVE-2026-64373: cpufreq: Fix hotplug-suspend race during reboot (bsc#1273776).\n- CVE-2026-64375: proc: protect ptrace_may_access() with exec_update_lock (FD links) (bsc#1273868).\n- CVE-2026-64378: writeback: fix race between cgroup_writeback_umount() and inode_switch_wbs() (bsc#1273603).\n- CVE-2026-64381: smb: client: Fix next buffer leak in receive_encrypted_standard() (bsc#1273860).\n- CVE-2026-64382: smb: client: fix double-free in SMB2_open() replay (bsc#1273291).\n- CVE-2026-64383: smb: client: fix double-free in SMB2_flush() replay (bsc#1273426).\n- CVE-2026-64384: smb: client: fix change notify replay double-free (bsc#1274541).\n- CVE-2026-64385: smb: client: fix double-free in SMB2_ioctl() replay (bsc#1274539).\n- CVE-2026-64386: smb: client: fix query_info() replay double-free (bsc#1274543).\n- CVE-2026-64387: smb: client: fix query directory replay double-free (bsc#1274545).\n- CVE-2026-64411: netfilter: ebtables: terminate table name before find_table_lock() (bsc#1274077).\n- CVE-2026-64412: netfilter: ebtables: module names must be null-terminated (bsc#1273780).\n- CVE-2026-64415: mm/swap: add cond_resched() in swap_reclaim_full_clusters to prevent softlockup (bsc#1273317).\n- CVE-2026-64416: mm: swap_cgroup: fix NULL deref in lookup_swap_cgroup_id on swapless host (bsc#1273286).\n- CVE-2026-64423: ipv4: igmp: remove multicast group from hash table on device destruction (bsc#1274274).\n- CVE-2026-64434: Bluetooth: L2CAP: Fix UAF in channel timeout by holding conn ref (bsc#1273880).\n- CVE-2026-64436: net: af_key: initialize alg_key_len for IPComp states (bsc#1274277).\n- CVE-2026-64450: tipc: fix out-of-bounds read in broadcast Gap ACK blocks (bsc#1273523).\n- CVE-2026-64452: 6lowpan: fix NHC entry use-after-free on error path (bsc#1273460).\n- CVE-2026-64458: mm/damon/ops-common: handle extreme intervals in damon_hot_score() (bsc#1273788).\n- CVE-2026-64463: usb: typec: tcpci_rt1711h: unregister TCPCI port with devres (bsc#1273273).\n- CVE-2026-64472: vfio/mlx5: Fix racy bitfields and tighten struct layout (bsc#1274075).\n- CVE-2026-64477: x86,fs/resctrl: Prevent out-of-bounds access while offlining CPU when SNC enabled (bsc#1274264).\n- CVE-2026-64507: bpf: Support for hardening against JIT spraying (bsc#1273999).\n- CVE-2026-64518: tcp: Fix out-of-bounds access for twsk in tcp_ao_established_key() (bsc#1273524).\n- CVE-2026-64519: NFSD: Fix infinite loop in layout state revocation (bsc#1274252).\n- CVE-2026-64526: ethtool: tsconfig: fix missing ethnl_ops_complete() (bsc#1274052).\n- CVE-2026-64534: nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error (bsc#1273803).\n- CVE-2026-64535: nvmet-tcp: Fix potential UAF when ddgst mismatch (bsc#1273809).\n- CVE-2026-64537: bridge: cfm: reject invalid CCM interval at configuration time (bsc#1273289).\n- CVE-2026-64538: ipv6: Fix null-ptr-deref in fib6_nh_mtu_change() (bsc#1273335).\n- CVE-2026-64541: net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket (bsc#1273303).\n- CVE-2026-64542: ipv6: ndisc: fix NULL deref in accept_untracked_na() (bsc#1273309).\n- CVE-2026-64543: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() (bsc#1273311).\n- CVE-2026-64545: net, bpf: check master for NULL in xdp_master_redirect() (bsc#1273318).\n- CVE-2026-64548: bpf, sockmap: reject overflowing copy + len in bpf_msg_push_data() (bsc#1273337).\n- CVE-2026-64551: sctp: validate STALE_COOKIE cause length before reading staleness (bsc#1273813).\n- CVE-2026-64552: virtio-net: fix len check in receive_big() (bsc#1273323).\n- CVE-2026-64553: net: psample: fix info leak in PSAMPLE_ATTR_DATA (bsc#1273336).\n- CVE-2026-64554: netfilter: bridge: fix stale prevhdr pointer in br_ip6_fragment() (bsc#1273340).\n- CVE-2026-64555: KVM: arm64: nv: Fix SPSR_EL2 restore in kvm_hyp_handle_mops() (bsc#1273331).\n- CVE-2026-64556: perf/core: Detach event groups during remove_on_exec (bsc#1273251).\n- CVE-2026-64563: rhashtable: clear stale iter-\u003ep on table restart (bsc#1273995).\n- CVE-2026-64567: btrfs: reject free space cache with more entries than pages (bsc#1274006).\n- CVE-2026-64569: mpls: fix NULL deref in mpls_valid_fib_dump_req() on CONFIG_INET=n (bsc#1274009).\n- CVE-2026-64572: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (bsc#1274014).\n- CVE-2026-64576: nexthop: initialize extack in nh_res_bucket_migrate() (bsc#1274030).\n- CVE-2026-64577: gtp: check skb_pull_data() return in gtp1u_send_echo_resp() (bsc#1274031).\n- CVE-2026-64579: xfrm: policy: preallocate inexact bins before xfrm_hash_rebuild reinsert (bsc#1274036).\n- CVE-2026-64581: xfrm: fix sk_dst_cache double-free in xfrm_user_policy() (bsc#1274041).\n- CVE-2026-64582: RDMA/rxe: Fix a use-after-free problem in rxe_mmap (bsc#1274040).\n- CVE-2026-64586: wifi: brcmfmac: drain bus_reset work on device removal (bsc#1274492).\n- CVE-2026-68082: libceph: fix two unsafe bare decodes in decode_lockers() (bsc#1274581).\n- CVE-2026-68086: mm/khugepaged: write all dirty file folios when collapsing (bsc#1274713).\n- CVE-2026-68096: audit: fix recursive locking deadlock in audit_dupe_exe() (bsc#1274730).\n- CVE-2026-68105: drm/amdgpu: Fix kernel panic during driver load failure (bsc#1274849).\n- CVE-2026-68116: vxlan: mdb: Fix source list corruption on a failed replace (bsc#1274876).\n- CVE-2026-68117: tipc: clear sock-\u003esk on the failed-insert path in tipc_sk_create() (bsc#1274881).\n- CVE-2026-68120: rtase: Workaround for TX hang caused by hardware packet parsing (bsc#1274887).\n- CVE-2026-68121: pppoe: reload header pointer after dev_hard_header() (bsc#1274888).\n- CVE-2026-68123: openvswitch: fix GSO userspace truncation underflow (bsc#1275169).\n- CVE-2026-68124: mctp: serial: handle zero-length frames to prevent rx buffer overflow (bsc#1275192).\n- CVE-2026-68127: ila: reload IPv6 header after pskb_may_pull in checksum adjust (bsc#1275237).\n- CVE-2026-68128: ice: reject out-of-range ptype in ice_parser_profile_init (bsc#1275238).\n- CVE-2026-68129: gve: fix Rx queue stall on alloc failure (bsc#1275517).\n- CVE-2026-68132: super: fix emergency thaw deadlock on frozen block devices (bsc#1275553).\n- CVE-2026-68133: ice: fix PTP Call Trace during PTP release (bsc#1275555).\n- CVE-2026-68135: net: hip04: fix RX buffer leak on build_skb failure (bsc#1275557).\n- CVE-2026-68136: net: gro: fix double aggregation of flush-marked skbs (bsc#1275474).\n- CVE-2026-68138: net/sched: serialize qdisc_rtab_list against concurrent get/put (bsc#1274941).\n- CVE-2026-68139: net/mlx5e: Use sender devcom for MPV master-up (bsc#1275578).\n- CVE-2026-68141: net/af_iucv: fix NULL deref in afiucv_hs_callback_syn() (bsc#1275094).\n- CVE-2026-68142: geneve: require CAP_NET_ADMIN in the device netns for changelink (bsc#1275582).\n- CVE-2026-68143: net: slip: serialize receive against buffer reallocation (bsc#1275583).\n- CVE-2026-68144: phonet: pep: fix use-after-free in pep_get_sb() (bsc#1275481).\n- CVE-2026-68145: iomap: fix out-of-bounds bitmap_set() with zero-length range (bsc#1275584).\n- CVE-2026-68148: fscrypt: Add missing superblock check in find_or_insert_direct_key() (bsc#1275588).\n- CVE-2026-68149: fs: preserve ACL_DONT_CACHE state in forget_cached_acl() (bsc#1275294).\n- CVE-2026-68152: amt: fix use-after-free in AMT delayed works (bsc#1275300).\n- CVE-2026-68153: libceph: remove debugfs files before client teardown (bsc#1275301).\n- CVE-2026-68154: libceph: reject zero bucket types in crush_decode (bsc#1275303).\n- CVE-2026-68155: libceph: Reject monmaps advertising zero monitors (bsc#1275304).\n- CVE-2026-68156: libceph: refresh auth-\u003eauthorizer_buf{,_len} after authorizer update (bsc#1275305).\n- CVE-2026-68157: libceph: guard missing CRUSH type name lookup (bsc#1275306).\n- CVE-2026-68158: libceph: Fix multiplication overflow in decode_new_up_state_weight() (bsc#1275307).\n- CVE-2026-68159: libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE (bsc#1275470).\n- CVE-2026-68161: sctp: close UDP tunnel sockets during netns teardown (bsc#1274892).\n- CVE-2026-68164: mm/damon/core: disallow overlapping input ranges for damon_set_regions() (bsc#1274955).\n- CVE-2026-68165: mm/damon/core: validate ranges in damon_set_regions() (bsc#1274927).\n- CVE-2026-68166: userfaultfd: prevent registration of special VMAs (bsc#1274930).\n- CVE-2026-68169: mptcp: pm: userspace: fix use-after-free in get_local_id (bsc#1274952).\n- CVE-2026-68183: firmware: stratix10-svc: fix memory leaks and list corruption bugs (bsc#1274957).\n- CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state() (bsc#1274803).\n- CVE-2026-68205: media: v4l2-fwnode: Fix subdev owner overwritten in v4l2_async_register_subdev_sensor() (bsc#1274934).\n- CVE-2026-68238: drm/amdgpu: Release VFCT ACPI table reference (bsc#1275704).\n- CVE-2026-68258: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size (bsc#1275866).\n- CVE-2026-68267: drm/xe/rtp: Add RING_FORCE_TO_NONPRIV_DENY to OA whitelists (bsc#1275139).\n- CVE-2026-68273: drm/amdgpu: Fix context pstate override handling (bsc#1275129).\n- CVE-2026-68284: bpf, sockmap: Fix cork use-after-free in tcp_bpf_sendmsg() (bsc#1275970).\n- CVE-2026-68286: drop_monitor: perform u64_stats updates under IRQ-disabled section (bsc#1275973).\n- CVE-2026-68288: net: drop_monitor: fix info leak in NET_DM_ATTR_PAYLOAD (bsc#1275975).\n- CVE-2026-68289: tipc: fix integer overflow in tipc_recvmsg() and tipc_recvstream() (bsc#1275976).\n- CVE-2026-68293: net/mlx5: Fix MCIA register buffer overflow on 32 dword reads (bsc#1275091).\n- CVE-2026-68294: net: qrtr: restrict socket creation to the initial network namespace (bsc#1275092).\n- CVE-2026-68296: net: gre: fix lltx regression for GRE tunnels with SEQ/CSUM (bsc#1275045).\n- CVE-2026-68297: tipc: fix u16 MTU truncation in media and bearer MTU validation (bsc#1275040).\n- CVE-2026-68299: vmxnet3: fix BUG_ON in vmxnet3_get_hdr_len() for Geneve packets (bsc#1275088).\n- CVE-2026-68300: sctp: auth: verify auth requirement when auth_chunk is NULL (bsc#1275083).\n- CVE-2026-68302: amt: re-read skb header pointers after every pull (bsc#1275081).\n- CVE-2026-68313: tipc: fix infinite loop in __tipc_nl_compat_dumpit (bsc#1274665).\n- CVE-2026-68315: sctp: validate stream count in sctp_process_strreset_inreq() (bsc#1274662).\n- CVE-2026-68319: pds_core: fix deadlock between reset thread and remove (bsc#1274657).\n- CVE-2026-68320: sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid (bsc#1274659).\n- CVE-2026-68321: net: txgbe: fix FDIR filter leak on remove (bsc#1274652).\n- CVE-2026-68322: rds: Fix inet6_addr_lst NULL dereference when IPv6 is disabled (bsc#1274656).\n- CVE-2026-68325: iommu/amd: Bound the early ACPI HID map (bsc#1274651).\n- CVE-2026-68328: nfp: Check resource mutex allocation (bsc#1274646).\n- CVE-2026-68329: iommu/amd: Wait for completion instead of returning early in iommu_completion_wait() (bsc#1274645).\n- CVE-2026-68331: dpaa2-eth: put MAC endpoint device on disconnect (bsc#1274642).\n- CVE-2026-68333: dpaa2-switch: put MAC endpoint device on disconnect (bsc#1274644).\n- CVE-2026-68335: rds: drop incoming messages that cross network namespace boundaries (bsc#1274640).\n- CVE-2026-68336: bonding: fix devconf_all NULL dereference when IPv6 is disabled (bsc#1274639).\n- CVE-2026-68338: net/packet: avoid fanout hook re-registration after unregister (bsc#1274637).\n- CVE-2026-68375: bnxt_en: Handle partially initialized auxiliary devices (bsc#1274835).\n- CVE-2026-68377: net/sched: act_tunnel_key: Defer dst_release to RCU callback (bsc#1274831).\n- CVE-2026-68386: bpf, sockmap: Reject unhashed UDP sockets on sockmap update (bsc#1274814).\n- CVE-2026-68393: Bluetooth: hci_sync: extend conn_hash lookup critical sections (bsc#1274904).\n- CVE-2026-68395: ata: sata_dwc_460ex: enable SATA interrupts only after IRQ handler is registered (bsc#1274900).\n- CVE-2026-68397: net/iucv: take a reference on the socket found in afiucv_hs_rcv() (bsc#1274898).\n- CVE-2026-68398: ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF (bsc#1274908).\n- CVE-2026-68399: bpf: Fix UAF in sock clone early bailouts (bsc#1274897).\n- CVE-2026-68408: wifi: cfg80211: convert pmsr_free_wk to wiphy_work to fix deadlock (bsc#1274709).\n- CVE-2026-68417: RDMA/siw: publish QP after initialization (bsc#1274696).\n- CVE-2026-68418: RDMA/irdma: Prevent user-triggered null deref on QP create (bsc#1274690).\n- CVE-2026-68419: RDMA/irdma: Prevent rereg_mr for non-mem regions (bsc#1274698).\n- CVE-2026-68422: btrfs: fix root leak if its reloc root is unexpected in merge_reloc_roots() (bsc#1274706).\n- CVE-2026-68425: IB/mad: Drop unmatched RMPP responses before reassembly (bsc#1274700).\n- CVE-2026-68426: xfrm: fix stale skb-\u003eprev after async crypto steals a GSO segment (bsc#1274705).\n- CVE-2026-68432: vxlan: require CAP_NET_ADMIN in the device netns for changelink (bsc#1274800).\n- CVE-2026-68433: libceph: bound get_version reply decode to front len (bsc#1274801).\n- CVE-2026-68442: btrfs: don't propagate EXTENT_FLAG_LOGGING to split extent maps (bsc#1274773).\n- CVE-2026-68448: ovl: check access to copy_file_range source with src mounter creds (bsc#1274838).\n- CVE-2026-68450: btrfs: free mapping node on duplicate reloc root insert (bsc#1274834).\n- CVE-2026-68470: wifi: mac80211: validate extension-frame layout before RX (bsc#1276500).\n- CVE-2026-68480: x86/bugs: Make Safe-RET robust against interrupt injection (bsc#1274208).\n- CVE-2026-72017: net: macb: drop in-flight Tx SKBs on close (bsc#1276840).\n- CVE-2026-72019: macsec: don't read an unset MAC header in macsec_encrypt() (bsc#1276865).\n- CVE-2026-72020: ipvs: reset full ip_vs_seq structs in ip_vs_conn_new (bsc#1275506).\n- CVE-2026-72022: llc: fix SAP refcount leak in llc_ui_autobind() (bsc#1276785).\n- CVE-2026-72023: octeontx2-pf: fix SQB pointer leak on init failure (bsc#1276793).\n- CVE-2026-72032: net/mlx5: HWS, fix matcher leak on resize target setup failure (bsc#1276955).\n- CVE-2026-72034: fhandle: reject detached mounts in capable_wrt_mount() (bsc#1276957).\n- CVE-2026-72035: net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1276961).\n- CVE-2026-72036: net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked (bsc#1277034).\n- CVE-2026-72045: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF (bsc#1277078).\n- CVE-2026-72046: gve: fix header buffer corruption with header-split and HW-GRO (bsc#1275519).\n- CVE-2026-72051: net: ip6_tunnel: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276801).\n- CVE-2026-72052: net: ip6_gre: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276803).\n- CVE-2026-72053: net: ipip: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276814).\n- CVE-2026-72054: net: ip_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276818).\n- CVE-2026-72055: net: ip6_vti: require CAP_NET_ADMIN in the device netns for changelink (bsc#1276821).\n- CVE-2026-72061: net: sit: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277249).\n- CVE-2026-72069: locking/rt: Fix the incorrect RCU protection in rt_spin_unlock() (bsc#1275528).\n- CVE-2026-72072: net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete (bsc#1277155).\n- CVE-2026-72083: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE (bsc#1275535).\n- CVE-2026-72084: scsi: target: core: Generate correct identifiers for PR OUT transport IDs (bsc#1275540).\n- CVE-2026-72100: dm-integrity: fix a bug if the bio is out of limits (bsc#1277311).\n- CVE-2026-72101: dm-integrity: fix leaking uninitialized kernel memory (bsc#1276831).\n- CVE-2026-72103: dm: avoid leaking the caller's thread keyring via the table device file (bsc#1277315).\n- CVE-2026-72106: dm-ioctl: fix a possible overflow in list_version_get_info (bsc#1277321).\n- CVE-2026-72107: dm era: fix out-of-bounds memory access for non-zero start sector (bsc#1277349).\n- CVE-2026-72108: dm thin metadata: fix metadata snapshot consistency on commit failure (bsc#1277350).\n- CVE-2026-72132: NFS: Charge unstable writes by request size, not folio size (bsc#1277551).\n- CVE-2026-72136: xfrm: xfrm_interface: require CAP_NET_ADMIN in the device netns for changelink (bsc#1277574).\n- CVE-2026-72137: xfrm: nat_keepalive: avoid double free on send error (bsc#1275587).\n- CVE-2026-72161: ocfs2: add journal NULL check in ocfs2_checkpoint_inode() (bsc#1277233).\n- CVE-2026-72163: ocfs2: fix NULL h_transaction deref in ocfs2_assure_trans_credits (bsc#1277231).\n- CVE-2026-72164: ocfs2: avoid moving extents to occupied clusters (bsc#1277553).\n- CVE-2026-72176: mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error (bsc#1277230).\n- CVE-2026-72177: mm/damon/sysfs-schemes: fix dir put orders in access_pattern_add_dirs() (bsc#1277227).\n- CVE-2026-72217: SUNRPC: Bound-check xdr_buf_to_bvec() stores before writing (bsc#1275655).\n- CVE-2026-72221: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (bsc#1275665).\n- CVE-2026-72222: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (bsc#1275669).\n- CVE-2026-72234: batman-adv: access unicast_ttvn skb-\u003edata only after skb realloc (bsc#1275672).\n- CVE-2026-72242: selinux: avoid sk_socket dereference in selinux_sctp_bind_connect() (bsc#1277655).\n- CVE-2026-72243: selinux: check connect-related permissions on TCP Fast Open (bsc#1277656).\n- CVE-2026-72251: netfilter: nf_nat_sip: reload possible stale data pointer (bsc#1275827).\n- CVE-2026-72254: netfilter: nft_fib: reject fib expression on the netdev egress hook (bsc#1277204).\n- CVE-2026-72280: KVM: arm64: nv: Drop bogus WARN for write to ZCR_EL2 (bsc#1277726).\n- CVE-2026-72282: KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers (bsc#1277728).\n- CVE-2026-72288: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling (bsc#1275886).\n- CVE-2026-72289: KVM: arm64: vgic: Check the interrupt is still ours before migrating it (bsc#1275905).\n- CVE-2026-72296: net: ife: require ETH_HLEN to be pullable in ife_decode() (bsc#1275923).\n- CVE-2026-72297: net: atm: reject out-of-range traffic classes in QoS validation (bsc#1277738).\n- CVE-2026-72306: vduse: Requeue failed read to send_list head (bsc#1277748).\n- CVE-2026-72307: mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace() (bsc#1277160).\n- CVE-2026-72308: mlxsw: fix refcount leak in mlxsw_sp_port_lag_join() (bsc#1277159).\n- CVE-2026-72317: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (bsc#1275925).\n- CVE-2026-72323: ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() (bsc#1275985).\n- CVE-2026-72325: perf/x86/amd/core: Avoid enabling BRS from the SVM reload path (bsc#1277761).\n- CVE-2026-72330: net/tls: Consume empty data records in tls_sw_read_sock() (bsc#1277764).\n- CVE-2026-72337: Bluetooth: 6lowpan: avoid untracked enable work (bsc#1277773).\n- CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).\n- CVE-2026-72341: net/mlx5e: Fix publication race for priv-\u003echannel_stats[] (bsc#1277660).\n- CVE-2026-72342: net/mlx5e: Fix HV VHCA stats agent registration race (bsc#1277775).\n- CVE-2026-72343: net/mlx5e: Fix HV VHCA stats zero-sized buffer allocation (bsc#1277776).\n- CVE-2026-72345: net/mlx5: LAG, Fix off-by-one in single-FDB error rollback (bsc#1277782).\n- CVE-2026-72347: netfilter: xt_connmark: reject invalid shift parameters (bsc#1277783).\n- CVE-2026-72350: netfilter: xt_u32: reject invalid shift counts (bsc#1277822).\n- CVE-2026-72366: netfs: Fix netfs_create_write_req() to handle async cache object creation (bsc#1276333).\n- CVE-2026-72379: fs: refuse O_TMPFILE creation with an unmapped fsuid or fsgid (bsc#1277818).\n- CVE-2026-72389: bridge: stp: Fix a potential use-after-free when deleting a bridge (bsc#1273869).\n- CVE-2026-72398: sctp: add INIT verification after cookie unpacking (bsc#1276381).\n- CVE-2026-72399: net: enetc: check the number of BDs needed for xdp_frame (bsc#1276553).\n- CVE-2026-72414: net: dsa: sja1105: round up PTP perout pin duration (bsc#1278039).\n- CVE-2026-72421: ipv4: fib: Don't ignore error route in local/main tables (bsc#1277023).\n- CVE-2026-72425: ice: fix FDIR CTRL VSI resource leak in ice_reset_all_vfs() (bsc#1277120).\n- CVE-2026-72430: net/sched: act_ct: fix nf_connlabels leak on two error paths (bsc#1277118).\n- CVE-2026-72437: md/raid1: free r1_bio when REQ_NOWAIT is set and read would block on retry (bsc#1277874).\n- CVE-2026-72438: md/raid10: fix writes_pending and barrier reference leaks on discard failures (bsc#1277115).\n- CVE-2026-72439: md/raid10: fix writes_pending leak on write request failures (bsc#1277876).\n- CVE-2026-72440: md/raid1: fix writes_pending and barrier reference leaks on write failures (bsc#1277114).\n- CVE-2026-72448: octeontx2-pf: Fix leak of SQ timestamp buffer on teardown (bsc#1277108).\n- CVE-2026-72450: xfrm: validate selector family and prefixlen during match (bsc#1278113).\n- CVE-2026-72459: apparmor: aa_label_alloc use aa_label_free on alloc failure (bsc#1277092).\n- CVE-2026-72460: apparmor: check label build before no_new_privs test (bsc#1277229).\n- CVE-2026-72464: xprtrdma: Post receive buffers after RPC completion (bsc#1277069).\n- CVE-2026-72466: xprtrdma: Fix bcall rep leak and unbounded peek (bsc#1277057).\n- CVE-2026-72467: xprtrdma: Check frwr_wp_create() during connect (bsc#1277059).\n- CVE-2026-72468: xprtrdma: Initialize re_id before removal registration (bsc#1277062).\n- CVE-2026-72469: xprtrdma: Fix ep kref imbalance on ADDR_CHANGE (bsc#1277047).\n- CVE-2026-72473: xprtrdma: Avoid 250 ms delay on backlog wakeup (bsc#1277037).\n- CVE-2026-72485: coresight: platform: defer connection counter increment until alloc succeeds (bsc#1276771).\n- CVE-2026-72487: PCI: Introduce named defines for PCI ROM (bsc#1276767).\n- CVE-2026-72488: soundwire: fix bug in sdw_add_element_group_count found by syzkaller (bsc#1276766).\n- CVE-2026-72494: RDMA/irdma: Replace waitqueue and flag with completion (bsc#1276941).\n- CVE-2026-72495: RDMA/bnxt_re: Avoid repeated requests to allocate WC pages (bsc#1276937).\n- CVE-2026-72497: RDMA/bnxt_re: Add a max slot check for SQ (bsc#1276913).\n- CVE-2026-72499: RDMA/bnxt_re: Free CQ toggle page after firmware teardown (bsc#1276551).\n- CVE-2026-72500: RDMA/bnxt_re: Free SRQ toggle page after firmware teardown (bsc#1276552).\n- CVE-2026-72501: RDMA/bnxt_re: Initialize dpi variable to zero (bsc#1276546).\n- CVE-2026-72502: tcp: ipv6: clamp default adverting MSS to avoid GSO_BY_FRAGS (0xFFFF) (bsc#1276542).\n- CVE-2026-74255: tipc: fix UAF in tipc_l2_send_msg() (bsc#1276547).\n- CVE-2026-74261: ALSA: seq: avoid stale FIFO cells during resize (bsc#1276528).\n- CVE-2026-74269: bnxt: fix head underflow on XDP head-grow (bsc#1276507).\n- CVE-2026-74270: handshake: Require admin permission for DONE command (bsc#1276512).\n- CVE-2026-74282: tipc: prevent snt_unacked underflow on CONN_ACK (bsc#1276473).\n- CVE-2026-74284: net/sched: sch_hfsc: Don't make class passive twice (bsc#1276468).\n- CVE-2026-74286: net: pfcp: allocate per-cpu tstats for PFCP netdevs (bsc#1276471).\n- CVE-2026-74296: RDMA/mlx5: Release the HW-provided UAR index rather than the SW one (bsc#1276452).\n- CVE-2026-74297: RDMA/mlx5: Fix undefined shift of user RQ WQE size (bsc#1276446).\n- CVE-2026-74307: ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT (bsc#1276905).\n- CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end (bsc#1276880).\n- CVE-2026-74313: vduse: hold vduse_lock across IDR lookup in open path (bsc#1276876).\n- CVE-2026-74316: NFSD: Handle layout stid in nfsd4_drop_revoked_stid() (bsc#1276870).\n- CVE-2026-74317: ixgbe: do not configure xps for XDP queues (bsc#1276866).\n- CVE-2026-74318: btrfs: fix deadlock cloning inline extent when using flushoncommit (bsc#1276864).\n- CVE-2026-74321: btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() (bsc#1277202).\n- CVE-2026-74334: RDMA/nldev: Fix locking when accessing mr-\u003epd (bsc#1277095).\n- CVE-2026-74345: RDMA/siw: Fix endpoint/socket association handling (bsc#1277285).\n- CVE-2026-74346: RDMA/irdma: Fix OOB read during CQ MR registration (bsc#1278155).\n- CVE-2026-74349: ocfs2: reject FITRIM ranges shorter than a cluster (bsc#1278180).\n- CVE-2026-74363: bpf: fix UAF by restoring RCU-delayed inode freeing in bpffs (bsc#1278070).\n- CVE-2026-74375: md: replace wait loop with wait_event() in md_handle_request() (bsc#1277649).\n- CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).\n- CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).\n- CVE-2026-74382: net/sched: cls_bpf: prevent unbounded recursion in offload rollback (bsc#1278240).\n- CVE-2026-74388: ALSA: seq: oss: Fix UAF at handling events with embedded SysEx data (bsc#1278253).\n- CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).\n- CVE-2026-74394: RDMA/srpt: fix integer overflow in immediate data length check (bsc#1277408).\n- CVE-2026-74395: RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference (bsc#1277077).\n- CVE-2026-74397: IB/mlx5: Fix transport-domain rollback and initialize lb mutex earlier (bsc#1278098).\n- CVE-2026-74406: vxlan: Fix potential null-ptr-deref in vxlan_gro_prepare_receive() (bsc#1276395).\n- CVE-2026-74464: net: openvswitch: fix skb leak on flow key update failure during ct (bsc#1277070).\n- CVE-2026-74474: vxlan: use pskb_network_may_pull() for transmit path header pulls (bsc#1276335).\n- CVE-2026-74475: vxlan: unclone skb head before modifying eth header in route_shortcircuit() (bsc#1276339).\n- CVE-2026-74476: veth: convert frag_list skbs before running XDP (bsc#1276341).\n- CVE-2026-74479: net: pktgen: fix proc entry use-after-free (bsc#1276354).\n- CVE-2026-74481: mm/page_reporting: use system_freezable_wq to fix UAF during suspend (bsc#1276355).\n- CVE-2026-74482: mm/huge_memory: unlock i_mmap_rwsem before releasing after-split folios (bsc#1276346).\n- CVE-2026-74495: igbvf: Fix leak in TX DMA error cleanup (bsc#1275864).\n- CVE-2026-74496: fou: Fix use-after-free in fou_create() (bsc#1275867).\n- CVE-2026-74510: Bluetooth: mgmt: fix UAF in pair command cancellation (bsc#1275950).\n- CVE-2026-74512: audit: fix potential use-after-free in audit_del_rule() (bsc#1275954).\n- CVE-2026-74513: dibs: fix use-after-free of dmb_node in loopback attach/detach/unregister (bsc#1275956).\n- CVE-2026-74517: KVM: x86: Cancel delayed I/O APIC EOI handling before destroying vCPUs (bsc#1276258).\n- CVE-2026-74518: mm/hugetlb: fix list corruption in allocate_file_region_entries() (bsc#1275798).\n- CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path (bsc#1275802).\n- CVE-2026-74527: octeontx2-af: Block VFs from clobbering special CGX PKIND state (bsc#1275805).\n- CVE-2026-74533: Bluetooth: ISO: fix race of kfree vs kref_get_unless_zero (bsc#1275804).\n- CVE-2026-74534: Bluetooth: ISO: Fix data-race on iso_pi(sk) in socket and HCI event paths (bsc#1275801).\n- CVE-2026-74535: Bluetooth: ISO: avoid deadlocks in iso_sock_timeout (bsc#1275812).\n- CVE-2026-74536: Bluetooth: ISO: fix leaking sk after socket release (bsc#1275799).\n- CVE-2026-74537: Bluetooth: ISO: hold sk properly in iso_conn_ready (bsc#1275687).\n- CVE-2026-74545: rtase: fix double free of multi-frag skb on DMA map failure (bsc#1275679).\n- CVE-2026-74548: forcedeth: fix UAF of txrx_stats in nv_remove (bsc#1275695).\n- CVE-2026-74550: net: do not send ICMP/NDISC Redirects when peer allocation fails (bsc#1275688).\n- CVE-2026-74555: scsi: libsas: Fix HA resume deadlock and hisi_sas disk-wake race (bsc#1275690).\n- CVE-2026-74556: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer (bsc#1275696).\n- CVE-2026-74557: scsi: libiscsi: Fix stale-data leak into the SCSI sense buffer (bsc#1275685).\n- CVE-2026-74563: rds: tcp: hold the RCU lock across ipv6_chk_addr() in rds_tcp_laddr_check() (bsc#1275574).\n- CVE-2026-74566: keys: make keyring key-chunk byte order agree with keyring_diff_objects() (bsc#1275566).\n- CVE-2026-74567: keys: fix out-of-bounds read in keyring_get_key_chunk() (bsc#1275569).\n- CVE-2026-74571: btrfs: skip global block reserve accounting for rescue mounts (bsc#1275561).\n- CVE-2026-74577: net: mpls: initialize rtm_tos in mpls_getroute() (bsc#1275572).\n- CVE-2026-74581: net: ipv6: clear suppressed fib6 rule result (bsc#1275782).\n- CVE-2026-74582: packet: use consistent hard_header_len in non-ring send paths (bsc#1275784).\n- CVE-2026-74584: RDMA/bnxt_re: zero shared page before exposing to userspace (bsc#1277066).\n- CVE-2026-74598: ipv6: fix Route Information option length validation (bsc#1277918).\n- CVE-2026-74610: tls: don't leave a full plaintext sk_msg ring unpushed (bsc#1277054).\n- CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).\n- CVE-2026-74615: vxlan: do not arm the ageing timer on a device that is down (bsc#1277901).\n- CVE-2026-74616: xdp: reject clones that overrun skb_shared_info tailroom (bsc#1277813).\n- CVE-2026-74622: net: atlantic: free RX pages of consumed but not refilled buffers (bsc#1277862).\n- CVE-2026-74644: mm/damon/ops-common: putback folios on invalid migrate nid (bsc#1277033).\n- CVE-2026-74665: net: fix skb length accounting after generic XDP frag adjustment (bsc#1277407).\n- CVE-2026-74669: ipvs: clear IPv4 options after rebasing tunnel ICMP errors (bsc#1277391).\n- CVE-2026-74695: netfilter: nf_flow_table: drop existing skb dst before skb_dst_set_noref() (bsc#1276931).\n- CVE-2026-74705: udp: fix potential use-after-free in tunnel segmentation (bsc#1276922).\n- CVE-2026-74712: vdpa/mlx5: Fix buffer length in create_direct_keys() (bsc#1276577).\n- CVE-2026-74717: net/mlx5: fw_tracer, return NULL on create error (bsc#1276569).\n- CVE-2026-74719: net/smc: fix qentry overwrite for CONFIRM_LINK and ADD_LINK_CONT in smc_llc_event_handler()\n  (bsc#1276572).\n- CVE-2026-74722: btrfs: fix memory leak in btrfs_do_encoded_write() (bsc#1276561).\n- CVE-2026-74723: btrfs: lzo: reject inline extents without valid headers (bsc#1276562).\n- CVE-2026-74730: NFS: Pin the 'struct nfs_server' during a FREE_STATEID call (bsc#1276566).\n- CVE-2026-74737: net: ethernet: ti: am65-cpsw-nuss: Fix port_id extraction from SRC TAG (bsc#1277898).\n- CVE-2026-74743: macvlan: inherit needed_headroom and needed_tailroom from lowerdev (bsc#1277908).\n- CVE-2026-74744: ipvlan: inherit needed_headroom and needed_tailroom from phy_dev (bsc#1278094).\n- CVE-2026-80529: xfs: don't swallow dquot recovery verification errors (bsc#1277688).\n- CVE-2026-80530: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN (bsc#1277668).\n- CVE-2026-80531: xfs: avoid UAF on sc-\u003etempip in xrep_tempfile_create (bsc#1277680).\n- CVE-2026-80533: xfs: don't walk off the end of a null sc-\u003esa.agi_bp in AGI repair (bsc#1277636).\n- CVE-2026-80534: xfs: fix ilock leak on error in xfs_dq_get_next_id (bsc#1277022).\n- CVE-2026-80535: xfs: don't double-lock when deleting a self-referential directory (bsc#1277641).\n- CVE-2026-80557: libceph: fix OOB read in decode_watchers() via missing bounds check (bsc#1277268).\n- CVE-2026-80558: libceph: Avoid using invalid osd indices from primary_temp (bsc#1277485).\n- CVE-2026-80561: libceph: fix multiple unsafe decodes in decode_locker() (bsc#1277265).\n- CVE-2026-80586: mptcp: options: reset DSS fields in case of unexpected size (bsc#1277328).\n- CVE-2026-80589: block: stop the timeout timer when releasing a never added disk (bsc#1277335).\n- CVE-2026-80590: inet: frags: strip GSO state from fragments before reassembly (bsc#1277275).\n- CVE-2026-80603: netfilter: nf_conntrack_irc: fix parse_dcc() off-by-one OOB read (bsc#1278293).\n- CVE-2026-80609: qede: fix out-of-bounds check for cqe-\u003elen_list (bsc#1278334).\n- CVE-2026-80629: octeontx2-af: npc: Fix size of entry2cntr_map (bsc#1277308).\n- CVE-2026-80646: ipv6: guard against possible NULL deref in __in6_dev_stats_get() (bsc#1277513).\n- CVE-2026-80647: RDMA/hns: Fix warning in poll cq direct mode (bsc#1278331).\n- CVE-2026-80667: net/mlx5: LAG, MPESW, Fix missing complete() on devcom error (bsc#1278324).\n- CVE-2026-80681: vxlan: re-fetch eth header after route_shortcircuit() (bsc#1278416).\n- CVE-2026-80693: idpf: bound interrupt-vector register fill to the allocated array (bsc#1278395).\n- CVE-2026-80714: ipvs: do not propagate one-packet flag to synced conns (bsc#1277561).\n- CVE-2026-80721: Bluetooth: ISO: ensure no dangling hcon references in iso_conn (bsc#1277845).\n- CVE-2026-80727: x86/mce: Set up the polling timer before CMCI discovery (bsc#1278703).\n- CVE-2026-80731: net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header (bsc#1278716).\n- CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown (bsc#1279487).\n- CVE-2026-80739: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock (bsc#1278733).\n- CVE-2026-80805: xfs: validate attr entry pointer before field access (bsc#1279580).\n- CVE-2026-80813: nvmet: fix NULL pointer dereference in nvmet_execute_identify_nslist() (bsc#1279537).\n- CVE-2026-80838: vxlan: keep the last remote linked during FDB flush (bsc#1279842).\n\nThe following non security issues were fixed:\n\n- accel/ivpu: Limit firmware log name prints to field size (git-fixes).\n- accel/ivpu: Validate firmware log buffer metadata (git-fixes).\n- accel/ivpu: Validate full buffer range in ivpu_to_cpu_addr (git-fixes).\n- accel/qaic: Address potential out-of-bounds read in resp_worker() (git-fixes).\n- accessibility: speakup: Fix incorrect string length computation in report_char_chartab_status() (git-fixes).\n- accessibility: speakup: unregister tty ldisc on later init failures (git-fixes).\n- ACPI: APEI: Fix ERST timeout unit conversion (git-fixes).\n- ACPI: battery: Adjust charging status validation check (git-fixes).\n- ACPI: EC: Avoid _REG disconnect on GPIO IRQ defer (git-fixes).\n- ACPI: PCI: Clear driver_data on all paths that free the acpi_pci_root (git-fixes).\n- ACPI: pfr_update: fix stack buffer overflow in query_capability() (git-fixes).\n- ACPI: processor: idle: Expand _LPI package sanity checks (git-fixes).\n- ACPI: processor: validate MADT IOAPIC entry bounds (git-fixes).\n- ACPI: processor_idle: Mark LPI enter functions as __cpuidle (git-fixes).\n- ACPI: scan: fix bus ID cleanup on device_add() failures (git-fixes).\n- ACPI: video: Release PCI device reference after lookup (git-fixes).\n- ALSA: 6fire: bound the MIDI event length from the device (git-fixes).\n- ALSA: 6fire: Fix UAF at error handling during probe (stable-fixes).\n- ALSA: bcd2000: clear the URB pointers on disconnect (git-fixes).\n- ALSA: caiaq: Decoupling ep1_in_urb in caiaq dev (git-fixes).\n- ALSA: caiaq: Fix potential double-free at error path (git-fixes).\n- ALSA: control: Don't add invalid kcontrols to LED layer (git-fixes).\n- ALSA: core: Fix use-after-free in snd_card_do_free() (git-fixes).\n- ALSA: ctxfi: Fix CA20K2 S/PDIF passthrough (git-fixes).\n- ALSA: dummy: Check card index validity at probe (stable-fixes).\n- ALSA: dummy: Report a change when one capture switch channel moves (git-fixes).\n- ALSA: harmony: initialize locks before requesting IRQ (git-fixes).\n- ALSA: hda/ext: preserve PPLCCTL bits when clearing reset (git-fixes).\n- ALSA: hda/realtek: Enable headset mic on F+ FLAPTOP r (stable-fixes).\n- ALSA: hda: Fix connection list comparison in proc output (git-fixes).\n- ALSA: hda: Report a change when only the channel status bytes move (git-fixes).\n- ALSA: hda: restore MFG widget enumeration after core split (git-fixes).\n- ALSA: hpi: Check transport errors during HPI6000 adapter initialization (git-fixes).\n- ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (git-fixes).\n- ALSA: pcxhr: initialize mutexes before requesting threaded IRQ (git-fixes).\n- ALSA: rawmidi: Return the error from snd_rawmidi_input_params() (git-fixes).\n- ALSA: scarlett2: Use a private URB for the notification endpoint (git-fixes).\n- ALSA: seq: Don't leak the extension cell pointer in the bounce payload (git-fixes).\n- ALSA: seq: midi: Optimize event_input locking with RCU (git-fixes).\n- ALSA: seq: midi: Serialize input teardown with event_input (git-fixes).\n- ALSA: ump: Fix corrupted data bytes at MIDI 1.0 SysEx to UMP conversion (git-fixes).\n- ALSA: usb-audio: Complete cleanup after system-resume errors (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_novation_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output() (git-fixes).\n- ALSA: usb-audio: fix OOB write on Type II inbound URBs (git-fixes).\n- ALSA: usb: Fix UAF at delayed release of MIDI2 EPs (git-fixes).\n- ALSA: usbusx2y: fix in04_last array size mismatch with in04_buf (git-fixes).\n- ALSA: usbusx2y: validate URB actual_length in interrupt callback (git-fixes).\n- ALSA: usx2y: bound the hwdep mmap fault offset (git-fixes).\n- ALSA: via82xx: Remove unreachable branch in snd_via686_pcm_pointer() (git-fixes).\n- apparmor: advertise the tcp fast open fix is applied (git-fixes).\n- ASoC: ab8500: Correct digital interface format setup (git-fixes).\n- ASoC: ab8500: Repair the DAPM capture graph (git-fixes).\n- ASoC: ab8500: Reset the audio block before configuring it (git-fixes).\n- ASoC: ab8500: Validate and program TDM slots correctly (git-fixes).\n- ASoC: adau1761: sort the register default table (git-fixes).\n- ASoC: amd: renoir: fix disable_pdm_interrupts() to clear mask bits (git-fixes).\n- ASoC: amd: yc: Add DMI entry for MSI Thin A15 B7UC (git-fixes).\n- ASoC: amd: yc: fix memory leak in acp6x_pdm_dma_close() (git-fixes).\n- ASoC: apple: mca: increase SERDES reset delay (git-fixes).\n- ASoC: bcm: bcm63xx: Publish the OF module aliases (git-fixes).\n- ASoC: codecs: lpass-wsa-macro: Fix enum kcontrol accesses (git-fixes).\n- ASoC: cs35l33: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l34: drain threaded IRQ before runtime suspend (git-fixes).\n- ASoC: cs35l41: sort the register default table (git-fixes).\n- ASoC: cs35l45: sort the register default table (git-fixes).\n- ASoC: cs4265: sort the register default table (git-fixes).\n- ASoC: cx2072x: sort the register default table (git-fixes).\n- ASoC: dapm: Fix off-by-one check on the second enum channel (git-fixes).\n- ASoC: fix unmet dependencies on PPC_BESTCOMM and SND_SOC_AC97_BUS (git-fixes).\n- ASoC: fsl-asoc-card: defer probe when the CPU DAI device is not ready (git-fixes).\n- ASoC: fsl: mpc5200-i2s: Free DMA resources on probe failure (git-fixes).\n- ASoC: fsl_audmix: rework runtime PM handling in probe (git-fixes).\n- ASoC: fsl_easrc: sort the register default table (git-fixes).\n- ASoC: hdac_hda: Fix hlink refcount leak on component registration failure (git-fixes).\n- ASoC: Intel: avs: Clean up streams if their initialization fails (git-fixes).\n- ASoC: Intel: avs: Clean up the bus when fetching ML caps fails (git-fixes).\n- ASoC: Intel: avs: Do not ignore -ENOENT when loading a topology (git-fixes).\n- ASoC: Intel: avs: Fix unbalanced module reference count (git-fixes).\n- AsoC: intel: sst: fix PCI device reference leak on probe failure (git-fixes).\n- ASoC: Intel: SST: Publish the PCI module aliases (git-fixes).\n- ASoC: loongson: Fix error handling in ACPI property parsing (git-fixes).\n- ASoC: max9860: sort the register default table (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Shorten memif_data table using macros (stable-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: Support \u003e32 bit DMA addresses (git-fixes).\n- ASoC: mediatek: mt8183-afe-pcm: use local `dev` pointer in driver callbacks (stable-fixes).\n- ASoC: mediatek: mt8183: Check runtime resume during probe (git-fixes).\n- ASoC: mediatek: mt8192-afe-pcm: Simplify probe() with local dev variable (stable-fixes).\n- ASoC: mediatek: mt8192: Check runtime resume during probe (git-fixes).\n- ASoC: meson: Keep link pointers valid on realloc failure (git-fixes).\n- ASoC: ml26124: sort the register default table (git-fixes).\n- ASoC: mt6351: Publish the OF module alias (git-fixes).\n- ASoC: pcm512x: sort the register default table (git-fixes).\n- ASoC: pxa: Use devm_clk_get_optional() for extclk clock (git-fixes).\n- ASoC: qcom: q6apm: keep the graph start count in sync with the DSP (git-fixes).\n- ASoC: rt274: sort the register default table (git-fixes).\n- ASoC: rt286: sort the register default table (git-fixes).\n- ASoC: rt298: sort the register default table (git-fixes).\n- ASoC: rt700-sdw: always drain jack work on remove (git-fixes).\n- ASoC: rt700: drop duplicate reg_default entry (git-fixes).\n- ASoC: rt700: sort the register default table (git-fixes).\n- ASoC: rt711-sdca: sort the register default tables (git-fixes).\n- ASoC: rt711: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-dmic: sort the register default table (git-fixes).\n- ASoC: rt712-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt715-sdca: drop duplicate reg_default entries (git-fixes).\n- ASoC: rt715-sdca: sort the register default tables (git-fixes).\n- ASoC: rt715: sort the register default table (git-fixes).\n- ASoC: rt1017-sdca-sdw: sort the register default table (git-fixes).\n- ASoC: rt1316-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318-sdw: sort the register default table (git-fixes).\n- ASoC: rt1318: sort the register default table (git-fixes).\n- ASoC: samsung: aries_audio_probe: double of_node_put due to direct assignment without of_node_get (git-fixes).\n- ASoC: sgtl5000: sort the register default table (git-fixes).\n- ASoC: SOF: sof-audio: Fix error path in sof_widget_setup_unlocked() (git-fixes).\n- ASoC: SOF: validate topology volume range before allocation (git-fixes).\n- ASoC: sprd: validate compress buffer sizes against fixed allocations (git-fixes).\n- ASoC: sti-sas: sort the register default table (git-fixes).\n- ASoC: sti: initialize IRQ lock before requesting IRQ (git-fixes).\n- ASoC: tas2552: sort the register default table (git-fixes).\n- ASoC: tas2764: sort the register default table (git-fixes).\n- ASoC: tas2780: sort the register default table (git-fixes).\n- ASoC: tegra210_i2s: sort the register default table (git-fixes).\n- ASoC: tegra210_mixer: sort the register default table (git-fixes).\n- ASoC: tegra: Fix the MIXER enable default value (git-fixes).\n- ASoC: tegra: Sort MBDRC register defaults (git-fixes).\n- ASoC: xilinx: formatter_pcm: fix stream_data leak on open error (git-fixes).\n- ASoC: xilinx: formatter_pcm: pass aud_drv_data to irq handlers (git-fixes).\n- ata: ahci: work around lost interrupts on Marvell 88SE61xx (git-fixes).\n- batman-adv: bla: fix freeing of claims on meshif deletion (git-fixes).\n- batman-adv: bla: prevent CRC corruptions after claim flush (git-fixes).\n- batman-adv: dat: avoid unaligned fault in IP extraction (git-fixes).\n- batman-adv: fix stale receive device on merged fragments (git-fixes).\n- batman-adv: mcast: ensure unshared skb for multicast packets (git-fixes).\n- batman-adv: mcast: linearize skbuff for packet generation (git-fixes).\n- batman-adv: reject unrepresentable multicast TVLV offsets (git-fixes).\n- blk-mq: reinsert cached request to the list (bsc#1273770).\n- Bluetooth: btintel: bound firmware ID by TLV length (git-fixes).\n- Bluetooth: btintel: Fix diagnostics event detection (git-fixes).\n- Bluetooth: btintel: validate version TLV value lengths (git-fixes).\n- Bluetooth: btintel_pcie: Clear automask on spurious interrupts (git-fixes).\n- Bluetooth: btintel_pcie: fix tx_handle bounds off-by-one (git-fixes).\n- Bluetooth: btintel_pcie: validate packet_len before skb_put_data (git-fixes).\n- Bluetooth: btmtk: Declare MT7920 (MT7961 1a) Bluetooth firmware (git-fixes).\n- Bluetooth: btmtk: Do not discard the subsystem reset timeout (git-fixes).\n- Bluetooth: btmtk: Fix short read errors in btmtk_usb_uhw_reg_read() (stable-fixes).\n- Bluetooth: btmtksdio: Fix out-of-bounds DMA read in the TX path (git-fixes).\n- Bluetooth: btmtksdio: Take exclusive ownership of the SKB before TX (git-fixes).\n- Bluetooth: btqca: Fix qca_set_bdaddr() waiting for wrong HCI event (git-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btrtl: Don't leak return code when parsing firmware format v2 (git-fixes).\n- Bluetooth: btusb: Fix BD_ADDR byte order in btusb_set_bdaddr_wcn6855() (git-fixes).\n- Bluetooth: btusb: Fix short read errors in btusb_qca_send_vendor_req() (stable-fixes).\n- Bluetooth: btusb: Fix UAF of btusb_data by rx_work (git-fixes).\n- Bluetooth: do not leak an hci_conn when a second LE connect is rejected (git-fixes).\n- Bluetooth: eir: Fix OOB read in eir_get_service_data() (git-fixes).\n- Bluetooth: hci_aml: validate firmware segment lengths (git-fixes).\n- Bluetooth: hci_bcm4377: Ignore reserved PHY in ext adv reports on BCM4378 (git-fixes).\n- Bluetooth: hci_bcm: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_conn: fix the SCO setup context lifetime (git-fixes).\n- Bluetooth: hci_conn: hold conn reference in abort_conn_sync() (git-fixes).\n- Bluetooth: hci_conn: re-enable advertising only for peripheral role (git-fixes).\n- Bluetooth: hci_core: Fix race condition during device registration (git-fixes).\n- Bluetooth: hci_core: use skb_get() instead of skb_clone() for req_skb (git-fixes).\n- Bluetooth: hci_event: clear HCI_LE_ADV only on a created connection (git-fixes).\n- Bluetooth: hci_event: fix LE list UAF on reset (git-fixes).\n- Bluetooth: hci_event: validate LE Set CIG Parameters response (git-fixes).\n- Bluetooth: hci_h5: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_intel: fix usage_count leak when autosuspend_delay is negative (git-fixes).\n- Bluetooth: hci_mrvl: Fix wrong return value check of wait_on_bit_timeout() (git-fixes).\n- Bluetooth: hci_sync: Clear HCI_CMD_PENDING when dropping the last request (git-fixes).\n- Bluetooth: hci_sync: Fix accept list UAF during suspend (git-fixes).\n- Bluetooth: hci_sync: free the advertising instance on the failure and cancel paths (git-fixes).\n- Bluetooth: hci_sync: make hci_cmd_sync_run_once return -EEXIST if exists (stable-fixes).\n- Bluetooth: hci_sync: Use bt_dev_err() to log error message in hci_update_event_filter_sync() (stable-fixes).\n- Bluetooth: hci_sysfs: Fix NULL pointer dereference in device_del() (git-fixes).\n- Bluetooth: hci_uart: Fix false success return in hci_uart_setup() (git-fixes).\n- Bluetooth: ISO: do not force BT_LISTEN after a failed BIG sync (git-fixes).\n- Bluetooth: ISO: fix use-after-free of listener socket in iso_conn_ready (git-fixes).\n- Bluetooth: L2CAP: clear FLAG_DEFER_SETUP only for same PID/PSM (git-fixes).\n- Bluetooth: L2CAP: fix chan mode for LE_CONN_REQ + EXT_FLOWCTL pchan (git-fixes).\n- Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect (git-fixes).\n- Bluetooth: mgmt: fix locking in unpair_device/disconnect_sync (git-fixes).\n- Bluetooth: MGMT: free the HCI command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: free the mesh send cancel command when it is cancelled (git-fixes).\n- Bluetooth: MGMT: reject HCI_CMD_SYNC params_len above 255 (git-fixes).\n- Bluetooth: MGMT: revalidate LOAD_CONN_PARAM queued update (git-fixes).\n- Bluetooth: MSFT: validate evt_prefix_len against the response length (git-fixes).\n- Bluetooth: qca: fix NVM tag length underflow in TLV parser (git-fixes).\n- Bluetooth: RFCOMM: serialize security confirmation handling (git-fixes).\n- Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept (git-fixes).\n- Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite loop (git-fixes).\n- Bluetooth: virtio_bt: avoid OOB read of build info string (git-fixes).\n- bnxt_en: Check return value of bnxt_hwrm_vnic_cfg (jsc#PED-16798).\n- bnxt_en: Delay for 5 seconds after AER DPC for all chips (jsc#PED-16798).\n- bnxt_en: Don't assume XDP is never enabled in bnxt_init_dflt_ring_mode() (jsc#PED-16798).\n- bnxt_en: Drop pci_save_state() after pci_restore_state() (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction (jsc#PED-16798).\n- bnxt_en: Implement XDP RSS hash metadata extraction for V3_CMP (jsc#PED-16798).\n- bnxt_en: Move bnxt_rss_ext_op into header (jsc#PED-16798).\n- bnxt_en: Refactor some basic ring setup and adjustment logic (jsc#PED-16798).\n- bnxt_en: Restore default stat ctxs for ULP when resource is available (jsc#PED-16798).\n- bnxt_en: Set bp-\u003emax_tpa according to what the FW supports (jsc#PED-16798).\n- bnxt_en: Use absolute target ns from ptp_clock_request (jsc#PED-16798).\n- bnxt_en: use bnxt_xdp_buff for xdp context (jsc#PED-16798).\n- bus: mhi: ep: Fix device refcount leak in the error path of MHI device creation (git-fixes).\n- bus: mhi: host: Fix controller cleanup on EDL sysfs failure (git-fixes).\n- bus: mhi: host: Flush the posted write after writing to MHI_SOC_RESET_REQ_OFFSET (git-fixes).\n- bus: ti-sysc: Fix /chosen node reference leak (git-fixes).\n- cacheinfo: don't propagate DT/ACPI error when arch supplies info (arm64) (git-fixes).\n- can: j1939: add missing calls in NETDEV_UNREGISTER notification handler (git-fixes).\n- can: j1939: use netdevice_tracker for j1939_{priv,session,ecu} tracking (stable-fixes).\n- char: xilinx_hwicap: unregister class on init errors (git-fixes).\n- cleanup: add a scoped version of CLASS() (stable-fixes).\n- cleanup: fix scoped_class() (git-fixes).\n- compiler_types: Introduce __flex_counter() and family (bsc#1280139).\n- cpufreq: intel_pstate: Add and use hybrid_get_cpu_type() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Avoid SMP calls to get cpu-type (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Fix hwp_get_cpu_scaling() (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use correct scaling factor on Raptor Lake-E (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use CPPC to get scaling factors (bsc#1240957 bsc#1249104 bsc#1265220).\n- cpufreq: intel_pstate: Use HYBRID_SCALING_FACTOR_ADL for Bartlett Lake (bsc#1240957 bsc#1249104 bsc#1265220).\n- crypto: aspeed - Propagate platform_get_irq() errors (git-fixes).\n- crypto: atmel-sha204a - fix heap info leak on I2C transfer failure (git-fixes).\n- crypto: atmel-tdes - use scatterlist length before DMA mapping (git-fixes).\n- crypto: ccm - Set rfc4309 maxauthsize from child (git-fixes).\n- crypto: ccp - Abort doing SEV INIT if SNP INIT fails (stable-fixes).\n- crypto: ccp - Add new SEV/SNP platform shutdown API (stable-fixes).\n- crypto: ccp - Always pass in an error pointer to __sev_platform_shutdown_locked() (git-fixes).\n- crypto: ccp - Fix __sev_snp_shutdown_locked (git-fixes).\n- crypto: ccp - Fix dereferencing uninitialized error pointer (git-fixes).\n- crypto: ccp - Fix memory leak in SEV INIT_EX path (git-fixes).\n- crypto: ccp - Fix possible deadlock in SEV init failure path (git-fixes).\n- crypto: ccp - Fix SNP panic notifier unregistration (git-fixes).\n- crypto: ccp - Move dev_info/err messages for SEV/SNP init and shutdown (stable-fixes).\n- crypto: ccp - Move SEV/SNP Platform initialization to KVM (stable-fixes).\n- crypto: ccp - Register SNP panic notifier only if SNP is enabled (stable-fixes).\n- crypto: ccp - Reset TMR size at SNP Shutdown (stable-fixes).\n- crypto: doc - Remove extra parenthesis (git-fixes).\n- crypto: hisilicon/sec2 - fix CCM algorithm long packet failure (git-fixes).\n- crypto: keembay - Fix AEAD unregister count in error path (git-fixes).\n- crypto: keembay - Initialize completion before requesting IRQ (git-fixes).\n- crypto: keembay - publish OF module alias for OCS AES/SM4 (git-fixes).\n- crypto: lskcipher - propagate errors from unaligned crypt (git-fixes).\n- crypto: mxs-dcp - fix source scatterlist length access (git-fixes).\n- crypto: qat - cancel work on re-enable SR-IOV timeout (git-fixes).\n- crypto: qat - clear AES key schedule from stack (git-fixes).\n- crypto: qce - fix CCM AAD buffer underallocation (git-fixes).\n- crypto: qce - fix error path in devm_qce_register_algs (git-fixes).\n- crypto: qcom-rng - Allow zero as a random number (git-fixes).\n- crypto: qcom-rng - Enable clock in hwrng case (git-fixes).\n- crypto: rk3288 - fail ahash requests on HASH idle timeout (git-fixes).\n- crypto: sa2ul - stop probe if context pool creation fails (git-fixes).\n- crypto: sl3516 - drop invalid sg_dma_len checks before DMA mapping (git-fixes).\n- crypto: tegra - Don't touch bo refcount in host1x bo pin/unpin (stable-fixes).\n- crypto: tegra - fix rctx-\u003ecryptlen calculation in tegra_gcm_do_one_req() (git-fixes).\n- cxl/acpi: Fix CXL_ACPI and CXL_PMEM Kconfig tristate mismatch (git-fixes).\n- cxl: Adjust the startup priority of cxl_pmem to be higher (git-fixes).\n- default_gfp(): avoid using the \"newfangled\" __VA_OPT__ trick (bsc#1280139).\n- device property: fix infinite loop in fwnode_for_each_child_node() (git-fixes).\n- dm/amdgpu: fix malformed link_settings debugfs output (git-fixes).\n- dma-mapping: add __dma_from_device_group_begin()/end() (bsc#1267586).\n- dmaengine: dw-edma: Clear stale requests on termination (git-fixes).\n- dmaengine: dw-edma: Complete descriptors before pausing (git-fixes).\n- dmaengine: dw-edma: Fix HDMA channel status register access (git-fixes).\n- dmaengine: dw-edma: Initialize IRQ data before requesting IRQs (git-fixes).\n- dmaengine: dw-edma: Serialize abort state updates (git-fixes).\n- dmaengine: dw-edma: Serialize channel state checks (git-fixes).\n- dmaengine: dw-edma: Terminate all descriptors without callbacks (git-fixes).\n- dmaengine: fsl-edma: tracing: no ptr dereference during log output (git-fixes).\n- dmaengine: hisilicon: Return -ENOMEM on dynamic memory allocation in probe (git-fixes).\n- dmaengine: mediatek: mtk-uart-apdma: Return -ENOMEM on memory allocation failure (git-fixes).\n- dmaengine: qcom-bam-dma: fix autosuspend cleanup during removal (git-fixes).\n- dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and MCDMA interrupt handlers (git-fixes).\n- dmaengine: xilinx_dma: Fix CPU stall in xilinx_dma_poll_timeout (git-fixes).\n- dmaengine: zynqmp_dma: fix kernel doc for zynqmp_dma_remove() (git-fixes).\n- driver core: soc: Unregister bus on early device registration failure (git-fixes).\n- drivers/virt: pkvm: Fix end calculation in mmio_guard_ioremap_hook() (git-fixes).\n- Drivers: hv: Use meaningful errnos for hypercall status codes (git-fixes).\n- drm/amd/display: Add AV mute wait frames to dce110_set_avmute (stable-fixes).\n- drm/amd/display: avoid divide-by-zero in __is_lut_linear() (git-fixes).\n- drm/amd/display: Check for tg ops in dce110_set_avmute (git-fixes).\n- drm/amd/display: dce100: skip non-DP stream encoders for DP MST (stable-fixes).\n- drm/amd/display: fix BT.2020 YCbCr limited output CSC matrix (git-fixes).\n- drm/amd/display: fix BT.2020 YCbCr output CSC matrices for DCE (git-fixes).\n- drm/amd/display: fix division by zero in get_estimated_bw() (git-fixes).\n- drm/amd/display: Fix NULL pointer dereference in amdgpu_dm_crtc_set_vblank() (git-fixes).\n- drm/amd/display: Increase HDMI AV mute wait from 2 to 3 frames (stable-fixes).\n- drm/amd/display: Remove unused-but-set variable hubp from (git-fixes).\n- drm/amd/display: validate plane degamma LUT size for private color prop (git-fixes).\n- drm/amd/pm: adjust the visibility of pp_table sysfs node (stable-fixes).\n- drm/amd/pm: fix gpu metrics energy accumulator for smu 13.0.0/13.0.7 (git-fixes).\n- drm/amd/pm: fix smu14 power limit range calculation (stable-fixes).\n- drm/amd/pm: make pp_features read-only when scpm is enabled (stable-fixes).\n- drm/amd/pm: Use same metric table for APU (stable-fixes).\n- drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read (git-fixes).\n- drm/amdgpu/gfx6: Fixup emit_cntxcntl() (git-fixes).\n- drm/amdgpu/gfx6: Fixup emitting SWITCH_BUFFER packets (git-fixes).\n- drm/amdgpu/gfx6: Use PFP on the compute queues too (git-fixes).\n- drm/amdgpu/gfx8: drop unecessary BUG_ON() (stable-fixes).\n- drm/amdgpu/gfx9.4.3: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx9: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx10: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx11: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/gfx12: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in SMU7 lookup (git-fixes).\n- drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup (git-fixes).\n- drm/amdgpu/sdma4.4.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma5.2: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma6.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/sdma7.0: replace BUG_ON() with WARN_ON() (stable-fixes).\n- drm/amdgpu/uvd: Fix forcing MSG, FB BOs into VCPU segment when it isn't at 0 (v2) (stable-fixes).\n- drm/amdgpu/uvd: Place VCPU BO only in VRAM for UVD 4.x and older (stable-fixes).\n- drm/amdgpu/vce: fix integer overflow in image size (stable-fixes).\n- drm/amdgpu/vcn4: avoid rereading IB param length (stable-fixes).\n- drm/amdgpu/vcn: fix integer overflow in dec_msg buffer count check (git-fixes).\n- drm/amdgpu: cap GTT size to physical RAM on APUs (stable-fixes).\n- drm/amdgpu: check ASPM on the dGPU host link (git-fixes).\n- drm/amdgpu: disallow multiple FENCE chunks in one submit (git-fixes).\n- drm/amdgpu: fix aperture iounmap skipped on device removal (git-fixes).\n- drm/amdgpu: fix autosuspend cleanup during removal (git-fixes).\n- drm/amdgpu: fix bo-\u003epin leaking in amdgpu_bo_create_reserved (stable-fixes).\n- drm/amdgpu: fix division by zero with invalid uvd dimensions (stable-fixes).\n- drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid() (stable-fixes).\n- drm/amdgpu: fix nbif 6.3.1 l1 low power not functional (git-fixes).\n- drm/amdgpu: Fix UVD decode image min size calculation (stable-fixes).\n- drm/amdgpu: Fix UVD dpb min size calculation for H264 (stable-fixes).\n- drm/amdgpu: Fix UVD min buffer sizes (stable-fixes).\n- drm/amdgpu: Fix VCE 3 ring align_mask (git-fixes).\n- drm/amdgpu: Fix VFCT bus number matching with soft filter (stable-fixes).\n- drm/amdgpu: Implement insert_end for VCE 3 (git-fixes).\n- drm/amdgpu: invoke pm_genpd_remove() before freeing genpd (stable-fixes).\n- drm/amdgpu: move debug_vm handling to amdgpu_cs_parser_fini (git-fixes).\n- drm/amdgpu: read TRUNCATE_COORD_MODE on gfx12 (git-fixes).\n- drm/amdgpu: reject oversized IBs with per-ring packet limits (stable-fixes).\n- drm/amdgpu: Reject UVD message with dimensions above 4096 (stable-fixes).\n- drm/amdgpu: Reject UVD message with invalid number of h265 refs (stable-fixes).\n- drm/amdgpu: remove unused function parameter (stable-fixes).\n- drm/amdgpu: restore UMD profile pstate after runtime resume (stable-fixes).\n- drm/amdgpu: validate GEM_CREATE domain combinations (stable-fixes).\n- drm/amdkfd: Check bounds in allocate_event_notification_slot (stable-fixes).\n- drm/amdkfd: fix 32-bit overflow in CWSR total size calculation (stable-fixes).\n- drm/amdkfd: Fix missing authorization check in KFD_IOC_DBG_TRAP_DISABLE (stable-fixes).\n- drm/amdkfd: fix QID bit leak in pqm_create_queue() (stable-fixes).\n- drm/amdkfd: guard against NULL restore_mqd in CRIU queue restore (git-fixes).\n- drm/amdkfd: Handle invalid event type in CRIU event restore (stable-fixes).\n- drm/amdkfd: Use kvcalloc to allocate arrays (stable-fixes).\n- drm/bridge: cdns-mhdp8546: Return an error pointer on allocation failure (git-fixes).\n- drm/bridge: dw-hdmi: fix i2c adapter leak on probe failure (git-fixes).\n- drm/bridge: ps8640: propagate AUX transfer register errors (git-fixes).\n- drm/bridge: tc358767: clamp the reported AUX read size to the request (git-fixes).\n- drm/connector/hdmi: Fix out of bounds memory read (git-fixes).\n- drm/connector: Fix epoch_counter docs to reflect reality (git-fixes).\n- drm/drm_exec: fix up contended obj when num_objects is 0 (git-fixes).\n- drm/gud: NUL-terminate TV mode names read from the device (git-fixes).\n- drm/gud: validate TV mode names before creating enum property (git-fixes).\n- drm/hibmc: Fix list of formats on the primary plane (git-fixes).\n- drm/hibmc: Use drm_atomic_helper_check_plane_state() (git-fixes).\n- drm/i915/hdcp: check streams bounds before overflow (git-fixes).\n- drm/i915/hdcp: Move to using intel_display in intel_hdcp (stable-fixes).\n- drm/i915/hdcp: require monotonically increasing seq_num_v (git-fixes).\n- drm/i915/hdcp: Skip inactive MST connectors when building stream list (stable-fixes).\n- drm/i915/vrr: Check HAS_VRR() first in intel_vrr_is_capable() (stable-fixes).\n- drm/i915/vrr: require valid min/max vfreq for VRR (git-fixes).\n- drm/i915: Fix memory leak in query_perf_config_list() (git-fixes).\n- drm/lima: call drm_mm_init() with a valid allocation range (git-fixes).\n- drm/msm/a6xx: Fix RBBM_CLOCK_CNTL3_TP0 value in a730_hwcg (git-fixes).\n- drm/msm/a6xx: Fix stale rpmh votes after suspend (git-fixes).\n- drm/msm/dpu: Drop sneaky dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: Drop dev_pm_opp_set_rate(0) (git-fixes).\n- drm/msm/dsi: round 6G byte clock rate to the PLL-achievable value (git-fixes).\n- drm/nouveau/uvmm: clear the dirty flag when unwinding an OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau/uvmm: fix NULL deref unwinding an OP_MAP_SPARSE op (git-fixes).\n- drm/nouveau/uvmm: fix premature region free on failed OP_UNMAP_SPARSE (git-fixes).\n- drm/nouveau: unsubscribe the channel-kill event before the fence context (git-fixes).\n- drm/nouveau: Use write-combined maps for coherent (git-fixes).\n- drm/panel-edp: fix i2c adapter leak on probe failure (git-fixes).\n- drm/panel: samsung-s6d16d0: Power off on prepare failure (git-fixes).\n- drm/panthor: fix firmware control interface bounds checks (git-fixes).\n- drm/panthor: return PTR_ERR() from devm_drm_dev_alloc() (git-fixes).\n- drm/panthor: skip zero-sized firmware sections (git-fixes).\n- drm/radeon: fix autosuspend cleanup during teardown (git-fixes).\n- drm/radeon: fix r100_copy_blit for large BOs (stable-fixes).\n- drm/radeon: restore hardware polling in fence_is_signaled to fix performance regression (git-fixes).\n- drm/rockchip: vop2: Recognise 10-bit YUV422 as YUV format (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates for ssd132x (git-fixes).\n- drm/ssd130x: fix column and row end address in partial updates in ssd133x (git-fixes).\n- drm/sun4i: crtc: Propagate layer initialization error (git-fixes).\n- drm/sun4i: Drop node references while building component list (git-fixes).\n- drm/sun4i: dw-hdmi: Drop TCON TOP port reference (git-fixes).\n- drm/sun4i: fix refcount leak in sun4i_backend_init_sat() (git-fixes).\n- drm/sun4i: hdmi-phy: Fix H6 8-bit MPLL config at 594 MHz (git-fixes).\n- drm/sun4i: hdmi: Don't leak sync polarity bits into packet control (git-fixes).\n- drm/sun4i: tcon: Drop remote endpoint reference (git-fixes).\n- drm/sun4i: tcon: Drop TCON TOP device reference (git-fixes).\n- drm/sun4i: tcon: Set output mux for DSI and LVDS (git-fixes).\n- drm/sun4i: vi scaler: Fix coefficient selection (git-fixes).\n- drm/tegra: dsi: Re-add clear enable register if DSI was powered by bootloader (git-fixes).\n- drm/tegra: fbdev: Do not assign to struct drm_fb_helper.info (git-fixes).\n- drm/tve200: add OF module alias for autoloading (git-fixes).\n- drm/virtio: Fix a NULL vs ERR_PTR() bug in virtio_gpu_user_framebuffer_create() (git-fixes).\n- drm/xe/oa: Check managed mutex initialization errors (git-fixes).\n- drm/xe/oa: Fix sync entry leak on OA config emit failure (git-fixes).\n- drm/xe/oa: Remove sysfs entry on idr_alloc failure in xe_oa_add_config_ioctl() (git-fixes).\n- drm/xe: Introduce xe_gt_dbg_printer() (stable-fixes).\n- drm/xe: Order ring writes before ring tail updates (git-fixes).\n- drm/xe: Stub out new pagefault layer (stable-fixes).\n- drm/xe: tests: fix error message in xe_migrate_sanity_test() (git-fixes).\n- drm: Fix drm_crtc_commit leak if signaled when PAGE_FLIP_EVENT is used (git-fixes).\n- drm: fix race between partial drm_dev_register() failure and ioctl (git-fixes).\n- drm: lcdif: Wait for vblank before disabling DMA (git-fixes).\n- drm: Remove unused header in drm_dumb_buffers.c (git-fixes).\n- efi: fix stale reference to efi_recover_from_page_fault() (git-fixes).\n- erspan: Initialize options_len before referencing options (bsc#1274727).\n- ethtool: rss: fix hkey leak when indir_size is 0 (git-fixes).\n- fbdev: bitblit: bound-check glyph index in bit_cursor() (git-fixes).\n- fbdev: core: Fix pointer desynchronization in fb_io_read() (git-fixes).\n- fbdev: kyro: Validate overlay viewport coordinates (git-fixes).\n- fbdev: omapfb: panel-dsi-cm: initialize lock before registering display (git-fixes).\n- fbdev: tdfxfb: fix PCI enable cleanup with pcim_enable_device() (git-fixes).\n- fbdev: uvesafb: unregister connector callback on init failure (git-fixes).\n- fbdev: vfb: defer cleanup until the last reference (git-fixes).\n- firmware: arm_scmi: Avoid IDR updates while cleaning channels (git-fixes).\n- firmware: arm_scmi: Clean up channels on setup failure (git-fixes).\n- firmware: arm_scmi: Drop handle on protocol bind failures (git-fixes).\n- firmware: arm_scmi: Fix requested device removal race (git-fixes).\n- firmware: arm_scmi: Free transport channel on IDR failure (git-fixes).\n- firmware: arm_scmi: Protect device request lookup with RCU (git-fixes).\n- firmware: arm_scmi: Publish channel state before callbacks (git-fixes).\n- firmware: arm_scmi: Quiesce notifications before teardown (git-fixes).\n- firmware: arm_scmi: Rate-limit queue-full warnings in IRQ context (git-fixes).\n- firmware: arm_scmi: Reject out of range DT protocol IDs (git-fixes).\n- firmware: arm_scmi: Roll back partial protocol table registration (git-fixes).\n- firmware: arm_scmi: Unregister device notifier before IDR teardown (git-fixes).\n- firmware: arm_scmi: Unrequest devices if driver registration fails (git-fixes).\n- firmware: arm_scmi: Unwind P2A receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Unwind TX receiver mailbox setup failure (git-fixes).\n- firmware: arm_scmi: Use channel ID for transport teardown (git-fixes).\n- firmware_loader: do not queue completed sysfs fallback requests (git-fixes).\n- fpga: altera-cvp: Avoid out-of-bounds read in trailing byte write (git-fixes).\n- fpga: dfl: fme: add error handling (git-fixes).\n- fpga: stratix10-soc: Fix SVC mailbox handling during reconfiguration (git-fixes).\n- fuse: fix race between interrupt and resend (git-fixes).\n- gpio: sloppy-logic-analyzer: fix use-after-free via debugfs trigger on unbind (git-fixes).\n- gpu: host1x: Avoid stack over-read in debug output helpers (git-fixes).\n- gpu: host1x: Fix offset calculation in trace_write_gather (git-fixes).\n- gpu: host1x: Fix use-after-free in host1x_bo_clear_cached_mappings (stable-fixes).\n- HID: asus: fix missing hid_is_usb() check (git-fixes).\n- HID: asus: simplify RGB init sequence (stable-fixes).\n- HID: bpf: serialize device reference release in struct_ops destroy path (git-fixes).\n- HID: core: fix number/pointer type confusion on long items (git-fixes).\n- HID: core: fix OOB read of field-\u003eusage in hid_set_field() (git-fixes).\n- HID: ft260: fix stack-use-after-return write in I2C read race (git-fixes).\n- HID: ft260: validate i2c input report length (stable-fixes).\n- HID: hyperv: validate initial device info bounds (git-fixes).\n- HID: i2c-hid: Fix \"(null)\" output when reading report descriptor fails (git-fixes).\n- HID: i2c-hid: goodix: Disable VDD on VDDIO enable failure (git-fixes).\n- HID: lg4ff: validate report length before fixed offsets (git-fixes).\n- HID: logitech-dj: Fix maxfield check in DJ short report validation (git-fixes).\n- HID: logitech-dj: fix wrong detection of bad DJ_SHORT output report (git-fixes).\n- HID: logitech-dj: Prevent REPORT_ID_DJ_SHORT related user initiated OOB write (stable-fixes).\n- HID: logitech-dj: Standardise hid_report_enum variable nomenclature (stable-fixes).\n- HID: magicmouse: do not keep a stale msc-\u003einput if no input is claimed (git-fixes).\n- HID: magicmouse: fix battery reporting for Bluetooth Magic Trackpad USB-C (git-fixes).\n- HID: magicmouse: Prevent out-of-bounds (OOB) read during DOUBLE_REPORT_ID (stable-fixes).\n- HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event() (git-fixes).\n- HID: magicmouse: re-enable multitouch after reset-resume (git-fixes).\n- HID: mcp2221: validate report size in mcp2221_raw_event() (git-fixes).\n- HID: multitouch: reclassify HTIX5288 to WIN_8_FORCE_MULTI_INPUT_NSMU (git-fixes).\n- HID: nintendo: Fix imu_timestamp_us double increment per report (git-fixes).\n- HID: nintendo: fix out-of-bounds read in joycon_ctlr_read_handler() (git-fixes).\n- HID: nintendo: register input device after capabilities are set (git-fixes).\n- HID: nintendo: stop device IO before hid_hw_stop on probe failure (git-fixes).\n- HID: picolcd: clamp eeprom debugfs read to bytes actually received (git-fixes).\n- HID: pidff: Rework pidff_set_time() to fix warnings (stable-fixes).\n- HID: pidff: Use ARRAY_SIZE macro instead of sizeof (stable-fixes).\n- HID: rmi: fix OOB access with undersized RMI reports (git-fixes).\n- HID: roccat: bound device-supplied profile index (git-fixes).\n- HID: roccat: free buffered reports when destroying device (git-fixes).\n- HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature (git-fixes).\n- HID: sensor: custom: Fix field sysfs group cleanup on failure (git-fixes).\n- HID: sensor: custom: Fix use-after-free in enable_sensor (git-fixes).\n- HID: synchronize input before cleaning up a failed probe (git-fixes).\n- HID: tmff: Use 64-bit arithmetic for force feedback scaling (git-fixes).\n- HID: wacom: validate report length in wacom_intuos_pro2_bt_irq (git-fixes).\n- hwmon: (ads7828) Fix external VREF regulator handling (git-fixes).\n- hwmon: (applesmc) fix key backlight workqueue leak on register failure (git-fixes).\n- hwmon: (aspeed-pwm-tacho) Propagate reset deassert errors (git-fixes).\n- hwmon: (chipcap2) fix channels in humidity alarm notifications (git-fixes).\n- hwmon: (coretemp) Fix core_data leak on CPUs without PTS (git-fixes).\n- hwmon: (corsair-cpro) Create debugfs entries after hwmon registration (git-fixes).\n- hwmon: (corsair-cpro) Remove debugfs entries when probe fails (git-fixes).\n- hwmon: (corsair-psu) fix possible out-of-bounds access on missing string termination (git-fixes).\n- hwmon: (gpio-fan) Fix use-after-free in alarm work (git-fixes).\n- hwmon: (gpio-fan) take fan_data-\u003elock in gpio_fan_shutdown() (git-fixes).\n- hwmon: (ina2xx) Add support for has_alerts configuration flag (stable-fixes).\n- hwmon: (ina2xx) Add support for INA234 (stable-fixes).\n- hwmon: (ina2xx) Add support for INA260 (stable-fixes).\n- hwmon: (ina2xx) Fix various overflow issues (git-fixes).\n- hwmon: (ina2xx) Make it easier to add more devices (stable-fixes).\n- hwmon: (ina2xx) Shift INA234 shunt and current registers (stable-fixes).\n- hwmon: (ina226) Add support for SY24655 (stable-fixes).\n- hwmon: (ltc4282) Avoid overflow in maximum power calculation (git-fixes).\n- hwmon: (ltc4282) Clamp negative current limits (git-fixes).\n- hwmon: (ltc4282) Fix parsing adi,current-limit-sense-microvolt (git-fixes).\n- hwmon: (ltc4282) Make sure clk_init_data is fully initialized (git-fixes).\n- hwmon: (max6621) fix negative temperature offset and crit readings (git-fixes).\n- hwmon: (max6621) fix temperature clamp range (git-fixes).\n- hwmon: (nzxt-smart2) Check return value of init_device() in probe (git-fixes).\n- hwmon: (pmbus) Clear generic status alarms with CLEAR_FAULTS (git-fixes).\n- hwmon: (pmbus/lm25066) Fix PMBus coefficient calculations (git-fixes).\n- hwmon: Switch back to struct platform_driver::remove() (stable-fixes).\n- hwrng: ks-sa - Fix runtime PM cleanup on registration failure (git-fixes).\n- hwrng: omap - Fix probe error path cleanup (git-fixes).\n- hwtracing: hisi_ptt: Propagate DMA reset timeout in trace_start() (git-fixes).\n- i2c: core: fix debugfs UAF on adapter removal (git-fixes).\n- i2c: imx: fix locked bus on SMBus block-read of 0 (atomic) (git-fixes).\n- i2c: imx: separate atomic, dma and non-dma use case (stable-fixes).\n- i2c: mux: demux-pinctrl: fix OF node leak on kstrdup failure (git-fixes).\n- i2c: mux: Fix channel node leak on adapter add failure (git-fixes).\n- i2c: ocores: Disable clock on failed resume (git-fixes).\n- i3c: dw: avoid shift-out-of-bounds when DAA assigns no devices (git-fixes).\n- i3c: dw: rename \"pclk\" to \"apb\" to match dt-binding (git-fixes).\n- i3c: master: Fix device_register() error path (git-fixes).\n- i3c: master: Fix info leak and UAF in device unregister path (git-fixes).\n- i3c: master: Fix potential UAF in i3c_device_uevent() (git-fixes).\n- i3c: master: svc: bound IBI payload to the requested max_payload_len (git-fixes).\n- ieee802154: 6lowpan: fix NULL dereference in lowpan_newlink (git-fixes).\n- ieee802154: cc2520: fix FIFOP work use-after-free (git-fixes).\n- ieee802154: hwsim: serialize pib updates to fix double-free (git-fixes).\n- iio: accel: dmard09: Implement IIO_CHAN_INFO_SCALE (git-fixes).\n- iio: adc: max34408: add missing 'select REGMAP_I2C' to Kconfig (git-fixes).\n- iio: adc: pac1921: fix wrong channel used in trigger handler read (git-fixes).\n- iio: buffer: Fix potential use-after-free in anonymous buffer release (git-fixes).\n- iio: buffer: Make IIO DMA fence release RCU-safe (git-fixes).\n- iio: buffer: Tie IIO dma fence lock lifetime to the fence (git-fixes).\n- iio: chemical: atlas-sensor: fix PM reference leak in buffer postenable (git-fixes).\n- iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove UAF (git-fixes).\n- iio: chemical: sgp30: Handle IAQ thread creation failure (git-fixes).\n- iio: dac: m62332: Fix regulator reference count imbalance (git-fixes).\n- iio: gyro: mpu3050: fix sign of raw angular velocity readings (git-fixes).\n- iio: light: cm32181: return zero after writing calibscale (git-fixes).\n- iio: light: gp2ap002: Disable regulators on resume failure (git-fixes).\n- iio: light: gp2ap002: re-enable irq if runtime suspend fails (git-fixes).\n- iio: light: isl29028: return zero in write_raw() on success (git-fixes).\n- iio: light: ltrf216a: fix runtime PM reference leak in error path (git-fixes).\n- iio: light: opt4001: Fix incompatible pointer type passed to div_u64_rem() (git-fixes).\n- iio: light: opt4001: Fix power down clearing bits of the wrong register (git-fixes).\n- iio: light: opt4001: Fix reversed GENMASK() arguments in fault count mask (git-fixes).\n- iio: light: opt4001: Reject integration times with a non-zero seconds part (git-fixes).\n- iio: light: tsl2583: return zero in write_raw() on success (git-fixes).\n- iio: light: tsl2772: fix ALS calibscale readback (git-fixes).\n- iio: orientation: hid-sensor-rotation: Avoid race between callback setup and device exposure (git-fixes).\n- iio: pressure: dps310: fix NULL pointer dereference on ACPI probe (git-fixes).\n- iio: pressure: mpl115: Fix runtime PM cleanup (git-fixes).\n- iio: srf04: fix pm_runtime handling on probe error path (git-fixes).\n- iio: temperature: hid-sensor-temperature: switch to non-devm iio_device_register() (git-fixes).\n- Input: atkbd - skip deactivate for HONOR ZQC-P (git-fixes).\n- Input: atkbd - skip deactivate for Xiaomi Book Pro 14's internal keyboard (stable-fixes).\n- Input: cs40l50-vibra - validate custom data from user space (git-fixes).\n- Input: evdev - fix information leak in evdev_pass_values() (stable-fixes).\n- Input: evdev - sanitize event type index when fetching event masks (stable-fixes).\n- Input: focaltech - fix array out-of-bounds in focaltech_process_rel_packet (git-fixes).\n- Input: focaltech - use signed coordinates to prevent underflow (git-fixes).\n- Input: hynitron_cstxxx - validate touch count and finger IDs (git-fixes).\n- Input: iforce - validate input packet lengths (stable-fixes).\n- Input: iqs5xx - validate firmware record destination span (git-fixes).\n- Input: mms114 - fix Y-resolution configuration (git-fixes).\n- Input: psxpad-spi - set driver data before use (git-fixes).\n- Input: reject inhibit and uninhibit requests on unregistering devices (git-fixes).\n- Input: sur40 - fix input device registration ordering (stable-fixes).\n- Input: sur40 - fix V4L error path cleanup (stable-fixes).\n- Input: synaptics-rmi4 - block s_input when F54 queue is busy (git-fixes).\n- Input: synaptics-rmi4 - bound the F54 report size to the allocated buffer (git-fixes).\n- Input: synaptics-rmi4 - fix F55 transmitter electrode count typo (git-fixes).\n- Input: synaptics-rmi4 - propagate F54 worker errors to V4L2 queue (git-fixes).\n- Input: synaptics-rmi4 - zero report size on F54 work error (git-fixes).\n- Input: xpad - add support for ZENAIM LEVERLESS (stable-fixes).\n- interconnect: Fix use after free in icc_get() and of_icc_get_by_index() (git-fixes).\n- io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (git-fixes).\n- io_uring/net: Avoid msghdr on op_connect/op_bind async data (git-fixes).\n- iommu/arm-smmu-v3: Manage teardown with devm (stable-fixes).\n- ip_tunnel: Use ip_tunnel_info() helper instead of 'info + 1' (bsc#1274727).\n- ipmi: ipmb: validate write message length (git-fixes).\n- ipmi: si: Fix NULL pointer dereference after failed registration (git-fixes).\n- KVM: arm64: Ensure FFA ranges are page aligned (git-fixes).\n- KVM: arm64: Fix bounds checking in do_ffa_mem_reclaim() (git-fixes).\n- KVM: arm64: Fix sign-extension of MMIO loads (git-fixes).\n- KVM: arm64: vgic: Reset in_kernel on private IRQ allocation failure (git-fixes).\n- KVM: arm64: Zero out the stack initialized data in the FFA handler (git-fixes).\n- KVM: nSVM: Always inject a #GP if mapping VMCB12 fails on nested VMRUN (git-fixes).\n- KVM: nSVM: Remove a user-triggerable WARN on nested_svm_load_cr3() succeeding (git-fixes).\n- KVM: nVMX: Ensure KVM_REQ_GET_NESTED_STATE_PAGES is cleared on VM-Exit (git-fixes).\n- KVM: nVMX: Service local TLB flushes on failed nested VM-Enter (git-fixes).\n- KVM: PPC: Book3S HV: Add support for compat CPU capabilities for KVM on PowerNV (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM (bsc#1263864 ltc#217835).\n- KVM: PPC: Book3S HV: Validate arch_compat against host compatibility mode (bsc#1263864 ltc#217835).\n- KVM: PPC: Document KVM_PPC_GET_COMPAT_CAPS ioctl (bsc#1263864 ltc#217835).\n- KVM: PPC: Introduce KVM_CAP_PPC_COMPAT_CAPS and wire up ioctl (bsc#1263864 ltc#217835).\n- KVM: SEV: Use to_kvm_sev_info() for fetching kvm_sev_info struct (git-fixes).\n- KVM: SVM: Add support to initialize SEV/SNP functionality in KVM (bsc#1279887).\n- KVM: SVM: Explicitly mark vmcb01 dirty after modifying VMCB intercepts (git-fixes).\n- KVM: SVM: Serialize accesses to the owner and mirror list with separate lock (git-fixes).\n- KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active (git-fixes).\n- KVM: TDX: Account all non-transient page allocations for per-TD structures (git-fixes).\n- KVM: TDX: Fix x2APIC MSR handling in tdx_has_emulated_msr() (git-fixes).\n- KVM: VMX: Don't register posted interrupt wakeup handler if alloc_kvm_area() fails (git-fixes).\n- KVM: x86/hyperv: Check for NULL vCPU Hyper-V object in kvm_hv_get_tlb_flush_fifo() (git-fixes).\n- KVM: x86/hyperv: Ensure vCPU's Hyper-V object is initialized on cross-vCPU accesses (git-fixes).\n- KVM: x86/hyperv: Get target FIFO in hv_tlb_flush_enqueue(), not caller (git-fixes).\n- KVM: x86/mmu: Recover TDP MMU NX huge pages using MMU read lock (bsc#1271050).\n- KVM: x86/mmu: Rename kvm_tdp_mmu_zap_sp() to better indicate its purpose (bsc#1271050).\n- KVM: x86/mmu: Track possible NX huge pages separately for TDP vs. Shadow MMU (bsc#1271050).\n- KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears because it was cleared from the PIC (git-fixes).\n- KVM: x86: Don't WARN if IRQ disappears when Xen emulation is enabled (git-fixes).\n- KVM: x86: Fix array_index_nospec() protection in kvm_vcpu_ioctl_x86_set_mce() (git-fixes).\n- KVM: x86: Fix emulated CPUID features being applied to wrong sub-leaf (git-fixes).\n- KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock (git-fixes).\n- leds: pca9532: Fix inverted GPIO output polarity (git-fixes).\n- leds: pca9532: Fix phantom device registration on missing hardware (git-fixes).\n- lib/string: fix memchr_inv() for large ranges (git-fixes).\n- lib/ucs2_string.c: fix out-of-bounds read in ucs2_strnlen() (git-fixes).\n- mac802154: fix data race and NULL deref on local-\u003eassoc_dev (git-fixes).\n- mac802154: fix netdev use-after-free in beacon worker (git-fixes).\n- mac802154: fix use-after-free of sdata via queued RX frames (git-fixes).\n- mailbox: pcc: Fix command timeout due to missed interrupt (git-fixes).\n- mailbox: qcom-cpucp: fix PREEMPT_RT self-deadlock in IRQ handler (git-fixes).\n- mailbox: qcom-cpucp: handle NULL data in send_data callback (git-fixes).\n- mailbox: qcom-ipcc: fix duplicate channel allocation across holes (git-fixes).\n- mailbox: rockchip: disable pclk on probe failure and unbind (git-fixes).\n- maple_tree: fix argument name in header (git-fixes).\n- md/raid1: create serial pool adding rdev to array with serialize_policy=1 (bsc#1272261).\n- media: airspy: Return queued buffers on start_streaming() failure (git-fixes).\n- media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL deref (git-fixes).\n- media: amphion: Remove obsolete frame_count check in venc_start_session (git-fixes).\n- media: bcm2835-unicam: Fix asc leaked in error/remove path (git-fixes).\n- media: cec-pin: Fix event FIFO ordering (git-fixes).\n- media: cec: disable delayed work before freeing an interrupted transmit (git-fixes).\n- media: cec: extron-da-hd-4k-plus: add sanity check (git-fixes).\n- media: cec: meson: ao-cec-g12a: name the CEC core regmap to avoid debugfs clash (git-fixes).\n- media: cec: Serialize exclusive follower delivery (git-fixes).\n- media: cec: stm32: prevent out-of-bounds write on RX overflow (git-fixes).\n- media: cedrus: clean up media device on probe failure (git-fixes).\n- media: cedrus: fix memory leak in cedrus_init_ctrls() (git-fixes).\n- media: chips-media: wave5: Guard bit depth check with initial_info_obtained (git-fixes).\n- media: chips-media: wave5: Move src_buf Removal to finish_encode (git-fixes).\n- media: cobalt: Avoid freeing ALSA private data twice (git-fixes).\n- media: cx231xx: fix devres lifetime (git-fixes).\n- media: cx231xx: reject geometry changes while the VBI queue is busy (git-fixes).\n- media: cx23885: add ioremap return check and cleanup (git-fixes).\n- media: cx23885: cancel NetUP CI work before teardown (git-fixes).\n- media: em28xx: defer audio-only extension registration (git-fixes).\n- media: em28xx: fix use-after-free of dev_next-\u003edevlist on disconnect (git-fixes).\n- media: go7007: defer the ALSA v4l2 put until card release (git-fixes).\n- media: hevc: add bounded tile-count helpers (git-fixes).\n- media: i2c: alvium: fix critical pointer access in alvium_ctrl_init (git-fixes).\n- media: i2c: alvium: Fix: Correct name of register in alvium_set_ctrl_auto_exposure (git-fixes).\n- media: i2c: imx219: Rename VTS to FRM_LENGTH (stable-fixes).\n- media: i2c: imx415: Return test pattern write errors (git-fixes).\n- media: i2c: ov02a10: fix endpoint parsing use-after-free (git-fixes).\n- media: i2c: ov7740: fix use-after-destroy in remove (git-fixes).\n- media: i2c: rdacm21: Fix missing media_entity_cleanup() (git-fixes).\n- media: imx219: Fix maximum frame length in lines (git-fixes).\n- media: intel/ipu6: fix async notifier cleanup leak on parse error (git-fixes).\n- media: intel/ipu6: Improve DWC PHY HSFREQRANGE band selection for overlapping ranges (git-fixes).\n- media: ipu6: Do not free aux device pdata after init (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_HAUPPAUGE_NEW keymap define (git-fixes).\n- media: keymaps: Remove obsolete RC_MAP_RC5_TV keymap define (git-fixes).\n- media: mc-entity: Add missing kerneldoc (git-fixes).\n- media: mediatek: vcodec: bound AV1 tile-start copy to the array capacity (git-fixes).\n- media: meson: vdec: Fix memory leak in error path of vdec_open (git-fixes).\n- media: meson: vdec: fix NULL pointer deref in vdec_try_fmt_common (git-fixes).\n- media: msi2500: Return queued buffers on start_streaming() failure (git-fixes).\n- media: nuvoton: npcm-video: fix error handling in npcm_video_init() (git-fixes).\n- media: nuvoton: npcm-video: fix memory leaks in probe and remove (git-fixes).\n- media: nxp: imx8-isi: Add missing v4l2_subdev_cleanup() in crossbar and pipe (git-fixes).\n- media: nxp: imx8-isi: Clean up already-initialized pipes on probe failure (git-fixes).\n- media: nxp: imx8-isi: Correct color map between V4L2 and ISI (git-fixes).\n- media: nxp: imx8-isi: Fix missing v4l2_subdev_cleanup() in pipe init error path (git-fixes).\n- media: nxp: imx8-isi: Fix potential out-of-bounds issues (git-fixes).\n- media: nxp: imx8-isi: Fix scale factor calculation for hardware rounding (git-fixes).\n- media: nxp: imx8-isi: Fix stream ID validation bypass in crossbar routing (git-fixes).\n- media: nxp: imx8-isi: Use BIT_ULL() for 64-bit stream masks (git-fixes).\n- media: platform: exynos4-is: Add hardware sync wait to fimc_is_hw_change_mode() (stable-fixes).\n- media: platform: mtk-mdp3: fix NULL deref on failed SCP lookup (git-fixes).\n- media: platform: mtk-mdp3: Fix SCP device refcounting (git-fixes).\n- media: pwc: Drain fill_buf on start_streaming() failure (git-fixes).\n- media: pwc: Return queued buffers on start_streaming() failure (git-fixes).\n- media: qcom: camss: Fix RDI streaming for CSID GEN2 (git-fixes).\n- media: radio-si476x: Unregister v4l2_device on probe failure (git-fixes).\n- media: rc: sunxi-cir: Unregister rc device on probe failure (git-fixes).\n- media: rtl2832: fix use-after-free in rtl2832_remove() (git-fixes).\n- media: rtl2832_sdr: release URBs and stream buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: Return queued buffers on start_streaming() failure (git-fixes).\n- media: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA leak (git-fixes).\n- media: s2255: bound JPEG frame size before copying into the buffer (git-fixes).\n- media: s2255: check firmware size before reading trailing marker (git-fixes).\n- media: saa7134: Fix a possible memory leak in saa7134_video_init1 (git-fixes).\n- media: saa7164: fix cleanup on resource allocation failure (git-fixes).\n- media: stm32: dcmi: unregister notifier on probe failure (git-fixes).\n- media: sun4i-csi: Return queued buffers on start_streaming() failure (git-fixes).\n- media: tda18250: fix possible integer overflow (git-fixes).\n- media: tegra-video: vi: fix invalid u32 return value in format lookup (git-fixes).\n- media: usbtv: keep device alive while ALSA card exists (git-fixes).\n- media: v4l2-async: avoid deleting unlinked ASC entry on link error (git-fixes).\n- media: v4l2-async: Unregister sub-device if asc_list is empty (git-fixes).\n- media: v4l2-ctrls-request: add NULL check in v4l2_ctrl_request_complete() (git-fixes).\n- media: v4l2-ctrls: Allow unknown HDR10 white point and luminance (git-fixes).\n- media: v4l2-ctrls: validate AV1 tile counts (git-fixes).\n- media: v4l2-ctrls: validate HEVC tile counts (git-fixes).\n- media: v4l2-fwnode: Fix fwnode leak in v4l2_fwnode_parse_link (git-fixes).\n- media: v4l2-h264: Fix memcmp() size in B1 reference list comparison (git-fixes).\n- media: v4l2-subdev: Fail {enable,disable}_streams and s_streaming nicely (git-fixes).\n- media: venus: fix payload size calculation in parse_raw_formats() (git-fixes).\n- media: venus: fix payload size returned by parse_caps() and parse_alloc_mode() (git-fixes).\n- media: verisilicon: hantro: bound G2 HEVC tile loop to the buffer capacity (git-fixes).\n- media: verisilicon: rockchip: guard VPU981 AV1 divisor and tile buffer (git-fixes).\n- media: verisilicon: rockchip: reject AV1 frames exceeding the tile capacity (git-fixes).\n- media: vicodec: fix out-of-bounds write in FWHT encoder (git-fixes).\n- media: video-i2c: fix kthread error pointer left in kthread_vid_cap on failure (git-fixes).\n- media: vimc: fix pixel format lookup in enum_framesizes (git-fixes).\n- media: vivid: add vivid_update_reduced_fps() (git-fixes).\n- media: vivid: check for vb2_is_busy() when toggling caps (git-fixes).\n- media: vivid: fix cleanup bugs in vivid_init() (git-fixes).\n- media: zoran: Avoid freeing a registered video_device twice (git-fixes).\n- mei: pull kvfree out of spinlock (git-fixes).\n- mfd: iqs62x: Reject zero-length firmware records (git-fixes).\n- mfd: rave-sp: validate received frame payload lengths (git-fixes).\n- mfd: sm501: Fix potential memory leaks during remove (git-fixes).\n- misc: bcm-vk: Use acquire/release for msgq_inited (git-fixes).\n- misc: fastrpc: fix channel ctx ref leak when session alloc fails (git-fixes).\n- misc: fastrpc: fix memory leak in fastrpc_channel_ctx_free (git-fixes).\n- misc: fastrpc: Remove buffer from list prior to unmap operation (git-fixes).\n- misc: fastrpc: take fl-\u003elock when moving mmaps on interrupted invoke (git-fixes).\n- misc: nsm: bound the device-reported response length (git-fixes).\n- misc: rtsx: add missing write register handling (git-fixes).\n- misc: sgi-gru: remove interrupt-context page-table walks (git-fixes).\n- misc: vmc_vmci: Fix potential memory leak in vmci_event_subscribe() (git-fixes).\n- mkspec-dtb: Move DTS prefix into package list.\n- mkspec-dtb: Move provides-obsoletes to package list.\n- mkspec-dtb: Put per-architecture package lists into a hash.\n- mkspec-dtb: re-indent.\n- mmc: atmel-mci: Fix use-after-free in atmci_remove due to race condition (git-fixes).\n- mmc: omap_hsmmc: fix busy_timeout overflow in ns conversion on 32-bit (git-fixes).\n- mmc: sdhci: unmap the bounce buffer before device release (git-fixes).\n- mmc: via-sdmmc: stop card-detect handling on probe failure (git-fixes).\n- mtd: afs: validate v2 image info bounds (git-fixes).\n- mtd: fix double free and WARN_ON in add_mtd_device() error paths (git-fixes).\n- mtd: mtdoops: free page bitmap when the backing MTD is removed (git-fixes).\n- mtd: mtdswap: Avoid freeing registered blktrans device twice (git-fixes).\n- mtd: mtdswap: remove debugfs stats file on teardown (git-fixes).\n- mtd: nand: mtk-ecc: stop on ECC idle timeouts (git-fixes).\n- mtd: part: reject MTDPART_OFS_RETAIN in mtd_add_partition() (git-fixes).\n- mtd: rawnand: validate ONFI extended parameter page sections (git-fixes).\n- mtd: spinand: fix direct mapping creation sizes (stable-fixes).\n- mtd: spinand: repeat reading in regular mode if continuous reading fails (stable-fixes).\n- mtd: spinand: try a regular dirmap if creating a dirmap for continuous reading fails (stable-fixes).\n- mtd: ubi: Release device reference on busy detach (git-fixes).\n- mtd: ubi: skip programming unused bits in ubi headers (stable-fixes).\n- net: Add options as a flexible array to struct ip_tunnel_info (bsc#1274727).\n- net: mana: Add debug knob to skip TX timeout recovery reset (git-fixes).\n- net: mana: Add handler for sriov configure (bsc#1272756).\n- net: mana: Cap MSI-X vectors to the device MSI-X table size (git-fixes).\n- net: mana: Extend RX CQE coalescing up to 8 packets (git-fixes).\n- net: mana: Fall back to scattered pages for GDMA queues (git-fixes).\n- net: mana: force full-page RX buffers via ethtool private flag (bsc#1269792).\n- net: mana: refactor mana_get_strings() and mana_get_sset_count() to use switch (bsc#1269792).\n- net: mana: Route ring-buffer access through offset-based helpers (git-fixes).\n- net: tap: set skb-\u003edev before parsing virtio net header in tap_get_user_xdp() (git-fixes bsc#1274550).\n- net: thunderbolt: Count delivered packets in rx_packets and rx_bytes (git-fixes).\n- net: thunderbolt: Mark the connection down when bringing it up fails (git-fixes).\n- net: thunderbolt: Release the Rx HopID that was handed out on mismatch (git-fixes).\n- net: thunderbolt: Tear down DMA paths before stopping the rings (git-fixes).\n- net: usb: ax88179_178a: fix skb leak in ax88179_tx_fixup() (git-fixes).\n- net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow (git-fixes).\n- net: usb: ipheth: fix carrier_work UAF on disconnect (git-fixes).\n- net: usb: qmi_wwan: add Telit Cinterion FE990D50 composition (git-fixes).\n- nfc: digital: clamp SENSF_RES length to the destination buffer (git-fixes).\n- nfc: digital: Do not dump a NULL response in command completion (git-fixes).\n- nfc: fdp: bound the device-reported read length and fix an skb leak (git-fixes).\n- nfc: llcp: avoid userspace overflow on invalid optlen (git-fixes).\n- nfc: llcp: bound SNL TLV parsing to the skb and add length checks (git-fixes).\n- nfc: llcp: bound the connect_sn TLV walk to the skb (git-fixes).\n- nfc: llcp: fix OOB read and u8 offset wrap in TLV parsers (git-fixes).\n- nfc: llcp: read llcp_sock-\u003elocal under the socket lock in getsockopt (git-fixes).\n- nfc: llcp: reject PDUs shorter than the LLCP header (git-fixes).\n- nfc: microread: validate target discovery payload lengths (git-fixes).\n- nfc: nci: fix double completion race in nci_data_exchange_complete (git-fixes).\n- nfc: nci: fix out-of-bounds write in nci_target_auto_activated() (git-fixes).\n- nfc: nci: fix uninit-value in the RF discover/activated NTF handlers (git-fixes).\n- nfc: nci: fix use of uninitialized memory in CORE_INIT_RSP parsing (git-fixes).\n- nfc: nci: free destination parameters when closing a connection (git-fixes).\n- nfc: pn533: hold a reference to the request skb during send_frame (git-fixes).\n- nfc: pn533: purge fragmented skbs during cleanup (git-fixes).\n- nfc: st21nfca: validate ATR_REQ length against the received frame (git-fixes).\n- nouveau/gem: reserve the bo in the info ioctl around the vma lookup (git-fixes).\n- nvme-tcp: fix usage of page_frag_cache (bsc#1267882).\n- nvmet-rdma: fix queue leak when connect backlog is exceeded (git-fixes).\n- of: fix out-of-bounds read in of_alias_scan() stem parser (git-fixes).\n- PCI/ASPM: Use pcie_capability_clear_and_set_word() for ASPM disable/restore (git-fixes).\n- PCI/proc: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI/proc: Use file_ns_capable() when checking config space read access (git-fixes).\n- PCI/proc: Warn on writes to kernel-exclusive config space regions (git-fixes).\n- PCI/sysfs: Avoid spurious runtime PM wakeup on config space accesses (git-fixes).\n- PCI: Add ACS quirk for Pericom PI7C9X2G608 switches [12d8:2608] (git-fixes).\n- PCI: hv: Set irq_retrigger callback for the Hyper-V PCI MSI irqchip (git-fixes).\n- PCI: j721e: Fix incorrect max_lanes for J7200 (git-fixes).\n- PCI: meson: Fix GPIO state while requesting PERST# (git-fixes).\n- PCI: plda: Fix IRQ domain leaks in the error paths of plda_init_interrupts() (git-fixes).\n- PCI: plda: Fix use-after-free of event IRQs during teardown (git-fixes).\n- perf: Reject exited events as group leaders (git-fixes).\n- pinctrl: bcm2835: Don't remove an unregistered GPIO chip (git-fixes).\n- pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip (git-fixes).\n- pinctrl: rockchip: Reset the pin count when recalculating SoC data (git-fixes).\n- platform/chrome: cros_ec_debugfs: Clean up console log on probe failure (git-fixes).\n- platform/chrome: cros_ec_debugfs: Unregister panic notifier (git-fixes).\n- platform/chrome: cros_ec_typec: Reject out-of-bounds PD cap count (git-fixes).\n- platform/chrome: sensorhub: Bound the EC-reported sensor number (git-fixes).\n- platform/chrome: sensorhub: Fix dropped timestamp events and log spam (git-fixes).\n- platform/chrome: sensorhub: Fix memory overread in ring handler (git-fixes).\n- platform/mellanox: mlxbf-pmc: Check ACPI_COMPANION() against NULL (git-fixes).\n- platform/surface: acpi-notify: Check ACPI companion before use (git-fixes).\n- platform/x86/amd/hsmp: Reject negative power cap writes in hwmon (git-fixes).\n- platform/x86: asus-wmi: fix resource leaks on probe failure (git-fixes).\n- platform/x86: dell-privacy: Fix race condition (git-fixes).\n- platform/x86: dell-wmi-base: Fix resource leak on module load failure (git-fixes).\n- platform/x86: dell-wmi-sysman: Don't hex dump attribute security buffer (git-fixes).\n- platform/x86: dell-wmi-sysman: Fix instance ID bounds (git-fixes).\n- platform/x86: hp-bioscfg: accept reduced ACPI packages from older HP BIOS (git-fixes).\n- platform/x86: hp-bioscfg: advance elem past consumed array elements (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read in sk_store() and kek_store() (git-fixes).\n- platform/x86: hp-bioscfg: fix heap OOB read on empty password write (git-fixes).\n- platform/x86: hp-bioscfg: fix new_password_store() overwriting current_password (git-fixes).\n- platform/x86: hp-bioscfg: fix off-by-one write in hp_get_string_from_buffer() (git-fixes).\n- platform/x86: hp-bioscfg: fix ORD_LIST_ELEMENTS never being parsed (git-fixes).\n- platform/x86: hp-bioscfg: fix password encoding bounds check (git-fixes).\n- platform/x86: hp-bioscfg: warn on element type mismatch instead of failing (git-fixes).\n- platform/x86: ishtp_eclite: Fix ACPI device reference leak in probe error path (git-fixes).\n- platform/x86: ISST: Add a NULL check for sst_inst (git-fixes).\n- platform/x86: ISST: Just allow 2 bits for SST feature enable (git-fixes).\n- platform/x86: ISST: Return error during profile addition (git-fixes).\n- platform/x86: ISST: Use PP level enable mask (git-fixes).\n- platform/x86: ISST: Validate level in perf mask ioctls (git-fixes).\n- platform/x86: ISST: Validate logical CPU id and clos id (git-fixes).\n- platform/x86: ISST: Validate parameter for core power state (git-fixes).\n- platform/x86: ISST: Validate parameter for frequency and priority (git-fixes).\n- platform/x86: ISST: Validate socket ID in clos_assoc ioctl (git-fixes).\n- PM: hibernate: Fix memory leak in snapshot_write_next() error path (git-fixes).\n- PM: sleep: Fix off-by-one in wakelocks number limit check (git-fixes).\n- power: supply: bd99954: Drop bad register fields (git-fixes).\n- power: supply: bq27xxx: bq27z561: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq28z610: fix invalid AverageEnergy address (git-fixes).\n- power: supply: bq27xxx: bq27520g4: fix REG_TTES address (git-fixes).\n- power: supply: bq256xx: drain usb_work before freeing the charger (git-fixes).\n- power: supply: bq24257: fix use-after-free on remove (git-fixes).\n- power: supply: bq25890: Fix power_supply reference leak (git-fixes).\n- power: supply: charger-manager: register regulators before exposing sysfs (git-fixes).\n- power: supply: cros_usbpd-charger: bound the EC-reported port count (git-fixes).\n- power: supply: cros_usbpd: Limit port counts to EC_USB_PD_MAX_PORTS (git-fixes).\n- power: supply: isp1704_charger: cancel work on remove (git-fixes).\n- power: supply: lp8727: fix use-after-free in lp8727_release_irq() (git-fixes).\n- power: supply: lp8788-charger: fix use-after-free on remove (git-fixes).\n- power: supply: max17040: drop incorrect I2C functionality check (git-fixes).\n- power: supply: max17040: propagate register read errors (git-fixes).\n- power: supply: max17040: synchronize work cancellation on suspend (git-fixes).\n- power: supply: qcom_battmgr: terminate the strings from firmware (git-fixes).\n- power: supply: rt9455: quiesce delayed work before teardown (git-fixes).\n- power: supply: sbs-battery: Use a per-device serial number buffer (git-fixes).\n- power: supply: sc2731_charger: cancel work on remove (git-fixes).\n- power: supply: twl4030_charger: cancel workers via devm (git-fixes).\n- power: supply: ucs1002: fix use-after-free on remove (git-fixes).\n- powercap: intel_rapl_tpmi: Handle PMU registration failure during probe (git-fixes).\n- powerpc/dt_cpu_ftrs: Set CPU_FTR_P11_PVR for Power11 and later processors (bsc#1263864 ltc#217835).\n- powerpc/kexec_file: Use inclusive range checks in add_usable_mem() (git-fixes).\n- powerpc/pseries: Ensure vpa,slb_shadow \u0026 dtl are unregistered during crash (bsc#1271256).\n- powerpc/pseries: lparcfg - fix kbuf[] underflow (bsc#1274753 ltc#221289 bsc#1274754 ltc#221288 bsc#1274752\n  ltc#221290).\n- powerpc/pseries: papr-phy-attest - validate cmd.length, plug mem leak (bsc#1274751 ltc#221105 bsc#1274750 ltc#221106).\n- powerpc/pseries: pci - logic bug (bsc#1274749 ltc#221282 bsc#1274755 ltc#221284 bsc#1274756 ltc#221283).\n- powerpc/rtas_pci: No hotplug on permanently removed device on pSeries (git-fixes).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in non-uapi headers (bsc#1263864 ltc#217835).\n- powerpc: Replace __ASSEMBLY__ with __ASSEMBLER__ in uapi headers (bsc#1263864 ltc#217835).\n- ppdev: prevent overflow when setting port timeout (git-fixes).\n- rapidio/tsi721: prevent a bad dereference in tsi721_db_dpc() (git-fixes).\n- rapidio: clear mport-\u003enet when rio_add_net() fails (git-fixes).\n- rapidio: mport_cdev: fix use-after-free in dma_req_free() (git-fixes).\n- RDMA/bnxt_re: Avoid displaying the kernel pointer (git-fixes).\n- RDMA/bnxt_re: Proper rollback if the ioremap fails (git-fixes).\n- RDMA/irdma: Remove redundant legacy_mode checks (git-fixes).\n- RDMA/mana_ib: drain QP references after partial table insertion (git-fixes).\n- RDMA/mana_ib: unify QP lookup table (git-fixes).\n- RDMA/mlx5: Fix integer overflow of user QP buffer size (git-fixes).\n- regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving dangling of_node pointer (git-fixes).\n- regulator: core: use system_freezable_wq for init complete work (git-fixes).\n- regulator: max8998_pmic_dt_parse_pdata: of_node_put on reg_np after ownership transferred to rdata (git-fixes).\n- regulator: qcom-refgen: correct the regulator type to CURRENT (git-fixes).\n- regulator: qcom-rpmh: Fix PMIC5 BOB bypass mode handling (git-fixes).\n- remoteproc: qcom: Fix glink-\u003enode reference leak in qcom_add_glink_subdev (git-fixes).\n- remoteproc: qcom_q6v5_adsp: Fix reference leak for device node (git-fixes).\n- remoteproc: scp: Fix device reference leak on failed lookup (git-fixes).\n- Revert \"drm/amdgpu: fix aperture mapping leak\" (git-fixes).\n- Revert \"media: v4l2-dev: fix error handling in __video_register_device()\" (git-fixes).\n- Revert \"net: thunderbolt: Enable end-to-end flow control also in transmit\" (git-fixes).\n- Revert \"thermal/drivers/hwmon: Cleanup coding style a bit\" (stable-fixes).\n- Revert \"wifi: mt76: Disable napi when removing device\" (git-fixes).\n- rpmsg: core: Fix incorrect return value documentation (git-fixes).\n- rpmsg: glink: smem: order FIFO read after availability check (git-fixes).\n- rtc: gamecube: check return value of devm_rtc_register_device() (git-fixes).\n- rtc: pcf8563: fix clock provider leak on unbind (git-fixes).\n- rtc: pcf85363: Add error checking to regmap calls in probe() (git-fixes).\n- rtc: rzn1: Disable alarm interrupt before reprogramming alarm registers (git-fixes).\n- rtc: rzn1: Fix weekday underflow when alarm crosses month boundary (git-fixes).\n- rtc: zynqmp: Return optional clock lookup errors (git-fixes).\n- s390/pkey: Check length in pkey_pckmo handler implementation (bsc#1270266).\n- s390/pkey: Check length in PKEY_VERIFYPROTK ioctl (bsc#1270267).\n- sched/psi: Create the psimon kthread outside of cgroup_mutex (bsc#1269134).\n- scsi: fnic: Abort timed-out NVMe LS requests (bsc#1236344).\n- scsi: fnic: Add and improve logs in FDMI and FDMI ABTS paths (bsc#1236344).\n- scsi: fnic: Add FDLS role handling for NVMe initiators (bsc#1236344).\n- scsi: fnic: Add the NVMe/FC transport path (bsc#1236344).\n- scsi: fnic: Advertise NVMe initiator service parameters (bsc#1236344).\n- scsi: fnic: Bump up version number (bsc#1236344).\n- scsi: fnic: Decode firmware role configuration (bsc#1236344).\n- scsi: fnic: Do not use GFP_ZERO for mempools (bsc#1236344).\n- scsi: fnic: Expose NVMe transport state in debugfs (bsc#1236344).\n- scsi: fnic: Handle NVMe LS frames in FDLS (bsc#1236344).\n- scsi: fnic: Make debug logging protocol independent (bsc#1236344).\n- scsi: fnic: Make fnic_queuecommand() easier to analyze (bsc#1236344).\n- scsi: fnic: Refactor in_remove flag and call to fnic_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Remove a useless struct mempool forward declaration (bsc#1236344).\n- scsi: fnic: Rename fnic_scsi_fcpio_reset() (bsc#1236344).\n- scsi: fnic: Route completions and resets by initiator role (bsc#1236344).\n- scsi: fnic: Self-assignment of intr_time_type has no effect (bsc#1236344).\n- scsi: fnic: Send NVMe LS requests through FDLS (bsc#1236344).\n- scsi: fnic: Switch to use %ptSp (bsc#1236344).\n- scsi: fnic: Track NVMe transport statistics (bsc#1236344).\n- scsi: fnic: Use fnic_num for non-SCSI identifiers (bsc#1236344).\n- scsi: fnic: Use mempool for receive frames (bsc#1236344).\n- scsi: qla2xxx: Add support to report MPI FW state (bsc#1275737).\n- scsi: qla2xxx: Declare qla2xxx_mqueuecommand() static (bsc#1275737).\n- scsi: qla2xxx: Use nr_cpu_ids instead of NR_CPUS for qp_cpu_map allocation (bsc#1275737).\n- scsi: storvsc: Support manual scans for all Hyper-V targets (git-fixes).\n- sctp: avoid auth_enable sysctl UAF during netns teardown (git-fixes).\n- selftests/alsa: Fix the step check for INTEGER controls (git-fixes).\n- serial: 8250_dma: Clear stale RX state on shutdown (git-fixes).\n- serial: amba-pl011: unprepare console clock on unregister (git-fixes).\n- serial: core: clear freed pointers on uart_register_driver() failure (git-fixes).\n- serial: imx: serialize imx_uart_ports lifetime (git-fixes).\n- serial: ma35d1: Fix OF node reference leaks in console init (git-fixes).\n- serial: qcom-geni: do not advance stale DMA completions (git-fixes).\n- serial: qcom-geni: fix TX DMA buffer flush (git-fixes).\n- serial: sc16is7xx: enable THRI before filling TX FIFO (git-fixes).\n- serial: sc16is7xx: rename EFR mutex with generic name (stable-fixes).\n- serial: sc16is7xx: use guards for simple mutex locks (stable-fixes).\n- slab.h: disable completely broken overflow handling in flex allocations (bsc#1280139).\n- slab: Introduce kmalloc_flex() and family (bsc#1280139).\n- slab: Introduce kmalloc_obj() and family (bsc#1280139).\n- slab: recognize @GFP parameter as optional in kernel-doc (bsc#1280139).\n- smb/client: handle overlapping allocated ranges in fallocate (bsc#1274902).\n- smb: client: harden POSIX SID length parsing (bsc#1273557).\n- smb: client: require net admin for CIFS SWN netlink (bsc#1273966).\n- smb: client: resolve SWN tcon from live registrations (bsc#1273872).\n- soc: fsl: qe: check platform_driver_register() in qe_ic_of_init() (git-fixes).\n- soc: qcom: rpmh-rsc: manage PM notifiers with devres (git-fixes).\n- soc: samsung: exynos-pmu: fix of_node refcount leak in exynos_get_pmu_regmap() (git-fixes).\n- software node: Fix software_node_get_reference_args() with index -1 (git-fixes).\n- soundwire: qcom: Fix port exhaustion check in stream_alloc_ports (git-fixes).\n- speakup: keyhelp: guard letter_offsets possible out-of-range indexing (git-fixes).\n- spi: bcm63xx-hsspi: disable clocks on resume failure (git-fixes).\n- spi: bcm63xx: disable clock on resume failure (git-fixes).\n- spi: bcmbca-hsspi: disable clocks on resume failure (git-fixes).\n- spi: davinci: switch to managed controller allocation (git-fixes).\n- spi: Fix DMA mapping ownership on partial map failure (git-fixes).\n- spi: img-spfi: don't disable runtime PM on DMA deferred probe (git-fixes).\n- spi: oc-tiny: switch to managed controller allocation (git-fixes).\n- spi: spi-cadence: enable SPI_CONTROLLER_MUST_TX (git-fixes).\n- spi: spi-cadence: Move TX FIFO full busy-wait into FIFO (git-fixes).\n- spi: spi-cadence: supports transmission with bits_per_word of 16 and 32 (stable-fixes).\n- spi: spi-fsl-dspi: Avoid setup_accel logic for DMA transfers (stable-fixes).\n- spi: sprd-adi: Fix probe succeeding without registering the controller (git-fixes).\n- staging: fbtft: Use sysfs_emit_at() to print to sysfs file (git-fixes).\n- staging: media: tegra-video: fix of_node_put() on VIP parse errors (git-fixes).\n- staging: media: tegra-video: vi: fix probe failure on skipped last port (git-fixes).\n- staging: octeon: add missing tasklet_kill in cvm_oct_tx_shutdown (git-fixes).\n- staging: rtl8723bs: fix mismatched free of HalData in rtw_sdio_if1_init() (git-fixes).\n- staging: rtl8723bs: fix missing shared-key auth challenge length check (git-fixes).\n- staging: rtl8723bs: fix OOB read / stack overflow in rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_action_frame_parse() (git-fixes).\n- staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() (git-fixes).\n- staging: rtl8723bs: fix OOB read in WMM_param_handler() (git-fixes).\n- staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr() (git-fixes).\n- staging: rtl8723bs: use kfree_sensitive() for key material (git-fixes).\n- staging: rtl8723bs: validate monitor transmit frame lengths (git-fixes).\n- staging: sm750fb: Add missing Kconfig dependency (git-fixes).\n- staging: sm750fb: gate dualview dataflow using g_dualview (git-fixes).\n- thermal/drivers/imx: Disable clock on runtime resume failure (git-fixes).\n- thermal/drivers/qoriq: Disable clock on resume failure (git-fixes).\n- thermal/drivers/rcar: Fix error checking in probe() (git-fixes).\n- thermal: intel: int3400: clean up ODVP on probe failures (git-fixes).\n- thermal: sysfs: switch to use scnprintf() to suppress truncation warning (git-fixes).\n- thunderbolt: Bound the DROM dual link port number before indexing sw-\u003eports (git-fixes).\n- thunderbolt: Fix bandwidth group reservation indexing (git-fixes).\n- thunderbolt: icm: Preserve USB4 proxy data-valid bit (git-fixes).\n- tlclk: if sscanf() fails, fall back to 0, not random value (git-fixes).\n- tpm: st33zp24: Return zero on status read failure (git-fixes).\n- tpm: st33zp24: Validate locality read result (git-fixes).\n- tpm: tpm_i2c_nuvoton: disable IRQ on wait timeout (git-fixes).\n- tty: clear cdev pointer after cdev_add() failure (git-fixes).\n- tty: hvc: restrict HVC_DCC to ARMv6+ and ARM64 (git-fixes).\n- tty: skip cdev_del() when no cdev is registered (git-fixes).\n- uio: Fix stale info pointer in failed registration path (git-fixes).\n- usb: atm: cxacru: properly kill rcv_urb on error in cxacru_cm() (git-fixes).\n- usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect (git-fixes).\n- usb: atm: usbatm: fix invalid ci_range initialization (git-fixes).\n- USB: c67x00: fix use-after-free in c67x00_add_iso_urb() (git-fixes).\n- usb: cdnsp: fix incorrect endian conversions for APB timeout register (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (git-fixes).\n- usb: core: Add lock to usb_wakeup_notification() (stable-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (git-fixes).\n- usb: core: Strengthen error handling in hub_hub_status() (stable-fixes).\n- usb: core: sysfs: add lock to bos_descriptors_read() (stable-fixes).\n- usb: dwc2: add missing @remotewakeup kernel-doc parameter (git-fixes).\n- usb: dwc2: gadget: Exit partial power down state when changing USB pull-up (git-fixes).\n- usb: dwc3: clear forceRM when issuing EndTransfer (git-fixes).\n- usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition (git-fixes).\n- usb: f_mass_storage: Bump local buffer size in fsg_common_create_luns() (git-fixes).\n- usb: fix UAF when probe runs concurrent to dyn ID removal (git-fixes).\n- usb: gadget: aspeed_udc: check endpoint DMA allocation (git-fixes).\n- usb: gadget: at91_udc: drain polled-VBUS timer/work before udc is freed (git-fixes).\n- usb: gadget: configfs: fix out-of-bounds read of qw_sign (git-fixes).\n- usb: gadget: f_fs: Fix fence cleanup in ffs_dmabuf_transfer() error paths (git-fixes).\n- usb: gadget: f_fs: Prevent deadlock during ep0 read loop (git-fixes).\n- usb: gadget: f_midi: initialize work in f_midi_alloc() (git-fixes).\n- usb: gadget: f_ncm: Use unsigned int for ndp_index (git-fixes).\n- usb: gadget: f_tcm: fix deadlock in usbg_make_tpg() (git-fixes).\n- usb: gadget: f_uac1_legacy: remove broken string configfs attributes (git-fixes).\n- usb: gadget: fix null pointer dereference in usb_put_function_instance() (git-fixes).\n- USB: gadget: fsl-udc: fix dev_printk() device (git-fixes).\n- usb: gadget: midi2: Fix null-pointer dereference in f_midi2_free_ep_reqs (git-fixes).\n- usb: gadget: midi2: remove default configfs groups on teardown (git-fixes).\n- usb: gadget: pch_udc: remove excess kernel-doc member for registered (git-fixes).\n- usb: gadget: r8a66597: avoid double free of ep0_req in probe error path (git-fixes).\n- usb: gadget: snps_udc_plat: clean up PHY on probe deferral (git-fixes).\n- usb: gadget: u_audio: Fix use-after-free on sound card disconnect (git-fixes).\n- usb: gadget: uac: validate rate list length before storing (git-fixes).\n- USB: gadget: Use str_enable_disable-like helpers (stable-fixes).\n- usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and uvc_function_unbind() (git-fixes).\n- usb: ljca: bound bank_num in ljca_enumerate_gpio() (git-fixes).\n- usb: mtu3: allow system suspend during active gadget connection (git-fixes).\n- usb: musb: omap2430: clean up probe error handling (stable-fixes).\n- usb: musb: omap2430: Do not put borrowed of_node in probe (git-fixes).\n- usb: musb: omap2430: Fix use-after-free in omap2430_probe() (git-fixes).\n- USB: phy: fsl-usb: fix missing static keywords (git-fixes).\n- usb: renesas_usbhs: Fix power-off ordering on unbind (git-fixes).\n- USB: serial: digi_acceleport: fix port registration order (git-fixes).\n- USB: serial: ftdi_sio: add support for E+H FXA291 (stable-fixes).\n- USB: serial: option: add TDTECH MT5710-CN (stable-fixes).\n- USB: serial: option: fix slab OOB read in interrupt URB callback (git-fixes).\n- USB: serial: spcp8x5: drop broken carrier detect support (git-fixes).\n- USB: storage: add NO_ATA_1X quirk for Longmai USB Key (stable-fixes).\n- usb: typec: qcom-pmic-typec: disable cc_debounce_dwork on stop (git-fixes).\n- usb: typec: qcom-pmic-typec: drain cc_debounce_dwork if port_start() fails (git-fixes).\n- usb: typec: qcom-pmic: cancel reset_work on stop (git-fixes).\n- usb: typec: tcpci: pass correct rx_type to tcpm_pd_receive() (git-fixes).\n- usb: typec: thunderbolt: Disable work before freeing tbt on remove (git-fixes).\n- usb: typec: ucsi: displayport: Fix OOB altmode array index (git-fixes).\n- usb: typec: ucsi: unregister debugfs entries on teardown (git-fixes).\n- usb: typec: ucsi: use UCSI_TIMEOUT_MS for sync command completion (git-fixes).\n- usb: usbfs: fix use-after-free of usb_device in usbdev_release() (git-fixes).\n- usb: usbtest: disable dynamic ID support (stable-fixes).\n- usb: xhci: Handle USB3 port events when there is one roothub (git-fixes).\n- vfs: Add a sysctl for automated deletion of dentry (bsc#1240890 bsc#1276586).\n- vt: add permission check for KDSKBMETA ioctl (stable-fixes).\n- vt: stabilize tty reference in kbd_keycode with tty_port_tty_get (stable-fixes).\n- w1: ds28e17: reject an oversize length on an I2C block read (git-fixes).\n- w1: ds2482: Fix signedness bug in ds2482_w1_triplet() (git-fixes).\n- watchdog: bd96801_wdt: Fix timeout for enabled WDG (git-fixes).\n- watchdog: fix hrtimer start when pretimeout is zero (git-fixes).\n- watchdog: msc313e: Avoid division by zero (git-fixes).\n- watchdog: msc313e: Enable clock before accessing hardware registers (git-fixes).\n- watchdog: msc313e: Fix clock leak and spurious timer in settimeout() (git-fixes).\n- watchdog: msc313e: Fix NULL pointer dereference in PM callbacks (git-fixes).\n- watchdog: msc313e: Fix spurious reset on suspend (git-fixes).\n- watchdog: msc313e: Fix undefined behavior (git-fixes).\n- watchdog: msc313e: Sync timeout value if WDT was running at boot (git-fixes).\n- watchdog: sunxi_wdt: preserve boot-enabled watchdog (git-fixes).\n- wifi: ath6kl: avoid buffer overreads in WMI event handlers (git-fixes).\n- wifi: ath6kl: clamp assoc request/response lengths before subtracting IE offsets (git-fixes).\n- wifi: ath10k: snoc: use memcpy_fromio() for MSA ramdump (git-fixes).\n- wifi: ath11k: Avoid buffer overread in ath11k_wmi_tlv_op_rx() (git-fixes).\n- wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate (git-fixes).\n- wifi: ath11k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: ath11k: fix overreads in ath11k_wmi_process_csa_switch_count_event() (git-fixes).\n- wifi: ath12k: Avoid buffer overread in ath12k_wmi_op_rx() (git-fixes).\n- wifi: ath12k: Correctly copy the hint BSSID in WMI scan request (git-fixes).\n- wifi: brcmfmac: Fix memory leak in brcmf_sdio_read_control() (git-fixes).\n- wifi: brcmfmac: fix P2P action frame handling without device vif (git-fixes).\n- wifi: brcmfmac: initialize SDIO data work before cleanup (git-fixes).\n- wifi: cfg80211: bound element ID read when checking non-inheritance (git-fixes).\n- wifi: cfg80211: cancel sched scan results work on unregister (git-fixes).\n- wifi: cfg80211: derive S1G beacon TSF from S1G fields (git-fixes).\n- wifi: cfg80211: reject unsupported PMSR FTM location requests (git-fixes).\n- wifi: cfg80211: validate PMSR FTM preamble range (git-fixes).\n- wifi: cfg80211: validate PMSR measurement type data (git-fixes).\n- wifi: ipw2100: fix potential memory leak in ipw2100_pci_init_one() (git-fixes).\n- wifi: iwlwifi: fix counter type in iwl_fwrt_dump_error_logs (git-fixes).\n- wifi: iwlwifi: guard against division by zero in iwl_dbg_tlv_alloc_fragments (git-fixes).\n- wifi: iwlwifi: mei: check SAP message length before reading it (git-fixes).\n- wifi: iwlwifi: mei: pass correct argument to function (git-fixes).\n- wifi: iwlwifi: mvm: fix off-by-one in TXF key sanitiser (git-fixes).\n- wifi: libertas: fix memory leak in helper_firmware_cb() (git-fixes).\n- wifi: mac80211: disconnect on CSA to channel 0 (git-fixes).\n- wifi: mac80211: fix fils_discovery double free on alloc failure (git-fixes).\n- wifi: mac80211: fix per-STA profile length in cross-link CSA parsing (git-fixes).\n- wifi: mac80211: fix unsol_bcast_probe_resp double free on alloc failure (git-fixes).\n- wifi: mac80211: free AP_VLAN bc_buf SKBs outside IRQ lock (git-fixes).\n- wifi: mac80211: send TWT teardown to peer after setup TX failure (git-fixes).\n- wifi: mac80211: skip default WMM setup for AP_VLAN links (git-fixes).\n- wifi: mac80211: skip unused probe response countdown offsets (git-fixes).\n- wifi: mt76: check txfree done event on the WED hw path (git-fixes).\n- wifi: mt76: fix 4th chain ACK RSSI bitmask in sta_poll (git-fixes).\n- wifi: mt76: fix ER-SU 106-tone RU check in RX rate decode (git-fixes).\n- wifi: mt76: fix HE DCM max-RU capability encoding (git-fixes).\n- wifi: mt76: fix non-AQL packet accounting for MLO stations (git-fixes).\n- wifi: mt76: fix stranded frames in mt76_txq_schedule_pending (git-fixes).\n- wifi: mt76: mt76x02: do not WARN on invalid rx descriptor length (git-fixes).\n- wifi: mt76: mt792x: Fix memory leak in SDIO TX path (git-fixes).\n- wifi: mt76: mt792x: fix use-after-free in mt76_rx_poll_complete (git-fixes).\n- wifi: mt76: mt7615: avoid waiting for mac work under the mt76 mutex (git-fixes).\n- wifi: mt76: mt7915: avoid nss underflow in mt7915_mcu_get_sta_nss (git-fixes).\n- wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear (git-fixes).\n- wifi: mt76: mt7915: fix double hif2 init on the non-WED path (git-fixes).\n- wifi: mt76: mt7915: fix ext PHY use-after-free on register error path (git-fixes).\n- wifi: mt76: mt7915: fix net_fill_forward_path for non-DBDC mt7986 (git-fixes).\n- wifi: mt76: mt7915: poll the correct SLP CTRL register for the second adie (git-fixes).\n- wifi: mt76: mt7915: release hif2 reference on probe IRQ failure (git-fixes).\n- wifi: mt76: mt7915: unlink TWT flow if the MCU rejects the agreement (git-fixes).\n- wifi: mt76: mt7915: unwind state on add_interface failure (git-fixes).\n- wifi: mt76: mt7915: use little-endian for bss_info_ra wire fields (git-fixes).\n- wifi: mt76: mt7915: write RX header translation bit to the correct register (git-fixes).\n- wifi: mt76: mt7921: skip unknown CLC firmware records (git-fixes).\n- wifi: mt76: mt7921: validate CLC firmware records (git-fixes).\n- wifi: mt76: mt7925: ensure tx headroom in usb_sdio_tx_prepare_skb (git-fixes).\n- wifi: mt76: mt7925: fix msg len mismatch between driver and firmware (git-fixes).\n- wifi: mt76: mt7925: update clc before setting sar power table (git-fixes).\n- wifi: mt76: mt7996: bound TLV walk in mt7996_mcu_get_chip_config (git-fixes).\n- wifi: mt76: mt7996: don't report a zero TX bitrate (git-fixes).\n- wifi: mt76: mt7996: fix capability of EHT-MCS 15 in MRU (git-fixes).\n- wifi: mt76: mt7996: fix reg addr remap when addr is 0 (git-fixes).\n- wifi: mt76: mt7996: reserve space for the CSA-abort countdown TLV (git-fixes).\n- wifi: mt76: mt7996: set MT76_MCU_RESET before waking MCU waiters on full reset (git-fixes).\n- wifi: mt76: mt7996: validate RX band_idx before dereferencing phys (git-fixes).\n- wifi: mt76: only consume the WO drop bit on WED v2 devices (git-fixes).\n- wifi: mt76: report data NSS for STBC frames in RX rate decode (git-fixes).\n- wifi: mwifiex: Detach sync cmd buffer on interrupted wait (git-fixes).\n- wifi: nl80211: free RNR data on MBSSID mismatch (git-fixes).\n- wifi: nl80211: validate nested MBSSID IE blobs (git-fixes).\n- wifi: p54: validate RX frame length in p54_rx_eeprom_readback() (git-fixes).\n- wifi: rtl8xxxu: fix use-after-free from rx_urb_wq on stop (git-fixes).\n- wifi: rtl818x: initialize eeprom_93cx6 struct to zero (git-fixes).\n- wifi: rtlwifi: pci: fix error path in rtl_pci_probe() (git-fixes).\n- wifi: rtlwifi: rtl8192du: check QoS TID before indexing tids (git-fixes).\n- wifi: rtlwifi: rtl8192du: Fix possible memory leak in rtl92du_init_sw_vars() (git-fixes).\n- wifi: rtw88: Fix potential memory leak in rtw_txq_push_skb() (git-fixes).\n- wifi: rtw88: pci: fix resource leak on failed NAPI setup (git-fixes).\n- wifi: rtw89: fix HE extended capability length check (git-fixes).\n- wifi: zd1211rw: reject secondary interfaces to prevent conflicts (git-fixes).\n- x86/virt/tdx: Print TDX module version during init (git-fixes).\n- x86/virt/tdx: Retrieve TDX module version (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_alloc_driver() failure (git-fixes).\n- xhci: dbgtty: Fix unregister on tty_register_driver() failure (git-fixes).\n- xhci: fix lost bounce buffers on TDs spanning several ring segments (git-fixes).\n","status":"published","published":"2026-09-22T14:23:31Z","modified":"2026-09-30T18:23:12.126873614Z","updated_at":"2026-11-02T15:54:03.991985Z"},{"id":"UBUNTU-CVE-2025-68780","description":"In the Linux kernel, the following vulnerability has been resolved: sched/deadline: only set free_cpus for online runqueues Commit 16b269436b72 (\"sched/deadline: Modify cpudl::free_cpus to reflect rd-\u003eonline\") introduced the cpudl_set/clear_freecpu functions to allow the cpu_dl::free_cpus mask to be manipulated by the deadline scheduler class rq_on/offline callbacks so the mask would also reflect this state. Commit 9659e1eeee28 (\"sched/deadline: Remove cpu_active_mask from cpudl_find()\") removed the check of the cpu_active_mask to save some processing on the premise that the cpudl::free_cpus mask already reflected the runqueue online state. Unfortunately, there are cases where it is possible for the cpudl_clear function to set the free_cpus bit for a CPU when the deadline runqueue is offline. When this occurs while a CPU is connected to the default root domain the flag may retain the bad state after the CPU has been unplugged. Later, a different CPU that is transitioning through the default root domain may push a deadline task to the powered down CPU when cpudl_find sees its free_cpus bit is set. If this happens the task will not have the opportunity to run. One example is outlined here: https://lore.kernel.org/lkml/20250110233010.2339521-1-opendmb@gmail.com Another occurs when the last deadline task is migrated from a CPU that has an offlined runqueue. The dequeue_task member of the deadline scheduler class will eventually call cpudl_clear and set the free_cpus bit for the CPU. This commit modifies the cpudl_clear function to be aware of the online state of the deadline runqueue so that the free_cpus mask can be updated appropriately. It is no longer necessary to manage the mask outside of the cpudl_set/clear functions so the cpudl_set/clear_freecpu functions are removed. In addition, since the free_cpus mask is now only updated under the cpudl lock the code was changed to use the non-atomic __cpumask functions.","status":"published","published":"2026-01-13T16:15:00Z","modified":"2026-11-11T09:39:20.230897026Z","updated_at":"2026-11-11T10:01:12.436405Z"},{"id":"USN-8096-1","title":"linux, linux-aws, linux-gcp, linux-gkeop, linux-ibm, linux-ibm-5.15, linux-intel-iotg, linux-kvm, linux-lowlatency, linux-nvidia, linux-nvidia-tegra, linux-nvidia-tegra-5.15, linux-oracle, linux-xilinx-zynqmp vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\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  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-16T14:37:39Z","modified":"2026-11-04T20:04:43.478113664Z","updated_at":"2026-11-04T21:43:05.815601Z"},{"id":"USN-8096-2","title":"linux-fips, linux-aws-fips, linux-gcp-fips vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\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  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-16T23:26:32Z","modified":"2026-11-04T20:01:32.668181992Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8096-3","title":"linux-aws-5.15, linux-gcp-5.15, linux-gke, linux-hwe-5.15, linux-intel-iotg-5.15, linux-lowlatency-hwe-5.15, linux-oracle-5.15 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\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  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-17T18:58:02Z","modified":"2026-11-04T20:02:21.623692755Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8096-4","title":"linux-realtime vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\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  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-17T19:09:30Z","modified":"2026-11-04T20:00:55.121160644Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8096-5","title":"linux-nvidia-tegra-igx vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\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  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-23T13:50:16Z","modified":"2026-11-04T20:00:59.234569299Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8116-1","title":"linux-intel-iot-realtime 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  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - Network traffic control;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2024-36903, CVE-2024-36927, CVE-2024-37354,\nCVE-2024-41014, CVE-2024-46830, CVE-2024-47666, CVE-2024-49968,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-22121, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38556, CVE-2025-40040, CVE-2025-40083,\nCVE-2025-40110, CVE-2025-40211, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68176, CVE-2025-68177, CVE-2025-68185,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68200,\nCVE-2025-68204, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71180, CVE-2025-71182,\nCVE-2026-22976, CVE-2026-22977, CVE-2026-22978, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23047)\n","status":"published","published":"2026-03-23T13:40:40Z","modified":"2026-11-04T20:01:42.2116858Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8141-1","title":"linux-raspi vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269)\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  - Nios II architecture;\n  - PowerPC architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Network sockets;\n  - XFRM subsystem;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - Rose network layer;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - Intel ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2022-49635, CVE-2024-36903, CVE-2024-36927,\nCVE-2024-37354, CVE-2024-41014, CVE-2024-46830, CVE-2024-47666,\nCVE-2024-49968, CVE-2024-53114, CVE-2024-56538, CVE-2024-58011,\nCVE-2025-21780, CVE-2025-21861, CVE-2025-22022, CVE-2025-22058,\nCVE-2025-22111, CVE-2025-22121, CVE-2025-23143, CVE-2025-38022,\nCVE-2025-38129, CVE-2025-38236, CVE-2025-38248, CVE-2025-38556,\nCVE-2025-38584, CVE-2025-39869, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39880, CVE-2025-39883, CVE-2025-39885, CVE-2025-39907,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39923, CVE-2025-39934,\nCVE-2025-39937, CVE-2025-39943, CVE-2025-39945, CVE-2025-39949,\nCVE-2025-39951, CVE-2025-39953, CVE-2025-39955, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39980, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40001,\nCVE-2025-40006, CVE-2025-40011, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40026, CVE-2025-40027, CVE-2025-40029, CVE-2025-40030,\nCVE-2025-40035, CVE-2025-40040, CVE-2025-40042, CVE-2025-40043,\nCVE-2025-40044, CVE-2025-40048, CVE-2025-40049, CVE-2025-40053,\nCVE-2025-40055, CVE-2025-40060, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40078, CVE-2025-40081, CVE-2025-40083, CVE-2025-40085,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40092, CVE-2025-40094,\nCVE-2025-40105, CVE-2025-40106, CVE-2025-40109, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40115, CVE-2025-40116,\nCVE-2025-40118, CVE-2025-40120, CVE-2025-40121, CVE-2025-40124,\nCVE-2025-40125, CVE-2025-40126, CVE-2025-40127, CVE-2025-40134,\nCVE-2025-40140, CVE-2025-40153, CVE-2025-40154, CVE-2025-40167,\nCVE-2025-40171, CVE-2025-40173, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40194,\nCVE-2025-40200, CVE-2025-40204, CVE-2025-40205, CVE-2025-40211,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68185, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68194, CVE-2025-68200, CVE-2025-68204,\nCVE-2025-68217, CVE-2025-68220, CVE-2025-68227, CVE-2025-68229,\nCVE-2025-68238, CVE-2025-68241, CVE-2025-68244, CVE-2025-68245,\nCVE-2025-68249, CVE-2025-68254, CVE-2025-68255, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68261, CVE-2025-68264, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68284, CVE-2025-68285, CVE-2025-68286,\nCVE-2025-68287, CVE-2025-68288, CVE-2025-68289, CVE-2025-68290,\nCVE-2025-68295, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68308, CVE-2025-68312, CVE-2025-68321, CVE-2025-68325,\nCVE-2025-68327, CVE-2025-68328, CVE-2025-68330, CVE-2025-68331,\nCVE-2025-68332, CVE-2025-68335, CVE-2025-68336, CVE-2025-68337,\nCVE-2025-68339, CVE-2025-68344, CVE-2025-68346, CVE-2025-68349,\nCVE-2025-68354, CVE-2025-68362, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68372, CVE-2025-68724, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-71064,\nCVE-2025-71066, CVE-2025-71068, CVE-2025-71069, CVE-2025-71075,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71081,\nCVE-2025-71082, CVE-2025-71083, CVE-2025-71084, CVE-2025-71085,\nCVE-2025-71086, CVE-2025-71087, CVE-2025-71091, CVE-2025-71093,\nCVE-2025-71094, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71102, CVE-2025-71104, CVE-2025-71105, CVE-2025-71108,\nCVE-2025-71111, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114,\nCVE-2025-71116, CVE-2025-71118, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71125, CVE-2025-71127, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71136, CVE-2025-71137, CVE-2025-71147,\nCVE-2025-71154, CVE-2025-71180, CVE-2025-71182, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22980, CVE-2026-22982,\nCVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23047)\n","status":"published","published":"2026-04-01T15:16:17Z","modified":"2026-11-04T20:01:19.439094326Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8163-1","title":"linux-azure-fips vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\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  - Nios II architecture;\n  - PowerPC architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Network sockets;\n  - XFRM subsystem;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - Rose network layer;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - Intel ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2022-49635, CVE-2023-53041, CVE-2024-36903,\nCVE-2024-36927, CVE-2024-37354, CVE-2024-41014, CVE-2024-46830,\nCVE-2024-47666, CVE-2024-49968, CVE-2024-53114, CVE-2024-56538,\nCVE-2024-58011, CVE-2025-21780, CVE-2025-21861, CVE-2025-22022,\nCVE-2025-22058, CVE-2025-22111, CVE-2025-22121, CVE-2025-23143,\nCVE-2025-37849, CVE-2025-38022, CVE-2025-38129, CVE-2025-38236,\nCVE-2025-38248, CVE-2025-38556, CVE-2025-38584, CVE-2025-39869,\nCVE-2025-39873, CVE-2025-39876, CVE-2025-39880, CVE-2025-39883,\nCVE-2025-39885, CVE-2025-39907, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39923, CVE-2025-39934, CVE-2025-39937, CVE-2025-39943,\nCVE-2025-39945, CVE-2025-39949, CVE-2025-39951, CVE-2025-39953,\nCVE-2025-39955, CVE-2025-39967, CVE-2025-39968, CVE-2025-39969,\nCVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973,\nCVE-2025-39980, CVE-2025-39985, CVE-2025-39986, CVE-2025-39987,\nCVE-2025-39988, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40001, CVE-2025-40006, CVE-2025-40011,\nCVE-2025-40020, CVE-2025-40021, CVE-2025-40026, CVE-2025-40027,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40035, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40048,\nCVE-2025-40049, CVE-2025-40053, CVE-2025-40055, CVE-2025-40060,\nCVE-2025-40068, CVE-2025-40070, CVE-2025-40078, CVE-2025-40081,\nCVE-2025-40083, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,\nCVE-2025-40127, CVE-2025-40134, CVE-2025-40140, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40167, CVE-2025-40171, CVE-2025-40173,\nCVE-2025-40178, CVE-2025-40179, CVE-2025-40183, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40194, CVE-2025-40200, CVE-2025-40204,\nCVE-2025-40205, CVE-2025-40211, CVE-2025-40215, CVE-2025-40219,\nCVE-2025-40220, CVE-2025-40223, CVE-2025-40231, CVE-2025-40233,\nCVE-2025-40240, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,\nCVE-2025-40248, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254,\nCVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40261,\nCVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40269,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40275,\nCVE-2025-40277, CVE-2025-40278, CVE-2025-40279, CVE-2025-40280,\nCVE-2025-40281, CVE-2025-40282, CVE-2025-40283, CVE-2025-40304,\nCVE-2025-40306, CVE-2025-40308, CVE-2025-40309, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40317,\nCVE-2025-40319, CVE-2025-40321, CVE-2025-40322, CVE-2025-40324,\nCVE-2025-40331, CVE-2025-40342, CVE-2025-40343, CVE-2025-40345,\nCVE-2025-40346, CVE-2025-40349, CVE-2025-40351, CVE-2025-40360,\nCVE-2025-40363, CVE-2025-68168, CVE-2025-68176, CVE-2025-68177,\nCVE-2025-68185, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68200, CVE-2025-68204, CVE-2025-68217, CVE-2025-68220,\nCVE-2025-68227, CVE-2025-68229, CVE-2025-68238, CVE-2025-68241,\nCVE-2025-68244, CVE-2025-68245, CVE-2025-68249, CVE-2025-68254,\nCVE-2025-68255, CVE-2025-68257, CVE-2025-68258, CVE-2025-68261,\nCVE-2025-68264, CVE-2025-68266, CVE-2025-68282, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68301,\nCVE-2025-68302, CVE-2025-68303, CVE-2025-68308, CVE-2025-68312,\nCVE-2025-68321, CVE-2025-68325, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68339, CVE-2025-68344,\nCVE-2025-68346, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68364, CVE-2025-68366, CVE-2025-68367, CVE-2025-68372,\nCVE-2025-68724, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732,\nCVE-2025-68733, CVE-2025-68734, CVE-2025-68740, CVE-2025-68746,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68764,\nCVE-2025-68765, CVE-2025-68767, CVE-2025-68769, CVE-2025-68771,\nCVE-2025-68774, CVE-2025-68776, CVE-2025-68777, CVE-2025-68780,\nCVE-2025-68782, CVE-2025-68783, CVE-2025-68785, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68795, CVE-2025-68796, CVE-2025-68797,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68803,\nCVE-2025-68804, CVE-2025-68808, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68818, CVE-2025-68819,\nCVE-2025-68820, CVE-2025-71064, CVE-2025-71066, CVE-2025-71068,\nCVE-2025-71069, CVE-2025-71075, CVE-2025-71077, CVE-2025-71078,\nCVE-2025-71079, CVE-2025-71081, CVE-2025-71082, CVE-2025-71083,\nCVE-2025-71084, CVE-2025-71085, CVE-2025-71086, CVE-2025-71087,\nCVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71096,\nCVE-2025-71097, CVE-2025-71098, CVE-2025-71102, CVE-2025-71104,\nCVE-2025-71105, CVE-2025-71108, CVE-2025-71111, CVE-2025-71112,\nCVE-2025-71113, CVE-2025-71114, CVE-2025-71116, CVE-2025-71118,\nCVE-2025-71120, CVE-2025-71121, CVE-2025-71125, CVE-2025-71127,\nCVE-2025-71131, CVE-2025-71132, CVE-2025-71133, CVE-2025-71136,\nCVE-2025-71137, CVE-2025-71147, CVE-2025-71154, CVE-2025-71180,\nCVE-2025-71182, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978,\nCVE-2026-22980, CVE-2026-22982, CVE-2026-22984, CVE-2026-22990,\nCVE-2026-22991, CVE-2026-22992, CVE-2026-23019, CVE-2026-23020,\nCVE-2026-23021, CVE-2026-23047, CVE-2026-23060, CVE-2026-23074,\nCVE-2026-23111, CVE-2026-23202, CVE-2026-23207)\n","status":"published","published":"2026-04-09T23:26:12Z","modified":"2026-11-04T20:01:30.971787913Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8163-2","title":"linux-azure vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\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  - Nios II architecture;\n  - PowerPC architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Network sockets;\n  - XFRM subsystem;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - Rose network layer;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - Intel ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2022-49635, CVE-2023-53041, CVE-2024-36903,\nCVE-2024-36927, CVE-2024-37354, CVE-2024-41014, CVE-2024-46830,\nCVE-2024-47666, CVE-2024-49968, CVE-2024-53114, CVE-2024-56538,\nCVE-2024-58011, CVE-2025-21780, CVE-2025-21861, CVE-2025-22022,\nCVE-2025-22058, CVE-2025-22111, CVE-2025-22121, CVE-2025-23143,\nCVE-2025-37849, CVE-2025-38022, CVE-2025-38129, CVE-2025-38236,\nCVE-2025-38248, CVE-2025-38556, CVE-2025-38584, CVE-2025-39869,\nCVE-2025-39873, CVE-2025-39876, CVE-2025-39880, CVE-2025-39883,\nCVE-2025-39885, CVE-2025-39907, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39923, CVE-2025-39934, CVE-2025-39937, CVE-2025-39943,\nCVE-2025-39945, CVE-2025-39949, CVE-2025-39951, CVE-2025-39953,\nCVE-2025-39955, CVE-2025-39967, CVE-2025-39968, CVE-2025-39969,\nCVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973,\nCVE-2025-39980, CVE-2025-39985, CVE-2025-39986, CVE-2025-39987,\nCVE-2025-39988, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40001, CVE-2025-40006, CVE-2025-40011,\nCVE-2025-40020, CVE-2025-40021, CVE-2025-40026, CVE-2025-40027,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40035, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40048,\nCVE-2025-40049, CVE-2025-40053, CVE-2025-40055, CVE-2025-40060,\nCVE-2025-40068, CVE-2025-40070, CVE-2025-40078, CVE-2025-40081,\nCVE-2025-40083, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,\nCVE-2025-40127, CVE-2025-40134, CVE-2025-40140, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40167, CVE-2025-40171, CVE-2025-40173,\nCVE-2025-40178, CVE-2025-40179, CVE-2025-40183, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40194, CVE-2025-40200, CVE-2025-40204,\nCVE-2025-40205, CVE-2025-40211, CVE-2025-40215, CVE-2025-40219,\nCVE-2025-40220, CVE-2025-40223, CVE-2025-40231, CVE-2025-40233,\nCVE-2025-40240, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,\nCVE-2025-40248, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254,\nCVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40261,\nCVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40269,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40275,\nCVE-2025-40277, CVE-2025-40278, CVE-2025-40279, CVE-2025-40280,\nCVE-2025-40281, CVE-2025-40282, CVE-2025-40283, CVE-2025-40304,\nCVE-2025-40306, CVE-2025-40308, CVE-2025-40309, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40317,\nCVE-2025-40319, CVE-2025-40321, CVE-2025-40322, CVE-2025-40324,\nCVE-2025-40331, CVE-2025-40342, CVE-2025-40343, CVE-2025-40345,\nCVE-2025-40346, CVE-2025-40349, CVE-2025-40351, CVE-2025-40360,\nCVE-2025-40363, CVE-2025-68168, CVE-2025-68176, CVE-2025-68177,\nCVE-2025-68185, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68200, CVE-2025-68204, CVE-2025-68217, CVE-2025-68220,\nCVE-2025-68227, CVE-2025-68229, CVE-2025-68238, CVE-2025-68241,\nCVE-2025-68244, CVE-2025-68245, CVE-2025-68249, CVE-2025-68254,\nCVE-2025-68255, CVE-2025-68257, CVE-2025-68258, CVE-2025-68261,\nCVE-2025-68264, CVE-2025-68266, CVE-2025-68282, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68301,\nCVE-2025-68302, CVE-2025-68303, CVE-2025-68308, CVE-2025-68312,\nCVE-2025-68321, CVE-2025-68325, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68339, CVE-2025-68344,\nCVE-2025-68346, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68364, CVE-2025-68366, CVE-2025-68367, CVE-2025-68372,\nCVE-2025-68724, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732,\nCVE-2025-68733, CVE-2025-68734, CVE-2025-68740, CVE-2025-68746,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68764,\nCVE-2025-68765, CVE-2025-68767, CVE-2025-68769, CVE-2025-68771,\nCVE-2025-68774, CVE-2025-68776, CVE-2025-68777, CVE-2025-68780,\nCVE-2025-68782, CVE-2025-68783, CVE-2025-68785, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68795, CVE-2025-68796, CVE-2025-68797,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68803,\nCVE-2025-68804, CVE-2025-68808, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68818, CVE-2025-68819,\nCVE-2025-68820, CVE-2025-71064, CVE-2025-71066, CVE-2025-71068,\nCVE-2025-71069, CVE-2025-71075, CVE-2025-71077, CVE-2025-71078,\nCVE-2025-71079, CVE-2025-71081, CVE-2025-71082, CVE-2025-71083,\nCVE-2025-71084, CVE-2025-71085, CVE-2025-71086, CVE-2025-71087,\nCVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71096,\nCVE-2025-71097, CVE-2025-71098, CVE-2025-71102, CVE-2025-71104,\nCVE-2025-71105, CVE-2025-71108, CVE-2025-71111, CVE-2025-71112,\nCVE-2025-71113, CVE-2025-71114, CVE-2025-71116, CVE-2025-71118,\nCVE-2025-71120, CVE-2025-71121, CVE-2025-71125, CVE-2025-71127,\nCVE-2025-71131, CVE-2025-71132, CVE-2025-71133, CVE-2025-71136,\nCVE-2025-71137, CVE-2025-71147, CVE-2025-71154, CVE-2025-71180,\nCVE-2025-71182, CVE-2026-22976, CVE-2026-22977, CVE-2026-22978,\nCVE-2026-22980, CVE-2026-22982, CVE-2026-22984, CVE-2026-22990,\nCVE-2026-22991, CVE-2026-22992, CVE-2026-23019, CVE-2026-23020,\nCVE-2026-23021, CVE-2026-23047, CVE-2026-23060, CVE-2026-23074,\nCVE-2026-23111, CVE-2026-23202, CVE-2026-23207)\n","status":"published","published":"2026-04-13T23:59:31Z","modified":"2026-11-04T20:01:02.954045618Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8177-1","title":"linux, linux-realtime vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Mouse) drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Freescale USB OTG Transceiver Driver;\n  - USB Type-C Connector System Software Interface driver;\n  - Watchdog drivers;\n  - BTRFS file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - XFS file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - BPF subsystem;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Key management;\n  - Landlock security;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-68351, CVE-2025-68353, CVE-2025-68365, CVE-2025-68368,\nCVE-2025-68725, CVE-2025-68736, CVE-2025-68745, CVE-2025-68767,\nCVE-2025-68768, CVE-2025-68769, CVE-2025-68770, CVE-2025-68771,\nCVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775,\nCVE-2025-68776, CVE-2025-68777, CVE-2025-68778, CVE-2025-68780,\nCVE-2025-68781, CVE-2025-68782, CVE-2025-68783, CVE-2025-68784,\nCVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788,\nCVE-2025-68791, CVE-2025-68792, CVE-2025-68793, CVE-2025-68794,\nCVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68798,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68802,\nCVE-2025-68803, CVE-2025-68804, CVE-2025-68805, CVE-2025-68806,\nCVE-2025-68807, CVE-2025-68808, CVE-2025-68809, CVE-2025-68810,\nCVE-2025-68811, CVE-2025-68813, CVE-2025-68814, CVE-2025-68815,\nCVE-2025-68816, CVE-2025-68817, CVE-2025-68818, CVE-2025-68819,\nCVE-2025-68820, CVE-2025-68821, CVE-2025-68822, CVE-2025-68823,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71070, CVE-2025-71071,\nCVE-2025-71072, CVE-2025-71073, CVE-2025-71075, CVE-2025-71076,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71080,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71089,\nCVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71095,\nCVE-2025-71096, CVE-2025-71097, CVE-2025-71098, CVE-2025-71099,\nCVE-2025-71100, CVE-2025-71101, CVE-2025-71102, CVE-2025-71104,\nCVE-2025-71105, CVE-2025-71107, CVE-2025-71108, CVE-2025-71109,\nCVE-2025-71111, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114,\nCVE-2025-71115, CVE-2025-71116, CVE-2025-71117, CVE-2025-71118,\nCVE-2025-71119, CVE-2025-71120, CVE-2025-71121, CVE-2025-71122,\nCVE-2025-71123, CVE-2025-71124, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71130, CVE-2025-71131, CVE-2025-71132, CVE-2025-71133,\nCVE-2025-71135, CVE-2025-71136, CVE-2025-71137, CVE-2025-71138,\nCVE-2025-71140, CVE-2025-71143, CVE-2025-71146, CVE-2025-71147,\nCVE-2025-71148, CVE-2025-71149, CVE-2025-71150, CVE-2025-71151,\nCVE-2025-71153, CVE-2025-71154, CVE-2025-71156, CVE-2025-71157,\nCVE-2026-23091, CVE-2026-23209)\n","status":"published","published":"2026-04-17T08:33:32Z","modified":"2026-11-04T20:00:59.855311339Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8177-2","title":"linux-realtime-6.17 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Mouse) drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Freescale USB OTG Transceiver Driver;\n  - USB Type-C Connector System Software Interface driver;\n  - Watchdog drivers;\n  - BTRFS file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - XFS file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - BPF subsystem;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Key management;\n  - Landlock security;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-68351, CVE-2025-68353, CVE-2025-68365, CVE-2025-68368,\nCVE-2025-68725, CVE-2025-68736, CVE-2025-68745, CVE-2025-68767,\nCVE-2025-68768, CVE-2025-68769, CVE-2025-68770, CVE-2025-68771,\nCVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775,\nCVE-2025-68776, CVE-2025-68777, CVE-2025-68778, CVE-2025-68780,\nCVE-2025-68781, CVE-2025-68782, CVE-2025-68783, CVE-2025-68784,\nCVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788,\nCVE-2025-68791, CVE-2025-68792, CVE-2025-68793, CVE-2025-68794,\nCVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68798,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68802,\nCVE-2025-68803, CVE-2025-68804, CVE-2025-68805, CVE-2025-68806,\nCVE-2025-68807, CVE-2025-68808, CVE-2025-68809, CVE-2025-68810,\nCVE-2025-68811, CVE-2025-68813, CVE-2025-68814, CVE-2025-68815,\nCVE-2025-68816, CVE-2025-68817, CVE-2025-68818, CVE-2025-68819,\nCVE-2025-68820, CVE-2025-68821, CVE-2025-68822, CVE-2025-68823,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71070, CVE-2025-71071,\nCVE-2025-71072, CVE-2025-71073, CVE-2025-71075, CVE-2025-71076,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71080,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71089,\nCVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71095,\nCVE-2025-71096, CVE-2025-71097, CVE-2025-71098, CVE-2025-71099,\nCVE-2025-71100, CVE-2025-71101, CVE-2025-71102, CVE-2025-71104,\nCVE-2025-71105, CVE-2025-71107, CVE-2025-71108, CVE-2025-71109,\nCVE-2025-71111, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114,\nCVE-2025-71115, CVE-2025-71116, CVE-2025-71117, CVE-2025-71118,\nCVE-2025-71119, CVE-2025-71120, CVE-2025-71121, CVE-2025-71122,\nCVE-2025-71123, CVE-2025-71124, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71130, CVE-2025-71131, CVE-2025-71132, CVE-2025-71133,\nCVE-2025-71135, CVE-2025-71136, CVE-2025-71137, CVE-2025-71138,\nCVE-2025-71140, CVE-2025-71143, CVE-2025-71146, CVE-2025-71147,\nCVE-2025-71148, CVE-2025-71149, CVE-2025-71150, CVE-2025-71151,\nCVE-2025-71153, CVE-2025-71154, CVE-2025-71156, CVE-2025-71157,\nCVE-2026-23091, CVE-2026-23209)\n","status":"published","published":"2026-04-17T08:30:25Z","modified":"2026-11-04T20:01:21.20250126Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8179-1","title":"linux, linux-aws, linux-aws-6.8, linux-gcp, linux-gke, linux-gkeop, linux-ibm, linux-lowlatency, linux-lowlatency-hwe-6.8 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68746, CVE-2025-68753, CVE-2025-68755, CVE-2025-68756,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68763,\nCVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68770, CVE-2025-68771, CVE-2025-68772,\nCVE-2025-68773, CVE-2025-68774, CVE-2025-68775, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68782,\nCVE-2025-68783, CVE-2025-68785, CVE-2025-68786, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68794, CVE-2025-68795, CVE-2025-68796,\nCVE-2025-68797, CVE-2025-68798, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68804, CVE-2025-68806, CVE-2025-68808,\nCVE-2025-68809, CVE-2025-68810, CVE-2025-68811, CVE-2025-68813,\nCVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68817,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71149,\nCVE-2025-71150, CVE-2025-71151, CVE-2025-71153, CVE-2025-71154,\nCVE-2026-23209)\n","status":"published","published":"2026-04-16T14:13:07Z","modified":"2026-11-04T20:03:13.295663568Z","updated_at":"2026-11-04T21:44:35.728664Z"},{"id":"USN-8179-2","title":"linux-aws-fips, linux-fips, linux-gcp-fips vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68746, CVE-2025-68753, CVE-2025-68755, CVE-2025-68756,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68763,\nCVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68770, CVE-2025-68771, CVE-2025-68772,\nCVE-2025-68773, CVE-2025-68774, CVE-2025-68775, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68782,\nCVE-2025-68783, CVE-2025-68785, CVE-2025-68786, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68794, CVE-2025-68795, CVE-2025-68796,\nCVE-2025-68797, CVE-2025-68798, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68804, CVE-2025-68806, CVE-2025-68808,\nCVE-2025-68809, CVE-2025-68810, CVE-2025-68811, CVE-2025-68813,\nCVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68817,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71149,\nCVE-2025-71150, CVE-2025-71151, CVE-2025-71153, CVE-2025-71154,\nCVE-2026-23209)\n","status":"published","published":"2026-04-17T09:36:13Z","modified":"2026-11-04T20:01:03.58249938Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8179-3","title":"linux-hwe-6.8, linux-ibm-6.8, linux-raspi vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68746, CVE-2025-68753, CVE-2025-68755, CVE-2025-68756,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68763,\nCVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68770, CVE-2025-68771, CVE-2025-68772,\nCVE-2025-68773, CVE-2025-68774, CVE-2025-68775, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68782,\nCVE-2025-68783, CVE-2025-68785, CVE-2025-68786, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68794, CVE-2025-68795, CVE-2025-68796,\nCVE-2025-68797, CVE-2025-68798, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68804, CVE-2025-68806, CVE-2025-68808,\nCVE-2025-68809, CVE-2025-68810, CVE-2025-68811, CVE-2025-68813,\nCVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68817,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71149,\nCVE-2025-71150, CVE-2025-71151, CVE-2025-71153, CVE-2025-71154,\nCVE-2026-23209)\n","status":"published","published":"2026-04-23T09:41:51Z","modified":"2026-11-04T20:02:00.522763798Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8179-4","title":"linux-gcp-6.8 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68746, CVE-2025-68753, CVE-2025-68755, CVE-2025-68756,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68763,\nCVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68770, CVE-2025-68771, CVE-2025-68772,\nCVE-2025-68773, CVE-2025-68774, CVE-2025-68775, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68782,\nCVE-2025-68783, CVE-2025-68785, CVE-2025-68786, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68794, CVE-2025-68795, CVE-2025-68796,\nCVE-2025-68797, CVE-2025-68798, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68804, CVE-2025-68806, CVE-2025-68808,\nCVE-2025-68809, CVE-2025-68810, CVE-2025-68811, CVE-2025-68813,\nCVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68817,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71150,\nCVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2026-23209)\n","status":"published","published":"2026-05-07T07:34:08Z","modified":"2026-11-04T20:01:41.542186472Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8183-1","title":"linux-gcp, linux-gcp-6.17 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Mouse) drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Freescale USB OTG Transceiver Driver;\n  - USB Type-C Connector System Software Interface driver;\n  - Watchdog drivers;\n  - BTRFS file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - XFS file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - BPF subsystem;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Key management;\n  - Landlock security;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-68351, CVE-2025-68353, CVE-2025-68365, CVE-2025-68368,\nCVE-2025-68725, CVE-2025-68736, CVE-2025-68745, CVE-2025-68767,\nCVE-2025-68768, CVE-2025-68769, CVE-2025-68770, CVE-2025-68771,\nCVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775,\nCVE-2025-68776, CVE-2025-68777, CVE-2025-68778, CVE-2025-68780,\nCVE-2025-68781, CVE-2025-68782, CVE-2025-68783, CVE-2025-68784,\nCVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788,\nCVE-2025-68791, CVE-2025-68792, CVE-2025-68793, CVE-2025-68794,\nCVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68798,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68802,\nCVE-2025-68803, CVE-2025-68804, CVE-2025-68805, CVE-2025-68806,\nCVE-2025-68807, CVE-2025-68808, CVE-2025-68809, CVE-2025-68810,\nCVE-2025-68811, CVE-2025-68813, CVE-2025-68814, CVE-2025-68815,\nCVE-2025-68816, CVE-2025-68817, CVE-2025-68818, CVE-2025-68819,\nCVE-2025-68820, CVE-2025-68821, CVE-2025-68822, CVE-2025-68823,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71070, CVE-2025-71071,\nCVE-2025-71072, CVE-2025-71073, CVE-2025-71075, CVE-2025-71076,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71081,\nCVE-2025-71082, CVE-2025-71083, CVE-2025-71084, CVE-2025-71085,\nCVE-2025-71086, CVE-2025-71087, CVE-2025-71089, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71095, CVE-2025-71096,\nCVE-2025-71097, CVE-2025-71098, CVE-2025-71099, CVE-2025-71100,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71115,\nCVE-2025-71116, CVE-2025-71117, CVE-2025-71118, CVE-2025-71119,\nCVE-2025-71120, CVE-2025-71121, CVE-2025-71122, CVE-2025-71123,\nCVE-2025-71124, CVE-2025-71125, CVE-2025-71126, CVE-2025-71130,\nCVE-2025-71131, CVE-2025-71132, CVE-2025-71133, CVE-2025-71135,\nCVE-2025-71136, CVE-2025-71137, CVE-2025-71138, CVE-2025-71140,\nCVE-2025-71143, CVE-2025-71146, CVE-2025-71147, CVE-2025-71148,\nCVE-2025-71149, CVE-2025-71150, CVE-2025-71151, CVE-2025-71153,\nCVE-2025-71154, CVE-2025-71156, CVE-2025-71157, CVE-2026-23091,\nCVE-2026-23209)\n","status":"published","published":"2026-04-17T09:06:33Z","modified":"2026-11-04T20:01:27.286363008Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8183-2","title":"linux-aws, linux-aws-6.17, linux-hwe-6.17, linux-oracle, linux-oracle-6.17 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Mouse) drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Freescale USB OTG Transceiver Driver;\n  - USB Type-C Connector System Software Interface driver;\n  - Watchdog drivers;\n  - BTRFS file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - XFS file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - BPF subsystem;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Key management;\n  - Landlock security;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-68351, CVE-2025-68353, CVE-2025-68365, CVE-2025-68368,\nCVE-2025-68725, CVE-2025-68736, CVE-2025-68745, CVE-2025-68767,\nCVE-2025-68768, CVE-2025-68769, CVE-2025-68770, CVE-2025-68771,\nCVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775,\nCVE-2025-68776, CVE-2025-68777, CVE-2025-68778, CVE-2025-68780,\nCVE-2025-68781, CVE-2025-68782, CVE-2025-68783, CVE-2025-68784,\nCVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788,\nCVE-2025-68791, CVE-2025-68792, CVE-2025-68793, CVE-2025-68794,\nCVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68798,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68802,\nCVE-2025-68803, CVE-2025-68804, CVE-2025-68805, CVE-2025-68806,\nCVE-2025-68807, CVE-2025-68808, CVE-2025-68809, CVE-2025-68810,\nCVE-2025-68811, CVE-2025-68813, CVE-2025-68814, CVE-2025-68815,\nCVE-2025-68816, CVE-2025-68817, CVE-2025-68818, CVE-2025-68819,\nCVE-2025-68820, CVE-2025-68821, CVE-2025-68822, CVE-2025-68823,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71070, CVE-2025-71071,\nCVE-2025-71072, CVE-2025-71073, CVE-2025-71075, CVE-2025-71076,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71081,\nCVE-2025-71082, CVE-2025-71083, CVE-2025-71084, CVE-2025-71085,\nCVE-2025-71086, CVE-2025-71087, CVE-2025-71089, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71095, CVE-2025-71096,\nCVE-2025-71097, CVE-2025-71098, CVE-2025-71099, CVE-2025-71100,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71115,\nCVE-2025-71116, CVE-2025-71117, CVE-2025-71118, CVE-2025-71119,\nCVE-2025-71120, CVE-2025-71121, CVE-2025-71122, CVE-2025-71123,\nCVE-2025-71124, CVE-2025-71125, CVE-2025-71126, CVE-2025-71130,\nCVE-2025-71131, CVE-2025-71132, CVE-2025-71133, CVE-2025-71135,\nCVE-2025-71136, CVE-2025-71137, CVE-2025-71138, CVE-2025-71140,\nCVE-2025-71143, CVE-2025-71146, CVE-2025-71147, CVE-2025-71148,\nCVE-2025-71149, CVE-2025-71150, CVE-2025-71151, CVE-2025-71153,\nCVE-2025-71154, CVE-2025-71156, CVE-2025-71157, CVE-2026-23091,\nCVE-2026-23209)\n","status":"published","published":"2026-04-23T09:27:17Z","modified":"2026-11-04T20:02:47.539237559Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8184-1","title":"linux-realtime, linux-realtime-6.8 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68746, CVE-2025-68753, CVE-2025-68755, CVE-2025-68756,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68763,\nCVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68770, CVE-2025-68771, CVE-2025-68772,\nCVE-2025-68773, CVE-2025-68774, CVE-2025-68775, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68782,\nCVE-2025-68783, CVE-2025-68785, CVE-2025-68786, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68794, CVE-2025-68795, CVE-2025-68796,\nCVE-2025-68797, CVE-2025-68798, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68804, CVE-2025-68806, CVE-2025-68808,\nCVE-2025-68809, CVE-2025-68810, CVE-2025-68811, CVE-2025-68813,\nCVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68817,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71080, CVE-2025-71081, CVE-2025-71082, CVE-2025-71083,\nCVE-2025-71084, CVE-2025-71085, CVE-2025-71086, CVE-2025-71087,\nCVE-2025-71088, CVE-2025-71089, CVE-2025-71091, CVE-2025-71093,\nCVE-2025-71094, CVE-2025-71095, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71101, CVE-2025-71102, CVE-2025-71104,\nCVE-2025-71105, CVE-2025-71107, CVE-2025-71108, CVE-2025-71109,\nCVE-2025-71111, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114,\nCVE-2025-71116, CVE-2025-71118, CVE-2025-71119, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71122, CVE-2025-71123, CVE-2025-71125,\nCVE-2025-71126, CVE-2025-71127, CVE-2025-71130, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71135, CVE-2025-71136,\nCVE-2025-71137, CVE-2025-71138, CVE-2025-71140, CVE-2025-71141,\nCVE-2025-71143, CVE-2025-71144, CVE-2025-71147, CVE-2025-71148,\nCVE-2025-71149, CVE-2025-71150, CVE-2025-71151, CVE-2025-71153,\nCVE-2025-71154, CVE-2026-23209)\n","status":"published","published":"2026-04-17T09:26:36Z","modified":"2026-11-04T20:02:31.825928772Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8185-1","title":"linux-nvidia, linux-nvidia-6.8 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68753, CVE-2025-68755, CVE-2025-68756, CVE-2025-68757,\nCVE-2025-68758, CVE-2025-68759, CVE-2025-68763, CVE-2025-68764,\nCVE-2025-68765, CVE-2025-68766, CVE-2025-68767, CVE-2025-68769,\nCVE-2025-68770, CVE-2025-68771, CVE-2025-68772, CVE-2025-68773,\nCVE-2025-68774, CVE-2025-68775, CVE-2025-68776, CVE-2025-68777,\nCVE-2025-68778, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788,\nCVE-2025-68794, CVE-2025-68795, CVE-2025-68796, CVE-2025-68797,\nCVE-2025-68798, CVE-2025-68799, CVE-2025-68800, CVE-2025-68801,\nCVE-2025-68804, CVE-2025-68806, CVE-2025-68808, CVE-2025-68809,\nCVE-2025-68810, CVE-2025-68811, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68817, CVE-2025-68818,\nCVE-2025-68819, CVE-2025-68820, CVE-2025-68821, CVE-2025-71064,\nCVE-2025-71065, CVE-2025-71066, CVE-2025-71067, CVE-2025-71068,\nCVE-2025-71069, CVE-2025-71071, CVE-2025-71072, CVE-2025-71075,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71081,\nCVE-2025-71082, CVE-2025-71083, CVE-2025-71084, CVE-2025-71085,\nCVE-2025-71086, CVE-2025-71087, CVE-2025-71088, CVE-2025-71089,\nCVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71095,\nCVE-2025-71096, CVE-2025-71097, CVE-2025-71098, CVE-2025-71101,\nCVE-2025-71102, CVE-2025-71104, CVE-2025-71105, CVE-2025-71107,\nCVE-2025-71108, CVE-2025-71109, CVE-2025-71111, CVE-2025-71112,\nCVE-2025-71113, CVE-2025-71114, CVE-2025-71116, CVE-2025-71118,\nCVE-2025-71119, CVE-2025-71120, CVE-2025-71121, CVE-2025-71122,\nCVE-2025-71123, CVE-2025-71125, CVE-2025-71126, CVE-2025-71127,\nCVE-2025-71130, CVE-2025-71131, CVE-2025-71132, CVE-2025-71133,\nCVE-2025-71135, CVE-2025-71136, CVE-2025-71137, CVE-2025-71138,\nCVE-2025-71140, CVE-2025-71141, CVE-2025-71143, CVE-2025-71144,\nCVE-2025-71147, CVE-2025-71148, CVE-2025-71149, CVE-2025-71150,\nCVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2026-23209)\n","status":"published","published":"2026-04-17T09:55:06Z","modified":"2026-11-04T20:02:30.754056894Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8185-2","title":"linux-nvidia-lowlatency vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68753, CVE-2025-68755, CVE-2025-68756, CVE-2025-68757,\nCVE-2025-68758, CVE-2025-68759, CVE-2025-68763, CVE-2025-68764,\nCVE-2025-68765, CVE-2025-68766, CVE-2025-68767, CVE-2025-68769,\nCVE-2025-68770, CVE-2025-68771, CVE-2025-68772, CVE-2025-68773,\nCVE-2025-68774, CVE-2025-68775, CVE-2025-68776, CVE-2025-68777,\nCVE-2025-68778, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788,\nCVE-2025-68794, CVE-2025-68795, CVE-2025-68796, CVE-2025-68797,\nCVE-2025-68798, CVE-2025-68799, CVE-2025-68800, CVE-2025-68801,\nCVE-2025-68804, CVE-2025-68806, CVE-2025-68808, CVE-2025-68809,\nCVE-2025-68810, CVE-2025-68811, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68817, CVE-2025-68818,\nCVE-2025-68819, CVE-2025-68820, CVE-2025-68821, CVE-2025-71064,\nCVE-2025-71065, CVE-2025-71066, CVE-2025-71067, CVE-2025-71068,\nCVE-2025-71069, CVE-2025-71071, CVE-2025-71072, CVE-2025-71075,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71081,\nCVE-2025-71082, CVE-2025-71083, CVE-2025-71084, CVE-2025-71085,\nCVE-2025-71086, CVE-2025-71087, CVE-2025-71088, CVE-2025-71089,\nCVE-2025-71091, CVE-2025-71093, CVE-2025-71094, CVE-2025-71095,\nCVE-2025-71096, CVE-2025-71097, CVE-2025-71098, CVE-2025-71101,\nCVE-2025-71102, CVE-2025-71104, CVE-2025-71105, CVE-2025-71107,\nCVE-2025-71108, CVE-2025-71109, CVE-2025-71111, CVE-2025-71112,\nCVE-2025-71113, CVE-2025-71114, CVE-2025-71116, CVE-2025-71118,\nCVE-2025-71119, CVE-2025-71120, CVE-2025-71121, CVE-2025-71122,\nCVE-2025-71123, CVE-2025-71125, CVE-2025-71126, CVE-2025-71127,\nCVE-2025-71130, CVE-2025-71131, CVE-2025-71132, CVE-2025-71133,\nCVE-2025-71135, CVE-2025-71136, CVE-2025-71137, CVE-2025-71138,\nCVE-2025-71140, CVE-2025-71141, CVE-2025-71143, CVE-2025-71144,\nCVE-2025-71147, CVE-2025-71148, CVE-2025-71149, CVE-2025-71150,\nCVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2026-23209)\n","status":"published","published":"2026-04-28T16:30:16Z","modified":"2026-11-04T20:02:27.129164299Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8203-1","title":"linux-oracle, linux-oracle-6.8 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68746, CVE-2025-68753, CVE-2025-68755, CVE-2025-68756,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68763,\nCVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68770, CVE-2025-68771, CVE-2025-68772,\nCVE-2025-68773, CVE-2025-68774, CVE-2025-68775, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68782,\nCVE-2025-68783, CVE-2025-68785, CVE-2025-68786, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68794, CVE-2025-68795, CVE-2025-68796,\nCVE-2025-68797, CVE-2025-68798, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68804, CVE-2025-68806, CVE-2025-68808,\nCVE-2025-68809, CVE-2025-68810, CVE-2025-68811, CVE-2025-68813,\nCVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68817,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71149,\nCVE-2025-71150, CVE-2025-71151, CVE-2025-71153, CVE-2025-71154,\nCVE-2026-23060, CVE-2026-23074, CVE-2026-23111, CVE-2026-23209)\n","status":"published","published":"2026-04-23T09:52:44Z","modified":"2026-11-04T20:02:33.906318206Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8204-1","title":"linux-raspi-realtime vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality.\n(CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68746, CVE-2025-68753, CVE-2025-68755, CVE-2025-68756,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68763,\nCVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68770, CVE-2025-68771, CVE-2025-68772,\nCVE-2025-68773, CVE-2025-68774, CVE-2025-68775, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68782,\nCVE-2025-68783, CVE-2025-68785, CVE-2025-68786, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68794, CVE-2025-68795, CVE-2025-68796,\nCVE-2025-68797, CVE-2025-68798, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68804, CVE-2025-68806, CVE-2025-68808,\nCVE-2025-68809, CVE-2025-68810, CVE-2025-68811, CVE-2025-68813,\nCVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68817,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71080, CVE-2025-71081, CVE-2025-71082, CVE-2025-71083,\nCVE-2025-71084, CVE-2025-71085, CVE-2025-71086, CVE-2025-71087,\nCVE-2025-71088, CVE-2025-71089, CVE-2025-71091, CVE-2025-71093,\nCVE-2025-71094, CVE-2025-71095, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71101, CVE-2025-71102, CVE-2025-71104,\nCVE-2025-71105, CVE-2025-71107, CVE-2025-71108, CVE-2025-71109,\nCVE-2025-71111, CVE-2025-71112, CVE-2025-71113, CVE-2025-71114,\nCVE-2025-71116, CVE-2025-71118, CVE-2025-71119, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71122, CVE-2025-71123, CVE-2025-71125,\nCVE-2025-71126, CVE-2025-71127, CVE-2025-71130, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71135, CVE-2025-71136,\nCVE-2025-71137, CVE-2025-71138, CVE-2025-71140, CVE-2025-71141,\nCVE-2025-71143, CVE-2025-71144, CVE-2025-71147, CVE-2025-71148,\nCVE-2025-71149, CVE-2025-71150, CVE-2025-71151, CVE-2025-71153,\nCVE-2025-71154, CVE-2026-23209)\n","status":"published","published":"2026-04-23T10:00:50Z","modified":"2026-11-04T20:02:31.149520524Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8243-1","title":"linux-azure-5.15 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\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  - Nios II architecture;\n  - PowerPC architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - CPU frequency scaling framework;\n  - DMA engine subsystem;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - UACCE accelerator framework;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Framebuffer layer;\n  - W1 Dallas's 1-wire bus driver;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Memory management;\n  - padata parallel execution mechanism;\n  - IP tunnels definitions;\n  - NFC subsystem;\n  - Network traffic control;\n  - Network sockets;\n  - XFRM subsystem;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - IRQ subsystem;\n  - Locking primitives;\n  - Padata parallel execution mechanism;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - Rose network layer;\n  - SCTP protocol;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Rust bindings mechanism;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - Turtle Beach Wavefront ALSA driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Intel ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n(CVE-2022-49465, CVE-2022-49635, CVE-2023-53421, CVE-2023-53520,\nCVE-2023-53662, CVE-2023-54207, CVE-2024-36903, CVE-2024-36927,\nCVE-2024-37354, CVE-2024-41014, CVE-2024-46830, CVE-2024-47666,\nCVE-2024-49968, CVE-2024-53114, CVE-2024-56538, CVE-2024-58011,\nCVE-2025-21780, CVE-2025-21861, CVE-2025-22022, CVE-2025-22058,\nCVE-2025-22111, CVE-2025-22121, CVE-2025-23143, CVE-2025-37849,\nCVE-2025-38022, CVE-2025-38057, CVE-2025-38125, CVE-2025-38129,\nCVE-2025-38232, CVE-2025-38236, CVE-2025-38248, CVE-2025-38408,\nCVE-2025-38556, CVE-2025-38584, CVE-2025-38591, CVE-2025-39869,\nCVE-2025-39873, CVE-2025-39876, CVE-2025-39880, CVE-2025-39883,\nCVE-2025-39885, CVE-2025-39907, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39923, CVE-2025-39934, CVE-2025-39937, CVE-2025-39943,\nCVE-2025-39945, CVE-2025-39949, CVE-2025-39951, CVE-2025-39953,\nCVE-2025-39955, CVE-2025-39967, CVE-2025-39968, CVE-2025-39969,\nCVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973,\nCVE-2025-39980, CVE-2025-39985, CVE-2025-39986, CVE-2025-39987,\nCVE-2025-39988, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40001, CVE-2025-40006, CVE-2025-40011,\nCVE-2025-40020, CVE-2025-40021, CVE-2025-40026, CVE-2025-40027,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40035, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40048,\nCVE-2025-40049, CVE-2025-40053, CVE-2025-40055, CVE-2025-40060,\nCVE-2025-40068, CVE-2025-40070, CVE-2025-40078, CVE-2025-40081,\nCVE-2025-40083, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40094, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,\nCVE-2025-40127, CVE-2025-40134, CVE-2025-40140, CVE-2025-40149,\nCVE-2025-40153, CVE-2025-40154, CVE-2025-40164, CVE-2025-40167,\nCVE-2025-40171, CVE-2025-40173, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40194,\nCVE-2025-40200, CVE-2025-40204, CVE-2025-40205, CVE-2025-40211,\nCVE-2025-40215, CVE-2025-40219, CVE-2025-40220, CVE-2025-40223,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40240, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40248, CVE-2025-40252,\nCVE-2025-40253, CVE-2025-40254, CVE-2025-40257, CVE-2025-40258,\nCVE-2025-40259, CVE-2025-40261, CVE-2025-40262, CVE-2025-40263,\nCVE-2025-40264, CVE-2025-40269, CVE-2025-40271, CVE-2025-40272,\nCVE-2025-40273, CVE-2025-40275, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40304, CVE-2025-40306, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40319, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40324, CVE-2025-40331, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40349,\nCVE-2025-40351, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68185, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68194, CVE-2025-68200, CVE-2025-68204,\nCVE-2025-68211, CVE-2025-68217, CVE-2025-68220, CVE-2025-68227,\nCVE-2025-68229, CVE-2025-68238, CVE-2025-68241, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68249, CVE-2025-68254, CVE-2025-68255,\nCVE-2025-68257, CVE-2025-68258, CVE-2025-68261, CVE-2025-68264,\nCVE-2025-68266, CVE-2025-68282, CVE-2025-68284, CVE-2025-68285,\nCVE-2025-68286, CVE-2025-68287, CVE-2025-68288, CVE-2025-68289,\nCVE-2025-68290, CVE-2025-68295, CVE-2025-68301, CVE-2025-68302,\nCVE-2025-68303, CVE-2025-68308, CVE-2025-68312, CVE-2025-68321,\nCVE-2025-68325, CVE-2025-68327, CVE-2025-68328, CVE-2025-68330,\nCVE-2025-68331, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68339, CVE-2025-68340, CVE-2025-68344,\nCVE-2025-68346, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68364, CVE-2025-68365, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68372, CVE-2025-68724, CVE-2025-68725, CVE-2025-68727,\nCVE-2025-68728, CVE-2025-68732, CVE-2025-68733, CVE-2025-68734,\nCVE-2025-68740, CVE-2025-68746, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68764, CVE-2025-68765, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68771, CVE-2025-68774, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68787, CVE-2025-68788, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68803, CVE-2025-68804, CVE-2025-68808,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68817, CVE-2025-68818, CVE-2025-68819, CVE-2025-68820,\nCVE-2025-71064, CVE-2025-71066, CVE-2025-71068, CVE-2025-71069,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71096, CVE-2025-71097,\nCVE-2025-71098, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71108, CVE-2025-71111, CVE-2025-71112, CVE-2025-71113,\nCVE-2025-71114, CVE-2025-71116, CVE-2025-71118, CVE-2025-71120,\nCVE-2025-71121, CVE-2025-71125, CVE-2025-71127, CVE-2025-71131,\nCVE-2025-71132, CVE-2025-71133, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71147, CVE-2025-71154, CVE-2025-71162, CVE-2025-71163,\nCVE-2025-71180, CVE-2025-71182, CVE-2025-71185, CVE-2025-71186,\nCVE-2025-71188, CVE-2025-71190, CVE-2025-71191, CVE-2025-71194,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71199, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22980, CVE-2026-22982,\nCVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23011, CVE-2026-23019, CVE-2026-23020,\nCVE-2026-23021, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23056,\nCVE-2026-23058, CVE-2026-23060, CVE-2026-23061, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23071, CVE-2026-23073, CVE-2026-23074,\nCVE-2026-23075, CVE-2026-23076, CVE-2026-23078, CVE-2026-23080,\nCVE-2026-23083, CVE-2026-23084, CVE-2026-23085, CVE-2026-23087,\nCVE-2026-23089, CVE-2026-23090, CVE-2026-23091, CVE-2026-23093,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23101, CVE-2026-23103, CVE-2026-23105,\nCVE-2026-23108, CVE-2026-23111, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23124, CVE-2026-23125, CVE-2026-23128,\nCVE-2026-23133, CVE-2026-23146, CVE-2026-23150, CVE-2026-23164,\nCVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-05-07T08:44:20Z","modified":"2026-11-04T20:02:34.955235626Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8245-1","title":"linux-azure, linux-azure-6.17, linux-oem-6.17 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Mouse) drivers;\n  - IOMMU subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Freescale USB OTG Transceiver Driver;\n  - USB Type-C Connector System Software Interface driver;\n  - Watchdog drivers;\n  - BTRFS file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - XFS file system;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - BPF subsystem;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Sun RPC protocol;\n  - Key management;\n  - Landlock security;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-68351, CVE-2025-68353, CVE-2025-68365, CVE-2025-68368,\nCVE-2025-68725, CVE-2025-68736, CVE-2025-68745, CVE-2025-68767,\nCVE-2025-68768, CVE-2025-68769, CVE-2025-68770, CVE-2025-68771,\nCVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775,\nCVE-2025-68776, CVE-2025-68777, CVE-2025-68778, CVE-2025-68780,\nCVE-2025-68781, CVE-2025-68782, CVE-2025-68783, CVE-2025-68784,\nCVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788,\nCVE-2025-68791, CVE-2025-68792, CVE-2025-68793, CVE-2025-68794,\nCVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68798,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68802,\nCVE-2025-68803, CVE-2025-68804, CVE-2025-68805, CVE-2025-68806,\nCVE-2025-68807, CVE-2025-68808, CVE-2025-68809, CVE-2025-68810,\nCVE-2025-68811, CVE-2025-68813, CVE-2025-68814, CVE-2025-68815,\nCVE-2025-68816, CVE-2025-68817, CVE-2025-68818, CVE-2025-68819,\nCVE-2025-68820, CVE-2025-68821, CVE-2025-68822, CVE-2025-68823,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71070, CVE-2025-71071,\nCVE-2025-71072, CVE-2025-71073, CVE-2025-71075, CVE-2025-71076,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71081,\nCVE-2025-71082, CVE-2025-71083, CVE-2025-71084, CVE-2025-71085,\nCVE-2025-71086, CVE-2025-71087, CVE-2025-71089, CVE-2025-71091,\nCVE-2025-71093, CVE-2025-71094, CVE-2025-71095, CVE-2025-71096,\nCVE-2025-71097, CVE-2025-71098, CVE-2025-71099, CVE-2025-71100,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71115,\nCVE-2025-71116, CVE-2025-71117, CVE-2025-71118, CVE-2025-71119,\nCVE-2025-71120, CVE-2025-71121, CVE-2025-71122, CVE-2025-71123,\nCVE-2025-71124, CVE-2025-71125, CVE-2025-71126, CVE-2025-71130,\nCVE-2025-71131, CVE-2025-71132, CVE-2025-71133, CVE-2025-71135,\nCVE-2025-71136, CVE-2025-71137, CVE-2025-71138, CVE-2025-71140,\nCVE-2025-71143, CVE-2025-71146, CVE-2025-71147, CVE-2025-71148,\nCVE-2025-71150, CVE-2025-71151, CVE-2025-71153, CVE-2025-71154,\nCVE-2025-71156, CVE-2025-71157, CVE-2026-23091, CVE-2026-23112,\nCVE-2026-23209, CVE-2026-23231)\n","status":"published","published":"2026-05-07T09:47:31Z","modified":"2026-11-04T20:01:25.095663503Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8258-1","title":"linux-azure vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68746, CVE-2025-68753, CVE-2025-68755, CVE-2025-68756,\nCVE-2025-68757, CVE-2025-68758, CVE-2025-68759, CVE-2025-68763,\nCVE-2025-68764, CVE-2025-68765, CVE-2025-68766, CVE-2025-68767,\nCVE-2025-68769, CVE-2025-68770, CVE-2025-68771, CVE-2025-68772,\nCVE-2025-68773, CVE-2025-68774, CVE-2025-68775, CVE-2025-68776,\nCVE-2025-68777, CVE-2025-68778, CVE-2025-68780, CVE-2025-68782,\nCVE-2025-68783, CVE-2025-68785, CVE-2025-68786, CVE-2025-68787,\nCVE-2025-68788, CVE-2025-68794, CVE-2025-68795, CVE-2025-68796,\nCVE-2025-68797, CVE-2025-68798, CVE-2025-68799, CVE-2025-68800,\nCVE-2025-68801, CVE-2025-68804, CVE-2025-68806, CVE-2025-68808,\nCVE-2025-68809, CVE-2025-68810, CVE-2025-68811, CVE-2025-68813,\nCVE-2025-68814, CVE-2025-68815, CVE-2025-68816, CVE-2025-68817,\nCVE-2025-68818, CVE-2025-68819, CVE-2025-68820, CVE-2025-68821,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71150,\nCVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2026-23112,\nCVE-2026-23209, CVE-2026-23231)\n","status":"published","published":"2026-05-07T15:27:52Z","modified":"2026-11-04T20:01:44.192195069Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8261-1","title":"linux-xilinx vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\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  - Nios II architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - Locking primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-21833, CVE-2025-22022, CVE-2025-22103,\nCVE-2025-22105, CVE-2025-22106, CVE-2025-22107, CVE-2025-22111,\nCVE-2025-22113, CVE-2025-22121, CVE-2025-22124, CVE-2025-22125,\nCVE-2025-23129, CVE-2025-23130, CVE-2025-23133, CVE-2025-23143,\nCVE-2025-37860, CVE-2025-38022, CVE-2025-38105, CVE-2025-38234,\nCVE-2025-38502, CVE-2025-38556, CVE-2025-38627, CVE-2025-38643,\nCVE-2025-38709, CVE-2025-39678, CVE-2025-39697, CVE-2025-39805,\nCVE-2025-39806, CVE-2025-39807, CVE-2025-39808, CVE-2025-39810,\nCVE-2025-39811, CVE-2025-39812, CVE-2025-39813, CVE-2025-39815,\nCVE-2025-39817, CVE-2025-39819, CVE-2025-39823, CVE-2025-39824,\nCVE-2025-39825, CVE-2025-39826, CVE-2025-39827, CVE-2025-39828,\nCVE-2025-39829, CVE-2025-39832, CVE-2025-39835, CVE-2025-39836,\nCVE-2025-39838, CVE-2025-39839, CVE-2025-39841, CVE-2025-39842,\nCVE-2025-39843, CVE-2025-39844, CVE-2025-39845, CVE-2025-39846,\nCVE-2025-39847, CVE-2025-39848, CVE-2025-39849, CVE-2025-39850,\nCVE-2025-39851, CVE-2025-39852, CVE-2025-39853, CVE-2025-39854,\nCVE-2025-39857, CVE-2025-39860, CVE-2025-39861, CVE-2025-39863,\nCVE-2025-39864, CVE-2025-39865, CVE-2025-39866, CVE-2025-39869,\nCVE-2025-39870, CVE-2025-39871, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39877, CVE-2025-39880, CVE-2025-39881, CVE-2025-39883,\nCVE-2025-39885, CVE-2025-39886, CVE-2025-39891, CVE-2025-39894,\nCVE-2025-39895, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40164, CVE-2025-40165, CVE-2025-40166,\nCVE-2025-40167, CVE-2025-40169, CVE-2025-40171, CVE-2025-40172,\nCVE-2025-40173, CVE-2025-40176, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40200, CVE-2025-40201, CVE-2025-40202,\nCVE-2025-40204, CVE-2025-40205, CVE-2025-40206, CVE-2025-40207,\nCVE-2025-40211, CVE-2025-40218, CVE-2025-40219, CVE-2025-40220,\nCVE-2025-40221, CVE-2025-40223, CVE-2025-40226, CVE-2025-40231,\nCVE-2025-40233, CVE-2025-40235, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40240, CVE-2025-40242, CVE-2025-40243, CVE-2025-40244,\nCVE-2025-40245, CVE-2025-40248, CVE-2025-40250, CVE-2025-40251,\nCVE-2025-40252, CVE-2025-40253, CVE-2025-40254, CVE-2025-40257,\nCVE-2025-40258, CVE-2025-40259, CVE-2025-40261, CVE-2025-40262,\nCVE-2025-40263, CVE-2025-40264, CVE-2025-40266, CVE-2025-40268,\nCVE-2025-40269, CVE-2025-40271, CVE-2025-40272, CVE-2025-40273,\nCVE-2025-40275, CVE-2025-40277, CVE-2025-40278, CVE-2025-40279,\nCVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283,\nCVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287,\nCVE-2025-40288, CVE-2025-40289, CVE-2025-40292, CVE-2025-40293,\nCVE-2025-40294, CVE-2025-40301, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40317,\nCVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40325,\nCVE-2025-40328, CVE-2025-40329, CVE-2025-40331, CVE-2025-40333,\nCVE-2025-40337, CVE-2025-40339, CVE-2025-40341, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40347,\nCVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40353,\nCVE-2025-40358, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168,\nCVE-2025-68171, CVE-2025-68172, CVE-2025-68173, CVE-2025-68176,\nCVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180,\nCVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68190,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68198,\nCVE-2025-68200, CVE-2025-68201, CVE-2025-68204, CVE-2025-68206,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68254, CVE-2025-68255, CVE-2025-68256,\nCVE-2025-68257, CVE-2025-68258, CVE-2025-68259, CVE-2025-68261,\nCVE-2025-68263, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68283, CVE-2025-68284, CVE-2025-68285,\nCVE-2025-68286, CVE-2025-68287, CVE-2025-68288, CVE-2025-68289,\nCVE-2025-68290, CVE-2025-68295, CVE-2025-68297, CVE-2025-68301,\nCVE-2025-68302, CVE-2025-68303, CVE-2025-68305, CVE-2025-68307,\nCVE-2025-68308, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68315, CVE-2025-68320, CVE-2025-68321,\nCVE-2025-68322, CVE-2025-68325, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68344, CVE-2025-68345,\nCVE-2025-68346, CVE-2025-68347, CVE-2025-68349, CVE-2025-68354,\nCVE-2025-68362, CVE-2025-68363, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68734, CVE-2025-68740, CVE-2025-68741, CVE-2025-68742,\nCVE-2025-68744, CVE-2025-68746, CVE-2025-68753, CVE-2025-68755,\nCVE-2025-68756, CVE-2025-68757, CVE-2025-68758, CVE-2025-68759,\nCVE-2025-68763, CVE-2025-68764, CVE-2025-68765, CVE-2025-68766,\nCVE-2025-68767, CVE-2025-68769, CVE-2025-68770, CVE-2025-68771,\nCVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775,\nCVE-2025-68776, CVE-2025-68777, CVE-2025-68778, CVE-2025-68780,\nCVE-2025-68782, CVE-2025-68783, CVE-2025-68785, CVE-2025-68786,\nCVE-2025-68787, CVE-2025-68788, CVE-2025-68794, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68798, CVE-2025-68799,\nCVE-2025-68800, CVE-2025-68801, CVE-2025-68804, CVE-2025-68806,\nCVE-2025-68808, CVE-2025-68809, CVE-2025-68810, CVE-2025-68811,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68817, CVE-2025-68818, CVE-2025-68819, CVE-2025-68820,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71125, CVE-2025-71126, CVE-2025-71127,\nCVE-2025-71130, CVE-2025-71131, CVE-2025-71132, CVE-2025-71133,\nCVE-2025-71135, CVE-2025-71136, CVE-2025-71137, CVE-2025-71138,\nCVE-2025-71140, CVE-2025-71141, CVE-2025-71143, CVE-2025-71147,\nCVE-2025-71148, CVE-2025-71150, CVE-2025-71151, CVE-2025-71153,\nCVE-2025-71154, CVE-2026-23060, CVE-2026-23074, CVE-2026-23111,\nCVE-2026-23112, CVE-2026-23209, CVE-2026-23231, CVE-2026-23273)\n","status":"published","published":"2026-05-07T15:54:20Z","modified":"2026-09-07T14:05:25.637433365Z","updated_at":"2026-11-02T16:58:22.951676Z"},{"id":"USN-8265-1","title":"linux-nvidia-tegra vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - ACPI drivers;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Hardware crypto device drivers;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - Watchdog drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - io_uring subsystem;\n  - Locking primitives;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Tracing infrastructure;\n  - Memory management;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - Rose network layer;\n  - Network traffic control;\n  - Network sockets;\n  - Sun RPC protocol;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-22022, CVE-2025-22111, CVE-2025-38022,\nCVE-2025-38234, CVE-2025-40164, CVE-2025-40325, CVE-2025-68206,\nCVE-2025-68254, CVE-2025-68255, CVE-2025-68256, CVE-2025-68257,\nCVE-2025-68258, CVE-2025-68259, CVE-2025-68261, CVE-2025-68263,\nCVE-2025-68264, CVE-2025-68265, CVE-2025-68266, CVE-2025-68291,\nCVE-2025-68325, CVE-2025-68332, CVE-2025-68335, CVE-2025-68336,\nCVE-2025-68337, CVE-2025-68344, CVE-2025-68345, CVE-2025-68346,\nCVE-2025-68347, CVE-2025-68349, CVE-2025-68354, CVE-2025-68362,\nCVE-2025-68363, CVE-2025-68364, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68740, CVE-2025-68741, CVE-2025-68742, CVE-2025-68744,\nCVE-2025-68753, CVE-2025-68755, CVE-2025-68756, CVE-2025-68757,\nCVE-2025-68758, CVE-2025-68759, CVE-2025-68763, CVE-2025-68764,\nCVE-2025-68765, CVE-2025-68766, CVE-2025-68767, CVE-2025-68769,\nCVE-2025-68770, CVE-2025-68771, CVE-2025-68772, CVE-2025-68773,\nCVE-2025-68774, CVE-2025-68775, CVE-2025-68776, CVE-2025-68777,\nCVE-2025-68778, CVE-2025-68780, CVE-2025-68782, CVE-2025-68783,\nCVE-2025-68785, CVE-2025-68786, CVE-2025-68787, CVE-2025-68788,\nCVE-2025-68794, CVE-2025-68795, CVE-2025-68796, CVE-2025-68797,\nCVE-2025-68798, CVE-2025-68799, CVE-2025-68800, CVE-2025-68801,\nCVE-2025-68804, CVE-2025-68806, CVE-2025-68808, CVE-2025-68809,\nCVE-2025-68810, CVE-2025-68811, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68817, CVE-2025-68818,\nCVE-2025-68819, CVE-2025-68820, CVE-2025-68821, CVE-2025-71064,\nCVE-2025-71065, CVE-2025-71066, CVE-2025-71067, CVE-2025-71068,\nCVE-2025-71069, CVE-2025-71071, CVE-2025-71072, CVE-2025-71075,\nCVE-2025-71077, CVE-2025-71078, CVE-2025-71079, CVE-2025-71080,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71150,\nCVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2026-23209)\n","status":"published","published":"2026-05-11T12:47:33Z","modified":"2026-11-04T20:01:45.20291432Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8440-1","title":"linux-azure-6.8 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\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  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PHY drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - W1 Dallas's 1-wire bus driver;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Perf events;\n  - Locking primitives;\n  - Shadow Call Stack mechanism;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Open vSwitch;\n  - Packet sockets;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-57795, CVE-2024-58096, CVE-2024-58097,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-37926, CVE-2025-38022,\nCVE-2025-38201, CVE-2025-38234, CVE-2025-38591, CVE-2025-40039,\nCVE-2025-40082, CVE-2025-40149, CVE-2025-40164, CVE-2025-40325,\nCVE-2025-68206, CVE-2025-68254, CVE-2025-68255, CVE-2025-68256,\nCVE-2025-68257, CVE-2025-68258, CVE-2025-68259, CVE-2025-68261,\nCVE-2025-68263, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266,\nCVE-2025-68291, CVE-2025-68325, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68344, CVE-2025-68345,\nCVE-2025-68346, CVE-2025-68347, CVE-2025-68349, CVE-2025-68351,\nCVE-2025-68354, CVE-2025-68358, CVE-2025-68362, CVE-2025-68363,\nCVE-2025-68364, CVE-2025-68365, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68725, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732,\nCVE-2025-68733, CVE-2025-68740, CVE-2025-68741, CVE-2025-68742,\nCVE-2025-68744, CVE-2025-68746, CVE-2025-68749, CVE-2025-68753,\nCVE-2025-68755, CVE-2025-68756, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68763, CVE-2025-68764, CVE-2025-68765,\nCVE-2025-68766, CVE-2025-68767, CVE-2025-68769, CVE-2025-68770,\nCVE-2025-68771, CVE-2025-68772, CVE-2025-68773, CVE-2025-68774,\nCVE-2025-68775, CVE-2025-68776, CVE-2025-68777, CVE-2025-68778,\nCVE-2025-68780, CVE-2025-68782, CVE-2025-68783, CVE-2025-68785,\nCVE-2025-68786, CVE-2025-68787, CVE-2025-68788, CVE-2025-68794,\nCVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68798,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68803,\nCVE-2025-68804, CVE-2025-68806, CVE-2025-68808, CVE-2025-68809,\nCVE-2025-68810, CVE-2025-68811, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68817, CVE-2025-68818,\nCVE-2025-68819, CVE-2025-68820, CVE-2025-68821, CVE-2025-68823,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71150,\nCVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2025-71160,\nCVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182,\nCVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71220, CVE-2025-71222, CVE-2025-71224,\nCVE-2025-71225, CVE-2025-71268, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982,\nCVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998,\nCVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23005, CVE-2026-23006, CVE-2026-23010, CVE-2026-23011,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23025,\nCVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032,\nCVE-2026-23033, CVE-2026-23035, CVE-2026-23037, CVE-2026-23038,\nCVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23053,\nCVE-2026-23054, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23068, CVE-2026-23069,\nCVE-2026-23071, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23078, CVE-2026-23080, CVE-2026-23083, CVE-2026-23084,\nCVE-2026-23085, CVE-2026-23086, CVE-2026-23087, CVE-2026-23088,\nCVE-2026-23089, CVE-2026-23090, CVE-2026-23091, CVE-2026-23093,\nCVE-2026-23094, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23105, CVE-2026-23107, CVE-2026-23108,\nCVE-2026-23110, CVE-2026-23112, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23204, CVE-2026-23205, CVE-2026-23206, CVE-2026-23209,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23231, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31676, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,\nCVE-2026-43362, CVE-2026-43494, CVE-2026-46028, CVE-2026-46323)\n","status":"published","published":"2026-06-16T22:30:05Z","modified":"2026-11-07T01:45:16.546246471Z","updated_at":"2026-11-07T01:57:06.567161Z"}]}}