{"id":"CVE-2026-23011","aliases":["AZL-77121","BELL-CVE-2026-23011","CLSA-2026-1778756832","CLSA-2026-1778757276","CLSA-2026-1778759582","CLSA-2026-1779987841","CLSA-2026-1780052998","CLSA-2026-1783791022","DEBIAN-CVE-2026-23011","DLA-4475-1","DLA-4476-1","DSA-6126-1","DSA-6127-1","EUVD-2026-4623","GHSA-5ww3-m3hh-c9fg","OESA-2026-1566","OESA-2026-1567","OESA-2026-1570","OESA-2026-2582","ROOT-OS-DEBIAN-11-CVE-2026-23011","ROOT-OS-DEBIAN-12-CVE-2026-23011","ROOT-OS-UBUNTU-2204-CVE-2026-23011","ROOT-OS-UBUNTU-2404-CVE-2026-23011","SUSE-SU-2026:0447-1","SUSE-SU-2026:0472-1","SUSE-SU-2026:0473-1","SUSE-SU-2026:0587-1","SUSE-SU-2026:20477-1","SUSE-SU-2026:20498-1","SUSE-SU-2026:20555-1","SUSE-SU-2026:20570-1","SUSE-SU-2026:20599-1","SUSE-SU-2026:20615-1","SUSE-SU-2026:20845-1","SUSE-SU-2026:20876-1","UBUNTU-CVE-2026-23011","USN-8162-1","USN-8180-1","USN-8180-2","USN-8180-3","USN-8180-4","USN-8180-5","USN-8180-6","USN-8186-1","USN-8187-1","USN-8188-1","USN-8243-1","USN-8275-1","USN-8278-1","USN-8278-2","USN-8289-1","USN-8289-2","USN-8296-1","USN-8296-2","USN-8297-1","USN-8393-1","USN-8440-1","USN-8499-1","USN-8570-1","USN-8570-2","USN-8594-1","USN-8604-1","USN-8605-1","USN-8669-1","openSUSE-SU-2026:20287-1"],"status":"published","title":"ipv4: ip_gre: make ipgre_header() robust","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\"ip6_gre: make ip6gre_header() robust\")\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u003eneeded_headroom and/or dev-\u003ehard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u003cTASK\u003e\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246","severity":{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-12","score":0.0021,"percentile":0.11268,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-119"],"published":"2026-01-25T14:36:24Z","modified":"2026-11-12T17:25:27Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.126.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.163-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.73-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["5.10.249","5.15.199","6.1.162","6.6.122","6.12.67","6.18.7"],"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.8-1"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:11","package":"rootio-linux","fixed_in":["5.10.262-1.aikido.113","5.10.262-1.aikido.114"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"Root:Debian:12","package":"rootio-linux","fixed_in":["6.1.190-1.aikido.167"],"sources":["osv"]},{"ecosystem":"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-1105.112~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-1106.115~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","fixed_in":["5.15.0-176.186~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","fixed_in":["5.15.0-1099.102~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","fixed_in":["5.15.0-1100.106~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","fixed_in":["5.15.0-175.185~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","fixed_in":["5.15.0-1057.57~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","fixed_in":["5.15.0-1102.108~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-riscv-5.15","fixed_in":["5.15.0-1099.103~20.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux","fixed_in":["5.15.0-176.186"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","fixed_in":["5.15.0-1105.112"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1057.60~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","fixed_in":["5.15.0-1110.119"],"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-1114.123"],"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-1105.114"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1060.63~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","fixed_in":["5.15.0-1101.107"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","fixed_in":["5.15.0-1088.96"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-124.124~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","fixed_in":["5.15.0-1099.102"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1055.56~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","fixed_in":["5.15.0-1100.106"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","fixed_in":["5.15.0-1097.102"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","fixed_in":["5.15.0-175.185"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-117.117.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","fixed_in":["5.15.0-1100.101"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1054.57~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","fixed_in":["5.15.0-1057.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","fixed_in":["5.15.0-1046.46"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","fixed_in":["5.15.0-1102.108"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1054.55~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","fixed_in":["5.15.0-1099.102"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-117.117~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-xilinx-zynqmp","fixed_in":["5.15.0-1070.74"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","fixed_in":["5.15.0-1089.91"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","fixed_in":["5.15.0-1097.99"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","fixed_in":["5.15.0-1104.113"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1051.52~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","fixed_in":["5.15.0-1105.112+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","fixed_in":["5.15.0-1110.119+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","fixed_in":["5.15.0-176.186+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","fixed_in":["5.15.0-1105.114+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-117.117"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1055.58"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1056.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","fixed_in":["6.17.0-1021.21~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-1058.61"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","fixed_in":["6.17.0-1021.24~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1054.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1041.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","fixed_in":["6.17.0-41.41~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1055.56"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-117.117.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1054.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","fixed_in":["6.17.0-1031.31"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1054.57.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1024.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","fixed_in":["6.17.0-1030.30"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1054.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","fixed_in":["6.17.0-1019.19~24.04.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1056.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1032.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1022.26"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2045.46"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1051.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","fixed_in":["6.17.0-1018.20~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1055.58+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1059.65+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-116.116+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1058.61+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.126.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.161-r0"},{"fixed":"6.1.163-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.66-r0"},{"fixed":"6.12.73-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":"TuxCare:CentOS:7","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:CentOS:7","package":"python-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:OracleLinux:7","package":"python-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:RHEL:7","package":"python-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.10.0-1160.144.1.el7.tuxcare.els5"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"bpftool","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.0.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-64k-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"libbpf-static","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:1.0.0-2.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.2","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-284.1101.el9_2.tuxcare.11.els2"}]}],"bundled":109},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-abi-stablelists","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-cross-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-debug-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-headers","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-ipaclones-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-debug-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-devel-matched","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-extra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-rt-modules-partner","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-selftests-internal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-tools-libs-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"kernel-uki-virt-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"libperf-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"python3-perf","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rtla","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:AlmaLinux:9.6","package":"rv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.14.0-570.62.1.el9_6.tuxcare.5.els2"}]}],"bundled":102},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-buildinfo-5.4.0-235-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-buildinfo-5.4.0-235-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-235","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-235-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-235-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-235","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-235-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-235-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-image-unsigned-5.4.0-235-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-image-unsigned-5.4.0-235-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-5.4.0-235-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-5.4.0-235-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-extra-5.4.0-235-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-source-5.4.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-235","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-235-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-235-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-235.255+tuxcare.els1"}]}],"bundled":40},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.10.0"},{"fixed":"5.10.249"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.11.0"},{"fixed":"5.15.199"}]},{"type":"ECOSYSTEM","events":[{"introduced":"5.16.0"},{"fixed":"6.1.162"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.122"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.67"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.7"}]}]},{"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.8-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.111-1","6.12.113-1","6.12.115-1","6.12.115-2","6.12.116-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.3-1","6.18.5-1","6.18.5-1~bpo13+1","6.18~rc4-1~exp1","6.18~rc4-1~exp2","6.18~rc5-1~exp1","6.18~rc6-1~exp1","6.18~rc7-1~exp1"]},{"source":"osv","ecosystem":"Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.249-1"}]}],"versions":["5.10.103-1","5.10.103-1~bpo10+1","5.10.106-1","5.10.113-1","5.10.120-1","5.10.120-1~bpo10+1","5.10.127-1","5.10.127-2","5.10.127-2~bpo10+1","5.10.136-1","5.10.140-1","5.10.148-1","5.10.149-1","5.10.149-2","5.10.158-1","5.10.158-2","5.10.162-1","5.10.178-1","5.10.178-2","5.10.178-3","5.10.179-1","5.10.179-2","5.10.179-3","5.10.179-4","5.10.179-5","5.10.191-1","5.10.197-1","5.10.205-1","5.10.205-2","5.10.209-1","5.10.209-2","5.10.216-1","5.10.218-1","5.10.221-1","5.10.223-1","5.10.226-1","5.10.234-1","5.10.237-1","5.10.244-1","5.10.247-1","5.10.46-4","5.10.46-5","5.10.70-1","5.10.70-1~bpo10+1","5.10.84-1","5.10.92-1","5.10.92-1~bpo10+1","5.10.92-2"],"bundled":165},{"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":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-142.0.0.136.oe2403sp1"}]}],"bundled":73},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-142.0.0.137.oe2403sp2"}]}],"bundled":73},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-142.0.0.124.oe2403"}]}],"bundled":73},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-145.3.14.145.oe2403sp3"}]}],"bundled":150},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"Root:Debian:12","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.190-1.aikido.167"}]}]},{"source":"osv","ecosystem":"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 Enterprise Module for Basesystem 15 SP7","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1.150700.17.21.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7_Update_9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.15.3.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.20.27.1"}]}],"bundled":172},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-source-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.20.27.1"}]}],"bundled":172},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-syms-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.20.27.1"}]}],"bundled":172},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.293.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kgraft-patch-SLE12-SP5_Update_77","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-8.3.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.293.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.293.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.293.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.293.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.293.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.293.1"}]}],"bundled":145},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7-RT_Update_9","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.1.3.2"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.31.2"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Real Time Module 15 SP7","package":"kernel-syms-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.7.31.1"}]}],"bundled":171},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":524},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1.21.16"}]}],"bundled":524},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":524},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":524},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":524},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1.21.16"}]}],"bundled":524},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":524},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-39.1"}]}],"bundled":524},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1.160000.2.7"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1.160000.2.7"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"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.26.1.160000.2.7"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"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.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-40.1"}]}],"bundled":655},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-40.1"}]}],"bundled":655},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-40.1"}]}],"bundled":655},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.1","package":"kernel-source-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-40.1"}]}],"bundled":655},{"source":"osv","ecosystem":"Ubuntu:Pro:14.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.11.0-12.19","3.12.0-1.3","3.12.0-2.5","3.12.0-2.7","3.12.0-3.8","3.12.0-3.9","3.12.0-4.10","3.12.0-4.12","3.12.0-5.13","3.12.0-7.15","3.13.0-1.16","3.13.0-2.17","3.13.0-3.18","3.13.0-4.19","3.13.0-5.20","3.13.0-6.23","3.13.0-7.25","3.13.0-7.26","3.13.0-8.27","3.13.0-8.28","3.13.0-10.30","3.13.0-11.31","3.13.0-12.32","3.13.0-13.33","3.13.0-14.34","3.13.0-15.35","3.13.0-16.36","3.13.0-17.37","3.13.0-18.38","3.13.0-19.39","3.13.0-19.40","3.13.0-20.42","3.13.0-21.43","3.13.0-22.44","3.13.0-23.45","3.13.0-24.46","3.13.0-24.47","3.13.0-27.50","3.13.0-29.53","3.13.0-30.54","3.13.0-30.55","3.13.0-32.57","3.13.0-33.58","3.13.0-34.60","3.13.0-35.62","3.13.0-36.63","3.13.0-37.64","3.13.0-39.66","3.13.0-40.69","3.13.0-41.70","3.13.0-43.72","3.13.0-44.73","3.13.0-45.74","3.13.0-46.75","3.13.0-46.76","3.13.0-46.77","3.13.0-46.79","3.13.0-48.80","3.13.0-49.81","3.13.0-49.83","3.13.0-51.84","3.13.0-52.85","3.13.0-52.86","3.13.0-53.88","3.13.0-53.89","3.13.0-54.91","3.13.0-55.92","3.13.0-55.94","3.13.0-57.95","3.13.0-58.97","3.13.0-59.98","3.13.0-61.100","3.13.0-62.102","3.13.0-63.103","3.13.0-65.105","3.13.0-65.106","3.13.0-66.108","3.13.0-67.110","3.13.0-68.111","3.13.0-70.113","3.13.0-71.114","3.13.0-73.116","3.13.0-74.118","3.13.0-76.120","3.13.0-77.121","3.13.0-79.123","3.13.0-83.127","3.13.0-85.129","3.13.0-86.130","3.13.0-86.131","3.13.0-87.133","3.13.0-88.135","3.13.0-91.138","3.13.0-92.139","3.13.0-93.140","3.13.0-95.142","3.13.0-96.143","3.13.0-98.145","3.13.0-100.147","3.13.0-101.148","3.13.0-103.150","3.13.0-105.152","3.13.0-106.153","3.13.0-107.154","3.13.0-108.155","3.13.0-109.156","3.13.0-110.157","3.13.0-111.158","3.13.0-112.159","3.13.0-113.160","3.13.0-115.162","3.13.0-116.163","3.13.0-117.164","3.13.0-119.166","3.13.0-121.170","3.13.0-123.172","3.13.0-125.174","3.13.0-126.175","3.13.0-128.177","3.13.0-129.178","3.13.0-132.181","3.13.0-133.182","3.13.0-135.184","3.13.0-137.186","3.13.0-139.188","3.13.0-141.190","3.13.0-142.191","3.13.0-143.192","3.13.0-144.193","3.13.0-145.194","3.13.0-147.196","3.13.0-149.199","3.13.0-151.201","3.13.0-153.203","3.13.0-155.205","3.13.0-156.206","3.13.0-157.207","3.13.0-158.208","3.13.0-160.210","3.13.0-161.211","3.13.0-162.212","3.13.0-163.213","3.13.0-164.214","3.13.0-165.215","3.13.0-166.216","3.13.0-167.217","3.13.0-168.218","3.13.0-169.219","3.13.0-170.220","3.13.0-171.222","3.13.0-172.223","3.13.0-173.224","3.13.0-174.225","3.13.0-175.226","3.13.0-176.227","3.13.0-180.231","3.13.0-181.232","3.13.0-182.233","3.13.0-183.234","3.13.0-184.235","3.13.0-185.236","3.13.0-186.237","3.13.0-187.238","3.13.0-188.239","3.13.0-189.240","3.13.0-190.241","3.13.0-191.242","3.13.0-192.243","3.13.0-193.244","3.13.0-194.245","3.13.0-195.246","3.13.0-196.247","3.13.0-197.248","3.13.0-198.249","3.13.0-199.250","3.13.0-200.251","3.13.0-201.252","3.13.0-202.253","3.13.0-203.254","3.13.0-204.255","3.13.0-205.256","3.13.0-206.257","3.13.0-207.258","3.13.0-208.259","3.13.0-209.260","3.13.0-210.261","3.13.0-211.262","3.13.0-212.263","3.13.0-214.265","3.13.0-215.266","3.13.0-217.268","3.13.0-218.269","3.13.0-219.270","3.13.0-220.271"]},{"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-1105.112~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","5.15.0-1103.110~20.04.1","5.15.0-1104.111~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-1106.115~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","5.15.0-1103.112~20.04.1","5.15.0-1104.113~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-176.186~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","5.15.0-173.183~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-1099.102~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","5.15.0-1097.100~20.04.1","5.15.0-1098.101~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-1100.106~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","5.15.0-1098.104~20.04.1","5.15.0-1099.105~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-175.185~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","5.15.0-173.183~20.04.1","5.15.0-174.184~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-1057.57~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","5.15.0-1055.55~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-1102.108~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","5.15.0-1100.106~20.04.1","5.15.0-1101.107~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-1099.103~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","5.15.0-1097.101~20.04.1","5.15.0-1098.102~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-176.186"}]}],"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","5.15.0-173.183","5.15.0-174.184"]},{"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-1105.112"}]}],"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","5.15.0-1103.110","5.15.0-1104.111"]},{"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-1057.60~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","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1055.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1110.119"}]}],"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","5.15.0-1109.118"]},{"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-1114.123"}]}],"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","5.15.0-1109.118.1","5.15.0-1110.119.1","5.15.0-1111.120.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-1105.114"}]}],"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","5.15.0-1103.112","5.15.0-1104.113"]},{"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-1060.63~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","6.8.0-1054.57~22.04.1","6.8.0-1058.61~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1101.107"}]}],"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","5.15.0-1099.105","5.15.0-1100.106"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1088.96"}]}],"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","5.15.0-1086.94","5.15.0-1087.95"]},{"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-124.124~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","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.102"}]}],"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","5.15.0-1097.100","5.15.0-1098.101"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56~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","6.8.0-1051.51~22.04.1","6.8.0-1052.52~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-1100.106"}]}],"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","5.15.0-1098.104","5.15.0-1099.105"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.102"}]}],"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","5.15.0-1095.100","5.15.0-1096.101"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-175.185"}]}],"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","5.15.0-173.183","5.15.0-174.184"]},{"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-117.117.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","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.101"}]}],"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","5.15.0-1098.99","5.15.0-1099.100"]},{"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-1054.57~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","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1057.57"}]}],"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","5.15.0-1055.55","5.15.0-1056.56"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1046.46"}]}],"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","5.15.0-1044.44","5.15.0-1045.45"]},{"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-1102.108"}]}],"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","5.15.0-1100.106","5.15.0-1101.107"]},{"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-1054.55~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","6.8.0-1049.50~22.04.1","6.8.0-1050.51~22.04.1","6.8.0-1052.53~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.102"}]}],"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","5.15.0-1097.100","5.15.0-1098.101"]},{"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-117.117~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","6.8.0-110.110~22.04.1","6.8.0-111.111~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-1070.74"}]}],"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","5.15.0-1067.71","5.15.0-1068.72","5.15.0-1069.73"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1089.91"}]}],"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","5.15.0-1086.88","5.15.0-1087.89"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.99"}]}],"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","5.15.0-1094.96","5.15.0-1096.98"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1104.113"}]}],"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","5.15.0-1102.111","5.15.0-1103.112"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52~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","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1042.47+fips1","5.15.0-1051.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1053.61+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-73.80+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-preview:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1048.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1105.112+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","5.15.0-1103.110+fips1","5.15.0-1104.111+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-1110.119+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","5.15.0-1109.118+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-176.186+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","5.15.0-173.183+fips1","5.15.0-174.184+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-1105.114+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","5.15.0-1103.112+fips1","5.15.0-1104.113+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117"}]}],"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","6.8.0-110.110","6.8.0-111.111"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58"}]}],"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","6.8.0-1052.55","6.8.0-1053.56"]},{"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"}]}],"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","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1019.19~24.04.1","6.17.0-1020.20~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.62"}]}],"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","6.8.0-1054.60"]},{"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-1021.21~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","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1018.18~24.04.1","6.17.0-1020.20~24.04.1"]},{"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-1058.61"}]}],"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","6.8.0-1054.57","6.8.0-1055.58"]},{"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-1021.24~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","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1016.17~24.04.1","6.17.0-1018.19~24.04.1","6.17.0-1020.22~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"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","6.8.0-1050.56","6.8.0-1051.57"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1041.44"}]}],"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","6.8.0-1037.40","6.8.0-1038.41"]},{"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-41.41~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","6.17.0-22.22~24.04.1","6.17.0-23.23~24.04.1","6.17.0-29.29~24.04.1","6.17.0-35.35~24.04.1","6.17.0-40.40~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56"}]}],"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","6.8.0-1051.51","6.8.0-1052.52"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.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","6.8.0-110.110.1","6.8.0-111.111.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-1054.57"}]}],"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","6.8.0-1051.54","6.8.0-1052.55"]},{"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-1031.31"}]}],"versions":["6.17.0-1004.4","6.17.0-1008.8","6.17.0-1014.14","6.17.0-1018.18","6.17.0-1021.21","6.17.0-1026.26","6.17.0-1029.29"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57.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","6.8.0-1051.54.1","6.8.0-1052.55.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"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","6.8.0-1022.22","6.8.0-1023.23"]},{"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-1030.30"}]}],"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","6.17.0-1020.20","6.17.0-1023.23","6.17.0-1024.24","6.17.0-1025.25","6.17.0-1028.28"]},{"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-1054.55"}]}],"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","6.8.0-1049.50","6.8.0-1050.51","6.8.0-1052.53"]},{"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-1019.19~24.04.3"}]}],"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","6.17.0-1011.11~24.04.1","6.17.0-1014.14~24.04.1","6.17.0-1016.16~24.04.1","6.17.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.60"}]}],"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","6.8.0-1052.56","6.8.0-1053.57"]},{"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"}]}],"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","6.17.0-22.22.1~24.04.1","6.17.0-23.23.1~24.04.1","6.17.0-29.29.1~24.04.1","6.17.0-35.35.1~24.04.1","6.17.0-38.38.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1032.33"}]}],"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","6.8.0-1029.30"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.26"}]}],"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","6.8.0-1017.21"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2045.46"}]}],"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","6.8.0-2042.43","6.8.0-2043.44"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52"}]}],"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","6.8.1-1047.48","6.8.1-1048.49"]},{"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-1018.20~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","6.17.0-1010.11~24.04.1","6.17.0-1011.12~24.04.1","6.17.0-1013.15~24.04.1","6.17.0-1014.16~24.04.1","6.17.0-1017.19~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-1055.58+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","6.8.0-1052.55+fips1","6.8.0-1053.56+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-1059.65+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","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-116.116+fips1"}]}],"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","6.8.0-110.110+fips2","6.8.0-111.111+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-1058.61+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","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.17.0-22.22","6.17.0-23.23","6.17.0-29.29","6.17.0-35.35","6.17.0-40.40"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1020.20"]},{"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"}]}],"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","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1016.17","6.17.0-1018.19","6.17.0-1020.22"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1016.16","6.17.0-1018.18"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.17.0-1013.13","6.17.0-1014.14","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.17.0-1010.11","6.17.0-1011.12","6.17.0-1013.15","6.17.0-1014.16","6.17.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","6.17.0-22.22.1","6.17.0-23.23.1","6.17.0-29.29.1","6.17.0-35.35.1","6.17.0-40.40.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-1057.57~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","5.15.0-1055.55~20.04.1"],"bundled":84},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-aws-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1105.112~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","5.15.0-1103.110~20.04.1","5.15.0-1104.111~20.04.1"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-lowlatency-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-175.185~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","5.15.0-173.183~20.04.1","5.15.0-174.184~20.04.1"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-176.186"}]}],"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","5.15.0-173.183","5.15.0-174.184"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1105.112"}]}],"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","5.15.0-1103.110","5.15.0-1104.111"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1105.114"}]}],"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","5.15.0-1103.112","5.15.0-1104.113"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1101.107"}]}],"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","5.15.0-1099.105","5.15.0-1100.106"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1088.96"}]}],"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","5.15.0-1086.94","5.15.0-1087.95"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-175.185"}]}],"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","5.15.0-173.183","5.15.0-174.184"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.101"}]}],"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","5.15.0-1098.99","5.15.0-1099.100"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1102.108"}]}],"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","5.15.0-1100.106","5.15.0-1101.107"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-176.186+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","5.15.0-173.183+fips1","5.15.0-174.184+fips1"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1105.114+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","5.15.0-1103.112+fips1","5.15.0-1104.113+fips1"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-intel-iotg-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.106~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","5.15.0-1098.104~20.04.1","5.15.0-1099.105~20.04.1"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-oracle-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1102.108~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","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1110.119"}]}],"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","5.15.0-1109.118"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iotg","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1100.106"}]}],"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","5.15.0-1098.104","5.15.0-1099.105"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.102"}]}],"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","5.15.0-1095.100","5.15.0-1096.101"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1110.119+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","5.15.0-1109.118+fips1"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-ibm-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.102~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","5.15.0-1097.100~20.04.1","5.15.0-1098.101~20.04.1"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.102"}]}],"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","5.15.0-1097.100","5.15.0-1098.101"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1099.102"}]}],"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","5.15.0-1097.100","5.15.0-1098.101"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1097.99"}]}],"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","5.15.0-1094.96","5.15.0-1096.98"],"bundled":81},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1104.113"}]}],"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","5.15.0-1102.111","5.15.0-1103.112"],"bundled":81},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1057.57"}]}],"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","5.15.0-1055.55","5.15.0-1056.56"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1046.46"}]}],"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","5.15.0-1044.44","5.15.0-1045.45"],"bundled":80},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-hwe-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-176.186~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","5.15.0-173.183~20.04.1"],"bundled":84},{"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:22.04:LTS","package":"linux-xilinx-zynqmp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1070.74"}]}],"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","5.15.0-1067.71","5.15.0-1068.72","5.15.0-1069.73"],"bundled":84},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56~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","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.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","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52~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","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117"}]}],"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","6.8.0-110.110","6.8.0-111.111"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58"}]}],"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","6.8.0-1052.55","6.8.0-1053.56"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"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","6.8.0-1054.57","6.8.0-1055.58"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"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","6.8.0-1050.56","6.8.0-1051.57"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1041.44"}]}],"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","6.8.0-1037.40","6.8.0-1038.41"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56"}]}],"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","6.8.0-1051.51","6.8.0-1052.52"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.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","6.8.0-110.110.1","6.8.0-111.111.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.60"}]}],"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","6.8.0-1052.56","6.8.0-1053.57"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2045.46"}]}],"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","6.8.0-2042.43","6.8.0-2043.44"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52"}]}],"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","6.8.1-1047.48","6.8.1-1048.49"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58+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","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61+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","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.62"}]}],"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","6.8.0-1054.60"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57"}]}],"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","6.8.0-1051.54","6.8.0-1052.55"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57.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","6.8.0-1051.54.1","6.8.0-1052.55.1"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57~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","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-116.116+fips1"}]}],"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","6.8.0-110.110+fips2","6.8.0-111.111+fips1"],"bundled":189},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"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","6.8.0-1022.22","6.8.0-1023.23"],"bundled":189},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-gcp-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.15.0-1106.115~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","5.15.0-1103.112~20.04.1","5.15.0-1104.113~20.04.1"],"bundled":83},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65+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","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1"],"bundled":218},{"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":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1032.33"}]}],"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","6.8.0-1029.30"],"bundled":516},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1021.24~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","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1016.17~24.04.1","6.17.0-1018.19~24.04.1","6.17.0-1020.22~24.04.1"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.20~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","6.17.0-1010.11~24.04.1","6.17.0-1011.12~24.04.1","6.17.0-1013.15~24.04.1","6.17.0-1014.16~24.04.1","6.17.0-1017.19~24.04.1"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1019.19~24.04.3"}]}],"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","6.17.0-1011.11~24.04.1","6.17.0-1014.14~24.04.1","6.17.0-1016.16~24.04.1","6.17.0-1018.18~24.04.1"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1030.30"}]}],"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","6.17.0-1020.20","6.17.0-1023.23","6.17.0-1024.24","6.17.0-1025.25","6.17.0-1028.28"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1021.21~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","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1018.18~24.04.1","6.17.0-1020.20~24.04.1"],"bundled":267},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.18~24.04.1"}]}],"versions":["6.17.0-1005.5~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1"],"bundled":266},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1031.31"}]}],"versions":["6.17.0-1004.4","6.17.0-1008.8","6.17.0-1014.14","6.17.0-1018.18","6.17.0-1021.21","6.17.0-1026.26","6.17.0-1029.29"],"bundled":227},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1.160000.2.7"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.26.1"}]}],"bundled":205}],"products":[{"vendor":"linux","product":"linux"},{"vendor":"linux","product":"linux_kernel"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp (6es7518-4ax00-1ab0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp (6es7518-4ax00-1ac0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp (6es7518-4fx00-1ab0)"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp (6es7518-4fx00-1ac0)"},{"vendor":"siemens","product":"siplus s7-1500 cpu 1518-4 pn/dp mfp (6ag1518-4ax00-4ac0)"}],"references":[{"url":"https://git.kernel.org/stable/c/eeb9a521de40c6fadccc12fa5205e5a1b364d5a8","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/8d5b6b2d79c1c22a5b0db1187a6439dff375a022","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/2ecf0aa7cc262472a9599cc51ba02ada0897a17a","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/06fe0801396a36cab865b34f666de1d65bc5ce8e","tags":["Patch","web"]},{"url":"https://git.kernel.org/stable/c/aa57bfea4674e6da8104fa3a37760a6f5f255dad","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/554201ed0a8f4d32e719f42caeaeb2735a9ed6ca","tags":["Patch","web","report"]},{"url":"https://git.kernel.org/stable/c/e67c577d89894811ce4dcd1a9ed29d8b63476667","tags":["Patch","web","report"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-019113.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-457936.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23011","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-5ww3-m3hh-c9fg"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-23011","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/centos7els/CLSA-2026-1778756832.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/oraclelinux7els/CLSA-2026-1778757276.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/rhel7els/CLSA-2026-1778759582.html","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/almalinux9.2esu/CLSA-2026-1779987841.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47400","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47457","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48899","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48986","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49257","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50297","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50391","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50535","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52492","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52529","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52610","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52832","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53168","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53197","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53202","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53390","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53409","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53437","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53451","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53577","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53585","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53594","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53613","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53615","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53641","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53726","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26894","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26924","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26950","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-27431","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35805","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35854","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35944","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35960","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36006","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36955","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-36957","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38605","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38615","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-39276","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-40923","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-42321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53164","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56644","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21653","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-2312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23243","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23270","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31402","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31415","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31427","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31686","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43052","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43427","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/tuxcare9.6esu/CLSA-2026-1780052998.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53200","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53279","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53295","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53368","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53375","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53411","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53423","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53481","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53535","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-38601","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-43098","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-45003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46791","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56584","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56709","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21638","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21639","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21640","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21707","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21732","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-21992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23155","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-23161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37788","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37836","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37989","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38335","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38393","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38412","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38438","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38466","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38544","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38709","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39673","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39748","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39754","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39763","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39850","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39931","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71098","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71161","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23108","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23119","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23164","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23395","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31485","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31492","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31575","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46243","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu20.04els/CLSA-2026-1783791022.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-48744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49799","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50300","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52572","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-52916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53494","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-6610","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26739","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26872","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26958","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-26961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35868","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-35937","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-41013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-46821","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-49991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50115","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-56759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68769","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23080","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31396","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31417","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31500","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31607","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31787","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43493","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46113","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53359","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23011.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-2026-23011","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38627","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68293","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68822","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71065","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71223","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71236","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23059","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23179","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23205","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23228","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1567","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1570","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68334","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71087","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71130","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23074","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23247","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23269","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23340","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23389","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23407","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23410","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23411","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23439","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23440","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23444","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23461","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23473","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31392","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31399","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31400","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31421","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31422","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31426","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31429","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31430","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31442","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31446","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31449","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31451","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31467","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31469","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31487","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31511","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31512","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31516","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31518","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31525","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31528","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31532","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31533","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31540","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31542","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31590","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31595","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31628","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31630","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31651","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31665","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31667","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31675","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31677","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31678","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31684","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31685","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31697","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31698","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31699","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31755","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31771","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31773","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31779","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-31781","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43043","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43061","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43064","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43079","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43148","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43240","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43262","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43273","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43292","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43345","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43366","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43406","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43419","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43428","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-43503","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45911","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45943","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45947","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-45999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46078","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46082","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46165","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46190","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20260447-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1205462","tags":["report"]},{"url":"https://bugzilla.suse.com/1214285","tags":["report"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1223800","tags":["report"]},{"url":"https://bugzilla.suse.com/1228490","tags":["report"]},{"url":"https://bugzilla.suse.com/1233563","tags":["report"]},{"url":"https://bugzilla.suse.com/1234842","tags":["report"]},{"url":"https://bugzilla.suse.com/1235566","tags":["report"]},{"url":"https://bugzilla.suse.com/1241437","tags":["report"]},{"url":"https://bugzilla.suse.com/1242505","tags":["report"]},{"url":"https://bugzilla.suse.com/1242909","tags":["report"]},{"url":"https://bugzilla.suse.com/1243662","tags":["report"]},{"url":"https://bugzilla.suse.com/1243677","tags":["report"]},{"url":"https://bugzilla.suse.com/1243678","tags":["report"]},{"url":"https://bugzilla.suse.com/1245538","tags":["report"]},{"url":"https://bugzilla.suse.com/1246022","tags":["report"]},{"url":"https://bugzilla.suse.com/1246184","tags":["report"]},{"url":"https://bugzilla.suse.com/1246447","tags":["report"]},{"url":"https://bugzilla.suse.com/1247030","tags":["report"]},{"url":"https://bugzilla.suse.com/1247712","tags":["report"]},{"url":"https://bugzilla.suse.com/1248211","tags":["report"]},{"url":"https://bugzilla.suse.com/1249307","tags":["report"]},{"url":"https://bugzilla.suse.com/1249904","tags":["report"]},{"url":"https://bugzilla.suse.com/1250032","tags":["report"]},{"url":"https://bugzilla.suse.com/1250082","tags":["report"]},{"url":"https://bugzilla.suse.com/1250388","tags":["report"]},{"url":"https://bugzilla.suse.com/1250705","tags":["report"]},{"url":"https://bugzilla.suse.com/1250748","tags":["report"]},{"url":"https://bugzilla.suse.com/1252511","tags":["report"]},{"url":"https://bugzilla.suse.com/1252712","tags":["report"]},{"url":"https://bugzilla.suse.com/1252891","tags":["report"]},{"url":"https://bugzilla.suse.com/1252900","tags":["report"]},{"url":"https://bugzilla.suse.com/1253087","tags":["report"]},{"url":"https://bugzilla.suse.com/1253330","tags":["report"]},{"url":"https://bugzilla.suse.com/1253340","tags":["report"]},{"url":"https://bugzilla.suse.com/1253348","tags":["report"]},{"url":"https://bugzilla.suse.com/1253433","tags":["report"]},{"url":"https://bugzilla.suse.com/1253443","tags":["report"]},{"url":"https://bugzilla.suse.com/1253451","tags":["report"]},{"url":"https://bugzilla.suse.com/1253471","tags":["report"]},{"url":"https://bugzilla.suse.com/1253739","tags":["report"]},{"url":"https://bugzilla.suse.com/1254244","tags":["report"]},{"url":"https://bugzilla.suse.com/1254447","tags":["report"]},{"url":"https://bugzilla.suse.com/1254465","tags":["report"]},{"url":"https://bugzilla.suse.com/1254510","tags":["report"]},{"url":"https://bugzilla.suse.com/1254624","tags":["report"]},{"url":"https://bugzilla.suse.com/1254767","tags":["report"]},{"url":"https://bugzilla.suse.com/1254835","tags":["report"]},{"url":"https://bugzilla.suse.com/1254839","tags":["report"]},{"url":"https://bugzilla.suse.com/1254842","tags":["report"]},{"url":"https://bugzilla.suse.com/1254845","tags":["report"]},{"url":"https://bugzilla.suse.com/1254852","tags":["report"]},{"url":"https://bugzilla.suse.com/1254871","tags":["report"]},{"url":"https://bugzilla.suse.com/1255102","tags":["report"]},{"url":"https://bugzilla.suse.com/1255120","tags":["report"]},{"url":"https://bugzilla.suse.com/1255128","tags":["report"]},{"url":"https://bugzilla.suse.com/1255138","tags":["report"]},{"url":"https://bugzilla.suse.com/1255140","tags":["report"]},{"url":"https://bugzilla.suse.com/1255157","tags":["report"]},{"url":"https://bugzilla.suse.com/1255164","tags":["report"]},{"url":"https://bugzilla.suse.com/1255172","tags":["report"]},{"url":"https://bugzilla.suse.com/1255216","tags":["report"]},{"url":"https://bugzilla.suse.com/1255226","tags":["report"]},{"url":"https://bugzilla.suse.com/1255241","tags":["report"]},{"url":"https://bugzilla.suse.com/1255255","tags":["report"]},{"url":"https://bugzilla.suse.com/1255260","tags":["report"]},{"url":"https://bugzilla.suse.com/1255261","tags":["report"]},{"url":"https://bugzilla.suse.com/1255266","tags":["report"]},{"url":"https://bugzilla.suse.com/1255268","tags":["report"]},{"url":"https://bugzilla.suse.com/1255269","tags":["report"]},{"url":"https://bugzilla.suse.com/1255327","tags":["report"]},{"url":"https://bugzilla.suse.com/1255346","tags":["report"]},{"url":"https://bugzilla.suse.com/1255377","tags":["report"]},{"url":"https://bugzilla.suse.com/1255401","tags":["report"]},{"url":"https://bugzilla.suse.com/1255403","tags":["report"]},{"url":"https://bugzilla.suse.com/1255417","tags":["report"]},{"url":"https://bugzilla.suse.com/1255482","tags":["report"]},{"url":"https://bugzilla.suse.com/1255488","tags":["report"]},{"url":"https://bugzilla.suse.com/1255537","tags":["report"]},{"url":"https://bugzilla.suse.com/1255539","tags":["report"]},{"url":"https://bugzilla.suse.com/1255544","tags":["report"]},{"url":"https://bugzilla.suse.com/1255547","tags":["report"]},{"url":"https://bugzilla.suse.com/1255548","tags":["report"]},{"url":"https://bugzilla.suse.com/1255552","tags":["report"]},{"url":"https://bugzilla.suse.com/1255568","tags":["report"]},{"url":"https://bugzilla.suse.com/1255569","tags":["report"]},{"url":"https://bugzilla.suse.com/1255615","tags":["report"]},{"url":"https://bugzilla.suse.com/1255622","tags":["report"]},{"url":"https://bugzilla.suse.com/1255695","tags":["report"]},{"url":"https://bugzilla.suse.com/1255930","tags":["report"]},{"url":"https://bugzilla.suse.com/1256280","tags":["report"]},{"url":"https://bugzilla.suse.com/1256528","tags":["report"]},{"url":"https://bugzilla.suse.com/1256568","tags":["report"]},{"url":"https://bugzilla.suse.com/1256579","tags":["report"]},{"url":"https://bugzilla.suse.com/1256582","tags":["report"]},{"url":"https://bugzilla.suse.com/1256584","tags":["report"]},{"url":"https://bugzilla.suse.com/1256586","tags":["report"]},{"url":"https://bugzilla.suse.com/1256591","tags":["report"]},{"url":"https://bugzilla.suse.com/1256592","tags":["report"]},{"url":"https://bugzilla.suse.com/1256593","tags":["report"]},{"url":"https://bugzilla.suse.com/1256594","tags":["report"]},{"url":"https://bugzilla.suse.com/1256597","tags":["report"]},{"url":"https://bugzilla.suse.com/1256605","tags":["report"]},{"url":"https://bugzilla.suse.com/1256606","tags":["report"]},{"url":"https://bugzilla.suse.com/1256607","tags":["report"]},{"url":"https://bugzilla.suse.com/1256608","tags":["report"]},{"url":"https://bugzilla.suse.com/1256609","tags":["report"]},{"url":"https://bugzilla.suse.com/1256610","tags":["report"]},{"url":"https://bugzilla.suse.com/1256611","tags":["report"]},{"url":"https://bugzilla.suse.com/1256612","tags":["report"]},{"url":"https://bugzilla.suse.com/1256613","tags":["report"]},{"url":"https://bugzilla.suse.com/1256616","tags":["report"]},{"url":"https://bugzilla.suse.com/1256617","tags":["report"]},{"url":"https://bugzilla.suse.com/1256619","tags":["report"]},{"url":"https://bugzilla.suse.com/1256622","tags":["report"]},{"url":"https://bugzilla.suse.com/1256623","tags":["report"]},{"url":"https://bugzilla.suse.com/1256625","tags":["report"]},{"url":"https://bugzilla.suse.com/1256627","tags":["report"]},{"url":"https://bugzilla.suse.com/1256628","tags":["report"]},{"url":"https://bugzilla.suse.com/1256630","tags":["report"]},{"url":"https://bugzilla.suse.com/1256638","tags":["report"]},{"url":"https://bugzilla.suse.com/1256641","tags":["report"]},{"url":"https://bugzilla.suse.com/1256645","tags":["report"]},{"url":"https://bugzilla.suse.com/1256646","tags":["report"]},{"url":"https://bugzilla.suse.com/1256650","tags":["report"]},{"url":"https://bugzilla.suse.com/1256651","tags":["report"]},{"url":"https://bugzilla.suse.com/1256653","tags":["report"]},{"url":"https://bugzilla.suse.com/1256654","tags":["report"]},{"url":"https://bugzilla.suse.com/1256655","tags":["report"]},{"url":"https://bugzilla.suse.com/1256659","tags":["report"]},{"url":"https://bugzilla.suse.com/1256660","tags":["report"]},{"url":"https://bugzilla.suse.com/1256661","tags":["report"]},{"url":"https://bugzilla.suse.com/1256664","tags":["report"]},{"url":"https://bugzilla.suse.com/1256665","tags":["report"]},{"url":"https://bugzilla.suse.com/1256674","tags":["report"]},{"url":"https://bugzilla.suse.com/1256680","tags":["report"]},{"url":"https://bugzilla.suse.com/1256682","tags":["report"]},{"url":"https://bugzilla.suse.com/1256688","tags":["report"]},{"url":"https://bugzilla.suse.com/1256689","tags":["report"]},{"url":"https://bugzilla.suse.com/1256690","tags":["report"]},{"url":"https://bugzilla.suse.com/1256726","tags":["report"]},{"url":"https://bugzilla.suse.com/1256728","tags":["report"]},{"url":"https://bugzilla.suse.com/1256730","tags":["report"]},{"url":"https://bugzilla.suse.com/1256733","tags":["report"]},{"url":"https://bugzilla.suse.com/1256737","tags":["report"]},{"url":"https://bugzilla.suse.com/1256741","tags":["report"]},{"url":"https://bugzilla.suse.com/1256742","tags":["report"]},{"url":"https://bugzilla.suse.com/1256744","tags":["report"]},{"url":"https://bugzilla.suse.com/1256748","tags":["report"]},{"url":"https://bugzilla.suse.com/1256749","tags":["report"]},{"url":"https://bugzilla.suse.com/1256752","tags":["report"]},{"url":"https://bugzilla.suse.com/1256754","tags":["report"]},{"url":"https://bugzilla.suse.com/1256756","tags":["report"]},{"url":"https://bugzilla.suse.com/1256757","tags":["report"]},{"url":"https://bugzilla.suse.com/1256759","tags":["report"]},{"url":"https://bugzilla.suse.com/1256760","tags":["report"]},{"url":"https://bugzilla.suse.com/1256761","tags":["report"]},{"url":"https://bugzilla.suse.com/1256763","tags":["report"]},{"url":"https://bugzilla.suse.com/1256770","tags":["report"]},{"url":"https://bugzilla.suse.com/1256773","tags":["report"]},{"url":"https://bugzilla.suse.com/1256774","tags":["report"]},{"url":"https://bugzilla.suse.com/1256777","tags":["report"]},{"url":"https://bugzilla.suse.com/1256779","tags":["report"]},{"url":"https://bugzilla.suse.com/1256781","tags":["report"]},{"url":"https://bugzilla.suse.com/1256785","tags":["report"]},{"url":"https://bugzilla.suse.com/1256792","tags":["report"]},{"url":"https://bugzilla.suse.com/1256794","tags":["report"]},{"url":"https://bugzilla.suse.com/1256861","tags":["report"]},{"url":"https://bugzilla.suse.com/1256863","tags":["report"]},{"url":"https://bugzilla.suse.com/1257035","tags":["report"]},{"url":"https://bugzilla.suse.com/1257053","tags":["report"]},{"url":"https://bugzilla.suse.com/1257154","tags":["report"]},{"url":"https://bugzilla.suse.com/1257155","tags":["report"]},{"url":"https://bugzilla.suse.com/1257158","tags":["report"]},{"url":"https://bugzilla.suse.com/1257163","tags":["report"]},{"url":"https://bugzilla.suse.com/1257164","tags":["report"]},{"url":"https://bugzilla.suse.com/1257167","tags":["report"]},{"url":"https://bugzilla.suse.com/1257168","tags":["report"]},{"url":"https://bugzilla.suse.com/1257180","tags":["report"]},{"url":"https://bugzilla.suse.com/1257202","tags":["report"]},{"url":"https://bugzilla.suse.com/1257204","tags":["report"]},{"url":"https://bugzilla.suse.com/1257207","tags":["report"]},{"url":"https://bugzilla.suse.com/1257208","tags":["report"]},{"url":"https://bugzilla.suse.com/1257215","tags":["report"]},{"url":"https://bugzilla.suse.com/1257217","tags":["report"]},{"url":"https://bugzilla.suse.com/1257218","tags":["report"]},{"url":"https://bugzilla.suse.com/1257220","tags":["report"]},{"url":"https://bugzilla.suse.com/1257221","tags":["report"]},{"url":"https://bugzilla.suse.com/1257227","tags":["report"]},{"url":"https://bugzilla.suse.com/1257232","tags":["report"]},{"url":"https://bugzilla.suse.com/1257234","tags":["report"]},{"url":"https://bugzilla.suse.com/1257236","tags":["report"]},{"url":"https://bugzilla.suse.com/1257245","tags":["report"]},{"url":"https://bugzilla.suse.com/1257277","tags":["report"]},{"url":"https://bugzilla.suse.com/1257282","tags":["report"]},{"url":"https://bugzilla.suse.com/1257296","tags":["report"]},{"url":"https://bugzilla.suse.com/1257473","tags":["report"]},{"url":"https://bugzilla.suse.com/1257603","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53714","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-27005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-42103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-22047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40355","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68174","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68296","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68365","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68367","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68773","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68775","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68776","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68777","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68820","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71098","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71132","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22984","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22985","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23011","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20260472-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1257332","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23010","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20260473-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1220840","tags":["report"]},{"url":"https://bugzilla.suse.com/1223007","tags":["report"]},{"url":"https://bugzilla.suse.com/1223675","tags":["report"]},{"url":"https://bugzilla.suse.com/1225527","tags":["report"]},{"url":"https://bugzilla.suse.com/1225741","tags":["report"]},{"url":"https://bugzilla.suse.com/1227863","tags":["report"]},{"url":"https://bugzilla.suse.com/1227988","tags":["report"]},{"url":"https://bugzilla.suse.com/1231908","tags":["report"]},{"url":"https://bugzilla.suse.com/1235428","tags":["report"]},{"url":"https://bugzilla.suse.com/1236702","tags":["report"]},{"url":"https://bugzilla.suse.com/1239346","tags":["report"]},{"url":"https://bugzilla.suse.com/1240299","tags":["report"]},{"url":"https://bugzilla.suse.com/1243471","tags":["report"]},{"url":"https://bugzilla.suse.com/1244904","tags":["report"]},{"url":"https://bugzilla.suse.com/1244938","tags":["report"]},{"url":"https://bugzilla.suse.com/1245110","tags":["report"]},{"url":"https://bugzilla.suse.com/1248341","tags":["report"]},{"url":"https://bugzilla.suse.com/1248363","tags":["report"]},{"url":"https://bugzilla.suse.com/1248643","tags":["report"]},{"url":"https://bugzilla.suse.com/1249658","tags":["report"]},{"url":"https://bugzilla.suse.com/1249827","tags":["report"]},{"url":"https://bugzilla.suse.com/1249842","tags":["report"]},{"url":"https://bugzilla.suse.com/1249854","tags":["report"]},{"url":"https://bugzilla.suse.com/1249928","tags":["report"]},{"url":"https://bugzilla.suse.com/1250759","tags":["report"]},{"url":"https://bugzilla.suse.com/1250868","tags":["report"]},{"url":"https://bugzilla.suse.com/1251770","tags":["report"]},{"url":"https://bugzilla.suse.com/1252542","tags":["report"]},{"url":"https://bugzilla.suse.com/1252909","tags":["report"]},{"url":"https://bugzilla.suse.com/1253318","tags":["report"]},{"url":"https://bugzilla.suse.com/1253453","tags":["report"]},{"url":"https://bugzilla.suse.com/1254572","tags":["report"]},{"url":"https://bugzilla.suse.com/1254657","tags":["report"]},{"url":"https://bugzilla.suse.com/1254673","tags":["report"]},{"url":"https://bugzilla.suse.com/1254689","tags":["report"]},{"url":"https://bugzilla.suse.com/1254707","tags":["report"]},{"url":"https://bugzilla.suse.com/1254986","tags":["report"]},{"url":"https://bugzilla.suse.com/1255094","tags":["report"]},{"url":"https://bugzilla.suse.com/1255122","tags":["report"]},{"url":"https://bugzilla.suse.com/1255131","tags":["report"]},{"url":"https://bugzilla.suse.com/1255169","tags":["report"]},{"url":"https://bugzilla.suse.com/1255171","tags":["report"]},{"url":"https://bugzilla.suse.com/1255246","tags":["report"]},{"url":"https://bugzilla.suse.com/1255279","tags":["report"]},{"url":"https://bugzilla.suse.com/1255297","tags":["report"]},{"url":"https://bugzilla.suse.com/1255351","tags":["report"]},{"url":"https://bugzilla.suse.com/1255380","tags":["report"]},{"url":"https://bugzilla.suse.com/1255428","tags":["report"]},{"url":"https://bugzilla.suse.com/1255553","tags":["report"]},{"url":"https://bugzilla.suse.com/1255565","tags":["report"]},{"url":"https://bugzilla.suse.com/1255571","tags":["report"]},{"url":"https://bugzilla.suse.com/1255594","tags":["report"]},{"url":"https://bugzilla.suse.com/1255611","tags":["report"]},{"url":"https://bugzilla.suse.com/1255762","tags":["report"]},{"url":"https://bugzilla.suse.com/1255773","tags":["report"]},{"url":"https://bugzilla.suse.com/1255804","tags":["report"]},{"url":"https://bugzilla.suse.com/1255810","tags":["report"]},{"url":"https://bugzilla.suse.com/1255812","tags":["report"]},{"url":"https://bugzilla.suse.com/1255839","tags":["report"]},{"url":"https://bugzilla.suse.com/1255844","tags":["report"]},{"url":"https://bugzilla.suse.com/1255874","tags":["report"]},{"url":"https://bugzilla.suse.com/1255880","tags":["report"]},{"url":"https://bugzilla.suse.com/1255905","tags":["report"]},{"url":"https://bugzilla.suse.com/1255908","tags":["report"]},{"url":"https://bugzilla.suse.com/1255925","tags":["report"]},{"url":"https://bugzilla.suse.com/1255939","tags":["report"]},{"url":"https://bugzilla.suse.com/1255943","tags":["report"]},{"url":"https://bugzilla.suse.com/1255961","tags":["report"]},{"url":"https://bugzilla.suse.com/1255970","tags":["report"]},{"url":"https://bugzilla.suse.com/1255983","tags":["report"]},{"url":"https://bugzilla.suse.com/1256038","tags":["report"]},{"url":"https://bugzilla.suse.com/1256058","tags":["report"]},{"url":"https://bugzilla.suse.com/1256106","tags":["report"]},{"url":"https://bugzilla.suse.com/1256122","tags":["report"]},{"url":"https://bugzilla.suse.com/1256125","tags":["report"]},{"url":"https://bugzilla.suse.com/1256127","tags":["report"]},{"url":"https://bugzilla.suse.com/1256130","tags":["report"]},{"url":"https://bugzilla.suse.com/1256131","tags":["report"]},{"url":"https://bugzilla.suse.com/1256132","tags":["report"]},{"url":"https://bugzilla.suse.com/1256149","tags":["report"]},{"url":"https://bugzilla.suse.com/1256155","tags":["report"]},{"url":"https://bugzilla.suse.com/1256165","tags":["report"]},{"url":"https://bugzilla.suse.com/1256168","tags":["report"]},{"url":"https://bugzilla.suse.com/1256184","tags":["report"]},{"url":"https://bugzilla.suse.com/1256191","tags":["report"]},{"url":"https://bugzilla.suse.com/1256216","tags":["report"]},{"url":"https://bugzilla.suse.com/1256219","tags":["report"]},{"url":"https://bugzilla.suse.com/1256221","tags":["report"]},{"url":"https://bugzilla.suse.com/1256229","tags":["report"]},{"url":"https://bugzilla.suse.com/1256258","tags":["report"]},{"url":"https://bugzilla.suse.com/1256267","tags":["report"]},{"url":"https://bugzilla.suse.com/1256282","tags":["report"]},{"url":"https://bugzilla.suse.com/1256305","tags":["report"]},{"url":"https://bugzilla.suse.com/1256320","tags":["report"]},{"url":"https://bugzilla.suse.com/1256354","tags":["report"]},{"url":"https://bugzilla.suse.com/1256369","tags":["report"]},{"url":"https://bugzilla.suse.com/1256386","tags":["report"]},{"url":"https://bugzilla.suse.com/1256395","tags":["report"]},{"url":"https://bugzilla.suse.com/1256398","tags":["report"]},{"url":"https://bugzilla.suse.com/1256580","tags":["report"]},{"url":"https://bugzilla.suse.com/1256585","tags":["report"]},{"url":"https://bugzilla.suse.com/1257229","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2022-48838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49943","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-49980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50716","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50719","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50770","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50777","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50868","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50885","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-50887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-50756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-52999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53747","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53992","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54067","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54243","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-36903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-41007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-56690","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-58020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-21681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37913","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40323","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68305","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68774","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20260587-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620477-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1012628","tags":["report"]},{"url":"https://bugzilla.suse.com/1065729","tags":["report"]},{"url":"https://bugzilla.suse.com/1194869","tags":["report"]},{"url":"https://bugzilla.suse.com/1214635","tags":["report"]},{"url":"https://bugzilla.suse.com/1214847","tags":["report"]},{"url":"https://bugzilla.suse.com/1215146","tags":["report"]},{"url":"https://bugzilla.suse.com/1215211","tags":["report"]},{"url":"https://bugzilla.suse.com/1215344","tags":["report"]},{"url":"https://bugzilla.suse.com/1216062","tags":["report"]},{"url":"https://bugzilla.suse.com/1216436","tags":["report"]},{"url":"https://bugzilla.suse.com/1219165","tags":["report"]},{"url":"https://bugzilla.suse.com/1220419","tags":["report"]},{"url":"https://bugzilla.suse.com/1223731","tags":["report"]},{"url":"https://bugzilla.suse.com/1234163","tags":["report"]},{"url":"https://bugzilla.suse.com/1245193","tags":["report"]},{"url":"https://bugzilla.suse.com/1245449","tags":["report"]},{"url":"https://bugzilla.suse.com/1246328","tags":["report"]},{"url":"https://bugzilla.suse.com/1247500","tags":["report"]},{"url":"https://bugzilla.suse.com/1248886","tags":["report"]},{"url":"https://bugzilla.suse.com/1249256","tags":["report"]},{"url":"https://bugzilla.suse.com/1250334","tags":["report"]},{"url":"https://bugzilla.suse.com/1252046","tags":["report"]},{"url":"https://bugzilla.suse.com/1252342","tags":["report"]},{"url":"https://bugzilla.suse.com/1252686","tags":["report"]},{"url":"https://bugzilla.suse.com/1252776","tags":["report"]},{"url":"https://bugzilla.suse.com/1252808","tags":["report"]},{"url":"https://bugzilla.suse.com/1252824","tags":["report"]},{"url":"https://bugzilla.suse.com/1252861","tags":["report"]},{"url":"https://bugzilla.suse.com/1252919","tags":["report"]},{"url":"https://bugzilla.suse.com/1252973","tags":["report"]},{"url":"https://bugzilla.suse.com/1253155","tags":["report"]},{"url":"https://bugzilla.suse.com/1253262","tags":["report"]},{"url":"https://bugzilla.suse.com/1253342","tags":["report"]},{"url":"https://bugzilla.suse.com/1253365","tags":["report"]},{"url":"https://bugzilla.suse.com/1253386","tags":["report"]},{"url":"https://bugzilla.suse.com/1253400","tags":["report"]},{"url":"https://bugzilla.suse.com/1253402","tags":["report"]},{"url":"https://bugzilla.suse.com/1253408","tags":["report"]},{"url":"https://bugzilla.suse.com/1253413","tags":["report"]},{"url":"https://bugzilla.suse.com/1253442","tags":["report"]},{"url":"https://bugzilla.suse.com/1253458","tags":["report"]},{"url":"https://bugzilla.suse.com/1253463","tags":["report"]},{"url":"https://bugzilla.suse.com/1253623","tags":["report"]},{"url":"https://bugzilla.suse.com/1253647","tags":["report"]},{"url":"https://bugzilla.suse.com/1254119","tags":["report"]},{"url":"https://bugzilla.suse.com/1254126","tags":["report"]},{"url":"https://bugzilla.suse.com/1254373","tags":["report"]},{"url":"https://bugzilla.suse.com/1254378","tags":["report"]},{"url":"https://bugzilla.suse.com/1254518","tags":["report"]},{"url":"https://bugzilla.suse.com/1254520","tags":["report"]},{"url":"https://bugzilla.suse.com/1254599","tags":["report"]},{"url":"https://bugzilla.suse.com/1254606","tags":["report"]},{"url":"https://bugzilla.suse.com/1254611","tags":["report"]},{"url":"https://bugzilla.suse.com/1254613","tags":["report"]},{"url":"https://bugzilla.suse.com/1254615","tags":["report"]},{"url":"https://bugzilla.suse.com/1254621","tags":["report"]},{"url":"https://bugzilla.suse.com/1254623","tags":["report"]},{"url":"https://bugzilla.suse.com/1254626","tags":["report"]},{"url":"https://bugzilla.suse.com/1254648","tags":["report"]},{"url":"https://bugzilla.suse.com/1254649","tags":["report"]},{"url":"https://bugzilla.suse.com/1254653","tags":["report"]},{"url":"https://bugzilla.suse.com/1254655","tags":["report"]},{"url":"https://bugzilla.suse.com/1254660","tags":["report"]},{"url":"https://bugzilla.suse.com/1254661","tags":["report"]},{"url":"https://bugzilla.suse.com/1254663","tags":["report"]},{"url":"https://bugzilla.suse.com/1254669","tags":["report"]},{"url":"https://bugzilla.suse.com/1254677","tags":["report"]},{"url":"https://bugzilla.suse.com/1254678","tags":["report"]},{"url":"https://bugzilla.suse.com/1254688","tags":["report"]},{"url":"https://bugzilla.suse.com/1254690","tags":["report"]},{"url":"https://bugzilla.suse.com/1254691","tags":["report"]},{"url":"https://bugzilla.suse.com/1254693","tags":["report"]},{"url":"https://bugzilla.suse.com/1254695","tags":["report"]},{"url":"https://bugzilla.suse.com/1254698","tags":["report"]},{"url":"https://bugzilla.suse.com/1254701","tags":["report"]},{"url":"https://bugzilla.suse.com/1254704","tags":["report"]},{"url":"https://bugzilla.suse.com/1254705","tags":["report"]},{"url":"https://bugzilla.suse.com/1254712","tags":["report"]},{"url":"https://bugzilla.suse.com/1254715","tags":["report"]},{"url":"https://bugzilla.suse.com/1254717","tags":["report"]},{"url":"https://bugzilla.suse.com/1254723","tags":["report"]},{"url":"https://bugzilla.suse.com/1254724","tags":["report"]},{"url":"https://bugzilla.suse.com/1254732","tags":["report"]},{"url":"https://bugzilla.suse.com/1254733","tags":["report"]},{"url":"https://bugzilla.suse.com/1254737","tags":["report"]},{"url":"https://bugzilla.suse.com/1254739","tags":["report"]},{"url":"https://bugzilla.suse.com/1254742","tags":["report"]},{"url":"https://bugzilla.suse.com/1254743","tags":["report"]},{"url":"https://bugzilla.suse.com/1254749","tags":["report"]},{"url":"https://bugzilla.suse.com/1254750","tags":["report"]},{"url":"https://bugzilla.suse.com/1254753","tags":["report"]},{"url":"https://bugzilla.suse.com/1254754","tags":["report"]},{"url":"https://bugzilla.suse.com/1254758","tags":["report"]},{"url":"https://bugzilla.suse.com/1254761","tags":["report"]},{"url":"https://bugzilla.suse.com/1254762","tags":["report"]},{"url":"https://bugzilla.suse.com/1254765","tags":["report"]},{"url":"https://bugzilla.suse.com/1254782","tags":["report"]},{"url":"https://bugzilla.suse.com/1254791","tags":["report"]},{"url":"https://bugzilla.suse.com/1254793","tags":["report"]},{"url":"https://bugzilla.suse.com/1254794","tags":["report"]},{"url":"https://bugzilla.suse.com/1254795","tags":["report"]},{"url":"https://bugzilla.suse.com/1254796","tags":["report"]},{"url":"https://bugzilla.suse.com/1254797","tags":["report"]},{"url":"https://bugzilla.suse.com/1254798","tags":["report"]},{"url":"https://bugzilla.suse.com/1254813","tags":["report"]},{"url":"https://bugzilla.suse.com/1254815","tags":["report"]},{"url":"https://bugzilla.suse.com/1254825","tags":["report"]},{"url":"https://bugzilla.suse.com/1254828","tags":["report"]},{"url":"https://bugzilla.suse.com/1254829","tags":["report"]},{"url":"https://bugzilla.suse.com/1254830","tags":["report"]},{"url":"https://bugzilla.suse.com/1254832","tags":["report"]},{"url":"https://bugzilla.suse.com/1254840","tags":["report"]},{"url":"https://bugzilla.suse.com/1254843","tags":["report"]},{"url":"https://bugzilla.suse.com/1254846","tags":["report"]},{"url":"https://bugzilla.suse.com/1254847","tags":["report"]},{"url":"https://bugzilla.suse.com/1254849","tags":["report"]},{"url":"https://bugzilla.suse.com/1254850","tags":["report"]},{"url":"https://bugzilla.suse.com/1254851","tags":["report"]},{"url":"https://bugzilla.suse.com/1254854","tags":["report"]},{"url":"https://bugzilla.suse.com/1254856","tags":["report"]},{"url":"https://bugzilla.suse.com/1254858","tags":["report"]},{"url":"https://bugzilla.suse.com/1254860","tags":["report"]},{"url":"https://bugzilla.suse.com/1254864","tags":["report"]},{"url":"https://bugzilla.suse.com/1254869","tags":["report"]},{"url":"https://bugzilla.suse.com/1254894","tags":["report"]},{"url":"https://bugzilla.suse.com/1254918","tags":["report"]},{"url":"https://bugzilla.suse.com/1254957","tags":["report"]},{"url":"https://bugzilla.suse.com/1254959","tags":["report"]},{"url":"https://bugzilla.suse.com/1254983","tags":["report"]},{"url":"https://bugzilla.suse.com/1255005","tags":["report"]},{"url":"https://bugzilla.suse.com/1255009","tags":["report"]},{"url":"https://bugzilla.suse.com/1255025","tags":["report"]},{"url":"https://bugzilla.suse.com/1255026","tags":["report"]},{"url":"https://bugzilla.suse.com/1255030","tags":["report"]},{"url":"https://bugzilla.suse.com/1255033","tags":["report"]},{"url":"https://bugzilla.suse.com/1255034","tags":["report"]},{"url":"https://bugzilla.suse.com/1255035","tags":["report"]},{"url":"https://bugzilla.suse.com/1255039","tags":["report"]},{"url":"https://bugzilla.suse.com/1255041","tags":["report"]},{"url":"https://bugzilla.suse.com/1255042","tags":["report"]},{"url":"https://bugzilla.suse.com/1255046","tags":["report"]},{"url":"https://bugzilla.suse.com/1255057","tags":["report"]},{"url":"https://bugzilla.suse.com/1255062","tags":["report"]},{"url":"https://bugzilla.suse.com/1255064","tags":["report"]},{"url":"https://bugzilla.suse.com/1255065","tags":["report"]},{"url":"https://bugzilla.suse.com/1255068","tags":["report"]},{"url":"https://bugzilla.suse.com/1255072","tags":["report"]},{"url":"https://bugzilla.suse.com/1255075","tags":["report"]},{"url":"https://bugzilla.suse.com/1255077","tags":["report"]},{"url":"https://bugzilla.suse.com/1255081","tags":["report"]},{"url":"https://bugzilla.suse.com/1255082","tags":["report"]},{"url":"https://bugzilla.suse.com/1255083","tags":["report"]},{"url":"https://bugzilla.suse.com/1255092","tags":["report"]},{"url":"https://bugzilla.suse.com/1255095","tags":["report"]},{"url":"https://bugzilla.suse.com/1255100","tags":["report"]},{"url":"https://bugzilla.suse.com/1255134","tags":["report"]},{"url":"https://bugzilla.suse.com/1255135","tags":["report"]},{"url":"https://bugzilla.suse.com/1255136","tags":["report"]},{"url":"https://bugzilla.suse.com/1255142","tags":["report"]},{"url":"https://bugzilla.suse.com/1255146","tags":["report"]},{"url":"https://bugzilla.suse.com/1255149","tags":["report"]},{"url":"https://bugzilla.suse.com/1255152","tags":["report"]},{"url":"https://bugzilla.suse.com/1255154","tags":["report"]},{"url":"https://bugzilla.suse.com/1255155","tags":["report"]},{"url":"https://bugzilla.suse.com/1255163","tags":["report"]},{"url":"https://bugzilla.suse.com/1255167","tags":["report"]},{"url":"https://bugzilla.suse.com/1255175","tags":["report"]},{"url":"https://bugzilla.suse.com/1255179","tags":["report"]},{"url":"https://bugzilla.suse.com/1255182","tags":["report"]},{"url":"https://bugzilla.suse.com/1255187","tags":["report"]},{"url":"https://bugzilla.suse.com/1255190","tags":["report"]},{"url":"https://bugzilla.suse.com/1255193","tags":["report"]},{"url":"https://bugzilla.suse.com/1255197","tags":["report"]},{"url":"https://bugzilla.suse.com/1255199","tags":["report"]},{"url":"https://bugzilla.suse.com/1255202","tags":["report"]},{"url":"https://bugzilla.suse.com/1255203","tags":["report"]},{"url":"https://bugzilla.suse.com/1255206","tags":["report"]},{"url":"https://bugzilla.suse.com/1255209","tags":["report"]},{"url":"https://bugzilla.suse.com/1255218","tags":["report"]},{"url":"https://bugzilla.suse.com/1255221","tags":["report"]},{"url":"https://bugzilla.suse.com/1255224","tags":["report"]},{"url":"https://bugzilla.suse.com/1255227","tags":["report"]},{"url":"https://bugzilla.suse.com/1255230","tags":["report"]},{"url":"https://bugzilla.suse.com/1255233","tags":["report"]},{"url":"https://bugzilla.suse.com/1255245","tags":["report"]},{"url":"https://bugzilla.suse.com/1255251","tags":["report"]},{"url":"https://bugzilla.suse.com/1255252","tags":["report"]},{"url":"https://bugzilla.suse.com/1255253","tags":["report"]},{"url":"https://bugzilla.suse.com/1255259","tags":["report"]},{"url":"https://bugzilla.suse.com/1255262","tags":["report"]},{"url":"https://bugzilla.suse.com/1255272","tags":["report"]},{"url":"https://bugzilla.suse.com/1255273","tags":["report"]},{"url":"https://bugzilla.suse.com/1255274","tags":["report"]},{"url":"https://bugzilla.suse.com/1255276","tags":["report"]},{"url":"https://bugzilla.suse.com/1255280","tags":["report"]},{"url":"https://bugzilla.suse.com/1255281","tags":["report"]},{"url":"https://bugzilla.suse.com/1255318","tags":["report"]},{"url":"https://bugzilla.suse.com/1255325","tags":["report"]},{"url":"https://bugzilla.suse.com/1255329","tags":["report"]},{"url":"https://bugzilla.suse.com/1255395","tags":["report"]},{"url":"https://bugzilla.suse.com/1255415","tags":["report"]},{"url":"https://bugzilla.suse.com/1255480","tags":["report"]},{"url":"https://bugzilla.suse.com/1255483","tags":["report"]},{"url":"https://bugzilla.suse.com/1255489","tags":["report"]},{"url":"https://bugzilla.suse.com/1255493","tags":["report"]},{"url":"https://bugzilla.suse.com/1255495","tags":["report"]},{"url":"https://bugzilla.suse.com/1255505","tags":["report"]},{"url":"https://bugzilla.suse.com/1255507","tags":["report"]},{"url":"https://bugzilla.suse.com/1255538","tags":["report"]},{"url":"https://bugzilla.suse.com/1255540","tags":["report"]},{"url":"https://bugzilla.suse.com/1255545","tags":["report"]},{"url":"https://bugzilla.suse.com/1255549","tags":["report"]},{"url":"https://bugzilla.suse.com/1255550","tags":["report"]},{"url":"https://bugzilla.suse.com/1255557","tags":["report"]},{"url":"https://bugzilla.suse.com/1255558","tags":["report"]},{"url":"https://bugzilla.suse.com/1255563","tags":["report"]},{"url":"https://bugzilla.suse.com/1255564","tags":["report"]},{"url":"https://bugzilla.suse.com/1255567","tags":["report"]},{"url":"https://bugzilla.suse.com/1255570","tags":["report"]},{"url":"https://bugzilla.suse.com/1255578","tags":["report"]},{"url":"https://bugzilla.suse.com/1255579","tags":["report"]},{"url":"https://bugzilla.suse.com/1255580","tags":["report"]},{"url":"https://bugzilla.suse.com/1255583","tags":["report"]},{"url":"https://bugzilla.suse.com/1255591","tags":["report"]},{"url":"https://bugzilla.suse.com/1255601","tags":["report"]},{"url":"https://bugzilla.suse.com/1255603","tags":["report"]},{"url":"https://bugzilla.suse.com/1255605","tags":["report"]},{"url":"https://bugzilla.suse.com/1255614","tags":["report"]},{"url":"https://bugzilla.suse.com/1255616","tags":["report"]},{"url":"https://bugzilla.suse.com/1255617","tags":["report"]},{"url":"https://bugzilla.suse.com/1255618","tags":["report"]},{"url":"https://bugzilla.suse.com/1255621","tags":["report"]},{"url":"https://bugzilla.suse.com/1255628","tags":["report"]},{"url":"https://bugzilla.suse.com/1255629","tags":["report"]},{"url":"https://bugzilla.suse.com/1255630","tags":["report"]},{"url":"https://bugzilla.suse.com/1255632","tags":["report"]},{"url":"https://bugzilla.suse.com/1255636","tags":["report"]},{"url":"https://bugzilla.suse.com/1255688","tags":["report"]},{"url":"https://bugzilla.suse.com/1255691","tags":["report"]},{"url":"https://bugzilla.suse.com/1255702","tags":["report"]},{"url":"https://bugzilla.suse.com/1255704","tags":["report"]},{"url":"https://bugzilla.suse.com/1255706","tags":["report"]},{"url":"https://bugzilla.suse.com/1255707","tags":["report"]},{"url":"https://bugzilla.suse.com/1255709","tags":["report"]},{"url":"https://bugzilla.suse.com/1255722","tags":["report"]},{"url":"https://bugzilla.suse.com/1255758","tags":["report"]},{"url":"https://bugzilla.suse.com/1255759","tags":["report"]},{"url":"https://bugzilla.suse.com/1255760","tags":["report"]},{"url":"https://bugzilla.suse.com/1255763","tags":["report"]},{"url":"https://bugzilla.suse.com/1255769","tags":["report"]},{"url":"https://bugzilla.suse.com/1255770","tags":["report"]},{"url":"https://bugzilla.suse.com/1255772","tags":["report"]},{"url":"https://bugzilla.suse.com/1255774","tags":["report"]},{"url":"https://bugzilla.suse.com/1255775","tags":["report"]},{"url":"https://bugzilla.suse.com/1255776","tags":["report"]},{"url":"https://bugzilla.suse.com/1255780","tags":["report"]},{"url":"https://bugzilla.suse.com/1255785","tags":["report"]},{"url":"https://bugzilla.suse.com/1255786","tags":["report"]},{"url":"https://bugzilla.suse.com/1255789","tags":["report"]},{"url":"https://bugzilla.suse.com/1255790","tags":["report"]},{"url":"https://bugzilla.suse.com/1255792","tags":["report"]},{"url":"https://bugzilla.suse.com/1255793","tags":["report"]},{"url":"https://bugzilla.suse.com/1255795","tags":["report"]},{"url":"https://bugzilla.suse.com/1255798","tags":["report"]},{"url":"https://bugzilla.suse.com/1255800","tags":["report"]},{"url":"https://bugzilla.suse.com/1255801","tags":["report"]},{"url":"https://bugzilla.suse.com/1255806","tags":["report"]},{"url":"https://bugzilla.suse.com/1255807","tags":["report"]},{"url":"https://bugzilla.suse.com/1255809","tags":["report"]},{"url":"https://bugzilla.suse.com/1255814","tags":["report"]},{"url":"https://bugzilla.suse.com/1255820","tags":["report"]},{"url":"https://bugzilla.suse.com/1255838","tags":["report"]},{"url":"https://bugzilla.suse.com/1255842","tags":["report"]},{"url":"https://bugzilla.suse.com/1255843","tags":["report"]},{"url":"https://bugzilla.suse.com/1255872","tags":["report"]},{"url":"https://bugzilla.suse.com/1255875","tags":["report"]},{"url":"https://bugzilla.suse.com/1255879","tags":["report"]},{"url":"https://bugzilla.suse.com/1255883","tags":["report"]},{"url":"https://bugzilla.suse.com/1255884","tags":["report"]},{"url":"https://bugzilla.suse.com/1255886","tags":["report"]},{"url":"https://bugzilla.suse.com/1255888","tags":["report"]},{"url":"https://bugzilla.suse.com/1255890","tags":["report"]},{"url":"https://bugzilla.suse.com/1255891","tags":["report"]},{"url":"https://bugzilla.suse.com/1255892","tags":["report"]},{"url":"https://bugzilla.suse.com/1255899","tags":["report"]},{"url":"https://bugzilla.suse.com/1255902","tags":["report"]},{"url":"https://bugzilla.suse.com/1255907","tags":["report"]},{"url":"https://bugzilla.suse.com/1255911","tags":["report"]},{"url":"https://bugzilla.suse.com/1255915","tags":["report"]},{"url":"https://bugzilla.suse.com/1255918","tags":["report"]},{"url":"https://bugzilla.suse.com/1255921","tags":["report"]},{"url":"https://bugzilla.suse.com/1255924","tags":["report"]},{"url":"https://bugzilla.suse.com/1255931","tags":["report"]},{"url":"https://bugzilla.suse.com/1255932","tags":["report"]},{"url":"https://bugzilla.suse.com/1255934","tags":["report"]},{"url":"https://bugzilla.suse.com/1255944","tags":["report"]},{"url":"https://bugzilla.suse.com/1255949","tags":["report"]},{"url":"https://bugzilla.suse.com/1255951","tags":["report"]},{"url":"https://bugzilla.suse.com/1255952","tags":["report"]},{"url":"https://bugzilla.suse.com/1255955","tags":["report"]},{"url":"https://bugzilla.suse.com/1255957","tags":["report"]},{"url":"https://bugzilla.suse.com/1255963","tags":["report"]},{"url":"https://bugzilla.suse.com/1255964","tags":["report"]},{"url":"https://bugzilla.suse.com/1255967","tags":["report"]},{"url":"https://bugzilla.suse.com/1255974","tags":["report"]},{"url":"https://bugzilla.suse.com/1255978","tags":["report"]},{"url":"https://bugzilla.suse.com/1255984","tags":["report"]},{"url":"https://bugzilla.suse.com/1255988","tags":["report"]},{"url":"https://bugzilla.suse.com/1255990","tags":["report"]},{"url":"https://bugzilla.suse.com/1255992","tags":["report"]},{"url":"https://bugzilla.suse.com/1255993","tags":["report"]},{"url":"https://bugzilla.suse.com/1255994","tags":["report"]},{"url":"https://bugzilla.suse.com/1255996","tags":["report"]},{"url":"https://bugzilla.suse.com/1256033","tags":["report"]},{"url":"https://bugzilla.suse.com/1256034","tags":["report"]},{"url":"https://bugzilla.suse.com/1256045","tags":["report"]},{"url":"https://bugzilla.suse.com/1256050","tags":["report"]},{"url":"https://bugzilla.suse.com/1256071","tags":["report"]},{"url":"https://bugzilla.suse.com/1256074","tags":["report"]},{"url":"https://bugzilla.suse.com/1256081","tags":["report"]},{"url":"https://bugzilla.suse.com/1256082","tags":["report"]},{"url":"https://bugzilla.suse.com/1256083","tags":["report"]},{"url":"https://bugzilla.suse.com/1256084","tags":["report"]},{"url":"https://bugzilla.suse.com/1256085","tags":["report"]},{"url":"https://bugzilla.suse.com/1256090","tags":["report"]},{"url":"https://bugzilla.suse.com/1256093","tags":["report"]},{"url":"https://bugzilla.suse.com/1256094","tags":["report"]},{"url":"https://bugzilla.suse.com/1256095","tags":["report"]},{"url":"https://bugzilla.suse.com/1256096","tags":["report"]},{"url":"https://bugzilla.suse.com/1256099","tags":["report"]},{"url":"https://bugzilla.suse.com/1256100","tags":["report"]},{"url":"https://bugzilla.suse.com/1256104","tags":["report"]},{"url":"https://bugzilla.suse.com/1256107","tags":["report"]},{"url":"https://bugzilla.suse.com/1256117","tags":["report"]},{"url":"https://bugzilla.suse.com/1256119","tags":["report"]},{"url":"https://bugzilla.suse.com/1256121","tags":["report"]},{"url":"https://bugzilla.suse.com/1256145","tags":["report"]},{"url":"https://bugzilla.suse.com/1256153","tags":["report"]},{"url":"https://bugzilla.suse.com/1256178","tags":["report"]},{"url":"https://bugzilla.suse.com/1256197","tags":["report"]},{"url":"https://bugzilla.suse.com/1256231","tags":["report"]},{"url":"https://bugzilla.suse.com/1256233","tags":["report"]},{"url":"https://bugzilla.suse.com/1256234","tags":["report"]},{"url":"https://bugzilla.suse.com/1256238","tags":["report"]},{"url":"https://bugzilla.suse.com/1256263","tags":["report"]},{"url":"https://bugzilla.suse.com/1256268","tags":["report"]},{"url":"https://bugzilla.suse.com/1256271","tags":["report"]},{"url":"https://bugzilla.suse.com/1256273","tags":["report"]},{"url":"https://bugzilla.suse.com/1256274","tags":["report"]},{"url":"https://bugzilla.suse.com/1256279","tags":["report"]},{"url":"https://bugzilla.suse.com/1256285","tags":["report"]},{"url":"https://bugzilla.suse.com/1256291","tags":["report"]},{"url":"https://bugzilla.suse.com/1256292","tags":["report"]},{"url":"https://bugzilla.suse.com/1256300","tags":["report"]},{"url":"https://bugzilla.suse.com/1256301","tags":["report"]},{"url":"https://bugzilla.suse.com/1256302","tags":["report"]},{"url":"https://bugzilla.suse.com/1256335","tags":["report"]},{"url":"https://bugzilla.suse.com/1256348","tags":["report"]},{"url":"https://bugzilla.suse.com/1256351","tags":["report"]},{"url":"https://bugzilla.suse.com/1256358","tags":["report"]},{"url":"https://bugzilla.suse.com/1256361","tags":["report"]},{"url":"https://bugzilla.suse.com/1256364","tags":["report"]},{"url":"https://bugzilla.suse.com/1256366","tags":["report"]},{"url":"https://bugzilla.suse.com/1256367","tags":["report"]},{"url":"https://bugzilla.suse.com/1256368","tags":["report"]},{"url":"https://bugzilla.suse.com/1256370","tags":["report"]},{"url":"https://bugzilla.suse.com/1256371","tags":["report"]},{"url":"https://bugzilla.suse.com/1256373","tags":["report"]},{"url":"https://bugzilla.suse.com/1256375","tags":["report"]},{"url":"https://bugzilla.suse.com/1256379","tags":["report"]},{"url":"https://bugzilla.suse.com/1256387","tags":["report"]},{"url":"https://bugzilla.suse.com/1256394","tags":["report"]},{"url":"https://bugzilla.suse.com/1256396","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-42752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53750","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53762","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53777","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53778","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53813","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53834","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53843","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53844","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53994","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53995","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53996","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53997","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54001","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54016","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54027","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54051","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54088","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54106","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54143","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54164","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54211","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54296","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54299","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2023-54326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-26944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40153","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40211","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40248","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40256","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40275","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40288","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40315","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40317","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40321","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40322","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40338","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40342","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68180","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68239","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68244","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68252","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68255","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68289","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68313","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68330","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68347","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68734","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68750","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68759","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68766","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620498-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620555-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1235905","tags":["report"]},{"url":"https://bugzilla.suse.com/1242974","tags":["report"]},{"url":"https://bugzilla.suse.com/1242986","tags":["report"]},{"url":"https://bugzilla.suse.com/1243452","tags":["report"]},{"url":"https://bugzilla.suse.com/1243507","tags":["report"]},{"url":"https://bugzilla.suse.com/1246282","tags":["report"]},{"url":"https://bugzilla.suse.com/1247292","tags":["report"]},{"url":"https://bugzilla.suse.com/1248166","tags":["report"]},{"url":"https://bugzilla.suse.com/1248175","tags":["report"]},{"url":"https://bugzilla.suse.com/1248178","tags":["report"]},{"url":"https://bugzilla.suse.com/1248179","tags":["report"]},{"url":"https://bugzilla.suse.com/1248185","tags":["report"]},{"url":"https://bugzilla.suse.com/1248188","tags":["report"]},{"url":"https://bugzilla.suse.com/1248196","tags":["report"]},{"url":"https://bugzilla.suse.com/1248206","tags":["report"]},{"url":"https://bugzilla.suse.com/1248208","tags":["report"]},{"url":"https://bugzilla.suse.com/1248209","tags":["report"]},{"url":"https://bugzilla.suse.com/1248212","tags":["report"]},{"url":"https://bugzilla.suse.com/1248213","tags":["report"]},{"url":"https://bugzilla.suse.com/1248214","tags":["report"]},{"url":"https://bugzilla.suse.com/1248216","tags":["report"]},{"url":"https://bugzilla.suse.com/1248217","tags":["report"]},{"url":"https://bugzilla.suse.com/1248222","tags":["report"]},{"url":"https://bugzilla.suse.com/1248227","tags":["report"]},{"url":"https://bugzilla.suse.com/1248228","tags":["report"]},{"url":"https://bugzilla.suse.com/1248229","tags":["report"]},{"url":"https://bugzilla.suse.com/1248232","tags":["report"]},{"url":"https://bugzilla.suse.com/1248234","tags":["report"]},{"url":"https://bugzilla.suse.com/1248240","tags":["report"]},{"url":"https://bugzilla.suse.com/1248360","tags":["report"]},{"url":"https://bugzilla.suse.com/1248366","tags":["report"]},{"url":"https://bugzilla.suse.com/1248384","tags":["report"]},{"url":"https://bugzilla.suse.com/1248626","tags":["report"]},{"url":"https://bugzilla.suse.com/1249609","tags":["report"]},{"url":"https://bugzilla.suse.com/1249895","tags":["report"]},{"url":"https://bugzilla.suse.com/1249998","tags":["report"]},{"url":"https://bugzilla.suse.com/1250738","tags":["report"]},{"url":"https://bugzilla.suse.com/1252773","tags":["report"]},{"url":"https://bugzilla.suse.com/1252784","tags":["report"]},{"url":"https://bugzilla.suse.com/1253049","tags":["report"]},{"url":"https://bugzilla.suse.com/1253078","tags":["report"]},{"url":"https://bugzilla.suse.com/1253079","tags":["report"]},{"url":"https://bugzilla.suse.com/1253344","tags":["report"]},{"url":"https://bugzilla.suse.com/1253500","tags":["report"]},{"url":"https://bugzilla.suse.com/1254308","tags":["report"]},{"url":"https://bugzilla.suse.com/1254977","tags":["report"]},{"url":"https://bugzilla.suse.com/1255232","tags":["report"]},{"url":"https://bugzilla.suse.com/1255319","tags":["report"]},{"url":"https://bugzilla.suse.com/1255459","tags":["report"]},{"url":"https://bugzilla.suse.com/1255506","tags":["report"]},{"url":"https://bugzilla.suse.com/1255526","tags":["report"]},{"url":"https://bugzilla.suse.com/1255527","tags":["report"]},{"url":"https://bugzilla.suse.com/1255529","tags":["report"]},{"url":"https://bugzilla.suse.com/1255530","tags":["report"]},{"url":"https://bugzilla.suse.com/1255536","tags":["report"]},{"url":"https://bugzilla.suse.com/1255542","tags":["report"]},{"url":"https://bugzilla.suse.com/1255593","tags":["report"]},{"url":"https://bugzilla.suse.com/1255694","tags":["report"]},{"url":"https://bugzilla.suse.com/1255703","tags":["report"]},{"url":"https://bugzilla.suse.com/1255708","tags":["report"]},{"url":"https://bugzilla.suse.com/1255811","tags":["report"]},{"url":"https://bugzilla.suse.com/1256632","tags":["report"]},{"url":"https://bugzilla.suse.com/1256643","tags":["report"]},{"url":"https://bugzilla.suse.com/1256656","tags":["report"]},{"url":"https://bugzilla.suse.com/1256667","tags":["report"]},{"url":"https://bugzilla.suse.com/1256668","tags":["report"]},{"url":"https://bugzilla.suse.com/1256677","tags":["report"]},{"url":"https://bugzilla.suse.com/1256683","tags":["report"]},{"url":"https://bugzilla.suse.com/1256716","tags":["report"]},{"url":"https://bugzilla.suse.com/1256755","tags":["report"]},{"url":"https://bugzilla.suse.com/1256793","tags":["report"]},{"url":"https://bugzilla.suse.com/1256864","tags":["report"]},{"url":"https://bugzilla.suse.com/1256865","tags":["report"]},{"url":"https://bugzilla.suse.com/1256867","tags":["report"]},{"url":"https://bugzilla.suse.com/1256975","tags":["report"]},{"url":"https://bugzilla.suse.com/1257015","tags":["report"]},{"url":"https://bugzilla.suse.com/1257159","tags":["report"]},{"url":"https://bugzilla.suse.com/1257179","tags":["report"]},{"url":"https://bugzilla.suse.com/1257225","tags":["report"]},{"url":"https://bugzilla.suse.com/1257243","tags":["report"]},{"url":"https://bugzilla.suse.com/1257276","tags":["report"]},{"url":"https://bugzilla.suse.com/1257279","tags":["report"]},{"url":"https://bugzilla.suse.com/1257309","tags":["report"]},{"url":"https://bugzilla.suse.com/1257504","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-54031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37841","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37904","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38423","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38520","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38521","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38530","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38538","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38543","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38548","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38550","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38551","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40147","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68211","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68341","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68359","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68376","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68778","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68811","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22981","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22986","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23002","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620570-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620599-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620615-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620845-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1233640","tags":["report"]},{"url":"https://bugzilla.suse.com/1236022","tags":["report"]},{"url":"https://bugzilla.suse.com/1241345","tags":["report"]},{"url":"https://bugzilla.suse.com/1243055","tags":["report"]},{"url":"https://bugzilla.suse.com/1249587","tags":["report"]},{"url":"https://bugzilla.suse.com/1251966","tags":["report"]},{"url":"https://bugzilla.suse.com/1252911","tags":["report"]},{"url":"https://bugzilla.suse.com/1252924","tags":["report"]},{"url":"https://bugzilla.suse.com/1253622","tags":["report"]},{"url":"https://bugzilla.suse.com/1253691","tags":["report"]},{"url":"https://bugzilla.suse.com/1254992","tags":["report"]},{"url":"https://bugzilla.suse.com/1255129","tags":["report"]},{"url":"https://bugzilla.suse.com/1255265","tags":["report"]},{"url":"https://bugzilla.suse.com/1255379","tags":["report"]},{"url":"https://bugzilla.suse.com/1255698","tags":["report"]},{"url":"https://bugzilla.suse.com/1256564","tags":["report"]},{"url":"https://bugzilla.suse.com/1256640","tags":["report"]},{"url":"https://bugzilla.suse.com/1256679","tags":["report"]},{"url":"https://bugzilla.suse.com/1256708","tags":["report"]},{"url":"https://bugzilla.suse.com/1256802","tags":["report"]},{"url":"https://bugzilla.suse.com/1257209","tags":["report"]},{"url":"https://bugzilla.suse.com/1257228","tags":["report"]},{"url":"https://bugzilla.suse.com/1257231","tags":["report"]},{"url":"https://bugzilla.suse.com/1257246","tags":["report"]},{"url":"https://bugzilla.suse.com/1257552","tags":["report"]},{"url":"https://bugzilla.suse.com/1257554","tags":["report"]},{"url":"https://bugzilla.suse.com/1257557","tags":["report"]},{"url":"https://bugzilla.suse.com/1257559","tags":["report"]},{"url":"https://bugzilla.suse.com/1257560","tags":["report"]},{"url":"https://bugzilla.suse.com/1257562","tags":["report"]},{"url":"https://bugzilla.suse.com/1257570","tags":["report"]},{"url":"https://bugzilla.suse.com/1257573","tags":["report"]},{"url":"https://bugzilla.suse.com/1257576","tags":["report"]},{"url":"https://bugzilla.suse.com/1257579","tags":["report"]},{"url":"https://bugzilla.suse.com/1257580","tags":["report"]},{"url":"https://bugzilla.suse.com/1257586","tags":["report"]},{"url":"https://bugzilla.suse.com/1257635","tags":["report"]},{"url":"https://bugzilla.suse.com/1257679","tags":["report"]},{"url":"https://bugzilla.suse.com/1257687","tags":["report"]},{"url":"https://bugzilla.suse.com/1257704","tags":["report"]},{"url":"https://bugzilla.suse.com/1257706","tags":["report"]},{"url":"https://bugzilla.suse.com/1257707","tags":["report"]},{"url":"https://bugzilla.suse.com/1257714","tags":["report"]},{"url":"https://bugzilla.suse.com/1257715","tags":["report"]},{"url":"https://bugzilla.suse.com/1257716","tags":["report"]},{"url":"https://bugzilla.suse.com/1257718","tags":["report"]},{"url":"https://bugzilla.suse.com/1257722","tags":["report"]},{"url":"https://bugzilla.suse.com/1257723","tags":["report"]},{"url":"https://bugzilla.suse.com/1257729","tags":["report"]},{"url":"https://bugzilla.suse.com/1257735","tags":["report"]},{"url":"https://bugzilla.suse.com/1257739","tags":["report"]},{"url":"https://bugzilla.suse.com/1257740","tags":["report"]},{"url":"https://bugzilla.suse.com/1257741","tags":["report"]},{"url":"https://bugzilla.suse.com/1257743","tags":["report"]},{"url":"https://bugzilla.suse.com/1257745","tags":["report"]},{"url":"https://bugzilla.suse.com/1257749","tags":["report"]},{"url":"https://bugzilla.suse.com/1257750","tags":["report"]},{"url":"https://bugzilla.suse.com/1257757","tags":["report"]},{"url":"https://bugzilla.suse.com/1257758","tags":["report"]},{"url":"https://bugzilla.suse.com/1257759","tags":["report"]},{"url":"https://bugzilla.suse.com/1257761","tags":["report"]},{"url":"https://bugzilla.suse.com/1257762","tags":["report"]},{"url":"https://bugzilla.suse.com/1257763","tags":["report"]},{"url":"https://bugzilla.suse.com/1257765","tags":["report"]},{"url":"https://bugzilla.suse.com/1257768","tags":["report"]},{"url":"https://bugzilla.suse.com/1257770","tags":["report"]},{"url":"https://bugzilla.suse.com/1257772","tags":["report"]},{"url":"https://bugzilla.suse.com/1257775","tags":["report"]},{"url":"https://bugzilla.suse.com/1257776","tags":["report"]},{"url":"https://bugzilla.suse.com/1257788","tags":["report"]},{"url":"https://bugzilla.suse.com/1257789","tags":["report"]},{"url":"https://bugzilla.suse.com/1257790","tags":["report"]},{"url":"https://bugzilla.suse.com/1257805","tags":["report"]},{"url":"https://bugzilla.suse.com/1257808","tags":["report"]},{"url":"https://bugzilla.suse.com/1257809","tags":["report"]},{"url":"https://bugzilla.suse.com/1257811","tags":["report"]},{"url":"https://bugzilla.suse.com/1257813","tags":["report"]},{"url":"https://bugzilla.suse.com/1257816","tags":["report"]},{"url":"https://bugzilla.suse.com/1257830","tags":["report"]},{"url":"https://bugzilla.suse.com/1257891","tags":["report"]},{"url":"https://bugzilla.suse.com/1257952","tags":["report"]},{"url":"https://bugzilla.suse.com/1258153","tags":["report"]},{"url":"https://bugzilla.suse.com/1258181","tags":["report"]},{"url":"https://bugzilla.suse.com/1258184","tags":["report"]},{"url":"https://bugzilla.suse.com/1258222","tags":["report"]},{"url":"https://bugzilla.suse.com/1258234","tags":["report"]},{"url":"https://bugzilla.suse.com/1258237","tags":["report"]},{"url":"https://bugzilla.suse.com/1258245","tags":["report"]},{"url":"https://bugzilla.suse.com/1258249","tags":["report"]},{"url":"https://bugzilla.suse.com/1258252","tags":["report"]},{"url":"https://bugzilla.suse.com/1258256","tags":["report"]},{"url":"https://bugzilla.suse.com/1258259","tags":["report"]},{"url":"https://bugzilla.suse.com/1258272","tags":["report"]},{"url":"https://bugzilla.suse.com/1258273","tags":["report"]},{"url":"https://bugzilla.suse.com/1258277","tags":["report"]},{"url":"https://bugzilla.suse.com/1258278","tags":["report"]},{"url":"https://bugzilla.suse.com/1258279","tags":["report"]},{"url":"https://bugzilla.suse.com/1258299","tags":["report"]},{"url":"https://bugzilla.suse.com/1258304","tags":["report"]},{"url":"https://bugzilla.suse.com/1258309","tags":["report"]},{"url":"https://bugzilla.suse.com/1258313","tags":["report"]},{"url":"https://bugzilla.suse.com/1258317","tags":["report"]},{"url":"https://bugzilla.suse.com/1258321","tags":["report"]},{"url":"https://bugzilla.suse.com/1258326","tags":["report"]},{"url":"https://bugzilla.suse.com/1258338","tags":["report"]},{"url":"https://bugzilla.suse.com/1258349","tags":["report"]},{"url":"https://bugzilla.suse.com/1258354","tags":["report"]},{"url":"https://bugzilla.suse.com/1258358","tags":["report"]},{"url":"https://bugzilla.suse.com/1258374","tags":["report"]},{"url":"https://bugzilla.suse.com/1258377","tags":["report"]},{"url":"https://bugzilla.suse.com/1258379","tags":["report"]},{"url":"https://bugzilla.suse.com/1258394","tags":["report"]},{"url":"https://bugzilla.suse.com/1258395","tags":["report"]},{"url":"https://bugzilla.suse.com/1258397","tags":["report"]},{"url":"https://bugzilla.suse.com/1258411","tags":["report"]},{"url":"https://bugzilla.suse.com/1258415","tags":["report"]},{"url":"https://bugzilla.suse.com/1258419","tags":["report"]},{"url":"https://bugzilla.suse.com/1258422","tags":["report"]},{"url":"https://bugzilla.suse.com/1258424","tags":["report"]},{"url":"https://bugzilla.suse.com/1258429","tags":["report"]},{"url":"https://bugzilla.suse.com/1258442","tags":["report"]},{"url":"https://bugzilla.suse.com/1258464","tags":["report"]},{"url":"https://bugzilla.suse.com/1258465","tags":["report"]},{"url":"https://bugzilla.suse.com/1258468","tags":["report"]},{"url":"https://bugzilla.suse.com/1258469","tags":["report"]},{"url":"https://bugzilla.suse.com/1258484","tags":["report"]},{"url":"https://bugzilla.suse.com/1258518","tags":["report"]},{"url":"https://bugzilla.suse.com/1258519","tags":["report"]},{"url":"https://bugzilla.suse.com/1258520","tags":["report"]},{"url":"https://bugzilla.suse.com/1258524","tags":["report"]},{"url":"https://bugzilla.suse.com/1258544","tags":["report"]},{"url":"https://bugzilla.suse.com/1258660","tags":["report"]},{"url":"https://bugzilla.suse.com/1258824","tags":["report"]},{"url":"https://bugzilla.suse.com/1258928","tags":["report"]},{"url":"https://bugzilla.suse.com/1259070","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-53817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-37861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68810","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71192","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71199","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71232","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71235","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-22998","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23003","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23037","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23058","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23080","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23083","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23094","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23096","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23102","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23104","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23112","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23113","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23145","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23146","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23150","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23151","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23163","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23166","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23172","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23176","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23229","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620876-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-23011","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23011","tags":["report"]},{"url":"https://git.kernel.org/linus/e67c577d89894811ce4dcd1a9ed29d8b63476667","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8162-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8180-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8180-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8186-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8187-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8188-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8180-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8180-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8180-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8243-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8180-6","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8275-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8278-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8289-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8296-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8297-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8296-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8289-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8278-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8393-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8440-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8499-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8570-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8594-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8604-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8605-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8570-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8669-1","tags":["advisory"]},{"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-37849","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-40164","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-68365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71080","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-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-23060","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-23074","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-23091","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-23111","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-23145","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-23209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2022-49635","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-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-22022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22058","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-23143","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-38236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38556","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-40040","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-40083","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-40110","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-40211","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-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-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-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-68249","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-68780","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-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://ubuntu.com/security/CVE-2026-23268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23269","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://launchpad.net/bugs/2143853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-2640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2023-32629","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23112","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-68351","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-68823","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-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-23200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23202","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-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-31676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43284","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-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":"https://ubuntu.com/security/CVE-2024-36347","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-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-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-68786","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-68806","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-68821","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-71071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71088","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-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-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-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-71141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71148","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-2026-23231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31657","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53359","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-23011","title":"ipv4: ip_gre: make ipgre_header() robust","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\"ip6_gre: make ip6gre_header() robust\")\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u003eneeded_headroom and/or dev-\u003ehard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u003cTASK\u003e\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246","status":"published","published":"2026-01-25T14:36:24.455Z","modified":"2026-11-10T12:41:19.368Z","cwes":["CWE-119"],"updated_at":"2026-11-10T13:38:44.039016Z"}],"euvd":[{"id":"EUVD-2026-4623","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\"ip6_gre: make ip6gre_header() robust\")\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u003eneeded_headroom and/or dev-\u003ehard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u003cTASK\u003e\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246","status":"published","published":"2026-01-25T14:36:24Z","modified":"2026-11-10T12:41:19Z","updated_at":"2026-11-10T14:21:11.690542Z"}],"ghsa":[{"id":"GHSA-5ww3-m3hh-c9fg","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\"ip6_gre: make ip6gre_header() robust\")\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u003eneeded_headroom and/or dev-\u003ehard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u003cTASK\u003e\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246","status":"published","published":"2026-01-25T15:30:27Z","modified":"2026-10-19T21:33:14Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"cwes":["CWE-119"],"updated_at":"2026-11-02T15:13:58.795037Z"}],"nvd":[{"id":"CVE-2026-23011","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\"ip6_gre: make ip6gre_header() robust\")\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u003eneeded_headroom and/or dev-\u003ehard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u003cTASK\u003e\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246","status":"published","published":"2026-01-25T15:15:55.977Z","modified":"2026-11-10T13:18:33.01Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium","assessor":"primary"}],"cwes":["CWE-119"],"updated_at":"2026-11-10T16:19:45.801381Z"}],"osv":[{"id":"BELL-CVE-2026-23011","status":"published","published":"2026-01-27T06:07:23.36669Z","modified":"2026-06-25T07:18:33.098132895Z","cvss":[{"version":"3.1","score":5.5,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","level":"medium"}],"updated_at":"2026-11-02T15:28:23.037038Z"},{"id":"DEBIAN-CVE-2026-23011","description":"In the Linux kernel, the following vulnerability has been resolved: ipv4: ip_gre: make ipgre_header() robust Analog to commit db5b4e39c4e6 (\"ip6_gre: make ip6gre_header() robust\") Over the years, syzbot found many ways to crash the kernel in ipgre_header() [1]. This involves team or bonding drivers ability to dynamically change their dev-\u003eneeded_headroom and/or dev-\u003ehard_header_len In this particular crash mld_newpack() allocated an skb with a too small reserve/headroom, and by the time mld_sendpack() was called, syzbot managed to attach an ipgre device. [1] skbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0 kernel BUG at net/core/skbuff.c:213 ! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Workqueue: mld mld_ifc_work RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213 Call Trace: \u003cTASK\u003e skb_under_panic net/core/skbuff.c:223 [inline] skb_push+0xc3/0xe0 net/core/skbuff.c:2641 ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897 dev_hard_header include/linux/netdevice.h:3436 [inline] neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618 NF_HOOK_COND include/linux/netfilter.h:307 [inline] ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247 NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318 mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855 mld_send_cr net/ipv6/mcast.c:2154 [inline] mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693 process_one_work kernel/workqueue.c:3257 [inline] process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421 kthread+0x711/0x8a0 kernel/kthread.c:463 ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246","status":"published","published":"2026-01-25T15:15:55.977Z","modified":"2026-11-11T10:01:02.147393505Z","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-11T10:35:16.464644Z"},{"id":"OESA-2026-1566","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\nudp: Deal with race between UDP socket address change and rehash\n\nIf a UDP socket changes its local address while it\u0026apos;s receiving\ndatagrams, as a result of connect(), there is a period during which\na lookup operation might fail to find it, after the address is changed\nbut before the secondary hash (port and address) and the four-tuple\nhash (local and remote ports and addresses) are updated.\n\nSecondary hash chains were introduced by commit 30fff9231fad (\u0026quot;udp:\nbind() optimisation\u0026quot;) and, as a result, a rehash operation became\nneeded to make a bound socket reachable again after a connect().\n\nThis operation was introduced by commit 719f835853a9 (\u0026quot;udp: add\nrehash on connect()\u0026quot;) which isn\u0026apos;t however a complete fix: the\nsocket will be found once the rehashing completes, but not while\nit\u0026apos;s pending.\n\nThis is noticeable with a socat(1) server in UDP4-LISTEN mode, and a\nclient sending datagrams to it. After the server receives the first\ndatagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to\nthe address of the sender, in order to set up a directed flow.\n\nNow, if the client, running on a different CPU thread, happens to\nsend a (subsequent) datagram while the server\u0026apos;s socket changes its\naddress, but is not rehashed yet, this will result in a failed\nlookup and a port unreachable error delivered to the client, as\napparent from the following reproducer:\n\n LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))\n dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in\n\n while :; do\n \ttaskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n \tsleep 0.1 || sleep 1\n \ttaskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null\n \twait\n done\n\nwhere the client will eventually get ECONNREFUSED on a write()\n(typically the second or third one of a given iteration):\n\n 2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused\n\nThis issue was first observed as a seldom failure in Podman\u0026apos;s tests\nchecking UDP functionality while using pasta(1) to connect the\ncontainer\u0026apos;s network namespace, which leads us to a reproducer with\nthe lookup error resulting in an ICMP packet on a tap device:\n\n LOCAL_ADDR=\u0026quot;$(ip -j -4 addr show|jq -rM \u0026apos;.[] | .addr_info[0] | select(.scope == \u0026quot;global\u0026quot;).local\u0026apos;)\u0026quot;\n\n while :; do\n \t./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n \tsleep 0.2 || sleep 1\n \tsocat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null\n \twait\n \tcmp tmp.in tmp.out\n done\n\nOnce this fails:\n\n tmp.in tmp.out differ: char 8193, line 29\n\nwe can finally have a look at what\u0026apos;s going on:\n\n $ tshark -r pasta.pcap\n 1 0.000000 :: ? ff02::16 ICMPv6 110 Multicast Listener Report Message v2\n 2 0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 3 0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 4 0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 5 0.168827 c6:47:05:8d:dc:04 ? Broadcast ARP 42 Who has 88.198.0.161? Tell 88.198.0.164\n 6 0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55\n 7 0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 8 0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable)\n 9 0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 10 0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 11 0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096\n 12 0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0\n\nOn the third datagram received, the network namespace of the container\ninitiates an ARP lookup to deliver the ICMP message.\n\nIn another variant of this reproducer, starting the client with:\n\n strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru\n---truncated---(CVE-2024-57974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()\n\nIf track_pfn_copy() fails, we already added the dst VMA to the maple\ntree. As fork() fails, we\u0026apos;ll cleanup the maple tree, and stumble over\nthe dst VMA for which we neither performed any reservation nor copied\nany page tables.\n\nConsequently untrack_pfn() will see VM_PAT and try obtaining the\nPAT information from the page table -- which fails because the page\ntable was not copied.\n\nThe easiest fix would be to simply clear the VM_PAT flag of the dst VMA\nif track_pfn_copy() fails. However, the whole thing is about \u0026quot;simply\u0026quot;\nclearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy()\nand performed a reservation, but copying the page tables fails, we\u0026apos;ll\nsimply clear the VM_PAT flag, not properly undoing the reservation ...\nwhich is also wrong.\n\nSo let\u0026apos;s fix it properly: set the VM_PAT flag only if the reservation\nsucceeded (leaving it clear initially), and undo the reservation if\nanything goes wrong while copying the page tables: clearing the VM_PAT\nflag after undoing the reservation.\n\nNote that any copied page table entries will get zapped when the VMA will\nget removed later, after copy_page_range() succeeded; as VM_PAT is not set\nthen, we won\u0026apos;t try cleaning VM_PAT up once more and untrack_pfn() will be\nhappy. Note that leaving these page tables in place without a reservation\nis not a problem, as we are aborting fork(); this process will never run.\n\nA reproducer can trigger this usually at the first try:\n\n https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c\n\n WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110\n Modules linked in: ...\n CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\n RIP: 0010:get_pat_info+0xf6/0x110\n ...\n Call Trace:\n \u0026lt;TASK\u0026gt;\n ...\n untrack_pfn+0x52/0x110\n unmap_single_vma+0xa6/0xe0\n unmap_vmas+0x105/0x1f0\n exit_mmap+0xf6/0x460\n __mmput+0x4b/0x120\n copy_process+0x1bf6/0x2aa0\n kernel_clone+0xab/0x440\n __do_sys_clone+0x66/0x90\n do_syscall_64+0x95/0x180\n\nLikely this case was missed in:\n\n d155df53f310 (\u0026quot;x86/mm/pat: clear VM_PAT if copy_p4d_range failed\u0026quot;)\n\n... and instead of undoing the reservation we simply cleared the VM_PAT flag.\n\nKeep the documentation of these functions in include/linux/pgtable.h,\none place is more than sufficient -- we should clean that up for the other\nfunctions like track_pfn_remap/untrack_pfn separately.(CVE-2025-22090)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: make fallback action and fallback decision atomic\n\nSyzkaller reported the following splat:\n\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline]\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n Modules linked in:\n CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary)\n Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline]\n RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00\n RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246\n RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45\n RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001\n RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000\n R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000\n FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432\n tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975\n tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166\n tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925\n tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363\n ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205\n ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233\n NF_HOOK include/linux/netfilter.h:317 [inline]\n NF_HOOK include/linux/netfilter.h:311 [inline]\n ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254\n dst_input include/net/dst.h:469 [inline]\n ip_rcv_finish net/ipv4/ip_input.c:447 [inline]\n NF_HOOK include/linux/netfilter.h:317 [inline]\n NF_HOOK include/linux/netfilter.h:311 [inline]\n ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567\n __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975\n __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088\n process_backlog+0x301/0x1360 net/core/dev.c:6440\n __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453\n napi_poll net/core/dev.c:7517 [inline]\n net_rx_action+0xb44/0x1010 net/core/dev.c:7644\n handle_softirqs+0x1d0/0x770 kernel/softirq.c:579\n do_softirq+0x3f/0x90 kernel/softirq.c:480\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407\n local_bh_enable include/linux/bottom_half.h:33 [inline]\n inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524\n mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985\n mptcp_check_listen_stop net/mptcp/mib.h:118 [inline]\n __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000\n mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066\n inet_release+0xed/0x200 net/ipv4/af_inet.c:435\n inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487\n __sock_release+0xb3/0x270 net/socket.c:649\n sock_close+0x1c/0x30 net/socket.c:1439\n __fput+0x402/0xb70 fs/file_table.c:465\n task_work_run+0x150/0x240 kernel/task_work.c:227\n resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n exit_to_user_mode_loop+0xd4\n---truncated---(CVE-2025-38491)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic\n\nThe decompress_io_ctx may be released asynchronously after\nI/O completion. If this file is deleted immediately after read,\nand the kworker of processing post_read_wq has not been executed yet\ndue to high workloads, It is possible that the inode(f2fs_inode_info)\nis evicted and freed before it is used f2fs_free_dic.\n\n The UAF case as below:\n Thread A Thread B\n - f2fs_decompress_end_io\n - f2fs_put_dic\n - queue_work\n add free_dic work to post_read_wq\n - do_unlink\n - iput\n - evict\n - call_rcu\n This file is deleted after read.\n\n Thread C kworker to process post_read_wq\n - rcu_do_batch\n - f2fs_free_inode\n - kmem_cache_free\n inode is freed by rcu\n - process_scheduled_works\n - f2fs_late_free_dic\n - f2fs_free_dic\n - f2fs_release_decomp_mem\n read (dic-\u0026gt;inode)-\u0026gt;i_compress_algorithm\n\nThis patch store compress_algorithm and sbi in dic to avoid inode UAF.\n\nIn addition, the previous solution is deprecated in [1] may cause system hang.\n[1] https://lore.kernel.org/all/(CVE-2025-38627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n[ceph] parse_longname(): strrchr() expects NUL-terminated string\n\n... and parse_longname() is not guaranteed that. That\u0026apos;s the reason\nwhy it uses kmemdup_nul() to build the argument for kstrtou64();\nthe problem is, kstrtou64() is not the only thing that need it.\n\nJust get a NUL-terminated copy of the entire thing and be done\nwith that...(CVE-2025-38660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: remove refcounting in expectation dumpers\n\nSame pattern as previous patch: do not keep the expectation object\nalive via refcount, only store a cookie value and then use that\nas the skip hint for dump resumption.\n\nAFAICS this has the same issue as the one resolved in the conntrack\ndumper, when we do\n if (!refcount_inc_not_zero(\u0026amp;exp-\u0026gt;use))\n\nto increment the refcount, there is a chance that exp == last, which\ncauses a double-increment of the refcount and subsequent memory leak.(CVE-2025-39764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: avoid accessing metadata when pointer is invalid in object_err()\n\nobject_err() reports details of an object for further debugging, such as\nthe freelist pointer, redzone, etc. However, if the pointer is invalid,\nattempting to access object metadata can lead to a crash since it does\nnot point to a valid object.\n\nOne known path to the crash is when alloc_consistency_checks()\ndetermines the pointer to the allocated object is invalid because of a\nfreelist corruption, and calls object_err() to report it. The debug code\nshould report and handle the corruption gracefully and not crash in the\nprocess.\n\nIn case the pointer is NULL or check_valid_pointer() returns false for\nthe pointer, only print the pointer value and skip accessing metadata.(CVE-2025-39902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix Rx page leak on multi-buffer frames\n\nThe ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each\nbuffer in the current frame. This function was introduced as part of\nhandling multi-buffer XDP support in the ice driver.\n\nIt works by iterating over the buffers from first_desc up to 1 plus the\ntotal number of fragments in the frame, cached from before the XDP program\nwas executed.\n\nIf the hardware posts a descriptor with a size of 0, the logic used in\nice_put_rx_mbuf() breaks. Such descriptors get skipped and don\u0026apos;t get added\nas fragments in ice_add_xdp_frag. Since the buffer isn\u0026apos;t counted as a\nfragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don\u0026apos;t\ncall ice_put_rx_buf().\n\nBecause we don\u0026apos;t call ice_put_rx_buf(), we don\u0026apos;t attempt to re-use the\npage or free it. This leaves a stale page in the ring, as we don\u0026apos;t\nincrement next_to_alloc.\n\nThe ice_reuse_rx_page() assumes that the next_to_alloc has been incremented\nproperly, and that it always points to a buffer with a NULL page. Since\nthis function doesn\u0026apos;t check, it will happily recycle a page over the top\nof the next_to_alloc buffer, losing track of the old page.\n\nNote that this leak only occurs for multi-buffer frames. The\nice_put_rx_mbuf() function always handles at least one buffer, so a\nsingle-buffer frame will always get handled correctly. It is not clear\nprecisely why the hardware hands us descriptors with a size of 0 sometimes,\nbut it happens somewhat regularly with \u0026quot;jumbo frames\u0026quot; used by 9K MTU.\n\nTo fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on\nall buffers between first_desc and next_to_clean. Borrow the logic of a\nsimilar function in i40e used for this same purpose. Use the same logic\nalso in ice_get_pgcnts().\n\nInstead of iterating over just the number of fragments, use a loop which\niterates until the current index reaches to the next_to_clean element just\npast the current frame. Unlike i40e, the ice_put_rx_mbuf() function does\ncall ice_put_rx_buf() on the last buffer of the frame indicating the end of\npacket.\n\nFor non-linear (multi-buffer) frames, we need to take care when adjusting\nthe pagecnt_bias. An XDP program might release fragments from the tail of\nthe frame, in which case that fragment page is already released. Only\nupdate the pagecnt_bias for the first descriptor and fragments still\nremaining post-XDP program. Take care to only access the shared info for\nfragmented buffers, as this avoids a significant cache miss.\n\nThe xdp_xmit value only needs to be updated if an XDP program is run, and\nonly once per packet. Drop the xdp_xmit pointer argument from\nice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function\ndirectly. This avoids needing to pass the argument and avoids an extra\nbit-wise OR for each buffer in the frame.\n\nMove the increment of the ntc local variable to ensure its updated *before*\nall calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic\nrequires the index of the element just after the current frame.\n\nNow that we use an index pointer in the ring to identify the packet, we no\nlonger need to track or cache the number of fragments in the rx_ring.(CVE-2025-39948)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: Set fb_display[i]-\u0026gt;mode to NULL when the mode is released\n\nRecently, we discovered the following issue through syzkaller:\n\nBUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0\nRead of size 4 at addr ff11000001b3c69c by task syz.xxx\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xab/0xe0\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb9/0x280\n kasan_report+0xb8/0xf0\n fb_mode_is_equal+0x285/0x2f0\n fbcon_mode_deleted+0x129/0x180\n fb_set_var+0xe7f/0x11d0\n do_fb_ioctl+0x6a0/0x750\n fb_ioctl+0xe0/0x140\n __x64_sys_ioctl+0x193/0x210\n do_syscall_64+0x5f/0x9c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nBased on experimentation and analysis, during framebuffer unregistration,\nonly the memory of fb_info-\u0026gt;modelist is freed, without setting the\ncorresponding fb_display[i]-\u0026gt;mode to NULL for the freed modes. This leads\nto UAF issues during subsequent accesses. Here\u0026apos;s an example of reproduction\nsteps:\n1. With /dev/fb0 already registered in the system, load a kernel module\n to register a new device /dev/fb1;\n2. Set fb1\u0026apos;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);\n3. Switch console from fb to VGA (to allow normal rmmod of the ko);\n4. Unload the kernel module, at this point fb1\u0026apos;s modelist is freed, leaving\n a wild pointer in fb_display[];\n5. Trigger the bug via system calls through fb0 attempting to delete a mode\n from fb0.\n\nAdd a check in do_unregister_framebuffer(): if the mode to be freed exists\nin fb_display[], set the corresponding mode pointer to NULL.(CVE-2025-40323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb\n\nThe Mesa issue referenced below pointed out a possible deadlock:\n\n[ 1231.611031] Possible interrupt unsafe locking scenario:\n\n[ 1231.611033] CPU0 CPU1\n[ 1231.611034] ---- ----\n[ 1231.611035] lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611038] local_irq_disable();\n[ 1231.611039] lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611041] lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611044] \u0026lt;Interrupt\u0026gt;\n[ 1231.611045] lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611047]\n *** DEADLOCK ***\n\nIn this example, CPU0 would be any function accessing job-\u0026gt;dependencies\nthrough the xa_* functions that don\u0026apos;t disable interrupts (eg:\ndrm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()).\n\nCPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling\ncallback so in an interrupt context. It will deadlock when trying to\ngrab the xa_lock which is already held by CPU0.\n\nReplacing all xa_* usage by their xa_*_irq counterparts would fix\nthis issue, but Christian pointed out another issue: dma_fence_signal\ntakes fence.lock and so does dma_fence_add_callback.\n\n dma_fence_signal() // locks f1.lock\n -\u0026gt; drm_sched_entity_kill_jobs_cb()\n -\u0026gt; foreach dependencies\n -\u0026gt; dma_fence_add_callback() // locks f2.lock\n\nThis will deadlock if f1 and f2 share the same spinlock.\n\nTo fix both issues, the code iterating on dependencies and re-arming them\nis moved out to drm_sched_entity_kill_jobs_work().\n\n[phasta: commit message nits](CVE-2025-40329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n Internal error: Oops: 000000009600004f [#1] SMP\n CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n Hardware name: LS1028A RDB Board (DT)\n pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : xfrm_input+0xde8/0x1318\n lr : xfrm_input+0x61c/0x1318\n sp : ffff800080003b20\n Call trace:\n xfrm_input+0xde8/0x1318\n xfrm6_rcv+0x38/0x44\n xfrm6_esp_rcv+0x48/0xa8\n ip6_protocol_deliver_rcu+0x94/0x4b0\n ip6_input_finish+0x44/0x70\n ip6_input+0x44/0xc0\n ipv6_rcv+0x6c/0x114\n __netif_receive_skb_one_core+0x5c/0x8c\n __netif_receive_skb+0x18/0x60\n process_backlog+0x78/0x17c\n __napi_poll+0x38/0x180\n net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imon: make send_packet() more robust\n\nsyzbot is reporting that imon has three problems which result in\nhung tasks due to forever holding device lock [1].\n\nFirst problem is that when usb_rx_callback_intf0() once got -EPROTO error\nafter ictx-\u0026gt;dev_present_intf0 became true, usb_rx_callback_intf0()\nresubmits urb after printk(), and resubmitted urb causes\nusb_rx_callback_intf0() to again get -EPROTO error. This results in\nprintk() flooding (RCU stalls).\n\nAlan Stern commented [2] that\n\n In theory it\u0026apos;s okay to resubmit _if_ the driver has a robust\n error-recovery scheme (such as giving up after some fixed limit on the\n number of errors or after some fixed time has elapsed, perhaps with a\n time delay to prevent a flood of errors). Most drivers don\u0026apos;t bother to\n do this; they simply give up right away. This makes them more\n vulnerable to short-term noise interference during USB transfers, but in\n reality such interference is quite rare. There\u0026apos;s nothing really wrong\n with giving up right away.\n\nbut imon has a poor error-recovery scheme which just retries forever;\nthis behavior should be fixed.\n\nSince I\u0026apos;m not sure whether it is safe for imon users to give up upon any\nerror code, this patch takes care of only union of error codes chosen from\nmodules in drivers/media/rc/ directory which handle -EPROTO error (i.e.\nir_toy, mceusb and igorplugusb).\n\nSecond problem is that when usb_rx_callback_intf0() once got -EPROTO error\nbefore ictx-\u0026gt;dev_present_intf0 becomes true, usb_rx_callback_intf0() always\nresubmits urb due to commit 8791d63af0cf (\u0026quot;[media] imon: don\u0026apos;t wedge\nhardware after early callbacks\u0026quot;). Move the ictx-\u0026gt;dev_present_intf0 test\nintroduced by commit 6f6b90c9231a (\u0026quot;[media] imon: don\u0026apos;t parse scancodes\nuntil intf configured\u0026quot;) to immediately before imon_incoming_packet(), or\nthe first problem explained above happens without printk() flooding (i.e.\nhung task).\n\nThird problem is that when usb_rx_callback_intf0() is not called for some\nreason (e.g. flaky hardware; the reproducer for this problem sometimes\nprevents usb_rx_callback_intf0() from being called),\nwait_for_completion_interruptible() in send_packet() never returns (i.e.\nhung task). As a workaround for such situation, change send_packet() to\nwait for completion with timeout of 10 seconds.(CVE-2025-68194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: arm: scmi: Fix genpd leak on provider registration failure\n\nIf of_genpd_add_provider_onecell() fails during probe, the previously\ncreated generic power domains are not removed, leading to a memory leak\nand potential kernel crash later in genpd_debug_add().\n\nAdd proper error handling to unwind the initialized domains before\nreturning from probe to ensure all resources are correctly released on\nfailure.\n\nExample crash trace observed without this fix:\n\n | Unable to handle kernel paging request at virtual address fffffffffffffc70\n | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT\n | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform\n | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n | pc : genpd_debug_add+0x2c/0x160\n | lr : genpd_debug_init+0x74/0x98\n | Call trace:\n | genpd_debug_add+0x2c/0x160 (P)\n | genpd_debug_init+0x74/0x98\n | do_one_initcall+0xd0/0x2d8\n | do_initcall_level+0xa0/0x140\n | do_initcalls+0x60/0xa8\n | do_basic_setup+0x28/0x40\n | kernel_init_freeable+0xe8/0x170\n | kernel_init+0x2c/0x140\n | ret_from_fork+0x10/0x20(CVE-2025-68204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0026apos;s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs.(CVE-2025-68209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksm: use range-walk function to jump over holes in scan_get_next_rmap_item\n\nCurrently, scan_get_next_rmap_item() walks every page address in a VMA to\nlocate mergeable pages. This becomes highly inefficient when scanning\nlarge virtual memory areas that contain mostly unmapped regions, causing\nksmd to use large amount of cpu without deduplicating much pages.\n\nThis patch replaces the per-address lookup with a range walk using\nwalk_page_range(). The range walker allows KSM to skip over entire\nunmapped holes in a VMA, avoiding unnecessary lookups. This problem was\npreviously discussed in [1].\n\nConsider the following test program which creates a 32 TiB mapping in the\nvirtual address space but only populates a single page:\n\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\n\n/* 32 TiB */\nconst size_t size = 32ul * 1024 * 1024 * 1024 * 1024;\n\nint main() {\n char *area = mmap(NULL, size, PROT_READ | PROT_WRITE,\n MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);\n\n if (area == MAP_FAILED) {\n perror(\u0026quot;mmap() failed\\n\u0026quot;);\n return -1;\n }\n\n /* Populate a single page such that we get an anon_vma. */\n *area = 0;\n\n /* Enable KSM. */\n madvise(area, size, MADV_MERGEABLE);\n pause();\n return 0;\n}\n\n$ ./ksm-sparse \u0026amp;\n$ echo 1 \u0026gt; /sys/kernel/mm/ksm/run \n\nWithout this patch ksmd uses 100% of the cpu for a long time (more then 1\nhour in my test machine) scanning all the 32 TiB virtual address space\nthat contain only one mapped page. This makes ksmd essentially deadlocked\nnot able to deduplicate anything of value. With this patch ksmd walks\nonly the one mapped page and skips the rest of the 32 TiB virtual address\nspace, making the scan fast using little cpu.(CVE-2025-68211)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempool: fix poisoning order\u0026gt;0 pages with HIGHMEM\n\nThe kernel test has reported:\n\n BUG: unable to handle page fault for address: fffba000\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n *pde = 03171067 *pte = 00000000\n Oops: Oops: 0002 [#1]\n CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G T 6.18.0-rc2-00031-gec7f31b2a2d3 #1 NONE a1d066dfe789f54bc7645c7989957d2bdee593ca\n Tainted: [T]=RANDSTRUCT\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n EIP: memset (arch/x86/include/asm/string_32.h:168 arch/x86/lib/memcpy_32.c:17)\n Code: a5 8b 4d f4 83 e1 03 74 02 f3 a4 83 c4 04 5e 5f 5d 2e e9 73 41 01 00 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c6 89 d0 89 f7 \u0026lt;f3\u0026gt; aa 89 f0 5e 5f 5d 2e e9 53 41 01 00 cc cc cc 55 89 e5 53 57 56\n EAX: 0000006b EBX: 00000015 ECX: 001fefff EDX: 0000006b\n ESI: fffb9000 EDI: fffba000 EBP: c611fbf0 ESP: c611fbe8\n DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010287\n CR0: 80050033 CR2: fffba000 CR3: 0316e000 CR4: 00040690\n Call Trace:\n poison_element (mm/mempool.c:83 mm/mempool.c:102)\n mempool_init_node (mm/mempool.c:142 mm/mempool.c:226)\n mempool_init_noprof (mm/mempool.c:250 (discriminator 1))\n ? mempool_alloc_pages (mm/mempool.c:640)\n bio_integrity_initfn (block/bio-integrity.c:483 (discriminator 8))\n ? mempool_alloc_pages (mm/mempool.c:640)\n do_one_initcall (init/main.c:1283)\n\nChristoph found out this is due to the poisoning code not dealing\nproperly with CONFIG_HIGHMEM because only the first page is mapped but\nthen the whole potentially high-order page is accessed.\n\nWe could give up on HIGHMEM here, but it\u0026apos;s straightforward to fix this\nwith a loop that\u0026apos;s mapping, poisoning or checking and unmapping\nindividual pages.(CVE-2025-68231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtdchar: fix integer overflow in read/write ioctls\n\nThe \u0026quot;req.start\u0026quot; and \u0026quot;req.len\u0026quot; variables are u64 values that come from the\nuser at the start of the function. We mask away the high 32 bits of\n\u0026quot;req.len\u0026quot; so that\u0026apos;s capped at U32_MAX but the \u0026quot;req.start\u0026quot; variable can go\nup to U64_MAX which means that the addition can still integer overflow.\n\nUse check_add_overflow() to fix this bug.(CVE-2025-68237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u0026gt;work\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\u0026quot;usb: gadget: core: flush gadget workqueue after\ndevice removal\u0026quot;) attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget\u0026apos;s memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a \u0026apos;teardown\u0026apos;\nflag and a \u0026apos;state_lock\u0026apos; spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.(CVE-2025-68282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: fix NULL pointer deference when splitting folio\n\nCommit c010d47f107f (\u0026quot;mm: thp: split huge page to any lower order pages\u0026quot;)\nintroduced an early check on the folio\u0026apos;s order via mapping-\u0026gt;flags before\nproceeding with the split work.\n\nThis check introduced a bug: for shmem folios in the swap cache and\ntruncated folios, the mapping pointer can be NULL. Accessing\nmapping-\u0026gt;flags in this state leads directly to a NULL pointer dereference.\n\nThis commit fixes the issue by moving the check for mapping != NULL before\nany attempt to access mapping-\u0026gt;flags.(CVE-2025-68293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU/AMD: Add RDSEED fix for Zen5\n\nThere\u0026apos;s an issue with RDSEED\u0026apos;s 16-bit and 32-bit register output\nvariants on Zen5 which return a random value of 0 \u0026quot;at a rate inconsistent\nwith randomness while incorrectly signaling success (CF=1)\u0026quot;. Search the\nweb for AMD-SB-7055 for more detail.\n\nAdd a fix glue which checks microcode revisions.\n\n [ bp: Add microcode revisions checking, rewrite. ](CVE-2025-68313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninet: frags: flush pending skbs in fqdir_pre_exit()\n\nWe have been seeing occasional deadlocks on pernet_ops_rwsem since\nSeptember in NIPA. The stuck task was usually modprobe (often loading\na driver like ipvlan), trying to take the lock as a Writer.\nlockdep does not track readers for rwsems so the read wasn\u0026apos;t obvious\nfrom the reports.\n\nOn closer inspection the Reader holding the lock was conntrack looping\nforever in nf_conntrack_cleanup_net_list(). Based on past experience\nwith occasional NIPA crashes I looked thru the tests which run before\nthe crash and noticed that the crash follows ip_defrag.sh. An immediate\nred flag. Scouring thru (de)fragmentation queues reveals skbs sitting\naround, holding conntrack references.\n\nThe problem is that since conntrack depends on nf_defrag_ipv6,\nnf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its\nnetns exit hooks run _after_ conntrack\u0026apos;s netns exit hook.\n\nFlush all fragment queue SKBs during fqdir_pre_exit() to release\nconntrack references before conntrack cleanup runs. Also flush\nthe queues in timer expiry handlers when they discover fqdir-\u0026gt;dead\nis set, in case packet sneaks in while we\u0026apos;re running the pre_exit\nflush.\n\nThe commit under Fixes is not exactly the culprit, but I think\npreviously the timer firing would eventually unblock the spinning\nconntrack.(CVE-2025-68768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix middle attribute validation in push_nsh() action\n\nThe push_nsh() action structure looks like this:\n\n OVS_ACTION_ATTR_PUSH_NSH(OVS_KEY_ATTR_NSH(OVS_NSH_KEY_ATTR_BASE,...))\n\nThe outermost OVS_ACTION_ATTR_PUSH_NSH attribute is OK\u0026apos;ed by the\nnla_for_each_nested() inside __ovs_nla_copy_actions(). The innermost\nOVS_NSH_KEY_ATTR_BASE/MD1/MD2 are OK\u0026apos;ed by the nla_for_each_nested()\ninside nsh_key_put_from_nlattr(). But nothing checks if the attribute\nin the middle is OK. We don\u0026apos;t even check that this attribute is the\nOVS_KEY_ATTR_NSH. We just do a double unwrap with a pair of nla_data()\ncalls - first time directly while calling validate_push_nsh() and the\nsecond time as part of the nla_for_each_nested() macro, which isn\u0026apos;t\nsafe, potentially causing invalid memory access if the size of this\nattribute is incorrect. The failure may not be noticed during\nvalidation due to larger netlink buffer, but cause trouble later during\naction execution where the buffer is allocated exactly to the size:\n\n BUG: KASAN: slab-out-of-bounds in nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n Read of size 184 at addr ffff88816459a634 by task a.out/22624\n\n CPU: 8 UID: 0 PID: 22624 6.18.0-rc7+ #115 PREEMPT(voluntary)\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x51/0x70\n print_address_description.constprop.0+0x2c/0x390\n kasan_report+0xdd/0x110\n kasan_check_range+0x35/0x1b0\n __asan_memcpy+0x20/0x60\n nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n push_nsh+0x82/0x120 [openvswitch]\n do_execute_actions+0x1405/0x2840 [openvswitch]\n ovs_execute_actions+0xd5/0x3b0 [openvswitch]\n ovs_packet_cmd_execute+0x949/0xdb0 [openvswitch]\n genl_family_rcv_msg_doit+0x1d6/0x2b0\n genl_family_rcv_msg+0x336/0x580\n genl_rcv_msg+0x9f/0x130\n netlink_rcv_skb+0x11f/0x370\n genl_rcv+0x24/0x40\n netlink_unicast+0x73e/0xaa0\n netlink_sendmsg+0x744/0xbf0\n __sys_sendto+0x3d6/0x450\n do_syscall_64+0x79/0x2c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n \u0026lt;/TASK\u0026gt;\n\nLet\u0026apos;s add some checks that the attribute is properly sized and it\u0026apos;s\nthe only one attribute inside the action. Technically, there is no\nreal reason for OVS_KEY_ATTR_NSH to be there, as we know that we\u0026apos;re\npushing an NSH header already, it just creates extra nesting, but\nthat\u0026apos;s how uAPI works today. So, keeping as it is.(CVE-2025-68785)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: alps - fix use-after-free bugs caused by dev3_register_work\n\nThe dev3_register_work delayed work item is initialized within\nalps_reconnect() and scheduled upon receipt of the first bare\nPS/2 packet from an external PS/2 device connected to the ALPS\ntouchpad. During device detachment, the original implementation\ncalls flush_workqueue() in psmouse_disconnect() to ensure\ncompletion of dev3_register_work. However, the flush_workqueue()\nin psmouse_disconnect() only blocks and waits for work items that\nwere already queued to the workqueue prior to its invocation. Any\nwork items submitted after flush_workqueue() is called are not\nincluded in the set of tasks that the flush operation awaits.\nThis means that after flush_workqueue() has finished executing,\nthe dev3_register_work could still be scheduled. Although the\npsmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(),\nthe scheduling of dev3_register_work remains unaffected.\n\nThe race condition can occur as follows:\n\nCPU 0 (cleanup path) | CPU 1 (delayed work)\npsmouse_disconnect() |\n psmouse_set_state() |\n flush_workqueue() | alps_report_bare_ps2_packet()\n alps_disconnect() | psmouse_queue_work()\n kfree(priv); // FREE | alps_register_bare_ps2_mouse()\n | priv = container_of(work...); // USE\n | priv-\u0026gt;dev3 // USE\n\nAdd disable_delayed_work_sync() in alps_disconnect() to ensure\nthat dev3_register_work is properly canceled and prevented from\nexecuting after the alps_data structure has been deallocated.\n\nThis bug is identified by static analysis.(CVE-2025-68822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential deadlock\n\nAs Jiaming Zhang and syzbot reported, there is potential deadlock in\nf2fs as below:\n\nChain exists of:\n \u0026amp;sbi-\u0026gt;cp_rwsem --\u0026gt; fs_reclaim --\u0026gt; sb_internal#2\n\n Possible unsafe locking scenario:\n\n CPU0 CPU1\n ---- ----\n rlock(sb_internal#2);\n lock(fs_reclaim);\n lock(sb_internal#2);\n rlock(\u0026amp;sbi-\u0026gt;cp_rwsem);\n\n *** DEADLOCK ***\n\n3 locks held by kswapd0/73:\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197\n #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890\n\nstack backtrace:\nCPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043\n check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175\n check_prev_add kernel/locking/lockdep.c:3165 [inline]\n check_prevs_add kernel/locking/lockdep.c:3284 [inline]\n validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908\n __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237\n lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868\n down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537\n f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]\n f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]\n f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791\n f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867\n f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925\n f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897\n evict+0x504/0x9c0 fs/inode.c:810\n f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853\n evict+0x504/0x9c0 fs/inode.c:810\n dispose_list fs/inode.c:852 [inline]\n prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000\n super_cache_scan+0x39b/0x4b0 fs/super.c:224\n do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437\n shrink_slab_memcg mm/shrinker.c:550 [inline]\n shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628\n shrink_one+0x28a/0x7c0 mm/vmscan.c:4955\n shrink_many mm/vmscan.c:5016 [inline]\n lru_gen_shrink_node mm/vmscan.c:5094 [inline]\n shrink_node+0x315d/0x3780 mm/vmscan.c:6081\n kswapd_shrink_node mm/vmscan.c:6941 [inline]\n balance_pgdat mm/vmscan.c:7124 [inline]\n kswapd+0x147c/0x2800 mm/vmscan.c:7389\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is deadlock among four locks as below:\n\nkswapd\n- fs_reclaim\t\t\t\t--- Lock A\n - shrink_one\n - evict\n - f2fs_evict_inode\n - sb_start_intwrite\t\t\t--- Lock B\n\n- iput\n - evict\n - f2fs_evict_inode\n - sb_start_intwrite\t\t\t--- Lock B\n - f2fs_truncate\n - f2fs_truncate_blocks\n - f2fs_do_truncate_blocks\n - f2fs_lock_op\t\t\t--- Lock C\n\nioctl\n- f2fs_ioc_commit_atomic_write\n - f2fs_lock_op\t\t\t\t--- Lock C\n - __f2fs_commit_atomic_write\n - __replace_atomic_write_block\n - f2fs_get_dnode_of_data\n - __get_node_folio\n - f2fs_check_nid_range\n - f2fs_handle_error\n - f2fs_record_errors\n - f2fs_down_write\t\t--- Lock D\n\nopen\n- do_open\n - do_truncate\n - security_inode_need_killpriv\n - f2fs_getxattr\n - lookup_all_xattrs\n - f2fs_handle_error\n - f2fs_record_errors\n - f2fs_down_write\t\t--- Lock D\n - f2fs_commit_super\n - read_mapping_folio\n - filemap_alloc_folio_noprof\n - prepare_alloc_pages\n - fs_reclaim_acquire\t--- Lock A\n\nIn order to a\n---truncated---(CVE-2025-71065)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: Avoid NULL pointer deref for evicted BOs\n\nIt is possible for a BO to exist that is not currently associated with a\nresource, e.g. because it has been evicted.\n\nWhen devcoredump tries to read the contents of all BOs for dumping, we need\nto expect this as well -- in this case, ENODATA is recorded instead of the\nbuffer contents.(CVE-2025-71083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n GID entry ref leak for dev syz1 index 2 ref=573\n WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS: 00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n -\u0026gt; team_port_disable()\n -\u0026gt; team_queue_override_port_del()\n -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n -\u0026gt; team_queue_override_port_prio_changed()\n -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly\n\nThe netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a\nLS_NLA_TYPE_DGID attribute, it is invalid if it does not.\n\nUse the nl parsing logic properly and call nla_parse_deprecated() to fill\nthe nlattrs array and then directly index that array to get the data for\nthe DGID. Just fail if it is NULL.\n\nRemove the for loop searching for the nla, and squash the validation and\nparsing into one function.\n\nFixes an uninitialized read from the stack triggered by userspace if it\ndoes not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE\nquery.\n\n BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline]\n BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n hex_byte_pack include/linux/hex.h:13 [inline]\n ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509\n ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633\n pointer+0xc09/0x1bd0 lib/vsprintf.c:2542\n vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930\n vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279\n vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426\n vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465\n vprintk+0x36/0x50 kernel/printk/printk_safe.c:82\n _printk+0x17e/0x1b0 kernel/printk/printk.c:2475\n ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline]\n ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141\n rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline]\n rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x333/0x3d0 net/socket.c:729\n ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617\n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671\n __sys_sendmsg+0x1aa/0x300 net/socket.c:2703\n __compat_sys_sendmsg net/compat.c:346 [inline]\n __do_compat_sys_sendmsg net/compat.c:353 [inline]\n __se_compat_sys_sendmsg net/compat.c:350 [inline]\n __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350\n ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371\n do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306\n do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331\n do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3(CVE-2025-71096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: Fix reference count leak when using error routes with nexthop objects\n\nWhen a nexthop object is deleted, it is marked as dead and then\nfib_table_flush() is called to flush all the routes that are using the\ndead nexthop.\n\nThe current logic in fib_table_flush() is to only flush error routes\n(e.g., blackhole) when it is called as part of network namespace\ndismantle (i.e., with flush_all=true). Therefore, error routes are not\nflushed when their nexthop object is deleted:\n\n # ip link add name dummy1 up type dummy\n # ip nexthop add id 1 dev dummy1\n # ip route add 198.51.100.1/32 nhid 1\n # ip route add blackhole 198.51.100.2/32 nhid 1\n # ip nexthop del id 1\n # ip route show\n blackhole 198.51.100.2 nhid 1 dev dummy1\n\nAs such, they keep holding a reference on the nexthop object which in\nturn holds a reference on the nexthop device, resulting in a reference\ncount leak:\n\n # ip link del dev dummy1\n [ 70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2\n\nFix by flushing error routes when their nexthop is marked as dead.\n\nIPv6 does not suffer from this problem.(CVE-2025-71097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Avoid walking the Namespace if start_node is NULL\n\nAlthough commit 0c9992315e73 (\u0026quot;ACPICA: Avoid walking the ACPI Namespace\nif it is not there\u0026quot;) fixed the situation when both start_node and\nacpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed\non Honor Magicbook 14 Pro [1].\n\nThat happens due to the access to the member of parent_node in\nacpi_ns_get_next_node(). The NULL pointer dereference will always\nhappen, no matter whether or not the start_node is equal to\nACPI_ROOT_OBJECT, so move the check of start_node being NULL\nout of the if block.\n\nUnfortunately, all the attempts to contact Honor have failed, they\nrefused to provide any technical support for Linux.\n\nThe bad DSDT table\u0026apos;s dump could be found on GitHub [2].\n\nDMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025\n\n[ rjw: Subject adjustment, changelog edits ](CVE-2025-71118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Sign extend kfunc call arguments\n\nThe kfunc calls are native calls so they should follow LoongArch calling\nconventions. Sign extend its arguments properly to avoid kernel panic.\nThis is done by adding a new emit_abi_ext() helper. The emit_abi_ext()\nhelper performs extension in place meaning a value already store in the\ntarget register (Note: this is different from the existing sign_extend()\nhelper and thus we can\u0026apos;t reuse it).(CVE-2025-71129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tilcdc: Fix removal actions in case of failed probe\n\nThe drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers\nshould only be called when the device has been successfully registered.\nCurrently, these functions are called unconditionally in tilcdc_fini(),\nwhich causes warnings during probe deferral scenarios.\n\n[ 7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68\n...\n[ 8.005820] drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108\n[ 8.005858] drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8\n[ 8.005885] drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144\n[ 8.005911] drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc]\n[ 8.005957] tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]\n\nFix this by rewriting the failed probe cleanup path using the standard\ngoto error handling pattern, which ensures that cleanup functions are\nonly called on successfully initialized resources. Additionally, remove\nthe now-unnecessary is_registered flag.(CVE-2025-71141)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: stm32: dmamux: fix device leak on route allocation\n\nMake sure to drop the reference taken when looking up the DMA mux\nplatform device during route allocation.\n\nNote that holding a reference to a device does not prevent its driver\ndata from going away so there is no point in keeping the reference.(CVE-2025-71186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()\n\nWhen ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().(CVE-2025-71220)\n\nIn the Linux kernel, a race condition vulnerability exists in the mmp_pdma driver. The vulnerability occurs in the mmp_pdma_residue() function which lacks proper locking mechanisms, potentially leading to use-after-free issues when accessing descriptor lists and descriptor contents.\n\nThe race condition occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors. This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan \u0026gt; 1).\n\nThe fix involves protecting the chain_running list iteration and descriptor access with the chan-\u0026gt;desc_lock spinlock.(CVE-2025-71221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: fix refcount leak in smb2_open()\n\nWhen ksmbd_vfs_getattr() fails, the reference count of ksmbd_file\nmust be released.(CVE-2025-71223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u0026gt;r1bio_pool) and conf-\u0026gt;raid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u0026gt;raid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too.(CVE-2025-71225)\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Free sp in error path to fix system crash System crash seen during load/unload test in a loop, [61110.449331] qla2xxx [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494](CVE-2025-71232)\n\nIn the Linux kernel, there is a race condition vulnerability in the SCSI qla2xxx driver. System crash was observed during load/unload loop testing. The root cause was a memory free operation occurring in interrupt context. When device discovery/fabric scan was in progress and module unload was issued setting the UNLOADING flag, work queue items could not be allocated and mapped memory had to be freed in interrupt context, leading to system crash.(CVE-2025-71235)\n\nA NULL pointer dereference vulnerability exists in the SCSI qla2xxx driver subsystem of the Linux kernel. When the system attempts to free associated memory in the qla_fab_async_scan function, it fails to validate whether the sp pointer is NULL, leading to kernel NULL pointer dereference and system crashes. This vulnerability can be exploited by attackers to cause denial of service.(CVE-2025-71236)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sock: fix hardened usercopy panic in sock_recv_errqueue\n\nskbuff_fclone_cache was created without defining a usercopy region,\n[1] unlike skbuff_head_cache which properly whitelists the cb[] field.\n[2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is\nenabled and the kernel attempts to copy sk_buff.cb data to userspace\nvia sock_recv_errqueue() -\u0026gt; put_cmsg().\n\nThe crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()\n (from skbuff_fclone_cache) [1]\n2. The skb is cloned via skb_clone() using the pre-allocated fclone\n[3] 3. The cloned skb is queued to sk_error_queue for timestamp\nreporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)\n5. sock_recv_errqueue() calls put_cmsg() to copy serr-\u0026gt;ee from skb-\u0026gt;cb\n[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no\n usercopy whitelist [5]\n\nWhen cloned skbs allocated from skbuff_fclone_cache are used in the\nsocket error queue, accessing the sock_exterr_skb structure in skb-\u0026gt;cb\nvia put_cmsg() triggers a usercopy hardening violation:\n\n[ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object \u0026apos;skbuff_fclone_cache\u0026apos; (offset 296, size 16)!\n[ 5.382796] kernel BUG at mm/usercopy.c:102!\n[ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n[ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7\n[ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80\n[ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff \u0026lt;0f\u0026gt; 0b 490\n[ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246\n[ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74\n[ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0\n[ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74\n[ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001\n[ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00\n[ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000\n[ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0\n[ 5.384903] PKRU: 55555554\n[ 5.384903] Call Trace:\n[ 5.384903] \u0026lt;TASK\u0026gt;\n[ 5.384903] __check_heap_object+0x9a/0xd0\n[ 5.384903] __check_object_size+0x46c/0x690\n[ 5.384903] put_cmsg+0x129/0x5e0\n[ 5.384903] sock_recv_errqueue+0x22f/0x380\n[ 5.384903] tls_sw_recvmsg+0x7ed/0x1960\n[ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 5.384903] ? schedule+0x6d/0x270\n[ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 5.384903] ? mutex_unlock+0x81/0xd0\n[ 5.384903] ? __pfx_mutex_unlock+0x10/0x10\n[ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10\n[ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0\n[ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40\n[ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5\n\nThe crash offset 296 corresponds to skb2-\u0026gt;cb within skbuff_fclones:\n - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -\n offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 =\n 272 + 24 (inside sock_exterr_skb.ee)\n\nThis patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.\n\n[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885\n[2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104\n[3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566\n[4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491\n[5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719(CVE-2026-22977)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix memory leak in skb_segment_list for GRO packets\n\nWhen skb_segment_list() is called during packet forwarding, it handles\npackets that were aggregated by the GRO engine.\n\nHistorically, the segmentation logic in skb_segment_list assumes that\nindividual segments are split from a parent SKB and may need to carry\ntheir own socket memory accounting. Accordingly, the code transfers\ntruesize from the parent to the newly created segments.\n\nPrior to commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;), this\ntruesize subtraction in skb_segment_list() was valid because fragments\nstill carry a reference to the original socket.\n\nHowever, commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;) changed\nthis behavior by ensuring that fraglist entries are explicitly\norphaned (skb-\u0026gt;sk = NULL) to prevent illegal orphaning later in the\nstack. This change meant that the entire socket memory charge remained\nwith the head SKB, but the corresponding accounting logic in\nskb_segment_list() was never updated.\n\nAs a result, the current code unconditionally adds each fragment\u0026apos;s\ntruesize to delta_truesize and subtracts it from the parent SKB. Since\nthe fragments are no longer charged to the socket, this subtraction\nresults in an effective under-count of memory when the head is freed.\nThis causes sk_wmem_alloc to remain non-zero, preventing socket\ndestruction and leading to a persistent memory leak.\n\nThe leak can be observed via KMEMLEAK when tearing down the networking\nenvironment:\n\nunreferenced object 0xffff8881e6eb9100 (size 2048):\n comm \u0026quot;ping\u0026quot;, pid 6720, jiffies 4295492526\n backtrace:\n kmem_cache_alloc_noprof+0x5c6/0x800\n sk_prot_alloc+0x5b/0x220\n sk_alloc+0x35/0xa00\n inet6_create.part.0+0x303/0x10d0\n __sock_create+0x248/0x640\n __sys_socket+0x11b/0x1d0\n\nSince skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST\npackets constructed by GRO, the truesize adjustment is removed.\n\nThe call to skb_release_head_state() must be preserved. As documented in\ncommit cf673ed0e057 (\u0026quot;net: fix fraglist segmentation reference count\nleak\u0026quot;), it is still required to correctly drop references to SKB\nextensions that may be overwritten during __copy_skb_header().(CVE-2026-22979)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in handle_auth_done()\n\nPerform an explicit bounds check on payload_len to avoid a possible\nout-of-bounds access in the callout.\n\n[ idryomov: changelog ](CVE-2026-22984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make free_choose_arg_map() resilient to partial allocation\n\nfree_choose_arg_map() may dereference a NULL pointer if its caller fails\nafter a partial allocation.\n\nFor example, in decode_choose_args(), if allocation of arg_map-\u0026gt;args\nfails, execution jumps to the fail label and free_choose_arg_map() is\ncalled. Since arg_map-\u0026gt;size is updated to a non-zero value before memory\nallocation, free_choose_arg_map() will iterate over arg_map-\u0026gt;args and\ndereference a NULL pointer.\n\nTo prevent this potential NULL pointer dereference and make\nfree_choose_arg_map() more resilient, add checks for pointers before\niterating.(CVE-2026-22991)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: do not free existing class in qfq_change_class()\n\nFixes qfq_change_class() error case.\n\ncl-\u0026gt;qdisc and cl should only be freed if a new class and qdisc\nwere allocated, or we risk various UAF.(CVE-2026-22999)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n\nBlamed commit did not take care of VLAN encapsulations\nas spotted by syzbot [1].\n\nUse skb_vlan_inet_prepare() instead of pskb_inet_may_pull().\n\n[1]\n BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729\n __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860\n ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903\n gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1\n ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438\n ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489\n NF_HOOK include/linux/netfilter.h:318 [inline]\n ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500\n ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590\n dst_input include/net/dst.h:474 [inline]\n ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79\n NF_HOOK include/linux/netfilter.h:318 [inline]\n ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311\n __netif_receive_skb_one_core net/core/dev.c:6139 [inline]\n __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252\n netif_receive_skb_internal net/core/dev.c:6338 [inline]\n netif_receive_skb+0x57/0x630 net/core/dev.c:6397\n tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485\n tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953\n tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n new_sync_write fs/read_write.c:593 [inline]\n vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n ksys_write fs/read_write.c:738 [inline]\n __do_sys_write fs/read_write.c:749 [inline]\n __se_sys_write fs/read_write.c:746 [inline]\n __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:4960 [inline]\n slab_alloc_node mm/slub.c:5263 [inline]\n kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315\n kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586\n __alloc_skb+0x805/0x1040 net/core/skbuff.c:690\n alloc_skb include/linux/skbuff.h:1383 [inline]\n alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712\n sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995\n tun_alloc_skb drivers/net/tun.c:1461 [inline]\n tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794\n tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n new_sync_write fs/read_write.c:593 [inline]\n vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n ksys_write fs/read_write.c:738 [inline]\n __do_sys_write fs/read_write.c:749 [inline]\n __se_sys_write fs/read_write.c:746 [inline]\n __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025(CVE-2026-23003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix use-after-free in inet6_addr_del().\n\nsyzbot reported use-after-free of inet6_ifaddr in\ninet6_addr_del(). [0]\n\nThe cited commit accidentally moved ipv6_del_addr() for\nmngtmpaddr before reading its ifp-\u0026gt;flags for temporary\naddresses in inet6_addr_del().\n\nLet\u0026apos;s move ipv6_del_addr() down to fix the UAF.\n\n[0]:\nBUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\nRead of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593\n\nCPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\n addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181\n inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f164cf8f749\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749\nRDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003\nRBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 9593:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n poison_kmalloc_redzone mm/kasan/common.c:397 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414\n kmalloc_noprof include/linux/slab.h:957 [inline]\n kzalloc_noprof include/linux/slab.h:1094 [inline]\n ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120\n inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050\n addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160\n inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 6099:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584\n poison_slab_object mm/kasan/common.c:252 [inline]\n __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284\n kasan_slab_free include/linux/kasan.h:234 [inline]\n slab_free_hook mm/slub.c:2540 [inline]\n slab_free_freelist_hook mm/slub.c:2569 [inline]\n slab_free_bulk mm/slub.c:6696 [inline]\n kmem_cache_free_bulk mm/slub.c:7383 [inline]\n kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362\n kfree_bulk include/linux/slab.h:830 [inline]\n kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523\n kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline]\n kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801\n process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257\n process_scheduled_works kernel/workqu\n---truncated---(CVE-2026-23010)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: fix memory leak in update_eth_regs_async()\n\nWhen asynchronously writing to the device registers and if usb_submit_urb()\nfail, the code fail to release allocated to this point resources.(CVE-2026-23021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT 8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n __dump_stack (lib/dump_stack.c:95)\n dump_stack_lvl (lib/dump_stack.c:123)\n dump_stack (lib/dump_stack.c:130)\n spin_dump (kernel/locking/spinlock_debug.c:71)\n do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n __free_frozen_pages (mm/page_alloc.c:2973)\n ___free_pages (mm/page_alloc.c:5295)\n __free_pages (mm/page_alloc.c:5334)\n tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n ? rcu_core (kernel/rcu/tree.c:?)\n rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n rcu_core_si (kernel/rcu/tree.c:2879)\n handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n irq_exit_rcu (kernel/softirq.c:741)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n free_pcppages_bulk (mm/page_alloc.c:1494)\n drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n __drain_all_pages (mm/page_alloc.c:2731)\n drain_all_pages (mm/page_alloc.c:2747)\n kcompactd (mm/compaction.c:3115)\n kthread (kernel/kthread.c:465)\n ? __cfi_kcompactd (mm/compaction.c:3166)\n ? __cfi_kthread (kernel/kthread.c:412)\n ret_from_fork (arch/x86/kernel/process.c:164)\n ? __cfi_kthread (kernel/kthread.c:412)\n ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock. The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback. However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op. Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;). The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized. Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix kmemleak by releasing references to fault configfs items\n\nWhen CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk\ndriver sets up fault injection support by creating the timeout_inject,\nrequeue_inject, and init_hctx_fault_inject configfs items as children\nof the top-level nullbX configfs group.\n\nHowever, when the nullbX device is removed, the references taken to\nthese fault-config configfs items are not released. As a result,\nkmemleak reports a memory leak, for example:\n\nunreferenced object 0xc00000021ff25c40 (size 32):\n comm \u0026quot;mkdir\u0026quot;, pid 10665, jiffies 4322121578\n hex dump (first 32 bytes):\n 69 6e 69 74 5f 68 63 74 78 5f 66 61 75 6c 74 5f init_hctx_fault_\n 69 6e 6a 65 63 74 00 88 00 00 00 00 00 00 00 00 inject..........\n backtrace (crc 1a018c86):\n __kmalloc_node_track_caller_noprof+0x494/0xbd8\n kvasprintf+0x74/0xf4\n config_item_set_name+0xf0/0x104\n config_group_init_type_name+0x48/0xfc\n fault_config_init+0x48/0xf0\n 0xc0080000180559e4\n configfs_mkdir+0x304/0x814\n vfs_mkdir+0x49c/0x604\n do_mkdirat+0x314/0x3d0\n sys_mkdir+0xa0/0xd8\n system_call_exception+0x1b0/0x4f0\n system_call_vectored_common+0x15c/0x2ec\n\nFix this by explicitly releasing the references to the fault-config\nconfigfs items when dropping the reference to the top-level nullbX\nconfigfs group.(CVE-2026-23032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u0026gt;paused, not just clear it\n\nCurrently calc_target() clears t-\u0026gt;paused if the request shouldn\u0026apos;t be\npaused anymore, but doesn\u0026apos;t ever set t-\u0026gt;paused even though it\u0026apos;s able to\ndetermine when the request should be paused. Setting t-\u0026gt;paused is left\nto __submit_request() which is fine for regular requests but doesn\u0026apos;t\nwork for linger requests -- since __submit_request() doesn\u0026apos;t operate\non linger requests, there is nowhere for lreq-\u0026gt;t.paused to be set.\nOne consequence of this is that watches don\u0026apos;t get reestablished on\npaused -\u0026gt; unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state. On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u0026gt;watch_mutex held:\n\n rbd_register_watch\n __rbd_register_watch\n ceph_osdc_watch\n linger_reg_commit_wait\n\nIt\u0026apos;s waiting for lreq-\u0026gt;reg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused. There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u0026gt;watch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \u0026quot;rbd unmap\u0026quot; would inevitably\nhang in D state on an attempt to grab the mutex.(CVE-2026-23047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix a deadlock when returning a delegation during open()\n\nBen Coddington reports seeing a hang in the following stack trace:\n 0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415\n 1 [ffffd0b50e177548] schedule at ffffffff9ca05717\n 2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1\n 3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb\n 4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5\n 5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]\n 6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]\n 7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]\n 8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]\n 9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]\n 10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]\n 11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]\n 12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]\n 13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]\n 14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]\n 15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]\n 16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]\n 17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea\n 18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e\n 19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935\n\nThe issue is that the delegreturn is being asked to wait for a layout\nreturn that cannot complete because a state recovery was initiated. The\nstate recovery cannot complete until the open() finishes processing the\ndelegations it was given.\n\nThe solution is to propagate the existing flags that indicate a\nnon-blocking call to the function pnfs_roc(), so that it knows not to\nwait in this situation.(CVE-2026-23050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nA buffer overflow vulnerability exists in the QLogic Fibre Channel driver (qla2xxx) of the Linux kernel. In the functions `qla27xx_copy_fpin_pkt()` and `qla27xx_copy_multiple_pkt()`, the code uses the firmware-reported `frame_size` to calculate the copy length into `item-\u0026gt;iocb`. However, the `iocb` member is defined as a fixed-size 64-byte array within `struct purex_item`. If the reported `frame_size` exceeds 64 bytes, subsequent `memcpy` calls will overflow the boundary of the `iocb` member. This cross-member write is unsafe and can lead to memory corruption, potentially exploitable to compromise the confidentiality, integrity, and availability of the kernel.(CVE-2026-23059)\n\nA NULL pointer dereference vulnerability exists in the be2net network driver within the Linux kernel, specifically in the be_cmd_get_mac_from_list() function. According to the function\u0026apos;s contract, when the parameter pmac_id_valid is set to false, the driver may request a PMAC_ID from the network card\u0026apos;s firmware and store it at the provided address pmac_id. However, there is a location within the driver where both conditions pmac_id_valid == false and pmac_id == NULL are passed simultaneously. This results in an attempt to dereference a NULL pointer, potentially leading to a kernel crash or system instability.(CVE-2026-23084)\n\nA memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the \u0026apos;itt\u0026apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit \u0026apos;unsigned long\u0026apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix isolate sysfs check condition\n\nuacce supports the device isolation feature. If the driver\nimplements the isolate_err_threshold_read and\nisolate_err_threshold_write callback functions, uacce will create\nsysfs files now. Users can read and configure the isolation policy\nthrough sysfs. Currently, sysfs files are created as long as either\nisolate_err_threshold_read or isolate_err_threshold_write callback\nfunctions are present.\n\nHowever, accessing a non-existent callback function may cause the\nsystem to crash. Therefore, intercept the creation of sysfs if\nneither read nor write exists; create sysfs if either is supported,\nbut intercept unsupported operations at the call site.(CVE-2026-23094)\n\nA deadlock vulnerability exists in the Linux kernel due to incorrect lock acquisition ordering. This vulnerability affects the migration functionality for hugetlb (huge page) file folios. The specific scenario is: when two kernel tasks (Tasks) attempt to acquire the `folio_lock` and `i_mmap_rwsem` locks in opposite orders, a circular wait is formed, leading to a system deadlock. For example, Task A holds `folio_lock` and then tries to acquire the `i_mmap_rwsem` read lock, while Task B holds the `i_mmap_rwsem` write lock and then tries to acquire `folio_lock`. This lock ordering violates the rules defined in mm/rmap.c. This vulnerability can render parts of the affected system unavailable, impacting system availability.(CVE-2026-23097)\n\nIn the Linux kernel SCSI core layer, there is a fragile ordering logic between marking commands as completed or failed, designed to ensure the error handler only wakes when the last running command completes or times out. This logic contains race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. Specifically, there are two issues: 1. A memory ordering issue within the `scsi_dec_host_busy()` function. The write operation that clears the `SCMD_STATE_INFLIGHT` flag may be reordered with read counting operations in `scsi_host_busy()`. This can cause other CPUs to see inconsistent busy counts, preventing the correct triggering of the error handler wake-up. 2. A general ordering issue with the `scsi_eh_inc_host_failed()` function. It counts busy commands before incrementing the `host_failed` count, which can race with the processing of a final command in `scsi_dec_host_busy()`, resulting in neither side waking the error handler task.(CVE-2026-23110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec\n\nnvmet_tcp_build_pdu_iovec() could walk past cmd-\u0026gt;req.sg when a PDU\nlength or offset exceeds sg_cnt and then use bogus sg-\u0026gt;length/offset\nvalues, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining\nentries, and sg-\u0026gt;length/offset before building the bvec.(CVE-2026-23112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove\n\nOn APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and\nih2 interrupt ring buffers are not initialized. This is by design, as\nthese secondary IH rings are only available on discrete GPUs. See\nvega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when\nAMD_IS_APU is set.\n\nHowever, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to\nget the timestamp of the last interrupt entry. When retry faults are\nenabled on APUs (noretry=0), this function is called from the SVM page\nfault recovery path, resulting in a NULL pointer dereference when\namdgpu_ih_decode_iv_ts_helper() attempts to access ih-\u0026gt;ring[].\n\nThe crash manifests as:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000004\n RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]\n Call Trace:\n amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]\n svm_range_restore_pages+0xae5/0x11c0 [amdgpu]\n amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu]\n gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]\n amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu]\n amdgpu_ih_process+0x84/0x100 [amdgpu]\n\nThis issue was exposed by commit 1446226d32a4 (\u0026quot;drm/amdgpu: Remove GC HW\nIP 9.3.0 from noretry=1\u0026quot;) which changed the default for Renoir APU from\nnoretry=1 to noretry=0, enabling retry fault handling and thus\nexercising the buggy code path.\n\nFix this by adding a check for ih1.ring_size before attempting to use\nit. Also restore the soft_ih support from commit dd299441654f (\u0026quot;drm/amdgpu:\nRework retry fault removal\u0026quot;). This is needed if the hardware doesn\u0026apos;t\nsupport secondary HW IH rings.\n\nv2: additional updates (Alex)\n\n(cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)(CVE-2026-23163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()\n\nWhen the socket is closed while in TCP_LISTEN a callback is run to\nflush all outstanding packets, which in turns calls\nnvmet_tcp_listen_data_ready() with the sk_callback_lock held.\nSo we need to check if we are in TCP_LISTEN before attempting\nto get the sk_callback_lock() to avoid a deadlock.(CVE-2026-23179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: amd: fix memory leak in acp3x pdm dma ops(CVE-2026-23190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()\n\nIn iscsit_dec_session_usage_count(), the function calls complete() while\nholding the sess-\u0026gt;session_usage_lock. Similar to the connection usage count\nlogic, the waiter signaled by complete() (e.g., in the session release\npath) may wake up and free the iscsit_session structure immediately.\n\nThis creates a race condition where the current thread may attempt to\nexecute spin_unlock_bh() on a session structure that has already been\ndeallocated, resulting in a KASAN slab-use-after-free.\n\nTo resolve this, release the session_usage_lock before calling complete()\nto ensure all dereferences of the sess pointer are finished before the\nwaiter is allowed to proceed with deallocation.(CVE-2026-23193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: fix memory leak in smb2_open_file()\n\nReproducer:\n\n 1. server: directories are exported read-only\n 2. client: mount -t cifs //${server_ip}/export /mnt\n 3. client: dd if=/dev/zero of=/mnt/file bs=512 count=1000 oflag=direct\n 4. client: umount /mnt\n 5. client: sleep 1\n 6. client: modprobe -r cifs\n\nThe error message is as follows:\n\n =============================================================================\n BUG cifs_small_rq (Not tainted): Objects remaining on __kmem_cache_shutdown()\n -----------------------------------------------------------------------------\n\n Object 0x00000000d47521be @offset=14336\n ...\n WARNING: mm/slub.c:1251 at __kmem_cache_shutdown+0x34e/0x440, CPU#0: modprobe/1577\n ...\n Call Trace:\n \u0026lt;TASK\u0026gt;\n kmem_cache_destroy+0x94/0x190\n cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n cleanup_module+0x4e/0x540 [cifs]\n __se_sys_delete_module+0x278/0x400\n __x64_sys_delete_module+0x5f/0x70\n x64_sys_call+0x2299/0x2ff0\n do_syscall_64+0x89/0x350\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n ...\n kmem_cache_destroy cifs_small_rq: Slab cache still has objects when called from cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n WARNING: mm/slab_common.c:532 at kmem_cache_destroy+0x16b/0x190, CPU#0: modprobe/1577(CVE-2026-23205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)\n\nIn the Linux kernel, the ksmbd component contains an infinite loop vulnerability. The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() sets work-\u0026gt;next_smb2_rcv_hdr_off to zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header\u0026apos;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with \u0026quot;bad smb2 signature\u0026quot; messages and high CPU usage.(CVE-2026-23220)\n\nIn the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection() On kthread_run() failure in ksmbd_tcp_new_connection(), the transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter. Replace free_transport() with ksmbd_tcp_disconnect(). The Linux kernel CVE team has assigned CVE-2026-23228 to this issue.(CVE-2026-23228)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:37.727225213Z","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-1567","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\nudp: Deal with race between UDP socket address change and rehash\n\nIf a UDP socket changes its local address while it\u0026apos;s receiving\ndatagrams, as a result of connect(), there is a period during which\na lookup operation might fail to find it, after the address is changed\nbut before the secondary hash (port and address) and the four-tuple\nhash (local and remote ports and addresses) are updated.\n\nSecondary hash chains were introduced by commit 30fff9231fad (\u0026quot;udp:\nbind() optimisation\u0026quot;) and, as a result, a rehash operation became\nneeded to make a bound socket reachable again after a connect().\n\nThis operation was introduced by commit 719f835853a9 (\u0026quot;udp: add\nrehash on connect()\u0026quot;) which isn\u0026apos;t however a complete fix: the\nsocket will be found once the rehashing completes, but not while\nit\u0026apos;s pending.\n\nThis is noticeable with a socat(1) server in UDP4-LISTEN mode, and a\nclient sending datagrams to it. After the server receives the first\ndatagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to\nthe address of the sender, in order to set up a directed flow.\n\nNow, if the client, running on a different CPU thread, happens to\nsend a (subsequent) datagram while the server\u0026apos;s socket changes its\naddress, but is not rehashed yet, this will result in a failed\nlookup and a port unreachable error delivered to the client, as\napparent from the following reproducer:\n\n LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))\n dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in\n\n while :; do\n \ttaskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n \tsleep 0.1 || sleep 1\n \ttaskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null\n \twait\n done\n\nwhere the client will eventually get ECONNREFUSED on a write()\n(typically the second or third one of a given iteration):\n\n 2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused\n\nThis issue was first observed as a seldom failure in Podman\u0026apos;s tests\nchecking UDP functionality while using pasta(1) to connect the\ncontainer\u0026apos;s network namespace, which leads us to a reproducer with\nthe lookup error resulting in an ICMP packet on a tap device:\n\n LOCAL_ADDR=\u0026quot;$(ip -j -4 addr show|jq -rM \u0026apos;.[] | .addr_info[0] | select(.scope == \u0026quot;global\u0026quot;).local\u0026apos;)\u0026quot;\n\n while :; do\n \t./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n \tsleep 0.2 || sleep 1\n \tsocat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null\n \twait\n \tcmp tmp.in tmp.out\n done\n\nOnce this fails:\n\n tmp.in tmp.out differ: char 8193, line 29\n\nwe can finally have a look at what\u0026apos;s going on:\n\n $ tshark -r pasta.pcap\n 1 0.000000 :: ? ff02::16 ICMPv6 110 Multicast Listener Report Message v2\n 2 0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 3 0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 4 0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 5 0.168827 c6:47:05:8d:dc:04 ? Broadcast ARP 42 Who has 88.198.0.161? Tell 88.198.0.164\n 6 0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55\n 7 0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 8 0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable)\n 9 0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 10 0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 11 0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096\n 12 0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0\n\nOn the third datagram received, the network namespace of the container\ninitiates an ARP lookup to deliver the ICMP message.\n\nIn another variant of this reproducer, starting the client with:\n\n strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru\n---truncated---(CVE-2024-57974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()\n\nIf track_pfn_copy() fails, we already added the dst VMA to the maple\ntree. As fork() fails, we\u0026apos;ll cleanup the maple tree, and stumble over\nthe dst VMA for which we neither performed any reservation nor copied\nany page tables.\n\nConsequently untrack_pfn() will see VM_PAT and try obtaining the\nPAT information from the page table -- which fails because the page\ntable was not copied.\n\nThe easiest fix would be to simply clear the VM_PAT flag of the dst VMA\nif track_pfn_copy() fails. However, the whole thing is about \u0026quot;simply\u0026quot;\nclearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy()\nand performed a reservation, but copying the page tables fails, we\u0026apos;ll\nsimply clear the VM_PAT flag, not properly undoing the reservation ...\nwhich is also wrong.\n\nSo let\u0026apos;s fix it properly: set the VM_PAT flag only if the reservation\nsucceeded (leaving it clear initially), and undo the reservation if\nanything goes wrong while copying the page tables: clearing the VM_PAT\nflag after undoing the reservation.\n\nNote that any copied page table entries will get zapped when the VMA will\nget removed later, after copy_page_range() succeeded; as VM_PAT is not set\nthen, we won\u0026apos;t try cleaning VM_PAT up once more and untrack_pfn() will be\nhappy. Note that leaving these page tables in place without a reservation\nis not a problem, as we are aborting fork(); this process will never run.\n\nA reproducer can trigger this usually at the first try:\n\n https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c\n\n WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110\n Modules linked in: ...\n CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\n RIP: 0010:get_pat_info+0xf6/0x110\n ...\n Call Trace:\n \u0026lt;TASK\u0026gt;\n ...\n untrack_pfn+0x52/0x110\n unmap_single_vma+0xa6/0xe0\n unmap_vmas+0x105/0x1f0\n exit_mmap+0xf6/0x460\n __mmput+0x4b/0x120\n copy_process+0x1bf6/0x2aa0\n kernel_clone+0xab/0x440\n __do_sys_clone+0x66/0x90\n do_syscall_64+0x95/0x180\n\nLikely this case was missed in:\n\n d155df53f310 (\u0026quot;x86/mm/pat: clear VM_PAT if copy_p4d_range failed\u0026quot;)\n\n... and instead of undoing the reservation we simply cleared the VM_PAT flag.\n\nKeep the documentation of these functions in include/linux/pgtable.h,\none place is more than sufficient -- we should clean that up for the other\nfunctions like track_pfn_remap/untrack_pfn separately.(CVE-2025-22090)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: make fallback action and fallback decision atomic\n\nSyzkaller reported the following splat:\n\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline]\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n Modules linked in:\n CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary)\n Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline]\n RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00\n RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246\n RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45\n RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001\n RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000\n R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000\n FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432\n tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975\n tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166\n tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925\n tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363\n ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205\n ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233\n NF_HOOK include/linux/netfilter.h:317 [inline]\n NF_HOOK include/linux/netfilter.h:311 [inline]\n ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254\n dst_input include/net/dst.h:469 [inline]\n ip_rcv_finish net/ipv4/ip_input.c:447 [inline]\n NF_HOOK include/linux/netfilter.h:317 [inline]\n NF_HOOK include/linux/netfilter.h:311 [inline]\n ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567\n __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975\n __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088\n process_backlog+0x301/0x1360 net/core/dev.c:6440\n __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453\n napi_poll net/core/dev.c:7517 [inline]\n net_rx_action+0xb44/0x1010 net/core/dev.c:7644\n handle_softirqs+0x1d0/0x770 kernel/softirq.c:579\n do_softirq+0x3f/0x90 kernel/softirq.c:480\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407\n local_bh_enable include/linux/bottom_half.h:33 [inline]\n inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524\n mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985\n mptcp_check_listen_stop net/mptcp/mib.h:118 [inline]\n __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000\n mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066\n inet_release+0xed/0x200 net/ipv4/af_inet.c:435\n inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487\n __sock_release+0xb3/0x270 net/socket.c:649\n sock_close+0x1c/0x30 net/socket.c:1439\n __fput+0x402/0xb70 fs/file_table.c:465\n task_work_run+0x150/0x240 kernel/task_work.c:227\n resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n exit_to_user_mode_loop+0xd4\n---truncated---(CVE-2025-38491)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic\n\nThe decompress_io_ctx may be released asynchronously after\nI/O completion. If this file is deleted immediately after read,\nand the kworker of processing post_read_wq has not been executed yet\ndue to high workloads, It is possible that the inode(f2fs_inode_info)\nis evicted and freed before it is used f2fs_free_dic.\n\n The UAF case as below:\n Thread A Thread B\n - f2fs_decompress_end_io\n - f2fs_put_dic\n - queue_work\n add free_dic work to post_read_wq\n - do_unlink\n - iput\n - evict\n - call_rcu\n This file is deleted after read.\n\n Thread C kworker to process post_read_wq\n - rcu_do_batch\n - f2fs_free_inode\n - kmem_cache_free\n inode is freed by rcu\n - process_scheduled_works\n - f2fs_late_free_dic\n - f2fs_free_dic\n - f2fs_release_decomp_mem\n read (dic-\u0026gt;inode)-\u0026gt;i_compress_algorithm\n\nThis patch store compress_algorithm and sbi in dic to avoid inode UAF.\n\nIn addition, the previous solution is deprecated in [1] may cause system hang.\n[1] https://lore.kernel.org/all/(CVE-2025-38627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n[ceph] parse_longname(): strrchr() expects NUL-terminated string\n\n... and parse_longname() is not guaranteed that. That\u0026apos;s the reason\nwhy it uses kmemdup_nul() to build the argument for kstrtou64();\nthe problem is, kstrtou64() is not the only thing that need it.\n\nJust get a NUL-terminated copy of the entire thing and be done\nwith that...(CVE-2025-38660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: remove refcounting in expectation dumpers\n\nSame pattern as previous patch: do not keep the expectation object\nalive via refcount, only store a cookie value and then use that\nas the skip hint for dump resumption.\n\nAFAICS this has the same issue as the one resolved in the conntrack\ndumper, when we do\n if (!refcount_inc_not_zero(\u0026amp;exp-\u0026gt;use))\n\nto increment the refcount, there is a chance that exp == last, which\ncauses a double-increment of the refcount and subsequent memory leak.(CVE-2025-39764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: avoid accessing metadata when pointer is invalid in object_err()\n\nobject_err() reports details of an object for further debugging, such as\nthe freelist pointer, redzone, etc. However, if the pointer is invalid,\nattempting to access object metadata can lead to a crash since it does\nnot point to a valid object.\n\nOne known path to the crash is when alloc_consistency_checks()\ndetermines the pointer to the allocated object is invalid because of a\nfreelist corruption, and calls object_err() to report it. The debug code\nshould report and handle the corruption gracefully and not crash in the\nprocess.\n\nIn case the pointer is NULL or check_valid_pointer() returns false for\nthe pointer, only print the pointer value and skip accessing metadata.(CVE-2025-39902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix Rx page leak on multi-buffer frames\n\nThe ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each\nbuffer in the current frame. This function was introduced as part of\nhandling multi-buffer XDP support in the ice driver.\n\nIt works by iterating over the buffers from first_desc up to 1 plus the\ntotal number of fragments in the frame, cached from before the XDP program\nwas executed.\n\nIf the hardware posts a descriptor with a size of 0, the logic used in\nice_put_rx_mbuf() breaks. Such descriptors get skipped and don\u0026apos;t get added\nas fragments in ice_add_xdp_frag. Since the buffer isn\u0026apos;t counted as a\nfragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don\u0026apos;t\ncall ice_put_rx_buf().\n\nBecause we don\u0026apos;t call ice_put_rx_buf(), we don\u0026apos;t attempt to re-use the\npage or free it. This leaves a stale page in the ring, as we don\u0026apos;t\nincrement next_to_alloc.\n\nThe ice_reuse_rx_page() assumes that the next_to_alloc has been incremented\nproperly, and that it always points to a buffer with a NULL page. Since\nthis function doesn\u0026apos;t check, it will happily recycle a page over the top\nof the next_to_alloc buffer, losing track of the old page.\n\nNote that this leak only occurs for multi-buffer frames. The\nice_put_rx_mbuf() function always handles at least one buffer, so a\nsingle-buffer frame will always get handled correctly. It is not clear\nprecisely why the hardware hands us descriptors with a size of 0 sometimes,\nbut it happens somewhat regularly with \u0026quot;jumbo frames\u0026quot; used by 9K MTU.\n\nTo fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on\nall buffers between first_desc and next_to_clean. Borrow the logic of a\nsimilar function in i40e used for this same purpose. Use the same logic\nalso in ice_get_pgcnts().\n\nInstead of iterating over just the number of fragments, use a loop which\niterates until the current index reaches to the next_to_clean element just\npast the current frame. Unlike i40e, the ice_put_rx_mbuf() function does\ncall ice_put_rx_buf() on the last buffer of the frame indicating the end of\npacket.\n\nFor non-linear (multi-buffer) frames, we need to take care when adjusting\nthe pagecnt_bias. An XDP program might release fragments from the tail of\nthe frame, in which case that fragment page is already released. Only\nupdate the pagecnt_bias for the first descriptor and fragments still\nremaining post-XDP program. Take care to only access the shared info for\nfragmented buffers, as this avoids a significant cache miss.\n\nThe xdp_xmit value only needs to be updated if an XDP program is run, and\nonly once per packet. Drop the xdp_xmit pointer argument from\nice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function\ndirectly. This avoids needing to pass the argument and avoids an extra\nbit-wise OR for each buffer in the frame.\n\nMove the increment of the ntc local variable to ensure its updated *before*\nall calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic\nrequires the index of the element just after the current frame.\n\nNow that we use an index pointer in the ring to identify the packet, we no\nlonger need to track or cache the number of fragments in the rx_ring.(CVE-2025-39948)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: Set fb_display[i]-\u0026gt;mode to NULL when the mode is released\n\nRecently, we discovered the following issue through syzkaller:\n\nBUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0\nRead of size 4 at addr ff11000001b3c69c by task syz.xxx\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xab/0xe0\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb9/0x280\n kasan_report+0xb8/0xf0\n fb_mode_is_equal+0x285/0x2f0\n fbcon_mode_deleted+0x129/0x180\n fb_set_var+0xe7f/0x11d0\n do_fb_ioctl+0x6a0/0x750\n fb_ioctl+0xe0/0x140\n __x64_sys_ioctl+0x193/0x210\n do_syscall_64+0x5f/0x9c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nBased on experimentation and analysis, during framebuffer unregistration,\nonly the memory of fb_info-\u0026gt;modelist is freed, without setting the\ncorresponding fb_display[i]-\u0026gt;mode to NULL for the freed modes. This leads\nto UAF issues during subsequent accesses. Here\u0026apos;s an example of reproduction\nsteps:\n1. With /dev/fb0 already registered in the system, load a kernel module\n to register a new device /dev/fb1;\n2. Set fb1\u0026apos;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);\n3. Switch console from fb to VGA (to allow normal rmmod of the ko);\n4. Unload the kernel module, at this point fb1\u0026apos;s modelist is freed, leaving\n a wild pointer in fb_display[];\n5. Trigger the bug via system calls through fb0 attempting to delete a mode\n from fb0.\n\nAdd a check in do_unregister_framebuffer(): if the mode to be freed exists\nin fb_display[], set the corresponding mode pointer to NULL.(CVE-2025-40323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb\n\nThe Mesa issue referenced below pointed out a possible deadlock:\n\n[ 1231.611031] Possible interrupt unsafe locking scenario:\n\n[ 1231.611033] CPU0 CPU1\n[ 1231.611034] ---- ----\n[ 1231.611035] lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611038] local_irq_disable();\n[ 1231.611039] lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611041] lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611044] \u0026lt;Interrupt\u0026gt;\n[ 1231.611045] lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611047]\n *** DEADLOCK ***\n\nIn this example, CPU0 would be any function accessing job-\u0026gt;dependencies\nthrough the xa_* functions that don\u0026apos;t disable interrupts (eg:\ndrm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()).\n\nCPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling\ncallback so in an interrupt context. It will deadlock when trying to\ngrab the xa_lock which is already held by CPU0.\n\nReplacing all xa_* usage by their xa_*_irq counterparts would fix\nthis issue, but Christian pointed out another issue: dma_fence_signal\ntakes fence.lock and so does dma_fence_add_callback.\n\n dma_fence_signal() // locks f1.lock\n -\u0026gt; drm_sched_entity_kill_jobs_cb()\n -\u0026gt; foreach dependencies\n -\u0026gt; dma_fence_add_callback() // locks f2.lock\n\nThis will deadlock if f1 and f2 share the same spinlock.\n\nTo fix both issues, the code iterating on dependencies and re-arming them\nis moved out to drm_sched_entity_kill_jobs_work().\n\n[phasta: commit message nits](CVE-2025-40329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n Internal error: Oops: 000000009600004f [#1] SMP\n CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n Hardware name: LS1028A RDB Board (DT)\n pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : xfrm_input+0xde8/0x1318\n lr : xfrm_input+0x61c/0x1318\n sp : ffff800080003b20\n Call trace:\n xfrm_input+0xde8/0x1318\n xfrm6_rcv+0x38/0x44\n xfrm6_esp_rcv+0x48/0xa8\n ip6_protocol_deliver_rcu+0x94/0x4b0\n ip6_input_finish+0x44/0x70\n ip6_input+0x44/0xc0\n ipv6_rcv+0x6c/0x114\n __netif_receive_skb_one_core+0x5c/0x8c\n __netif_receive_skb+0x18/0x60\n process_backlog+0x78/0x17c\n __napi_poll+0x38/0x180\n net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imon: make send_packet() more robust\n\nsyzbot is reporting that imon has three problems which result in\nhung tasks due to forever holding device lock [1].\n\nFirst problem is that when usb_rx_callback_intf0() once got -EPROTO error\nafter ictx-\u0026gt;dev_present_intf0 became true, usb_rx_callback_intf0()\nresubmits urb after printk(), and resubmitted urb causes\nusb_rx_callback_intf0() to again get -EPROTO error. This results in\nprintk() flooding (RCU stalls).\n\nAlan Stern commented [2] that\n\n In theory it\u0026apos;s okay to resubmit _if_ the driver has a robust\n error-recovery scheme (such as giving up after some fixed limit on the\n number of errors or after some fixed time has elapsed, perhaps with a\n time delay to prevent a flood of errors). Most drivers don\u0026apos;t bother to\n do this; they simply give up right away. This makes them more\n vulnerable to short-term noise interference during USB transfers, but in\n reality such interference is quite rare. There\u0026apos;s nothing really wrong\n with giving up right away.\n\nbut imon has a poor error-recovery scheme which just retries forever;\nthis behavior should be fixed.\n\nSince I\u0026apos;m not sure whether it is safe for imon users to give up upon any\nerror code, this patch takes care of only union of error codes chosen from\nmodules in drivers/media/rc/ directory which handle -EPROTO error (i.e.\nir_toy, mceusb and igorplugusb).\n\nSecond problem is that when usb_rx_callback_intf0() once got -EPROTO error\nbefore ictx-\u0026gt;dev_present_intf0 becomes true, usb_rx_callback_intf0() always\nresubmits urb due to commit 8791d63af0cf (\u0026quot;[media] imon: don\u0026apos;t wedge\nhardware after early callbacks\u0026quot;). Move the ictx-\u0026gt;dev_present_intf0 test\nintroduced by commit 6f6b90c9231a (\u0026quot;[media] imon: don\u0026apos;t parse scancodes\nuntil intf configured\u0026quot;) to immediately before imon_incoming_packet(), or\nthe first problem explained above happens without printk() flooding (i.e.\nhung task).\n\nThird problem is that when usb_rx_callback_intf0() is not called for some\nreason (e.g. flaky hardware; the reproducer for this problem sometimes\nprevents usb_rx_callback_intf0() from being called),\nwait_for_completion_interruptible() in send_packet() never returns (i.e.\nhung task). As a workaround for such situation, change send_packet() to\nwait for completion with timeout of 10 seconds.(CVE-2025-68194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: arm: scmi: Fix genpd leak on provider registration failure\n\nIf of_genpd_add_provider_onecell() fails during probe, the previously\ncreated generic power domains are not removed, leading to a memory leak\nand potential kernel crash later in genpd_debug_add().\n\nAdd proper error handling to unwind the initialized domains before\nreturning from probe to ensure all resources are correctly released on\nfailure.\n\nExample crash trace observed without this fix:\n\n | Unable to handle kernel paging request at virtual address fffffffffffffc70\n | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT\n | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform\n | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n | pc : genpd_debug_add+0x2c/0x160\n | lr : genpd_debug_init+0x74/0x98\n | Call trace:\n | genpd_debug_add+0x2c/0x160 (P)\n | genpd_debug_init+0x74/0x98\n | do_one_initcall+0xd0/0x2d8\n | do_initcall_level+0xa0/0x140\n | do_initcalls+0x60/0xa8\n | do_basic_setup+0x28/0x40\n | kernel_init_freeable+0xe8/0x170\n | kernel_init+0x2c/0x140\n | ret_from_fork+0x10/0x20(CVE-2025-68204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0026apos;s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs.(CVE-2025-68209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksm: use range-walk function to jump over holes in scan_get_next_rmap_item\n\nCurrently, scan_get_next_rmap_item() walks every page address in a VMA to\nlocate mergeable pages. This becomes highly inefficient when scanning\nlarge virtual memory areas that contain mostly unmapped regions, causing\nksmd to use large amount of cpu without deduplicating much pages.\n\nThis patch replaces the per-address lookup with a range walk using\nwalk_page_range(). The range walker allows KSM to skip over entire\nunmapped holes in a VMA, avoiding unnecessary lookups. This problem was\npreviously discussed in [1].\n\nConsider the following test program which creates a 32 TiB mapping in the\nvirtual address space but only populates a single page:\n\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\n\n/* 32 TiB */\nconst size_t size = 32ul * 1024 * 1024 * 1024 * 1024;\n\nint main() {\n char *area = mmap(NULL, size, PROT_READ | PROT_WRITE,\n MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);\n\n if (area == MAP_FAILED) {\n perror(\u0026quot;mmap() failed\\n\u0026quot;);\n return -1;\n }\n\n /* Populate a single page such that we get an anon_vma. */\n *area = 0;\n\n /* Enable KSM. */\n madvise(area, size, MADV_MERGEABLE);\n pause();\n return 0;\n}\n\n$ ./ksm-sparse \u0026amp;\n$ echo 1 \u0026gt; /sys/kernel/mm/ksm/run \n\nWithout this patch ksmd uses 100% of the cpu for a long time (more then 1\nhour in my test machine) scanning all the 32 TiB virtual address space\nthat contain only one mapped page. This makes ksmd essentially deadlocked\nnot able to deduplicate anything of value. With this patch ksmd walks\nonly the one mapped page and skips the rest of the 32 TiB virtual address\nspace, making the scan fast using little cpu.(CVE-2025-68211)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempool: fix poisoning order\u0026gt;0 pages with HIGHMEM\n\nThe kernel test has reported:\n\n BUG: unable to handle page fault for address: fffba000\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n *pde = 03171067 *pte = 00000000\n Oops: Oops: 0002 [#1]\n CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G T 6.18.0-rc2-00031-gec7f31b2a2d3 #1 NONE a1d066dfe789f54bc7645c7989957d2bdee593ca\n Tainted: [T]=RANDSTRUCT\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n EIP: memset (arch/x86/include/asm/string_32.h:168 arch/x86/lib/memcpy_32.c:17)\n Code: a5 8b 4d f4 83 e1 03 74 02 f3 a4 83 c4 04 5e 5f 5d 2e e9 73 41 01 00 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c6 89 d0 89 f7 \u0026lt;f3\u0026gt; aa 89 f0 5e 5f 5d 2e e9 53 41 01 00 cc cc cc 55 89 e5 53 57 56\n EAX: 0000006b EBX: 00000015 ECX: 001fefff EDX: 0000006b\n ESI: fffb9000 EDI: fffba000 EBP: c611fbf0 ESP: c611fbe8\n DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010287\n CR0: 80050033 CR2: fffba000 CR3: 0316e000 CR4: 00040690\n Call Trace:\n poison_element (mm/mempool.c:83 mm/mempool.c:102)\n mempool_init_node (mm/mempool.c:142 mm/mempool.c:226)\n mempool_init_noprof (mm/mempool.c:250 (discriminator 1))\n ? mempool_alloc_pages (mm/mempool.c:640)\n bio_integrity_initfn (block/bio-integrity.c:483 (discriminator 8))\n ? mempool_alloc_pages (mm/mempool.c:640)\n do_one_initcall (init/main.c:1283)\n\nChristoph found out this is due to the poisoning code not dealing\nproperly with CONFIG_HIGHMEM because only the first page is mapped but\nthen the whole potentially high-order page is accessed.\n\nWe could give up on HIGHMEM here, but it\u0026apos;s straightforward to fix this\nwith a loop that\u0026apos;s mapping, poisoning or checking and unmapping\nindividual pages.(CVE-2025-68231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtdchar: fix integer overflow in read/write ioctls\n\nThe \u0026quot;req.start\u0026quot; and \u0026quot;req.len\u0026quot; variables are u64 values that come from the\nuser at the start of the function. We mask away the high 32 bits of\n\u0026quot;req.len\u0026quot; so that\u0026apos;s capped at U32_MAX but the \u0026quot;req.start\u0026quot; variable can go\nup to U64_MAX which means that the addition can still integer overflow.\n\nUse check_add_overflow() to fix this bug.(CVE-2025-68237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u0026gt;work\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\u0026quot;usb: gadget: core: flush gadget workqueue after\ndevice removal\u0026quot;) attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget\u0026apos;s memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a \u0026apos;teardown\u0026apos;\nflag and a \u0026apos;state_lock\u0026apos; spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.(CVE-2025-68282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: fix NULL pointer deference when splitting folio\n\nCommit c010d47f107f (\u0026quot;mm: thp: split huge page to any lower order pages\u0026quot;)\nintroduced an early check on the folio\u0026apos;s order via mapping-\u0026gt;flags before\nproceeding with the split work.\n\nThis check introduced a bug: for shmem folios in the swap cache and\ntruncated folios, the mapping pointer can be NULL. Accessing\nmapping-\u0026gt;flags in this state leads directly to a NULL pointer dereference.\n\nThis commit fixes the issue by moving the check for mapping != NULL before\nany attempt to access mapping-\u0026gt;flags.(CVE-2025-68293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU/AMD: Add RDSEED fix for Zen5\n\nThere\u0026apos;s an issue with RDSEED\u0026apos;s 16-bit and 32-bit register output\nvariants on Zen5 which return a random value of 0 \u0026quot;at a rate inconsistent\nwith randomness while incorrectly signaling success (CF=1)\u0026quot;. Search the\nweb for AMD-SB-7055 for more detail.\n\nAdd a fix glue which checks microcode revisions.\n\n [ bp: Add microcode revisions checking, rewrite. ](CVE-2025-68313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninet: frags: flush pending skbs in fqdir_pre_exit()\n\nWe have been seeing occasional deadlocks on pernet_ops_rwsem since\nSeptember in NIPA. The stuck task was usually modprobe (often loading\na driver like ipvlan), trying to take the lock as a Writer.\nlockdep does not track readers for rwsems so the read wasn\u0026apos;t obvious\nfrom the reports.\n\nOn closer inspection the Reader holding the lock was conntrack looping\nforever in nf_conntrack_cleanup_net_list(). Based on past experience\nwith occasional NIPA crashes I looked thru the tests which run before\nthe crash and noticed that the crash follows ip_defrag.sh. An immediate\nred flag. Scouring thru (de)fragmentation queues reveals skbs sitting\naround, holding conntrack references.\n\nThe problem is that since conntrack depends on nf_defrag_ipv6,\nnf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its\nnetns exit hooks run _after_ conntrack\u0026apos;s netns exit hook.\n\nFlush all fragment queue SKBs during fqdir_pre_exit() to release\nconntrack references before conntrack cleanup runs. Also flush\nthe queues in timer expiry handlers when they discover fqdir-\u0026gt;dead\nis set, in case packet sneaks in while we\u0026apos;re running the pre_exit\nflush.\n\nThe commit under Fixes is not exactly the culprit, but I think\npreviously the timer firing would eventually unblock the spinning\nconntrack.(CVE-2025-68768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix middle attribute validation in push_nsh() action\n\nThe push_nsh() action structure looks like this:\n\n OVS_ACTION_ATTR_PUSH_NSH(OVS_KEY_ATTR_NSH(OVS_NSH_KEY_ATTR_BASE,...))\n\nThe outermost OVS_ACTION_ATTR_PUSH_NSH attribute is OK\u0026apos;ed by the\nnla_for_each_nested() inside __ovs_nla_copy_actions(). The innermost\nOVS_NSH_KEY_ATTR_BASE/MD1/MD2 are OK\u0026apos;ed by the nla_for_each_nested()\ninside nsh_key_put_from_nlattr(). But nothing checks if the attribute\nin the middle is OK. We don\u0026apos;t even check that this attribute is the\nOVS_KEY_ATTR_NSH. We just do a double unwrap with a pair of nla_data()\ncalls - first time directly while calling validate_push_nsh() and the\nsecond time as part of the nla_for_each_nested() macro, which isn\u0026apos;t\nsafe, potentially causing invalid memory access if the size of this\nattribute is incorrect. The failure may not be noticed during\nvalidation due to larger netlink buffer, but cause trouble later during\naction execution where the buffer is allocated exactly to the size:\n\n BUG: KASAN: slab-out-of-bounds in nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n Read of size 184 at addr ffff88816459a634 by task a.out/22624\n\n CPU: 8 UID: 0 PID: 22624 6.18.0-rc7+ #115 PREEMPT(voluntary)\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x51/0x70\n print_address_description.constprop.0+0x2c/0x390\n kasan_report+0xdd/0x110\n kasan_check_range+0x35/0x1b0\n __asan_memcpy+0x20/0x60\n nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n push_nsh+0x82/0x120 [openvswitch]\n do_execute_actions+0x1405/0x2840 [openvswitch]\n ovs_execute_actions+0xd5/0x3b0 [openvswitch]\n ovs_packet_cmd_execute+0x949/0xdb0 [openvswitch]\n genl_family_rcv_msg_doit+0x1d6/0x2b0\n genl_family_rcv_msg+0x336/0x580\n genl_rcv_msg+0x9f/0x130\n netlink_rcv_skb+0x11f/0x370\n genl_rcv+0x24/0x40\n netlink_unicast+0x73e/0xaa0\n netlink_sendmsg+0x744/0xbf0\n __sys_sendto+0x3d6/0x450\n do_syscall_64+0x79/0x2c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n \u0026lt;/TASK\u0026gt;\n\nLet\u0026apos;s add some checks that the attribute is properly sized and it\u0026apos;s\nthe only one attribute inside the action. Technically, there is no\nreal reason for OVS_KEY_ATTR_NSH to be there, as we know that we\u0026apos;re\npushing an NSH header already, it just creates extra nesting, but\nthat\u0026apos;s how uAPI works today. So, keeping as it is.(CVE-2025-68785)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: alps - fix use-after-free bugs caused by dev3_register_work\n\nThe dev3_register_work delayed work item is initialized within\nalps_reconnect() and scheduled upon receipt of the first bare\nPS/2 packet from an external PS/2 device connected to the ALPS\ntouchpad. During device detachment, the original implementation\ncalls flush_workqueue() in psmouse_disconnect() to ensure\ncompletion of dev3_register_work. However, the flush_workqueue()\nin psmouse_disconnect() only blocks and waits for work items that\nwere already queued to the workqueue prior to its invocation. Any\nwork items submitted after flush_workqueue() is called are not\nincluded in the set of tasks that the flush operation awaits.\nThis means that after flush_workqueue() has finished executing,\nthe dev3_register_work could still be scheduled. Although the\npsmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(),\nthe scheduling of dev3_register_work remains unaffected.\n\nThe race condition can occur as follows:\n\nCPU 0 (cleanup path) | CPU 1 (delayed work)\npsmouse_disconnect() |\n psmouse_set_state() |\n flush_workqueue() | alps_report_bare_ps2_packet()\n alps_disconnect() | psmouse_queue_work()\n kfree(priv); // FREE | alps_register_bare_ps2_mouse()\n | priv = container_of(work...); // USE\n | priv-\u0026gt;dev3 // USE\n\nAdd disable_delayed_work_sync() in alps_disconnect() to ensure\nthat dev3_register_work is properly canceled and prevented from\nexecuting after the alps_data structure has been deallocated.\n\nThis bug is identified by static analysis.(CVE-2025-68822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential deadlock\n\nAs Jiaming Zhang and syzbot reported, there is potential deadlock in\nf2fs as below:\n\nChain exists of:\n \u0026amp;sbi-\u0026gt;cp_rwsem --\u0026gt; fs_reclaim --\u0026gt; sb_internal#2\n\n Possible unsafe locking scenario:\n\n CPU0 CPU1\n ---- ----\n rlock(sb_internal#2);\n lock(fs_reclaim);\n lock(sb_internal#2);\n rlock(\u0026amp;sbi-\u0026gt;cp_rwsem);\n\n *** DEADLOCK ***\n\n3 locks held by kswapd0/73:\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197\n #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890\n\nstack backtrace:\nCPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043\n check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175\n check_prev_add kernel/locking/lockdep.c:3165 [inline]\n check_prevs_add kernel/locking/lockdep.c:3284 [inline]\n validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908\n __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237\n lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868\n down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537\n f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]\n f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]\n f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791\n f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867\n f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925\n f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897\n evict+0x504/0x9c0 fs/inode.c:810\n f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853\n evict+0x504/0x9c0 fs/inode.c:810\n dispose_list fs/inode.c:852 [inline]\n prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000\n super_cache_scan+0x39b/0x4b0 fs/super.c:224\n do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437\n shrink_slab_memcg mm/shrinker.c:550 [inline]\n shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628\n shrink_one+0x28a/0x7c0 mm/vmscan.c:4955\n shrink_many mm/vmscan.c:5016 [inline]\n lru_gen_shrink_node mm/vmscan.c:5094 [inline]\n shrink_node+0x315d/0x3780 mm/vmscan.c:6081\n kswapd_shrink_node mm/vmscan.c:6941 [inline]\n balance_pgdat mm/vmscan.c:7124 [inline]\n kswapd+0x147c/0x2800 mm/vmscan.c:7389\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is deadlock among four locks as below:\n\nkswapd\n- fs_reclaim\t\t\t\t--- Lock A\n - shrink_one\n - evict\n - f2fs_evict_inode\n - sb_start_intwrite\t\t\t--- Lock B\n\n- iput\n - evict\n - f2fs_evict_inode\n - sb_start_intwrite\t\t\t--- Lock B\n - f2fs_truncate\n - f2fs_truncate_blocks\n - f2fs_do_truncate_blocks\n - f2fs_lock_op\t\t\t--- Lock C\n\nioctl\n- f2fs_ioc_commit_atomic_write\n - f2fs_lock_op\t\t\t\t--- Lock C\n - __f2fs_commit_atomic_write\n - __replace_atomic_write_block\n - f2fs_get_dnode_of_data\n - __get_node_folio\n - f2fs_check_nid_range\n - f2fs_handle_error\n - f2fs_record_errors\n - f2fs_down_write\t\t--- Lock D\n\nopen\n- do_open\n - do_truncate\n - security_inode_need_killpriv\n - f2fs_getxattr\n - lookup_all_xattrs\n - f2fs_handle_error\n - f2fs_record_errors\n - f2fs_down_write\t\t--- Lock D\n - f2fs_commit_super\n - read_mapping_folio\n - filemap_alloc_folio_noprof\n - prepare_alloc_pages\n - fs_reclaim_acquire\t--- Lock A\n\nIn order to a\n---truncated---(CVE-2025-71065)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: Avoid NULL pointer deref for evicted BOs\n\nIt is possible for a BO to exist that is not currently associated with a\nresource, e.g. because it has been evicted.\n\nWhen devcoredump tries to read the contents of all BOs for dumping, we need\nto expect this as well -- in this case, ENODATA is recorded instead of the\nbuffer contents.(CVE-2025-71083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n GID entry ref leak for dev syz1 index 2 ref=573\n WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS: 00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n -\u0026gt; team_port_disable()\n -\u0026gt; team_queue_override_port_del()\n -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n -\u0026gt; team_queue_override_port_prio_changed()\n -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly\n\nThe netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a\nLS_NLA_TYPE_DGID attribute, it is invalid if it does not.\n\nUse the nl parsing logic properly and call nla_parse_deprecated() to fill\nthe nlattrs array and then directly index that array to get the data for\nthe DGID. Just fail if it is NULL.\n\nRemove the for loop searching for the nla, and squash the validation and\nparsing into one function.\n\nFixes an uninitialized read from the stack triggered by userspace if it\ndoes not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE\nquery.\n\n BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline]\n BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n hex_byte_pack include/linux/hex.h:13 [inline]\n ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509\n ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633\n pointer+0xc09/0x1bd0 lib/vsprintf.c:2542\n vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930\n vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279\n vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426\n vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465\n vprintk+0x36/0x50 kernel/printk/printk_safe.c:82\n _printk+0x17e/0x1b0 kernel/printk/printk.c:2475\n ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline]\n ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141\n rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline]\n rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x333/0x3d0 net/socket.c:729\n ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617\n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671\n __sys_sendmsg+0x1aa/0x300 net/socket.c:2703\n __compat_sys_sendmsg net/compat.c:346 [inline]\n __do_compat_sys_sendmsg net/compat.c:353 [inline]\n __se_compat_sys_sendmsg net/compat.c:350 [inline]\n __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350\n ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371\n do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306\n do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331\n do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3(CVE-2025-71096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: Fix reference count leak when using error routes with nexthop objects\n\nWhen a nexthop object is deleted, it is marked as dead and then\nfib_table_flush() is called to flush all the routes that are using the\ndead nexthop.\n\nThe current logic in fib_table_flush() is to only flush error routes\n(e.g., blackhole) when it is called as part of network namespace\ndismantle (i.e., with flush_all=true). Therefore, error routes are not\nflushed when their nexthop object is deleted:\n\n # ip link add name dummy1 up type dummy\n # ip nexthop add id 1 dev dummy1\n # ip route add 198.51.100.1/32 nhid 1\n # ip route add blackhole 198.51.100.2/32 nhid 1\n # ip nexthop del id 1\n # ip route show\n blackhole 198.51.100.2 nhid 1 dev dummy1\n\nAs such, they keep holding a reference on the nexthop object which in\nturn holds a reference on the nexthop device, resulting in a reference\ncount leak:\n\n # ip link del dev dummy1\n [ 70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2\n\nFix by flushing error routes when their nexthop is marked as dead.\n\nIPv6 does not suffer from this problem.(CVE-2025-71097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Avoid walking the Namespace if start_node is NULL\n\nAlthough commit 0c9992315e73 (\u0026quot;ACPICA: Avoid walking the ACPI Namespace\nif it is not there\u0026quot;) fixed the situation when both start_node and\nacpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed\non Honor Magicbook 14 Pro [1].\n\nThat happens due to the access to the member of parent_node in\nacpi_ns_get_next_node(). The NULL pointer dereference will always\nhappen, no matter whether or not the start_node is equal to\nACPI_ROOT_OBJECT, so move the check of start_node being NULL\nout of the if block.\n\nUnfortunately, all the attempts to contact Honor have failed, they\nrefused to provide any technical support for Linux.\n\nThe bad DSDT table\u0026apos;s dump could be found on GitHub [2].\n\nDMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025\n\n[ rjw: Subject adjustment, changelog edits ](CVE-2025-71118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Sign extend kfunc call arguments\n\nThe kfunc calls are native calls so they should follow LoongArch calling\nconventions. Sign extend its arguments properly to avoid kernel panic.\nThis is done by adding a new emit_abi_ext() helper. The emit_abi_ext()\nhelper performs extension in place meaning a value already store in the\ntarget register (Note: this is different from the existing sign_extend()\nhelper and thus we can\u0026apos;t reuse it).(CVE-2025-71129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tilcdc: Fix removal actions in case of failed probe\n\nThe drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers\nshould only be called when the device has been successfully registered.\nCurrently, these functions are called unconditionally in tilcdc_fini(),\nwhich causes warnings during probe deferral scenarios.\n\n[ 7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68\n...\n[ 8.005820] drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108\n[ 8.005858] drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8\n[ 8.005885] drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144\n[ 8.005911] drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc]\n[ 8.005957] tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]\n\nFix this by rewriting the failed probe cleanup path using the standard\ngoto error handling pattern, which ensures that cleanup functions are\nonly called on successfully initialized resources. Additionally, remove\nthe now-unnecessary is_registered flag.(CVE-2025-71141)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: stm32: dmamux: fix device leak on route allocation\n\nMake sure to drop the reference taken when looking up the DMA mux\nplatform device during route allocation.\n\nNote that holding a reference to a device does not prevent its driver\ndata from going away so there is no point in keeping the reference.(CVE-2025-71186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()\n\nWhen ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().(CVE-2025-71220)\n\nIn the Linux kernel, a race condition vulnerability exists in the mmp_pdma driver. The vulnerability occurs in the mmp_pdma_residue() function which lacks proper locking mechanisms, potentially leading to use-after-free issues when accessing descriptor lists and descriptor contents.\n\nThe race condition occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors. This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan \u0026gt; 1).\n\nThe fix involves protecting the chain_running list iteration and descriptor access with the chan-\u0026gt;desc_lock spinlock.(CVE-2025-71221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: fix refcount leak in smb2_open()\n\nWhen ksmbd_vfs_getattr() fails, the reference count of ksmbd_file\nmust be released.(CVE-2025-71223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u0026gt;r1bio_pool) and conf-\u0026gt;raid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u0026gt;raid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too.(CVE-2025-71225)\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Free sp in error path to fix system crash System crash seen during load/unload test in a loop, [61110.449331] qla2xxx [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494](CVE-2025-71232)\n\nIn the Linux kernel, there is a race condition vulnerability in the SCSI qla2xxx driver. System crash was observed during load/unload loop testing. The root cause was a memory free operation occurring in interrupt context. When device discovery/fabric scan was in progress and module unload was issued setting the UNLOADING flag, work queue items could not be allocated and mapped memory had to be freed in interrupt context, leading to system crash.(CVE-2025-71235)\n\nA NULL pointer dereference vulnerability exists in the SCSI qla2xxx driver subsystem of the Linux kernel. When the system attempts to free associated memory in the qla_fab_async_scan function, it fails to validate whether the sp pointer is NULL, leading to kernel NULL pointer dereference and system crashes. This vulnerability can be exploited by attackers to cause denial of service.(CVE-2025-71236)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sock: fix hardened usercopy panic in sock_recv_errqueue\n\nskbuff_fclone_cache was created without defining a usercopy region,\n[1] unlike skbuff_head_cache which properly whitelists the cb[] field.\n[2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is\nenabled and the kernel attempts to copy sk_buff.cb data to userspace\nvia sock_recv_errqueue() -\u0026gt; put_cmsg().\n\nThe crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()\n (from skbuff_fclone_cache) [1]\n2. The skb is cloned via skb_clone() using the pre-allocated fclone\n[3] 3. The cloned skb is queued to sk_error_queue for timestamp\nreporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)\n5. sock_recv_errqueue() calls put_cmsg() to copy serr-\u0026gt;ee from skb-\u0026gt;cb\n[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no\n usercopy whitelist [5]\n\nWhen cloned skbs allocated from skbuff_fclone_cache are used in the\nsocket error queue, accessing the sock_exterr_skb structure in skb-\u0026gt;cb\nvia put_cmsg() triggers a usercopy hardening violation:\n\n[ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object \u0026apos;skbuff_fclone_cache\u0026apos; (offset 296, size 16)!\n[ 5.382796] kernel BUG at mm/usercopy.c:102!\n[ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n[ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7\n[ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80\n[ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff \u0026lt;0f\u0026gt; 0b 490\n[ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246\n[ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74\n[ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0\n[ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74\n[ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001\n[ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00\n[ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000\n[ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0\n[ 5.384903] PKRU: 55555554\n[ 5.384903] Call Trace:\n[ 5.384903] \u0026lt;TASK\u0026gt;\n[ 5.384903] __check_heap_object+0x9a/0xd0\n[ 5.384903] __check_object_size+0x46c/0x690\n[ 5.384903] put_cmsg+0x129/0x5e0\n[ 5.384903] sock_recv_errqueue+0x22f/0x380\n[ 5.384903] tls_sw_recvmsg+0x7ed/0x1960\n[ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 5.384903] ? schedule+0x6d/0x270\n[ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 5.384903] ? mutex_unlock+0x81/0xd0\n[ 5.384903] ? __pfx_mutex_unlock+0x10/0x10\n[ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10\n[ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0\n[ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40\n[ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5\n\nThe crash offset 296 corresponds to skb2-\u0026gt;cb within skbuff_fclones:\n - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -\n offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 =\n 272 + 24 (inside sock_exterr_skb.ee)\n\nThis patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.\n\n[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885\n[2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104\n[3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566\n[4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491\n[5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719(CVE-2026-22977)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix memory leak in skb_segment_list for GRO packets\n\nWhen skb_segment_list() is called during packet forwarding, it handles\npackets that were aggregated by the GRO engine.\n\nHistorically, the segmentation logic in skb_segment_list assumes that\nindividual segments are split from a parent SKB and may need to carry\ntheir own socket memory accounting. Accordingly, the code transfers\ntruesize from the parent to the newly created segments.\n\nPrior to commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;), this\ntruesize subtraction in skb_segment_list() was valid because fragments\nstill carry a reference to the original socket.\n\nHowever, commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;) changed\nthis behavior by ensuring that fraglist entries are explicitly\norphaned (skb-\u0026gt;sk = NULL) to prevent illegal orphaning later in the\nstack. This change meant that the entire socket memory charge remained\nwith the head SKB, but the corresponding accounting logic in\nskb_segment_list() was never updated.\n\nAs a result, the current code unconditionally adds each fragment\u0026apos;s\ntruesize to delta_truesize and subtracts it from the parent SKB. Since\nthe fragments are no longer charged to the socket, this subtraction\nresults in an effective under-count of memory when the head is freed.\nThis causes sk_wmem_alloc to remain non-zero, preventing socket\ndestruction and leading to a persistent memory leak.\n\nThe leak can be observed via KMEMLEAK when tearing down the networking\nenvironment:\n\nunreferenced object 0xffff8881e6eb9100 (size 2048):\n comm \u0026quot;ping\u0026quot;, pid 6720, jiffies 4295492526\n backtrace:\n kmem_cache_alloc_noprof+0x5c6/0x800\n sk_prot_alloc+0x5b/0x220\n sk_alloc+0x35/0xa00\n inet6_create.part.0+0x303/0x10d0\n __sock_create+0x248/0x640\n __sys_socket+0x11b/0x1d0\n\nSince skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST\npackets constructed by GRO, the truesize adjustment is removed.\n\nThe call to skb_release_head_state() must be preserved. As documented in\ncommit cf673ed0e057 (\u0026quot;net: fix fraglist segmentation reference count\nleak\u0026quot;), it is still required to correctly drop references to SKB\nextensions that may be overwritten during __copy_skb_header().(CVE-2026-22979)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in handle_auth_done()\n\nPerform an explicit bounds check on payload_len to avoid a possible\nout-of-bounds access in the callout.\n\n[ idryomov: changelog ](CVE-2026-22984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make free_choose_arg_map() resilient to partial allocation\n\nfree_choose_arg_map() may dereference a NULL pointer if its caller fails\nafter a partial allocation.\n\nFor example, in decode_choose_args(), if allocation of arg_map-\u0026gt;args\nfails, execution jumps to the fail label and free_choose_arg_map() is\ncalled. Since arg_map-\u0026gt;size is updated to a non-zero value before memory\nallocation, free_choose_arg_map() will iterate over arg_map-\u0026gt;args and\ndereference a NULL pointer.\n\nTo prevent this potential NULL pointer dereference and make\nfree_choose_arg_map() more resilient, add checks for pointers before\niterating.(CVE-2026-22991)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: do not free existing class in qfq_change_class()\n\nFixes qfq_change_class() error case.\n\ncl-\u0026gt;qdisc and cl should only be freed if a new class and qdisc\nwere allocated, or we risk various UAF.(CVE-2026-22999)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n\nBlamed commit did not take care of VLAN encapsulations\nas spotted by syzbot [1].\n\nUse skb_vlan_inet_prepare() instead of pskb_inet_may_pull().\n\n[1]\n BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729\n __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860\n ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903\n gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1\n ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438\n ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489\n NF_HOOK include/linux/netfilter.h:318 [inline]\n ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500\n ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590\n dst_input include/net/dst.h:474 [inline]\n ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79\n NF_HOOK include/linux/netfilter.h:318 [inline]\n ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311\n __netif_receive_skb_one_core net/core/dev.c:6139 [inline]\n __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252\n netif_receive_skb_internal net/core/dev.c:6338 [inline]\n netif_receive_skb+0x57/0x630 net/core/dev.c:6397\n tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485\n tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953\n tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n new_sync_write fs/read_write.c:593 [inline]\n vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n ksys_write fs/read_write.c:738 [inline]\n __do_sys_write fs/read_write.c:749 [inline]\n __se_sys_write fs/read_write.c:746 [inline]\n __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:4960 [inline]\n slab_alloc_node mm/slub.c:5263 [inline]\n kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315\n kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586\n __alloc_skb+0x805/0x1040 net/core/skbuff.c:690\n alloc_skb include/linux/skbuff.h:1383 [inline]\n alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712\n sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995\n tun_alloc_skb drivers/net/tun.c:1461 [inline]\n tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794\n tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n new_sync_write fs/read_write.c:593 [inline]\n vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n ksys_write fs/read_write.c:738 [inline]\n __do_sys_write fs/read_write.c:749 [inline]\n __se_sys_write fs/read_write.c:746 [inline]\n __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025(CVE-2026-23003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix use-after-free in inet6_addr_del().\n\nsyzbot reported use-after-free of inet6_ifaddr in\ninet6_addr_del(). [0]\n\nThe cited commit accidentally moved ipv6_del_addr() for\nmngtmpaddr before reading its ifp-\u0026gt;flags for temporary\naddresses in inet6_addr_del().\n\nLet\u0026apos;s move ipv6_del_addr() down to fix the UAF.\n\n[0]:\nBUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\nRead of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593\n\nCPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\n addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181\n inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f164cf8f749\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749\nRDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003\nRBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 9593:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n poison_kmalloc_redzone mm/kasan/common.c:397 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414\n kmalloc_noprof include/linux/slab.h:957 [inline]\n kzalloc_noprof include/linux/slab.h:1094 [inline]\n ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120\n inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050\n addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160\n inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 6099:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584\n poison_slab_object mm/kasan/common.c:252 [inline]\n __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284\n kasan_slab_free include/linux/kasan.h:234 [inline]\n slab_free_hook mm/slub.c:2540 [inline]\n slab_free_freelist_hook mm/slub.c:2569 [inline]\n slab_free_bulk mm/slub.c:6696 [inline]\n kmem_cache_free_bulk mm/slub.c:7383 [inline]\n kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362\n kfree_bulk include/linux/slab.h:830 [inline]\n kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523\n kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline]\n kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801\n process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257\n process_scheduled_works kernel/workqu\n---truncated---(CVE-2026-23010)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: fix memory leak in update_eth_regs_async()\n\nWhen asynchronously writing to the device registers and if usb_submit_urb()\nfail, the code fail to release allocated to this point resources.(CVE-2026-23021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT 8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n __dump_stack (lib/dump_stack.c:95)\n dump_stack_lvl (lib/dump_stack.c:123)\n dump_stack (lib/dump_stack.c:130)\n spin_dump (kernel/locking/spinlock_debug.c:71)\n do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n __free_frozen_pages (mm/page_alloc.c:2973)\n ___free_pages (mm/page_alloc.c:5295)\n __free_pages (mm/page_alloc.c:5334)\n tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n ? rcu_core (kernel/rcu/tree.c:?)\n rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n rcu_core_si (kernel/rcu/tree.c:2879)\n handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n irq_exit_rcu (kernel/softirq.c:741)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n free_pcppages_bulk (mm/page_alloc.c:1494)\n drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n __drain_all_pages (mm/page_alloc.c:2731)\n drain_all_pages (mm/page_alloc.c:2747)\n kcompactd (mm/compaction.c:3115)\n kthread (kernel/kthread.c:465)\n ? __cfi_kcompactd (mm/compaction.c:3166)\n ? __cfi_kthread (kernel/kthread.c:412)\n ret_from_fork (arch/x86/kernel/process.c:164)\n ? __cfi_kthread (kernel/kthread.c:412)\n ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock. The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback. However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op. Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;). The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized. Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix kmemleak by releasing references to fault configfs items\n\nWhen CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk\ndriver sets up fault injection support by creating the timeout_inject,\nrequeue_inject, and init_hctx_fault_inject configfs items as children\nof the top-level nullbX configfs group.\n\nHowever, when the nullbX device is removed, the references taken to\nthese fault-config configfs items are not released. As a result,\nkmemleak reports a memory leak, for example:\n\nunreferenced object 0xc00000021ff25c40 (size 32):\n comm \u0026quot;mkdir\u0026quot;, pid 10665, jiffies 4322121578\n hex dump (first 32 bytes):\n 69 6e 69 74 5f 68 63 74 78 5f 66 61 75 6c 74 5f init_hctx_fault_\n 69 6e 6a 65 63 74 00 88 00 00 00 00 00 00 00 00 inject..........\n backtrace (crc 1a018c86):\n __kmalloc_node_track_caller_noprof+0x494/0xbd8\n kvasprintf+0x74/0xf4\n config_item_set_name+0xf0/0x104\n config_group_init_type_name+0x48/0xfc\n fault_config_init+0x48/0xf0\n 0xc0080000180559e4\n configfs_mkdir+0x304/0x814\n vfs_mkdir+0x49c/0x604\n do_mkdirat+0x314/0x3d0\n sys_mkdir+0xa0/0xd8\n system_call_exception+0x1b0/0x4f0\n system_call_vectored_common+0x15c/0x2ec\n\nFix this by explicitly releasing the references to the fault-config\nconfigfs items when dropping the reference to the top-level nullbX\nconfigfs group.(CVE-2026-23032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u0026gt;paused, not just clear it\n\nCurrently calc_target() clears t-\u0026gt;paused if the request shouldn\u0026apos;t be\npaused anymore, but doesn\u0026apos;t ever set t-\u0026gt;paused even though it\u0026apos;s able to\ndetermine when the request should be paused. Setting t-\u0026gt;paused is left\nto __submit_request() which is fine for regular requests but doesn\u0026apos;t\nwork for linger requests -- since __submit_request() doesn\u0026apos;t operate\non linger requests, there is nowhere for lreq-\u0026gt;t.paused to be set.\nOne consequence of this is that watches don\u0026apos;t get reestablished on\npaused -\u0026gt; unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state. On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u0026gt;watch_mutex held:\n\n rbd_register_watch\n __rbd_register_watch\n ceph_osdc_watch\n linger_reg_commit_wait\n\nIt\u0026apos;s waiting for lreq-\u0026gt;reg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused. There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u0026gt;watch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \u0026quot;rbd unmap\u0026quot; would inevitably\nhang in D state on an attempt to grab the mutex.(CVE-2026-23047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix a deadlock when returning a delegation during open()\n\nBen Coddington reports seeing a hang in the following stack trace:\n 0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415\n 1 [ffffd0b50e177548] schedule at ffffffff9ca05717\n 2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1\n 3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb\n 4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5\n 5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]\n 6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]\n 7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]\n 8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]\n 9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]\n 10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]\n 11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]\n 12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]\n 13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]\n 14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]\n 15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]\n 16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]\n 17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea\n 18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e\n 19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935\n\nThe issue is that the delegreturn is being asked to wait for a layout\nreturn that cannot complete because a state recovery was initiated. The\nstate recovery cannot complete until the open() finishes processing the\ndelegations it was given.\n\nThe solution is to propagate the existing flags that indicate a\nnon-blocking call to the function pnfs_roc(), so that it knows not to\nwait in this situation.(CVE-2026-23050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nA buffer overflow vulnerability exists in the QLogic Fibre Channel driver (qla2xxx) of the Linux kernel. In the functions `qla27xx_copy_fpin_pkt()` and `qla27xx_copy_multiple_pkt()`, the code uses the firmware-reported `frame_size` to calculate the copy length into `item-\u0026gt;iocb`. However, the `iocb` member is defined as a fixed-size 64-byte array within `struct purex_item`. If the reported `frame_size` exceeds 64 bytes, subsequent `memcpy` calls will overflow the boundary of the `iocb` member. This cross-member write is unsafe and can lead to memory corruption, potentially exploitable to compromise the confidentiality, integrity, and availability of the kernel.(CVE-2026-23059)\n\nA NULL pointer dereference vulnerability exists in the be2net network driver within the Linux kernel, specifically in the be_cmd_get_mac_from_list() function. According to the function\u0026apos;s contract, when the parameter pmac_id_valid is set to false, the driver may request a PMAC_ID from the network card\u0026apos;s firmware and store it at the provided address pmac_id. However, there is a location within the driver where both conditions pmac_id_valid == false and pmac_id == NULL are passed simultaneously. This results in an attempt to dereference a NULL pointer, potentially leading to a kernel crash or system instability.(CVE-2026-23084)\n\nA memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the \u0026apos;itt\u0026apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit \u0026apos;unsigned long\u0026apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix isolate sysfs check condition\n\nuacce supports the device isolation feature. If the driver\nimplements the isolate_err_threshold_read and\nisolate_err_threshold_write callback functions, uacce will create\nsysfs files now. Users can read and configure the isolation policy\nthrough sysfs. Currently, sysfs files are created as long as either\nisolate_err_threshold_read or isolate_err_threshold_write callback\nfunctions are present.\n\nHowever, accessing a non-existent callback function may cause the\nsystem to crash. Therefore, intercept the creation of sysfs if\nneither read nor write exists; create sysfs if either is supported,\nbut intercept unsupported operations at the call site.(CVE-2026-23094)\n\nA deadlock vulnerability exists in the Linux kernel due to incorrect lock acquisition ordering. This vulnerability affects the migration functionality for hugetlb (huge page) file folios. The specific scenario is: when two kernel tasks (Tasks) attempt to acquire the `folio_lock` and `i_mmap_rwsem` locks in opposite orders, a circular wait is formed, leading to a system deadlock. For example, Task A holds `folio_lock` and then tries to acquire the `i_mmap_rwsem` read lock, while Task B holds the `i_mmap_rwsem` write lock and then tries to acquire `folio_lock`. This lock ordering violates the rules defined in mm/rmap.c. This vulnerability can render parts of the affected system unavailable, impacting system availability.(CVE-2026-23097)\n\nIn the Linux kernel SCSI core layer, there is a fragile ordering logic between marking commands as completed or failed, designed to ensure the error handler only wakes when the last running command completes or times out. This logic contains race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. Specifically, there are two issues: 1. A memory ordering issue within the `scsi_dec_host_busy()` function. The write operation that clears the `SCMD_STATE_INFLIGHT` flag may be reordered with read counting operations in `scsi_host_busy()`. This can cause other CPUs to see inconsistent busy counts, preventing the correct triggering of the error handler wake-up. 2. A general ordering issue with the `scsi_eh_inc_host_failed()` function. It counts busy commands before incrementing the `host_failed` count, which can race with the processing of a final command in `scsi_dec_host_busy()`, resulting in neither side waking the error handler task.(CVE-2026-23110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec\n\nnvmet_tcp_build_pdu_iovec() could walk past cmd-\u0026gt;req.sg when a PDU\nlength or offset exceeds sg_cnt and then use bogus sg-\u0026gt;length/offset\nvalues, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining\nentries, and sg-\u0026gt;length/offset before building the bvec.(CVE-2026-23112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove\n\nOn APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and\nih2 interrupt ring buffers are not initialized. This is by design, as\nthese secondary IH rings are only available on discrete GPUs. See\nvega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when\nAMD_IS_APU is set.\n\nHowever, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to\nget the timestamp of the last interrupt entry. When retry faults are\nenabled on APUs (noretry=0), this function is called from the SVM page\nfault recovery path, resulting in a NULL pointer dereference when\namdgpu_ih_decode_iv_ts_helper() attempts to access ih-\u0026gt;ring[].\n\nThe crash manifests as:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000004\n RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]\n Call Trace:\n amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]\n svm_range_restore_pages+0xae5/0x11c0 [amdgpu]\n amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu]\n gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]\n amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu]\n amdgpu_ih_process+0x84/0x100 [amdgpu]\n\nThis issue was exposed by commit 1446226d32a4 (\u0026quot;drm/amdgpu: Remove GC HW\nIP 9.3.0 from noretry=1\u0026quot;) which changed the default for Renoir APU from\nnoretry=1 to noretry=0, enabling retry fault handling and thus\nexercising the buggy code path.\n\nFix this by adding a check for ih1.ring_size before attempting to use\nit. Also restore the soft_ih support from commit dd299441654f (\u0026quot;drm/amdgpu:\nRework retry fault removal\u0026quot;). This is needed if the hardware doesn\u0026apos;t\nsupport secondary HW IH rings.\n\nv2: additional updates (Alex)\n\n(cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)(CVE-2026-23163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()\n\nWhen the socket is closed while in TCP_LISTEN a callback is run to\nflush all outstanding packets, which in turns calls\nnvmet_tcp_listen_data_ready() with the sk_callback_lock held.\nSo we need to check if we are in TCP_LISTEN before attempting\nto get the sk_callback_lock() to avoid a deadlock.(CVE-2026-23179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: amd: fix memory leak in acp3x pdm dma ops(CVE-2026-23190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()\n\nIn iscsit_dec_session_usage_count(), the function calls complete() while\nholding the sess-\u0026gt;session_usage_lock. Similar to the connection usage count\nlogic, the waiter signaled by complete() (e.g., in the session release\npath) may wake up and free the iscsit_session structure immediately.\n\nThis creates a race condition where the current thread may attempt to\nexecute spin_unlock_bh() on a session structure that has already been\ndeallocated, resulting in a KASAN slab-use-after-free.\n\nTo resolve this, release the session_usage_lock before calling complete()\nto ensure all dereferences of the sess pointer are finished before the\nwaiter is allowed to proceed with deallocation.(CVE-2026-23193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: fix memory leak in smb2_open_file()\n\nReproducer:\n\n 1. server: directories are exported read-only\n 2. client: mount -t cifs //${server_ip}/export /mnt\n 3. client: dd if=/dev/zero of=/mnt/file bs=512 count=1000 oflag=direct\n 4. client: umount /mnt\n 5. client: sleep 1\n 6. client: modprobe -r cifs\n\nThe error message is as follows:\n\n =============================================================================\n BUG cifs_small_rq (Not tainted): Objects remaining on __kmem_cache_shutdown()\n -----------------------------------------------------------------------------\n\n Object 0x00000000d47521be @offset=14336\n ...\n WARNING: mm/slub.c:1251 at __kmem_cache_shutdown+0x34e/0x440, CPU#0: modprobe/1577\n ...\n Call Trace:\n \u0026lt;TASK\u0026gt;\n kmem_cache_destroy+0x94/0x190\n cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n cleanup_module+0x4e/0x540 [cifs]\n __se_sys_delete_module+0x278/0x400\n __x64_sys_delete_module+0x5f/0x70\n x64_sys_call+0x2299/0x2ff0\n do_syscall_64+0x89/0x350\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n ...\n kmem_cache_destroy cifs_small_rq: Slab cache still has objects when called from cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n WARNING: mm/slab_common.c:532 at kmem_cache_destroy+0x16b/0x190, CPU#0: modprobe/1577(CVE-2026-23205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)\n\nIn the Linux kernel, the ksmbd component contains an infinite loop vulnerability. The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() sets work-\u0026gt;next_smb2_rcv_hdr_off to zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header\u0026apos;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with \u0026quot;bad smb2 signature\u0026quot; messages and high CPU usage.(CVE-2026-23220)\n\nIn the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection() On kthread_run() failure in ksmbd_tcp_new_connection(), the transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter. Replace free_transport() with ksmbd_tcp_disconnect(). The Linux kernel CVE team has assigned CVE-2026-23228 to this issue.(CVE-2026-23228)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:37.776858405Z","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-1570","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\nudp: Deal with race between UDP socket address change and rehash\n\nIf a UDP socket changes its local address while it\u0026apos;s receiving\ndatagrams, as a result of connect(), there is a period during which\na lookup operation might fail to find it, after the address is changed\nbut before the secondary hash (port and address) and the four-tuple\nhash (local and remote ports and addresses) are updated.\n\nSecondary hash chains were introduced by commit 30fff9231fad (\u0026quot;udp:\nbind() optimisation\u0026quot;) and, as a result, a rehash operation became\nneeded to make a bound socket reachable again after a connect().\n\nThis operation was introduced by commit 719f835853a9 (\u0026quot;udp: add\nrehash on connect()\u0026quot;) which isn\u0026apos;t however a complete fix: the\nsocket will be found once the rehashing completes, but not while\nit\u0026apos;s pending.\n\nThis is noticeable with a socat(1) server in UDP4-LISTEN mode, and a\nclient sending datagrams to it. After the server receives the first\ndatagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to\nthe address of the sender, in order to set up a directed flow.\n\nNow, if the client, running on a different CPU thread, happens to\nsend a (subsequent) datagram while the server\u0026apos;s socket changes its\naddress, but is not rehashed yet, this will result in a failed\nlookup and a port unreachable error delivered to the client, as\napparent from the following reproducer:\n\n LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))\n dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in\n\n while :; do\n \ttaskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n \tsleep 0.1 || sleep 1\n \ttaskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null\n \twait\n done\n\nwhere the client will eventually get ECONNREFUSED on a write()\n(typically the second or third one of a given iteration):\n\n 2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused\n\nThis issue was first observed as a seldom failure in Podman\u0026apos;s tests\nchecking UDP functionality while using pasta(1) to connect the\ncontainer\u0026apos;s network namespace, which leads us to a reproducer with\nthe lookup error resulting in an ICMP packet on a tap device:\n\n LOCAL_ADDR=\u0026quot;$(ip -j -4 addr show|jq -rM \u0026apos;.[] | .addr_info[0] | select(.scope == \u0026quot;global\u0026quot;).local\u0026apos;)\u0026quot;\n\n while :; do\n \t./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n \tsleep 0.2 || sleep 1\n \tsocat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null\n \twait\n \tcmp tmp.in tmp.out\n done\n\nOnce this fails:\n\n tmp.in tmp.out differ: char 8193, line 29\n\nwe can finally have a look at what\u0026apos;s going on:\n\n $ tshark -r pasta.pcap\n 1 0.000000 :: ? ff02::16 ICMPv6 110 Multicast Listener Report Message v2\n 2 0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 3 0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 4 0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 5 0.168827 c6:47:05:8d:dc:04 ? Broadcast ARP 42 Who has 88.198.0.161? Tell 88.198.0.164\n 6 0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55\n 7 0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 8 0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable)\n 9 0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 10 0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n 11 0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096\n 12 0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0\n\nOn the third datagram received, the network namespace of the container\ninitiates an ARP lookup to deliver the ICMP message.\n\nIn another variant of this reproducer, starting the client with:\n\n strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru\n---truncated---(CVE-2024-57974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()\n\nIf track_pfn_copy() fails, we already added the dst VMA to the maple\ntree. As fork() fails, we\u0026apos;ll cleanup the maple tree, and stumble over\nthe dst VMA for which we neither performed any reservation nor copied\nany page tables.\n\nConsequently untrack_pfn() will see VM_PAT and try obtaining the\nPAT information from the page table -- which fails because the page\ntable was not copied.\n\nThe easiest fix would be to simply clear the VM_PAT flag of the dst VMA\nif track_pfn_copy() fails. However, the whole thing is about \u0026quot;simply\u0026quot;\nclearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy()\nand performed a reservation, but copying the page tables fails, we\u0026apos;ll\nsimply clear the VM_PAT flag, not properly undoing the reservation ...\nwhich is also wrong.\n\nSo let\u0026apos;s fix it properly: set the VM_PAT flag only if the reservation\nsucceeded (leaving it clear initially), and undo the reservation if\nanything goes wrong while copying the page tables: clearing the VM_PAT\nflag after undoing the reservation.\n\nNote that any copied page table entries will get zapped when the VMA will\nget removed later, after copy_page_range() succeeded; as VM_PAT is not set\nthen, we won\u0026apos;t try cleaning VM_PAT up once more and untrack_pfn() will be\nhappy. Note that leaving these page tables in place without a reservation\nis not a problem, as we are aborting fork(); this process will never run.\n\nA reproducer can trigger this usually at the first try:\n\n https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c\n\n WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110\n Modules linked in: ...\n CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\n RIP: 0010:get_pat_info+0xf6/0x110\n ...\n Call Trace:\n \u0026lt;TASK\u0026gt;\n ...\n untrack_pfn+0x52/0x110\n unmap_single_vma+0xa6/0xe0\n unmap_vmas+0x105/0x1f0\n exit_mmap+0xf6/0x460\n __mmput+0x4b/0x120\n copy_process+0x1bf6/0x2aa0\n kernel_clone+0xab/0x440\n __do_sys_clone+0x66/0x90\n do_syscall_64+0x95/0x180\n\nLikely this case was missed in:\n\n d155df53f310 (\u0026quot;x86/mm/pat: clear VM_PAT if copy_p4d_range failed\u0026quot;)\n\n... and instead of undoing the reservation we simply cleared the VM_PAT flag.\n\nKeep the documentation of these functions in include/linux/pgtable.h,\none place is more than sufficient -- we should clean that up for the other\nfunctions like track_pfn_remap/untrack_pfn separately.(CVE-2025-22090)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: make fallback action and fallback decision atomic\n\nSyzkaller reported the following splat:\n\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline]\n WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n Modules linked in:\n CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary)\n Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline]\n RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00\n RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246\n RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45\n RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001\n RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000\n R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000\n FS: 00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432\n tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975\n tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166\n tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925\n tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363\n ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205\n ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233\n NF_HOOK include/linux/netfilter.h:317 [inline]\n NF_HOOK include/linux/netfilter.h:311 [inline]\n ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254\n dst_input include/net/dst.h:469 [inline]\n ip_rcv_finish net/ipv4/ip_input.c:447 [inline]\n NF_HOOK include/linux/netfilter.h:317 [inline]\n NF_HOOK include/linux/netfilter.h:311 [inline]\n ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567\n __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975\n __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088\n process_backlog+0x301/0x1360 net/core/dev.c:6440\n __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453\n napi_poll net/core/dev.c:7517 [inline]\n net_rx_action+0xb44/0x1010 net/core/dev.c:7644\n handle_softirqs+0x1d0/0x770 kernel/softirq.c:579\n do_softirq+0x3f/0x90 kernel/softirq.c:480\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407\n local_bh_enable include/linux/bottom_half.h:33 [inline]\n inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524\n mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985\n mptcp_check_listen_stop net/mptcp/mib.h:118 [inline]\n __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000\n mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066\n inet_release+0xed/0x200 net/ipv4/af_inet.c:435\n inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487\n __sock_release+0xb3/0x270 net/socket.c:649\n sock_close+0x1c/0x30 net/socket.c:1439\n __fput+0x402/0xb70 fs/file_table.c:465\n task_work_run+0x150/0x240 kernel/task_work.c:227\n resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n exit_to_user_mode_loop+0xd4\n---truncated---(CVE-2025-38491)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic\n\nThe decompress_io_ctx may be released asynchronously after\nI/O completion. If this file is deleted immediately after read,\nand the kworker of processing post_read_wq has not been executed yet\ndue to high workloads, It is possible that the inode(f2fs_inode_info)\nis evicted and freed before it is used f2fs_free_dic.\n\n The UAF case as below:\n Thread A Thread B\n - f2fs_decompress_end_io\n - f2fs_put_dic\n - queue_work\n add free_dic work to post_read_wq\n - do_unlink\n - iput\n - evict\n - call_rcu\n This file is deleted after read.\n\n Thread C kworker to process post_read_wq\n - rcu_do_batch\n - f2fs_free_inode\n - kmem_cache_free\n inode is freed by rcu\n - process_scheduled_works\n - f2fs_late_free_dic\n - f2fs_free_dic\n - f2fs_release_decomp_mem\n read (dic-\u0026gt;inode)-\u0026gt;i_compress_algorithm\n\nThis patch store compress_algorithm and sbi in dic to avoid inode UAF.\n\nIn addition, the previous solution is deprecated in [1] may cause system hang.\n[1] https://lore.kernel.org/all/(CVE-2025-38627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n[ceph] parse_longname(): strrchr() expects NUL-terminated string\n\n... and parse_longname() is not guaranteed that. That\u0026apos;s the reason\nwhy it uses kmemdup_nul() to build the argument for kstrtou64();\nthe problem is, kstrtou64() is not the only thing that need it.\n\nJust get a NUL-terminated copy of the entire thing and be done\nwith that...(CVE-2025-38660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: remove refcounting in expectation dumpers\n\nSame pattern as previous patch: do not keep the expectation object\nalive via refcount, only store a cookie value and then use that\nas the skip hint for dump resumption.\n\nAFAICS this has the same issue as the one resolved in the conntrack\ndumper, when we do\n if (!refcount_inc_not_zero(\u0026amp;exp-\u0026gt;use))\n\nto increment the refcount, there is a chance that exp == last, which\ncauses a double-increment of the refcount and subsequent memory leak.(CVE-2025-39764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: avoid accessing metadata when pointer is invalid in object_err()\n\nobject_err() reports details of an object for further debugging, such as\nthe freelist pointer, redzone, etc. However, if the pointer is invalid,\nattempting to access object metadata can lead to a crash since it does\nnot point to a valid object.\n\nOne known path to the crash is when alloc_consistency_checks()\ndetermines the pointer to the allocated object is invalid because of a\nfreelist corruption, and calls object_err() to report it. The debug code\nshould report and handle the corruption gracefully and not crash in the\nprocess.\n\nIn case the pointer is NULL or check_valid_pointer() returns false for\nthe pointer, only print the pointer value and skip accessing metadata.(CVE-2025-39902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix Rx page leak on multi-buffer frames\n\nThe ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each\nbuffer in the current frame. This function was introduced as part of\nhandling multi-buffer XDP support in the ice driver.\n\nIt works by iterating over the buffers from first_desc up to 1 plus the\ntotal number of fragments in the frame, cached from before the XDP program\nwas executed.\n\nIf the hardware posts a descriptor with a size of 0, the logic used in\nice_put_rx_mbuf() breaks. Such descriptors get skipped and don\u0026apos;t get added\nas fragments in ice_add_xdp_frag. Since the buffer isn\u0026apos;t counted as a\nfragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don\u0026apos;t\ncall ice_put_rx_buf().\n\nBecause we don\u0026apos;t call ice_put_rx_buf(), we don\u0026apos;t attempt to re-use the\npage or free it. This leaves a stale page in the ring, as we don\u0026apos;t\nincrement next_to_alloc.\n\nThe ice_reuse_rx_page() assumes that the next_to_alloc has been incremented\nproperly, and that it always points to a buffer with a NULL page. Since\nthis function doesn\u0026apos;t check, it will happily recycle a page over the top\nof the next_to_alloc buffer, losing track of the old page.\n\nNote that this leak only occurs for multi-buffer frames. The\nice_put_rx_mbuf() function always handles at least one buffer, so a\nsingle-buffer frame will always get handled correctly. It is not clear\nprecisely why the hardware hands us descriptors with a size of 0 sometimes,\nbut it happens somewhat regularly with \u0026quot;jumbo frames\u0026quot; used by 9K MTU.\n\nTo fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on\nall buffers between first_desc and next_to_clean. Borrow the logic of a\nsimilar function in i40e used for this same purpose. Use the same logic\nalso in ice_get_pgcnts().\n\nInstead of iterating over just the number of fragments, use a loop which\niterates until the current index reaches to the next_to_clean element just\npast the current frame. Unlike i40e, the ice_put_rx_mbuf() function does\ncall ice_put_rx_buf() on the last buffer of the frame indicating the end of\npacket.\n\nFor non-linear (multi-buffer) frames, we need to take care when adjusting\nthe pagecnt_bias. An XDP program might release fragments from the tail of\nthe frame, in which case that fragment page is already released. Only\nupdate the pagecnt_bias for the first descriptor and fragments still\nremaining post-XDP program. Take care to only access the shared info for\nfragmented buffers, as this avoids a significant cache miss.\n\nThe xdp_xmit value only needs to be updated if an XDP program is run, and\nonly once per packet. Drop the xdp_xmit pointer argument from\nice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function\ndirectly. This avoids needing to pass the argument and avoids an extra\nbit-wise OR for each buffer in the frame.\n\nMove the increment of the ntc local variable to ensure its updated *before*\nall calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic\nrequires the index of the element just after the current frame.\n\nNow that we use an index pointer in the ring to identify the packet, we no\nlonger need to track or cache the number of fragments in the rx_ring.(CVE-2025-39948)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: Set fb_display[i]-\u0026gt;mode to NULL when the mode is released\n\nRecently, we discovered the following issue through syzkaller:\n\nBUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0\nRead of size 4 at addr ff11000001b3c69c by task syz.xxx\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xab/0xe0\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb9/0x280\n kasan_report+0xb8/0xf0\n fb_mode_is_equal+0x285/0x2f0\n fbcon_mode_deleted+0x129/0x180\n fb_set_var+0xe7f/0x11d0\n do_fb_ioctl+0x6a0/0x750\n fb_ioctl+0xe0/0x140\n __x64_sys_ioctl+0x193/0x210\n do_syscall_64+0x5f/0x9c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nBased on experimentation and analysis, during framebuffer unregistration,\nonly the memory of fb_info-\u0026gt;modelist is freed, without setting the\ncorresponding fb_display[i]-\u0026gt;mode to NULL for the freed modes. This leads\nto UAF issues during subsequent accesses. Here\u0026apos;s an example of reproduction\nsteps:\n1. With /dev/fb0 already registered in the system, load a kernel module\n to register a new device /dev/fb1;\n2. Set fb1\u0026apos;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);\n3. Switch console from fb to VGA (to allow normal rmmod of the ko);\n4. Unload the kernel module, at this point fb1\u0026apos;s modelist is freed, leaving\n a wild pointer in fb_display[];\n5. Trigger the bug via system calls through fb0 attempting to delete a mode\n from fb0.\n\nAdd a check in do_unregister_framebuffer(): if the mode to be freed exists\nin fb_display[], set the corresponding mode pointer to NULL.(CVE-2025-40323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb\n\nThe Mesa issue referenced below pointed out a possible deadlock:\n\n[ 1231.611031] Possible interrupt unsafe locking scenario:\n\n[ 1231.611033] CPU0 CPU1\n[ 1231.611034] ---- ----\n[ 1231.611035] lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611038] local_irq_disable();\n[ 1231.611039] lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611041] lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611044] \u0026lt;Interrupt\u0026gt;\n[ 1231.611045] lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611047]\n *** DEADLOCK ***\n\nIn this example, CPU0 would be any function accessing job-\u0026gt;dependencies\nthrough the xa_* functions that don\u0026apos;t disable interrupts (eg:\ndrm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()).\n\nCPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling\ncallback so in an interrupt context. It will deadlock when trying to\ngrab the xa_lock which is already held by CPU0.\n\nReplacing all xa_* usage by their xa_*_irq counterparts would fix\nthis issue, but Christian pointed out another issue: dma_fence_signal\ntakes fence.lock and so does dma_fence_add_callback.\n\n dma_fence_signal() // locks f1.lock\n -\u0026gt; drm_sched_entity_kill_jobs_cb()\n -\u0026gt; foreach dependencies\n -\u0026gt; dma_fence_add_callback() // locks f2.lock\n\nThis will deadlock if f1 and f2 share the same spinlock.\n\nTo fix both issues, the code iterating on dependencies and re-arming them\nis moved out to drm_sched_entity_kill_jobs_work().\n\n[phasta: commit message nits](CVE-2025-40329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n Internal error: Oops: 000000009600004f [#1] SMP\n CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n Hardware name: LS1028A RDB Board (DT)\n pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n pc : xfrm_input+0xde8/0x1318\n lr : xfrm_input+0x61c/0x1318\n sp : ffff800080003b20\n Call trace:\n xfrm_input+0xde8/0x1318\n xfrm6_rcv+0x38/0x44\n xfrm6_esp_rcv+0x48/0xa8\n ip6_protocol_deliver_rcu+0x94/0x4b0\n ip6_input_finish+0x44/0x70\n ip6_input+0x44/0xc0\n ipv6_rcv+0x6c/0x114\n __netif_receive_skb_one_core+0x5c/0x8c\n __netif_receive_skb+0x18/0x60\n process_backlog+0x78/0x17c\n __napi_poll+0x38/0x180\n net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imon: make send_packet() more robust\n\nsyzbot is reporting that imon has three problems which result in\nhung tasks due to forever holding device lock [1].\n\nFirst problem is that when usb_rx_callback_intf0() once got -EPROTO error\nafter ictx-\u0026gt;dev_present_intf0 became true, usb_rx_callback_intf0()\nresubmits urb after printk(), and resubmitted urb causes\nusb_rx_callback_intf0() to again get -EPROTO error. This results in\nprintk() flooding (RCU stalls).\n\nAlan Stern commented [2] that\n\n In theory it\u0026apos;s okay to resubmit _if_ the driver has a robust\n error-recovery scheme (such as giving up after some fixed limit on the\n number of errors or after some fixed time has elapsed, perhaps with a\n time delay to prevent a flood of errors). Most drivers don\u0026apos;t bother to\n do this; they simply give up right away. This makes them more\n vulnerable to short-term noise interference during USB transfers, but in\n reality such interference is quite rare. There\u0026apos;s nothing really wrong\n with giving up right away.\n\nbut imon has a poor error-recovery scheme which just retries forever;\nthis behavior should be fixed.\n\nSince I\u0026apos;m not sure whether it is safe for imon users to give up upon any\nerror code, this patch takes care of only union of error codes chosen from\nmodules in drivers/media/rc/ directory which handle -EPROTO error (i.e.\nir_toy, mceusb and igorplugusb).\n\nSecond problem is that when usb_rx_callback_intf0() once got -EPROTO error\nbefore ictx-\u0026gt;dev_present_intf0 becomes true, usb_rx_callback_intf0() always\nresubmits urb due to commit 8791d63af0cf (\u0026quot;[media] imon: don\u0026apos;t wedge\nhardware after early callbacks\u0026quot;). Move the ictx-\u0026gt;dev_present_intf0 test\nintroduced by commit 6f6b90c9231a (\u0026quot;[media] imon: don\u0026apos;t parse scancodes\nuntil intf configured\u0026quot;) to immediately before imon_incoming_packet(), or\nthe first problem explained above happens without printk() flooding (i.e.\nhung task).\n\nThird problem is that when usb_rx_callback_intf0() is not called for some\nreason (e.g. flaky hardware; the reproducer for this problem sometimes\nprevents usb_rx_callback_intf0() from being called),\nwait_for_completion_interruptible() in send_packet() never returns (i.e.\nhung task). As a workaround for such situation, change send_packet() to\nwait for completion with timeout of 10 seconds.(CVE-2025-68194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: arm: scmi: Fix genpd leak on provider registration failure\n\nIf of_genpd_add_provider_onecell() fails during probe, the previously\ncreated generic power domains are not removed, leading to a memory leak\nand potential kernel crash later in genpd_debug_add().\n\nAdd proper error handling to unwind the initialized domains before\nreturning from probe to ensure all resources are correctly released on\nfailure.\n\nExample crash trace observed without this fix:\n\n | Unable to handle kernel paging request at virtual address fffffffffffffc70\n | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT\n | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform\n | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n | pc : genpd_debug_add+0x2c/0x160\n | lr : genpd_debug_init+0x74/0x98\n | Call trace:\n | genpd_debug_add+0x2c/0x160 (P)\n | genpd_debug_init+0x74/0x98\n | do_one_initcall+0xd0/0x2d8\n | do_initcall_level+0xa0/0x140\n | do_initcalls+0x60/0xa8\n | do_basic_setup+0x28/0x40\n | kernel_init_freeable+0xe8/0x170\n | kernel_init+0x2c/0x140\n | ret_from_fork+0x10/0x20(CVE-2025-68204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0026apos;s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs.(CVE-2025-68209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksm: use range-walk function to jump over holes in scan_get_next_rmap_item\n\nCurrently, scan_get_next_rmap_item() walks every page address in a VMA to\nlocate mergeable pages. This becomes highly inefficient when scanning\nlarge virtual memory areas that contain mostly unmapped regions, causing\nksmd to use large amount of cpu without deduplicating much pages.\n\nThis patch replaces the per-address lookup with a range walk using\nwalk_page_range(). The range walker allows KSM to skip over entire\nunmapped holes in a VMA, avoiding unnecessary lookups. This problem was\npreviously discussed in [1].\n\nConsider the following test program which creates a 32 TiB mapping in the\nvirtual address space but only populates a single page:\n\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\n\n/* 32 TiB */\nconst size_t size = 32ul * 1024 * 1024 * 1024 * 1024;\n\nint main() {\n char *area = mmap(NULL, size, PROT_READ | PROT_WRITE,\n MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);\n\n if (area == MAP_FAILED) {\n perror(\u0026quot;mmap() failed\\n\u0026quot;);\n return -1;\n }\n\n /* Populate a single page such that we get an anon_vma. */\n *area = 0;\n\n /* Enable KSM. */\n madvise(area, size, MADV_MERGEABLE);\n pause();\n return 0;\n}\n\n$ ./ksm-sparse \u0026amp;\n$ echo 1 \u0026gt; /sys/kernel/mm/ksm/run \n\nWithout this patch ksmd uses 100% of the cpu for a long time (more then 1\nhour in my test machine) scanning all the 32 TiB virtual address space\nthat contain only one mapped page. This makes ksmd essentially deadlocked\nnot able to deduplicate anything of value. With this patch ksmd walks\nonly the one mapped page and skips the rest of the 32 TiB virtual address\nspace, making the scan fast using little cpu.(CVE-2025-68211)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempool: fix poisoning order\u0026gt;0 pages with HIGHMEM\n\nThe kernel test has reported:\n\n BUG: unable to handle page fault for address: fffba000\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n *pde = 03171067 *pte = 00000000\n Oops: Oops: 0002 [#1]\n CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G T 6.18.0-rc2-00031-gec7f31b2a2d3 #1 NONE a1d066dfe789f54bc7645c7989957d2bdee593ca\n Tainted: [T]=RANDSTRUCT\n Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n EIP: memset (arch/x86/include/asm/string_32.h:168 arch/x86/lib/memcpy_32.c:17)\n Code: a5 8b 4d f4 83 e1 03 74 02 f3 a4 83 c4 04 5e 5f 5d 2e e9 73 41 01 00 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c6 89 d0 89 f7 \u0026lt;f3\u0026gt; aa 89 f0 5e 5f 5d 2e e9 53 41 01 00 cc cc cc 55 89 e5 53 57 56\n EAX: 0000006b EBX: 00000015 ECX: 001fefff EDX: 0000006b\n ESI: fffb9000 EDI: fffba000 EBP: c611fbf0 ESP: c611fbe8\n DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010287\n CR0: 80050033 CR2: fffba000 CR3: 0316e000 CR4: 00040690\n Call Trace:\n poison_element (mm/mempool.c:83 mm/mempool.c:102)\n mempool_init_node (mm/mempool.c:142 mm/mempool.c:226)\n mempool_init_noprof (mm/mempool.c:250 (discriminator 1))\n ? mempool_alloc_pages (mm/mempool.c:640)\n bio_integrity_initfn (block/bio-integrity.c:483 (discriminator 8))\n ? mempool_alloc_pages (mm/mempool.c:640)\n do_one_initcall (init/main.c:1283)\n\nChristoph found out this is due to the poisoning code not dealing\nproperly with CONFIG_HIGHMEM because only the first page is mapped but\nthen the whole potentially high-order page is accessed.\n\nWe could give up on HIGHMEM here, but it\u0026apos;s straightforward to fix this\nwith a loop that\u0026apos;s mapping, poisoning or checking and unmapping\nindividual pages.(CVE-2025-68231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtdchar: fix integer overflow in read/write ioctls\n\nThe \u0026quot;req.start\u0026quot; and \u0026quot;req.len\u0026quot; variables are u64 values that come from the\nuser at the start of the function. We mask away the high 32 bits of\n\u0026quot;req.len\u0026quot; so that\u0026apos;s capped at U32_MAX but the \u0026quot;req.start\u0026quot; variable can go\nup to U64_MAX which means that the addition can still integer overflow.\n\nUse check_add_overflow() to fix this bug.(CVE-2025-68237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u0026gt;work\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\u0026quot;usb: gadget: core: flush gadget workqueue after\ndevice removal\u0026quot;) attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget\u0026apos;s memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a \u0026apos;teardown\u0026apos;\nflag and a \u0026apos;state_lock\u0026apos; spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.(CVE-2025-68282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: fix NULL pointer deference when splitting folio\n\nCommit c010d47f107f (\u0026quot;mm: thp: split huge page to any lower order pages\u0026quot;)\nintroduced an early check on the folio\u0026apos;s order via mapping-\u0026gt;flags before\nproceeding with the split work.\n\nThis check introduced a bug: for shmem folios in the swap cache and\ntruncated folios, the mapping pointer can be NULL. Accessing\nmapping-\u0026gt;flags in this state leads directly to a NULL pointer dereference.\n\nThis commit fixes the issue by moving the check for mapping != NULL before\nany attempt to access mapping-\u0026gt;flags.(CVE-2025-68293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU/AMD: Add RDSEED fix for Zen5\n\nThere\u0026apos;s an issue with RDSEED\u0026apos;s 16-bit and 32-bit register output\nvariants on Zen5 which return a random value of 0 \u0026quot;at a rate inconsistent\nwith randomness while incorrectly signaling success (CF=1)\u0026quot;. Search the\nweb for AMD-SB-7055 for more detail.\n\nAdd a fix glue which checks microcode revisions.\n\n [ bp: Add microcode revisions checking, rewrite. ](CVE-2025-68313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninet: frags: flush pending skbs in fqdir_pre_exit()\n\nWe have been seeing occasional deadlocks on pernet_ops_rwsem since\nSeptember in NIPA. The stuck task was usually modprobe (often loading\na driver like ipvlan), trying to take the lock as a Writer.\nlockdep does not track readers for rwsems so the read wasn\u0026apos;t obvious\nfrom the reports.\n\nOn closer inspection the Reader holding the lock was conntrack looping\nforever in nf_conntrack_cleanup_net_list(). Based on past experience\nwith occasional NIPA crashes I looked thru the tests which run before\nthe crash and noticed that the crash follows ip_defrag.sh. An immediate\nred flag. Scouring thru (de)fragmentation queues reveals skbs sitting\naround, holding conntrack references.\n\nThe problem is that since conntrack depends on nf_defrag_ipv6,\nnf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its\nnetns exit hooks run _after_ conntrack\u0026apos;s netns exit hook.\n\nFlush all fragment queue SKBs during fqdir_pre_exit() to release\nconntrack references before conntrack cleanup runs. Also flush\nthe queues in timer expiry handlers when they discover fqdir-\u0026gt;dead\nis set, in case packet sneaks in while we\u0026apos;re running the pre_exit\nflush.\n\nThe commit under Fixes is not exactly the culprit, but I think\npreviously the timer firing would eventually unblock the spinning\nconntrack.(CVE-2025-68768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix middle attribute validation in push_nsh() action\n\nThe push_nsh() action structure looks like this:\n\n OVS_ACTION_ATTR_PUSH_NSH(OVS_KEY_ATTR_NSH(OVS_NSH_KEY_ATTR_BASE,...))\n\nThe outermost OVS_ACTION_ATTR_PUSH_NSH attribute is OK\u0026apos;ed by the\nnla_for_each_nested() inside __ovs_nla_copy_actions(). The innermost\nOVS_NSH_KEY_ATTR_BASE/MD1/MD2 are OK\u0026apos;ed by the nla_for_each_nested()\ninside nsh_key_put_from_nlattr(). But nothing checks if the attribute\nin the middle is OK. We don\u0026apos;t even check that this attribute is the\nOVS_KEY_ATTR_NSH. We just do a double unwrap with a pair of nla_data()\ncalls - first time directly while calling validate_push_nsh() and the\nsecond time as part of the nla_for_each_nested() macro, which isn\u0026apos;t\nsafe, potentially causing invalid memory access if the size of this\nattribute is incorrect. The failure may not be noticed during\nvalidation due to larger netlink buffer, but cause trouble later during\naction execution where the buffer is allocated exactly to the size:\n\n BUG: KASAN: slab-out-of-bounds in nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n Read of size 184 at addr ffff88816459a634 by task a.out/22624\n\n CPU: 8 UID: 0 PID: 22624 6.18.0-rc7+ #115 PREEMPT(voluntary)\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x51/0x70\n print_address_description.constprop.0+0x2c/0x390\n kasan_report+0xdd/0x110\n kasan_check_range+0x35/0x1b0\n __asan_memcpy+0x20/0x60\n nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n push_nsh+0x82/0x120 [openvswitch]\n do_execute_actions+0x1405/0x2840 [openvswitch]\n ovs_execute_actions+0xd5/0x3b0 [openvswitch]\n ovs_packet_cmd_execute+0x949/0xdb0 [openvswitch]\n genl_family_rcv_msg_doit+0x1d6/0x2b0\n genl_family_rcv_msg+0x336/0x580\n genl_rcv_msg+0x9f/0x130\n netlink_rcv_skb+0x11f/0x370\n genl_rcv+0x24/0x40\n netlink_unicast+0x73e/0xaa0\n netlink_sendmsg+0x744/0xbf0\n __sys_sendto+0x3d6/0x450\n do_syscall_64+0x79/0x2c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n \u0026lt;/TASK\u0026gt;\n\nLet\u0026apos;s add some checks that the attribute is properly sized and it\u0026apos;s\nthe only one attribute inside the action. Technically, there is no\nreal reason for OVS_KEY_ATTR_NSH to be there, as we know that we\u0026apos;re\npushing an NSH header already, it just creates extra nesting, but\nthat\u0026apos;s how uAPI works today. So, keeping as it is.(CVE-2025-68785)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: alps - fix use-after-free bugs caused by dev3_register_work\n\nThe dev3_register_work delayed work item is initialized within\nalps_reconnect() and scheduled upon receipt of the first bare\nPS/2 packet from an external PS/2 device connected to the ALPS\ntouchpad. During device detachment, the original implementation\ncalls flush_workqueue() in psmouse_disconnect() to ensure\ncompletion of dev3_register_work. However, the flush_workqueue()\nin psmouse_disconnect() only blocks and waits for work items that\nwere already queued to the workqueue prior to its invocation. Any\nwork items submitted after flush_workqueue() is called are not\nincluded in the set of tasks that the flush operation awaits.\nThis means that after flush_workqueue() has finished executing,\nthe dev3_register_work could still be scheduled. Although the\npsmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(),\nthe scheduling of dev3_register_work remains unaffected.\n\nThe race condition can occur as follows:\n\nCPU 0 (cleanup path) | CPU 1 (delayed work)\npsmouse_disconnect() |\n psmouse_set_state() |\n flush_workqueue() | alps_report_bare_ps2_packet()\n alps_disconnect() | psmouse_queue_work()\n kfree(priv); // FREE | alps_register_bare_ps2_mouse()\n | priv = container_of(work...); // USE\n | priv-\u0026gt;dev3 // USE\n\nAdd disable_delayed_work_sync() in alps_disconnect() to ensure\nthat dev3_register_work is properly canceled and prevented from\nexecuting after the alps_data structure has been deallocated.\n\nThis bug is identified by static analysis.(CVE-2025-68822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential deadlock\n\nAs Jiaming Zhang and syzbot reported, there is potential deadlock in\nf2fs as below:\n\nChain exists of:\n \u0026amp;sbi-\u0026gt;cp_rwsem --\u0026gt; fs_reclaim --\u0026gt; sb_internal#2\n\n Possible unsafe locking scenario:\n\n CPU0 CPU1\n ---- ----\n rlock(sb_internal#2);\n lock(fs_reclaim);\n lock(sb_internal#2);\n rlock(\u0026amp;sbi-\u0026gt;cp_rwsem);\n\n *** DEADLOCK ***\n\n3 locks held by kswapd0/73:\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197\n #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890\n\nstack backtrace:\nCPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043\n check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175\n check_prev_add kernel/locking/lockdep.c:3165 [inline]\n check_prevs_add kernel/locking/lockdep.c:3284 [inline]\n validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908\n __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237\n lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868\n down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537\n f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]\n f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]\n f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791\n f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867\n f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925\n f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897\n evict+0x504/0x9c0 fs/inode.c:810\n f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853\n evict+0x504/0x9c0 fs/inode.c:810\n dispose_list fs/inode.c:852 [inline]\n prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000\n super_cache_scan+0x39b/0x4b0 fs/super.c:224\n do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437\n shrink_slab_memcg mm/shrinker.c:550 [inline]\n shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628\n shrink_one+0x28a/0x7c0 mm/vmscan.c:4955\n shrink_many mm/vmscan.c:5016 [inline]\n lru_gen_shrink_node mm/vmscan.c:5094 [inline]\n shrink_node+0x315d/0x3780 mm/vmscan.c:6081\n kswapd_shrink_node mm/vmscan.c:6941 [inline]\n balance_pgdat mm/vmscan.c:7124 [inline]\n kswapd+0x147c/0x2800 mm/vmscan.c:7389\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is deadlock among four locks as below:\n\nkswapd\n- fs_reclaim\t\t\t\t--- Lock A\n - shrink_one\n - evict\n - f2fs_evict_inode\n - sb_start_intwrite\t\t\t--- Lock B\n\n- iput\n - evict\n - f2fs_evict_inode\n - sb_start_intwrite\t\t\t--- Lock B\n - f2fs_truncate\n - f2fs_truncate_blocks\n - f2fs_do_truncate_blocks\n - f2fs_lock_op\t\t\t--- Lock C\n\nioctl\n- f2fs_ioc_commit_atomic_write\n - f2fs_lock_op\t\t\t\t--- Lock C\n - __f2fs_commit_atomic_write\n - __replace_atomic_write_block\n - f2fs_get_dnode_of_data\n - __get_node_folio\n - f2fs_check_nid_range\n - f2fs_handle_error\n - f2fs_record_errors\n - f2fs_down_write\t\t--- Lock D\n\nopen\n- do_open\n - do_truncate\n - security_inode_need_killpriv\n - f2fs_getxattr\n - lookup_all_xattrs\n - f2fs_handle_error\n - f2fs_record_errors\n - f2fs_down_write\t\t--- Lock D\n - f2fs_commit_super\n - read_mapping_folio\n - filemap_alloc_folio_noprof\n - prepare_alloc_pages\n - fs_reclaim_acquire\t--- Lock A\n\nIn order to a\n---truncated---(CVE-2025-71065)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: Avoid NULL pointer deref for evicted BOs\n\nIt is possible for a BO to exist that is not currently associated with a\nresource, e.g. because it has been evicted.\n\nWhen devcoredump tries to read the contents of all BOs for dumping, we need\nto expect this as well -- in this case, ENODATA is recorded instead of the\nbuffer contents.(CVE-2025-71083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n GID entry ref leak for dev syz1 index 2 ref=573\n WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS: 00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n -\u0026gt; team_port_disable()\n -\u0026gt; team_queue_override_port_del()\n -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n -\u0026gt; team_queue_override_port_prio_changed()\n -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly\n\nThe netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a\nLS_NLA_TYPE_DGID attribute, it is invalid if it does not.\n\nUse the nl parsing logic properly and call nla_parse_deprecated() to fill\nthe nlattrs array and then directly index that array to get the data for\nthe DGID. Just fail if it is NULL.\n\nRemove the for loop searching for the nla, and squash the validation and\nparsing into one function.\n\nFixes an uninitialized read from the stack triggered by userspace if it\ndoes not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE\nquery.\n\n BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline]\n BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n hex_byte_pack include/linux/hex.h:13 [inline]\n ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509\n ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633\n pointer+0xc09/0x1bd0 lib/vsprintf.c:2542\n vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930\n vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279\n vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426\n vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465\n vprintk+0x36/0x50 kernel/printk/printk_safe.c:82\n _printk+0x17e/0x1b0 kernel/printk/printk.c:2475\n ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline]\n ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141\n rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline]\n rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:714 [inline]\n __sock_sendmsg+0x333/0x3d0 net/socket.c:729\n ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617\n ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671\n __sys_sendmsg+0x1aa/0x300 net/socket.c:2703\n __compat_sys_sendmsg net/compat.c:346 [inline]\n __do_compat_sys_sendmsg net/compat.c:353 [inline]\n __se_compat_sys_sendmsg net/compat.c:350 [inline]\n __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350\n ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371\n do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306\n do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331\n do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3(CVE-2025-71096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: Fix reference count leak when using error routes with nexthop objects\n\nWhen a nexthop object is deleted, it is marked as dead and then\nfib_table_flush() is called to flush all the routes that are using the\ndead nexthop.\n\nThe current logic in fib_table_flush() is to only flush error routes\n(e.g., blackhole) when it is called as part of network namespace\ndismantle (i.e., with flush_all=true). Therefore, error routes are not\nflushed when their nexthop object is deleted:\n\n # ip link add name dummy1 up type dummy\n # ip nexthop add id 1 dev dummy1\n # ip route add 198.51.100.1/32 nhid 1\n # ip route add blackhole 198.51.100.2/32 nhid 1\n # ip nexthop del id 1\n # ip route show\n blackhole 198.51.100.2 nhid 1 dev dummy1\n\nAs such, they keep holding a reference on the nexthop object which in\nturn holds a reference on the nexthop device, resulting in a reference\ncount leak:\n\n # ip link del dev dummy1\n [ 70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2\n\nFix by flushing error routes when their nexthop is marked as dead.\n\nIPv6 does not suffer from this problem.(CVE-2025-71097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Avoid walking the Namespace if start_node is NULL\n\nAlthough commit 0c9992315e73 (\u0026quot;ACPICA: Avoid walking the ACPI Namespace\nif it is not there\u0026quot;) fixed the situation when both start_node and\nacpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed\non Honor Magicbook 14 Pro [1].\n\nThat happens due to the access to the member of parent_node in\nacpi_ns_get_next_node(). The NULL pointer dereference will always\nhappen, no matter whether or not the start_node is equal to\nACPI_ROOT_OBJECT, so move the check of start_node being NULL\nout of the if block.\n\nUnfortunately, all the attempts to contact Honor have failed, they\nrefused to provide any technical support for Linux.\n\nThe bad DSDT table\u0026apos;s dump could be found on GitHub [2].\n\nDMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025\n\n[ rjw: Subject adjustment, changelog edits ](CVE-2025-71118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Sign extend kfunc call arguments\n\nThe kfunc calls are native calls so they should follow LoongArch calling\nconventions. Sign extend its arguments properly to avoid kernel panic.\nThis is done by adding a new emit_abi_ext() helper. The emit_abi_ext()\nhelper performs extension in place meaning a value already store in the\ntarget register (Note: this is different from the existing sign_extend()\nhelper and thus we can\u0026apos;t reuse it).(CVE-2025-71129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tilcdc: Fix removal actions in case of failed probe\n\nThe drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers\nshould only be called when the device has been successfully registered.\nCurrently, these functions are called unconditionally in tilcdc_fini(),\nwhich causes warnings during probe deferral scenarios.\n\n[ 7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68\n...\n[ 8.005820] drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108\n[ 8.005858] drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8\n[ 8.005885] drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144\n[ 8.005911] drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc]\n[ 8.005957] tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]\n\nFix this by rewriting the failed probe cleanup path using the standard\ngoto error handling pattern, which ensures that cleanup functions are\nonly called on successfully initialized resources. Additionally, remove\nthe now-unnecessary is_registered flag.(CVE-2025-71141)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: stm32: dmamux: fix device leak on route allocation\n\nMake sure to drop the reference taken when looking up the DMA mux\nplatform device during route allocation.\n\nNote that holding a reference to a device does not prevent its driver\ndata from going away so there is no point in keeping the reference.(CVE-2025-71186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()\n\nWhen ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().(CVE-2025-71220)\n\nIn the Linux kernel, a race condition vulnerability exists in the mmp_pdma driver. The vulnerability occurs in the mmp_pdma_residue() function which lacks proper locking mechanisms, potentially leading to use-after-free issues when accessing descriptor lists and descriptor contents.\n\nThe race condition occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors. This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan \u0026gt; 1).\n\nThe fix involves protecting the chain_running list iteration and descriptor access with the chan-\u0026gt;desc_lock spinlock.(CVE-2025-71221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: fix refcount leak in smb2_open()\n\nWhen ksmbd_vfs_getattr() fails, the reference count of ksmbd_file\nmust be released.(CVE-2025-71223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u0026gt;r1bio_pool) and conf-\u0026gt;raid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u0026gt;raid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too.(CVE-2025-71225)\n\nIn the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Free sp in error path to fix system crash System crash seen during load/unload test in a loop, [61110.449331] qla2xxx [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494](CVE-2025-71232)\n\nIn the Linux kernel, there is a race condition vulnerability in the SCSI qla2xxx driver. System crash was observed during load/unload loop testing. The root cause was a memory free operation occurring in interrupt context. When device discovery/fabric scan was in progress and module unload was issued setting the UNLOADING flag, work queue items could not be allocated and mapped memory had to be freed in interrupt context, leading to system crash.(CVE-2025-71235)\n\nA NULL pointer dereference vulnerability exists in the SCSI qla2xxx driver subsystem of the Linux kernel. When the system attempts to free associated memory in the qla_fab_async_scan function, it fails to validate whether the sp pointer is NULL, leading to kernel NULL pointer dereference and system crashes. This vulnerability can be exploited by attackers to cause denial of service.(CVE-2025-71236)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sock: fix hardened usercopy panic in sock_recv_errqueue\n\nskbuff_fclone_cache was created without defining a usercopy region,\n[1] unlike skbuff_head_cache which properly whitelists the cb[] field.\n[2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is\nenabled and the kernel attempts to copy sk_buff.cb data to userspace\nvia sock_recv_errqueue() -\u0026gt; put_cmsg().\n\nThe crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()\n (from skbuff_fclone_cache) [1]\n2. The skb is cloned via skb_clone() using the pre-allocated fclone\n[3] 3. The cloned skb is queued to sk_error_queue for timestamp\nreporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)\n5. sock_recv_errqueue() calls put_cmsg() to copy serr-\u0026gt;ee from skb-\u0026gt;cb\n[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no\n usercopy whitelist [5]\n\nWhen cloned skbs allocated from skbuff_fclone_cache are used in the\nsocket error queue, accessing the sock_exterr_skb structure in skb-\u0026gt;cb\nvia put_cmsg() triggers a usercopy hardening violation:\n\n[ 5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object \u0026apos;skbuff_fclone_cache\u0026apos; (offset 296, size 16)!\n[ 5.382796] kernel BUG at mm/usercopy.c:102!\n[ 5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n[ 5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7\n[ 5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[ 5.384903] RIP: 0010:usercopy_abort+0x6c/0x80\n[ 5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff \u0026lt;0f\u0026gt; 0b 490\n[ 5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246\n[ 5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74\n[ 5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0\n[ 5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74\n[ 5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001\n[ 5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00\n[ 5.384903] FS: 0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000\n[ 5.384903] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0\n[ 5.384903] PKRU: 55555554\n[ 5.384903] Call Trace:\n[ 5.384903] \u0026lt;TASK\u0026gt;\n[ 5.384903] __check_heap_object+0x9a/0xd0\n[ 5.384903] __check_object_size+0x46c/0x690\n[ 5.384903] put_cmsg+0x129/0x5e0\n[ 5.384903] sock_recv_errqueue+0x22f/0x380\n[ 5.384903] tls_sw_recvmsg+0x7ed/0x1960\n[ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 5.384903] ? schedule+0x6d/0x270\n[ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 5.384903] ? mutex_unlock+0x81/0xd0\n[ 5.384903] ? __pfx_mutex_unlock+0x10/0x10\n[ 5.384903] ? __pfx_tls_sw_recvmsg+0x10/0x10\n[ 5.384903] ? _raw_spin_lock_irqsave+0x8f/0xf0\n[ 5.384903] ? _raw_read_unlock_irqrestore+0x20/0x40\n[ 5.384903] ? srso_alias_return_thunk+0x5/0xfbef5\n\nThe crash offset 296 corresponds to skb2-\u0026gt;cb within skbuff_fclones:\n - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -\n offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 =\n 272 + 24 (inside sock_exterr_skb.ee)\n\nThis patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.\n\n[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885\n[2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104\n[3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566\n[4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491\n[5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719(CVE-2026-22977)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix memory leak in skb_segment_list for GRO packets\n\nWhen skb_segment_list() is called during packet forwarding, it handles\npackets that were aggregated by the GRO engine.\n\nHistorically, the segmentation logic in skb_segment_list assumes that\nindividual segments are split from a parent SKB and may need to carry\ntheir own socket memory accounting. Accordingly, the code transfers\ntruesize from the parent to the newly created segments.\n\nPrior to commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;), this\ntruesize subtraction in skb_segment_list() was valid because fragments\nstill carry a reference to the original socket.\n\nHowever, commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;) changed\nthis behavior by ensuring that fraglist entries are explicitly\norphaned (skb-\u0026gt;sk = NULL) to prevent illegal orphaning later in the\nstack. This change meant that the entire socket memory charge remained\nwith the head SKB, but the corresponding accounting logic in\nskb_segment_list() was never updated.\n\nAs a result, the current code unconditionally adds each fragment\u0026apos;s\ntruesize to delta_truesize and subtracts it from the parent SKB. Since\nthe fragments are no longer charged to the socket, this subtraction\nresults in an effective under-count of memory when the head is freed.\nThis causes sk_wmem_alloc to remain non-zero, preventing socket\ndestruction and leading to a persistent memory leak.\n\nThe leak can be observed via KMEMLEAK when tearing down the networking\nenvironment:\n\nunreferenced object 0xffff8881e6eb9100 (size 2048):\n comm \u0026quot;ping\u0026quot;, pid 6720, jiffies 4295492526\n backtrace:\n kmem_cache_alloc_noprof+0x5c6/0x800\n sk_prot_alloc+0x5b/0x220\n sk_alloc+0x35/0xa00\n inet6_create.part.0+0x303/0x10d0\n __sock_create+0x248/0x640\n __sys_socket+0x11b/0x1d0\n\nSince skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST\npackets constructed by GRO, the truesize adjustment is removed.\n\nThe call to skb_release_head_state() must be preserved. As documented in\ncommit cf673ed0e057 (\u0026quot;net: fix fraglist segmentation reference count\nleak\u0026quot;), it is still required to correctly drop references to SKB\nextensions that may be overwritten during __copy_skb_header().(CVE-2026-22979)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in handle_auth_done()\n\nPerform an explicit bounds check on payload_len to avoid a possible\nout-of-bounds access in the callout.\n\n[ idryomov: changelog ](CVE-2026-22984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make free_choose_arg_map() resilient to partial allocation\n\nfree_choose_arg_map() may dereference a NULL pointer if its caller fails\nafter a partial allocation.\n\nFor example, in decode_choose_args(), if allocation of arg_map-\u0026gt;args\nfails, execution jumps to the fail label and free_choose_arg_map() is\ncalled. Since arg_map-\u0026gt;size is updated to a non-zero value before memory\nallocation, free_choose_arg_map() will iterate over arg_map-\u0026gt;args and\ndereference a NULL pointer.\n\nTo prevent this potential NULL pointer dereference and make\nfree_choose_arg_map() more resilient, add checks for pointers before\niterating.(CVE-2026-22991)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: do not free existing class in qfq_change_class()\n\nFixes qfq_change_class() error case.\n\ncl-\u0026gt;qdisc and cl should only be freed if a new class and qdisc\nwere allocated, or we risk various UAF.(CVE-2026-22999)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n\nBlamed commit did not take care of VLAN encapsulations\nas spotted by syzbot [1].\n\nUse skb_vlan_inet_prepare() instead of pskb_inet_may_pull().\n\n[1]\n BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729\n __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860\n ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903\n gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1\n ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438\n ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489\n NF_HOOK include/linux/netfilter.h:318 [inline]\n ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500\n ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590\n dst_input include/net/dst.h:474 [inline]\n ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79\n NF_HOOK include/linux/netfilter.h:318 [inline]\n ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311\n __netif_receive_skb_one_core net/core/dev.c:6139 [inline]\n __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252\n netif_receive_skb_internal net/core/dev.c:6338 [inline]\n netif_receive_skb+0x57/0x630 net/core/dev.c:6397\n tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485\n tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953\n tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n new_sync_write fs/read_write.c:593 [inline]\n vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n ksys_write fs/read_write.c:738 [inline]\n __do_sys_write fs/read_write.c:749 [inline]\n __se_sys_write fs/read_write.c:746 [inline]\n __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n slab_post_alloc_hook mm/slub.c:4960 [inline]\n slab_alloc_node mm/slub.c:5263 [inline]\n kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315\n kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586\n __alloc_skb+0x805/0x1040 net/core/skbuff.c:690\n alloc_skb include/linux/skbuff.h:1383 [inline]\n alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712\n sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995\n tun_alloc_skb drivers/net/tun.c:1461 [inline]\n tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794\n tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n new_sync_write fs/read_write.c:593 [inline]\n vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n ksys_write fs/read_write.c:738 [inline]\n __do_sys_write fs/read_write.c:749 [inline]\n __se_sys_write fs/read_write.c:746 [inline]\n __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025(CVE-2026-23003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix use-after-free in inet6_addr_del().\n\nsyzbot reported use-after-free of inet6_ifaddr in\ninet6_addr_del(). [0]\n\nThe cited commit accidentally moved ipv6_del_addr() for\nmngtmpaddr before reading its ifp-\u0026gt;flags for temporary\naddresses in inet6_addr_del().\n\nLet\u0026apos;s move ipv6_del_addr() down to fix the UAF.\n\n[0]:\nBUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\nRead of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593\n\nCPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\n addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181\n inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f164cf8f749\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749\nRDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003\nRBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 9593:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n poison_kmalloc_redzone mm/kasan/common.c:397 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414\n kmalloc_noprof include/linux/slab.h:957 [inline]\n kzalloc_noprof include/linux/slab.h:1094 [inline]\n ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120\n inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050\n addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160\n inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 6099:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584\n poison_slab_object mm/kasan/common.c:252 [inline]\n __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284\n kasan_slab_free include/linux/kasan.h:234 [inline]\n slab_free_hook mm/slub.c:2540 [inline]\n slab_free_freelist_hook mm/slub.c:2569 [inline]\n slab_free_bulk mm/slub.c:6696 [inline]\n kmem_cache_free_bulk mm/slub.c:7383 [inline]\n kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362\n kfree_bulk include/linux/slab.h:830 [inline]\n kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523\n kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline]\n kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801\n process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257\n process_scheduled_works kernel/workqu\n---truncated---(CVE-2026-23010)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: fix memory leak in update_eth_regs_async()\n\nWhen asynchronously writing to the device registers and if usb_submit_urb()\nfail, the code fail to release allocated to this point resources.(CVE-2026-23021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT 8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n __dump_stack (lib/dump_stack.c:95)\n dump_stack_lvl (lib/dump_stack.c:123)\n dump_stack (lib/dump_stack.c:130)\n spin_dump (kernel/locking/spinlock_debug.c:71)\n do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n __free_frozen_pages (mm/page_alloc.c:2973)\n ___free_pages (mm/page_alloc.c:5295)\n __free_pages (mm/page_alloc.c:5334)\n tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n ? rcu_core (kernel/rcu/tree.c:?)\n rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n rcu_core_si (kernel/rcu/tree.c:2879)\n handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n irq_exit_rcu (kernel/softirq.c:741)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n free_pcppages_bulk (mm/page_alloc.c:1494)\n drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n __drain_all_pages (mm/page_alloc.c:2731)\n drain_all_pages (mm/page_alloc.c:2747)\n kcompactd (mm/compaction.c:3115)\n kthread (kernel/kthread.c:465)\n ? __cfi_kcompactd (mm/compaction.c:3166)\n ? __cfi_kthread (kernel/kthread.c:412)\n ret_from_fork (arch/x86/kernel/process.c:164)\n ? __cfi_kthread (kernel/kthread.c:412)\n ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock. The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback. However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op. Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;). The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized. Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix kmemleak by releasing references to fault configfs items\n\nWhen CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk\ndriver sets up fault injection support by creating the timeout_inject,\nrequeue_inject, and init_hctx_fault_inject configfs items as children\nof the top-level nullbX configfs group.\n\nHowever, when the nullbX device is removed, the references taken to\nthese fault-config configfs items are not released. As a result,\nkmemleak reports a memory leak, for example:\n\nunreferenced object 0xc00000021ff25c40 (size 32):\n comm \u0026quot;mkdir\u0026quot;, pid 10665, jiffies 4322121578\n hex dump (first 32 bytes):\n 69 6e 69 74 5f 68 63 74 78 5f 66 61 75 6c 74 5f init_hctx_fault_\n 69 6e 6a 65 63 74 00 88 00 00 00 00 00 00 00 00 inject..........\n backtrace (crc 1a018c86):\n __kmalloc_node_track_caller_noprof+0x494/0xbd8\n kvasprintf+0x74/0xf4\n config_item_set_name+0xf0/0x104\n config_group_init_type_name+0x48/0xfc\n fault_config_init+0x48/0xf0\n 0xc0080000180559e4\n configfs_mkdir+0x304/0x814\n vfs_mkdir+0x49c/0x604\n do_mkdirat+0x314/0x3d0\n sys_mkdir+0xa0/0xd8\n system_call_exception+0x1b0/0x4f0\n system_call_vectored_common+0x15c/0x2ec\n\nFix this by explicitly releasing the references to the fault-config\nconfigfs items when dropping the reference to the top-level nullbX\nconfigfs group.(CVE-2026-23032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u0026gt;paused, not just clear it\n\nCurrently calc_target() clears t-\u0026gt;paused if the request shouldn\u0026apos;t be\npaused anymore, but doesn\u0026apos;t ever set t-\u0026gt;paused even though it\u0026apos;s able to\ndetermine when the request should be paused. Setting t-\u0026gt;paused is left\nto __submit_request() which is fine for regular requests but doesn\u0026apos;t\nwork for linger requests -- since __submit_request() doesn\u0026apos;t operate\non linger requests, there is nowhere for lreq-\u0026gt;t.paused to be set.\nOne consequence of this is that watches don\u0026apos;t get reestablished on\npaused -\u0026gt; unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state. On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u0026gt;watch_mutex held:\n\n rbd_register_watch\n __rbd_register_watch\n ceph_osdc_watch\n linger_reg_commit_wait\n\nIt\u0026apos;s waiting for lreq-\u0026gt;reg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused. There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u0026gt;watch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \u0026quot;rbd unmap\u0026quot; would inevitably\nhang in D state on an attempt to grab the mutex.(CVE-2026-23047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix a deadlock when returning a delegation during open()\n\nBen Coddington reports seeing a hang in the following stack trace:\n 0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415\n 1 [ffffd0b50e177548] schedule at ffffffff9ca05717\n 2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1\n 3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb\n 4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5\n 5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]\n 6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]\n 7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]\n 8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]\n 9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]\n 10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]\n 11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]\n 12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]\n 13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]\n 14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]\n 15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]\n 16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]\n 17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea\n 18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e\n 19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935\n\nThe issue is that the delegreturn is being asked to wait for a layout\nreturn that cannot complete because a state recovery was initiated. The\nstate recovery cannot complete until the open() finishes processing the\ndelegations it was given.\n\nThe solution is to propagate the existing flags that indicate a\nnon-blocking call to the function pnfs_roc(), so that it knows not to\nwait in this situation.(CVE-2026-23050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nA buffer overflow vulnerability exists in the QLogic Fibre Channel driver (qla2xxx) of the Linux kernel. In the functions `qla27xx_copy_fpin_pkt()` and `qla27xx_copy_multiple_pkt()`, the code uses the firmware-reported `frame_size` to calculate the copy length into `item-\u0026gt;iocb`. However, the `iocb` member is defined as a fixed-size 64-byte array within `struct purex_item`. If the reported `frame_size` exceeds 64 bytes, subsequent `memcpy` calls will overflow the boundary of the `iocb` member. This cross-member write is unsafe and can lead to memory corruption, potentially exploitable to compromise the confidentiality, integrity, and availability of the kernel.(CVE-2026-23059)\n\nA NULL pointer dereference vulnerability exists in the be2net network driver within the Linux kernel, specifically in the be_cmd_get_mac_from_list() function. According to the function\u0026apos;s contract, when the parameter pmac_id_valid is set to false, the driver may request a PMAC_ID from the network card\u0026apos;s firmware and store it at the provided address pmac_id. However, there is a location within the driver where both conditions pmac_id_valid == false and pmac_id == NULL are passed simultaneously. This results in an attempt to dereference a NULL pointer, potentially leading to a kernel crash or system instability.(CVE-2026-23084)\n\nA memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the \u0026apos;itt\u0026apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit \u0026apos;unsigned long\u0026apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix isolate sysfs check condition\n\nuacce supports the device isolation feature. If the driver\nimplements the isolate_err_threshold_read and\nisolate_err_threshold_write callback functions, uacce will create\nsysfs files now. Users can read and configure the isolation policy\nthrough sysfs. Currently, sysfs files are created as long as either\nisolate_err_threshold_read or isolate_err_threshold_write callback\nfunctions are present.\n\nHowever, accessing a non-existent callback function may cause the\nsystem to crash. Therefore, intercept the creation of sysfs if\nneither read nor write exists; create sysfs if either is supported,\nbut intercept unsupported operations at the call site.(CVE-2026-23094)\n\nA deadlock vulnerability exists in the Linux kernel due to incorrect lock acquisition ordering. This vulnerability affects the migration functionality for hugetlb (huge page) file folios. The specific scenario is: when two kernel tasks (Tasks) attempt to acquire the `folio_lock` and `i_mmap_rwsem` locks in opposite orders, a circular wait is formed, leading to a system deadlock. For example, Task A holds `folio_lock` and then tries to acquire the `i_mmap_rwsem` read lock, while Task B holds the `i_mmap_rwsem` write lock and then tries to acquire `folio_lock`. This lock ordering violates the rules defined in mm/rmap.c. This vulnerability can render parts of the affected system unavailable, impacting system availability.(CVE-2026-23097)\n\nIn the Linux kernel SCSI core layer, there is a fragile ordering logic between marking commands as completed or failed, designed to ensure the error handler only wakes when the last running command completes or times out. This logic contains race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. Specifically, there are two issues: 1. A memory ordering issue within the `scsi_dec_host_busy()` function. The write operation that clears the `SCMD_STATE_INFLIGHT` flag may be reordered with read counting operations in `scsi_host_busy()`. This can cause other CPUs to see inconsistent busy counts, preventing the correct triggering of the error handler wake-up. 2. A general ordering issue with the `scsi_eh_inc_host_failed()` function. It counts busy commands before incrementing the `host_failed` count, which can race with the processing of a final command in `scsi_dec_host_busy()`, resulting in neither side waking the error handler task.(CVE-2026-23110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec\n\nnvmet_tcp_build_pdu_iovec() could walk past cmd-\u0026gt;req.sg when a PDU\nlength or offset exceeds sg_cnt and then use bogus sg-\u0026gt;length/offset\nvalues, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining\nentries, and sg-\u0026gt;length/offset before building the bvec.(CVE-2026-23112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove\n\nOn APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and\nih2 interrupt ring buffers are not initialized. This is by design, as\nthese secondary IH rings are only available on discrete GPUs. See\nvega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when\nAMD_IS_APU is set.\n\nHowever, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to\nget the timestamp of the last interrupt entry. When retry faults are\nenabled on APUs (noretry=0), this function is called from the SVM page\nfault recovery path, resulting in a NULL pointer dereference when\namdgpu_ih_decode_iv_ts_helper() attempts to access ih-\u0026gt;ring[].\n\nThe crash manifests as:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000004\n RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]\n Call Trace:\n amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]\n svm_range_restore_pages+0xae5/0x11c0 [amdgpu]\n amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu]\n gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]\n amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu]\n amdgpu_ih_process+0x84/0x100 [amdgpu]\n\nThis issue was exposed by commit 1446226d32a4 (\u0026quot;drm/amdgpu: Remove GC HW\nIP 9.3.0 from noretry=1\u0026quot;) which changed the default for Renoir APU from\nnoretry=1 to noretry=0, enabling retry fault handling and thus\nexercising the buggy code path.\n\nFix this by adding a check for ih1.ring_size before attempting to use\nit. Also restore the soft_ih support from commit dd299441654f (\u0026quot;drm/amdgpu:\nRework retry fault removal\u0026quot;). This is needed if the hardware doesn\u0026apos;t\nsupport secondary HW IH rings.\n\nv2: additional updates (Alex)\n\n(cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)(CVE-2026-23163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()\n\nWhen the socket is closed while in TCP_LISTEN a callback is run to\nflush all outstanding packets, which in turns calls\nnvmet_tcp_listen_data_ready() with the sk_callback_lock held.\nSo we need to check if we are in TCP_LISTEN before attempting\nto get the sk_callback_lock() to avoid a deadlock.(CVE-2026-23179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: amd: fix memory leak in acp3x pdm dma ops(CVE-2026-23190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()\n\nIn iscsit_dec_session_usage_count(), the function calls complete() while\nholding the sess-\u0026gt;session_usage_lock. Similar to the connection usage count\nlogic, the waiter signaled by complete() (e.g., in the session release\npath) may wake up and free the iscsit_session structure immediately.\n\nThis creates a race condition where the current thread may attempt to\nexecute spin_unlock_bh() on a session structure that has already been\ndeallocated, resulting in a KASAN slab-use-after-free.\n\nTo resolve this, release the session_usage_lock before calling complete()\nto ensure all dereferences of the sess pointer are finished before the\nwaiter is allowed to proceed with deallocation.(CVE-2026-23193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: fix memory leak in smb2_open_file()\n\nReproducer:\n\n 1. server: directories are exported read-only\n 2. client: mount -t cifs //${server_ip}/export /mnt\n 3. client: dd if=/dev/zero of=/mnt/file bs=512 count=1000 oflag=direct\n 4. client: umount /mnt\n 5. client: sleep 1\n 6. client: modprobe -r cifs\n\nThe error message is as follows:\n\n =============================================================================\n BUG cifs_small_rq (Not tainted): Objects remaining on __kmem_cache_shutdown()\n -----------------------------------------------------------------------------\n\n Object 0x00000000d47521be @offset=14336\n ...\n WARNING: mm/slub.c:1251 at __kmem_cache_shutdown+0x34e/0x440, CPU#0: modprobe/1577\n ...\n Call Trace:\n \u0026lt;TASK\u0026gt;\n kmem_cache_destroy+0x94/0x190\n cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n cleanup_module+0x4e/0x540 [cifs]\n __se_sys_delete_module+0x278/0x400\n __x64_sys_delete_module+0x5f/0x70\n x64_sys_call+0x2299/0x2ff0\n do_syscall_64+0x89/0x350\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n ...\n kmem_cache_destroy cifs_small_rq: Slab cache still has objects when called from cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n WARNING: mm/slab_common.c:532 at kmem_cache_destroy+0x16b/0x190, CPU#0: modprobe/1577(CVE-2026-23205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)\n\nIn the Linux kernel, the ksmbd component contains an infinite loop vulnerability. The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() sets work-\u0026gt;next_smb2_rcv_hdr_off to zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header\u0026apos;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with \u0026quot;bad smb2 signature\u0026quot; messages and high CPU usage.(CVE-2026-23220)\n\nIn the Linux kernel, the following vulnerability has been resolved: smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection() On kthread_run() failure in ksmbd_tcp_new_connection(), the transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter. Replace free_transport() with ksmbd_tcp_disconnect(). The Linux kernel CVE team has assigned CVE-2026-23228 to this issue.(CVE-2026-23228)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:38.135892245Z","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-2582","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\nmISDN: hfcpci: Fix warning when deleting uninitialized timer\n\nWith CONFIG_DEBUG_OBJECTS_TIMERS unloading hfcpci module leads\nto the following splat:\n\n[ 250.215892] ODEBUG: assert_init not available (active state 0) object: ffffffffc01a3dc0 object type: timer_list hint: 0x0\n[ 250.217520] WARNING: CPU: 0 PID: 233 at lib/debugobjects.c:612 debug_print_object+0x1b6/0x2c0\n[ 250.218775] Modules linked in: hfcpci(-) mISDN_core\n[ 250.219537] CPU: 0 UID: 0 PID: 233 Comm: rmmod Not tainted 6.17.0-rc2-g6f713187ac98 #2 PREEMPT(voluntary)\n[ 250.220940] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[ 250.222377] RIP: 0010:debug_print_object+0x1b6/0x2c0\n[ 250.223131] Code: fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 4f 41 56 48 8b 14 dd a0 4e 01 9f 48 89 ee 48 c7 c7 20 46 01 9f e8 cb 84d\n[ 250.225805] RSP: 0018:ffff888015ea7c08 EFLAGS: 00010286\n[ 250.226608] RAX: 0000000000000000 RBX: 0000000000000005 RCX: ffffffff9be93a95\n[ 250.227708] RDX: 1ffff1100d945138 RSI: 0000000000000008 RDI: ffff88806ca289c0\n[ 250.228993] RBP: ffffffff9f014a00 R08: 0000000000000001 R09: ffffed1002bd4f39\n[ 250.230043] R10: ffff888015ea79cf R11: 0000000000000001 R12: 0000000000000001\n[ 250.231185] R13: ffffffff9eea0520 R14: 0000000000000000 R15: ffff888015ea7cc8\n[ 250.232454] FS: 00007f3208f01540(0000) GS:ffff8880caf5a000(0000) knlGS:0000000000000000\n[ 250.233851] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 250.234856] CR2: 00007f32090a7421 CR3: 0000000004d63000 CR4: 00000000000006f0\n[ 250.236117] Call Trace:\n[ 250.236599] \u0026lt;TASK\u0026gt;\n[ 250.236967] ? trace_irq_enable.constprop.0+0xd4/0x130\n[ 250.237920] debug_object_assert_init+0x1f6/0x310\n[ 250.238762] ? __pfx_debug_object_assert_init+0x10/0x10\n[ 250.239658] ? __lock_acquire+0xdea/0x1c70\n[ 250.240369] __try_to_del_timer_sync+0x69/0x140\n[ 250.241172] ? __pfx___try_to_del_timer_sync+0x10/0x10\n[ 250.242058] ? __timer_delete_sync+0xc6/0x120\n[ 250.242842] ? lock_acquire+0x30/0x80\n[ 250.243474] ? __timer_delete_sync+0xc6/0x120\n[ 250.244262] __timer_delete_sync+0x98/0x120\n[ 250.245015] HFC_cleanup+0x10/0x20 [hfcpci]\n[ 250.245704] __do_sys_delete_module+0x348/0x510\n[ 250.246461] ? __pfx___do_sys_delete_module+0x10/0x10\n[ 250.247338] do_syscall_64+0xc1/0x360\n[ 250.247924] entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFix this by initializing hfc_tl timer with DEFINE_TIMER macro.\nAlso, use mod_timer instead of manual timeout update.(CVE-2025-39833)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86/amd/pmc: Add support for Van Gogh SoC\n\nThe ROG Xbox Ally (non-X) SoC features a similar architecture to the\nSteam Deck. While the Steam Deck supports S3 (s2idle causes a crash),\nthis support was dropped by the Xbox Ally which only S0ix suspend.\n\nSince the handler is missing here, this causes the device to not suspend\nand the AMD GPU driver to crash while trying to resume afterwards due to\na power hang.(CVE-2025-68334)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: Move team device type change at the end of team_port_add\n\nAttempting to add a port device that is already up will expectedly fail,\nbut not before modifying the team device header_ops.\n\nIn the case of the syzbot reproducer the gre0 device is\nalready in state UP when it attempts to add it as a\nport device of team0, this fails but before that\nheader_ops-\u0026gt;create of team0 is changed from eth_header to ipgre_header\nin the call to team_dev_type_check_change.\n\nLater when we end up in ipgre_header() struct ip_tunnel* points to nonsense\nas the private data of the device still holds a struct team.\n\nExample sequence of iproute2 commands to reproduce the hang/BUG():\nip link add dev team0 type team\nip link add dev gre0 type gre\nip link set dev gre0 up\nip link set dev gre0 master team0\nip link set dev team0 up\nping -I team0 1.1.1.1\n\nMove team_dev_type_check_change down where all other checks have passed\nas it changes the dev type with no way to restore it in case\none of the checks that follow it fail.\n\nAlso make sure to preserve the origial mtu assignment:\n - If port_dev is not the same type as dev, dev takes mtu from port_dev\n - If port_dev is the same type as dev, port_dev takes mtu from dev\n\nThis is done by adding a conditional before the call to dev_set_mtu\nto prevent it from assigning port_dev-\u0026gt;mtu = dev-\u0026gt;mtu and instead\nletting team_dev_type_check_change assign dev-\u0026gt;mtu = port_dev-\u0026gt;mtu.\nThe conditional is needed because the patch moves the call to\nteam_dev_type_check_change past dev_set_mtu.\n\nTesting:\n - team device driver in-tree selftests\n - Add/remove various devices as slaves of team device\n - syzbot(CVE-2025-68340)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlxsw: spectrum_router: Fix neighbour use-after-free\n\nWe sometimes observe use-after-free when dereferencing a neighbour [1].\nThe problem seems to be that the driver stores a pointer to the\nneighbour, but without holding a reference on it. A reference is only\ntaken when the neighbour is used by a nexthop.\n\nFix by simplifying the reference counting scheme. Always take a\nreference when storing a neighbour pointer in a neighbour entry. Avoid\ntaking a referencing when the neighbour is used by a nexthop as the\nneighbour entry associated with the nexthop already holds a reference.\n\nTested by running the test that uncovered the problem over 300 times.\nWithout this patch the problem was reproduced after a handful of\niterations.\n\n[1]\nBUG: KASAN: slab-use-after-free in mlxsw_sp_neigh_entry_update+0x2d4/0x310\nRead of size 8 at addr ffff88817f8e3420 by task ip/3929\n\nCPU: 3 UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full)\nHardware name: Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xa0\n print_address_description.constprop.0+0x6e/0x300\n print_report+0xfc/0x1fb\n kasan_report+0xe4/0x110\n mlxsw_sp_neigh_entry_update+0x2d4/0x310\n mlxsw_sp_router_rif_gone_sync+0x35f/0x510\n mlxsw_sp_rif_destroy+0x1ea/0x730\n mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0\n __mlxsw_sp_inetaddr_lag_event+0xcc/0x130\n __mlxsw_sp_inetaddr_event+0xf5/0x3c0\n mlxsw_sp_router_netdevice_event+0x1015/0x1580\n notifier_call_chain+0xcc/0x150\n call_netdevice_notifiers_info+0x7e/0x100\n __netdev_upper_dev_unlink+0x10b/0x210\n netdev_upper_dev_unlink+0x79/0xa0\n vrf_del_slave+0x18/0x50\n do_set_master+0x146/0x7d0\n do_setlink.isra.0+0x9a0/0x2880\n rtnl_newlink+0x637/0xb20\n rtnetlink_rcv_msg+0x6fe/0xb90\n netlink_rcv_skb+0x123/0x380\n netlink_unicast+0x4a3/0x770\n netlink_sendmsg+0x75b/0xc90\n __sock_sendmsg+0xbe/0x160\n ____sys_sendmsg+0x5b2/0x7d0\n ___sys_sendmsg+0xfd/0x180\n __sys_sendmsg+0x124/0x1c0\n do_syscall_64+0xbb/0xfd0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n[...]\n\nAllocated by task 109:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7b/0x90\n __kmalloc_noprof+0x2c1/0x790\n neigh_alloc+0x6af/0x8f0\n ___neigh_create+0x63/0xe90\n mlxsw_sp_nexthop_neigh_init+0x430/0x7e0\n mlxsw_sp_nexthop_type_init+0x212/0x960\n mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280\n mlxsw_sp_nexthop6_group_get+0x392/0x6a0\n mlxsw_sp_fib6_entry_create+0x46a/0xfd0\n mlxsw_sp_router_fib6_replace+0x1ed/0x5f0\n mlxsw_sp_router_fib6_event_work+0x10a/0x2a0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nFreed by task 154:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_save_free_info+0x3b/0x60\n __kasan_slab_free+0x43/0x70\n kmem_cache_free_bulk.part.0+0x1eb/0x5e0\n kvfree_rcu_bulk+0x1f2/0x260\n kfree_rcu_work+0x130/0x1b0\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20\n\nLast potentially related work creation:\n kasan_save_stack+0x30/0x50\n kasan_record_aux_stack+0x8c/0xa0\n kvfree_call_rcu+0x93/0x5b0\n mlxsw_sp_router_neigh_event_work+0x67d/0x860\n process_one_work+0xd57/0x1390\n worker_thread+0x4d6/0xd40\n kthread+0x355/0x5b0\n ret_from_fork+0x1d4/0x270\n ret_from_fork_asm+0x11/0x20(CVE-2025-68801)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix off-by-one issues in iavf_config_rss_reg()\n\nThere are off-by-one bugs when configuring RSS hash key and lookup\ntable, causing out-of-bounds reads to memory [1] and out-of-bounds\nwrites to device registers.\n\nBefore commit 43a3d9ba34c9 (\u0026quot;i40evf: Allow PF driver to configure RSS\u0026quot;),\nthe loop upper bounds were:\n i \u0026lt;= I40E_VFQF_{HKEY,HLUT}_MAX_INDEX\nwhich is safe since the value is the last valid index.\n\nThat commit changed the bounds to:\n i \u0026lt;= adapter-\u0026gt;rss_{key,lut}_size / 4\nwhere `rss_{key,lut}_size / 4` is the number of dwords, so the last\nvalid index is `(rss_{key,lut}_size / 4) - 1`. Therefore, using `\u0026lt;=`\naccesses one element past the end.\n\nFix the issues by using `\u0026lt;` instead of `\u0026lt;=`, ensuring we do not exceed\nthe bounds.\n\n[1] KASAN splat about rss_key_size off-by-one\n BUG: KASAN: slab-out-of-bounds in iavf_config_rss+0x619/0x800\n Read of size 4 at addr ffff888102c50134 by task kworker/u8:6/63\n\n CPU: 0 UID: 0 PID: 63 Comm: kworker/u8:6 Not tainted 6.18.0-rc2-enjuk-tnguy-00378-g3005f5b77652-dirty #156 PREEMPT(voluntary)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n Workqueue: iavf iavf_watchdog_task\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xb0\n print_report+0x170/0x4f3\n kasan_report+0xe1/0x1a0\n iavf_config_rss+0x619/0x800\n iavf_watchdog_task+0x2be7/0x3230\n process_one_work+0x7fd/0x1420\n worker_thread+0x4d1/0xd40\n kthread+0x344/0x660\n ret_from_fork+0x249/0x320\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n\n Allocated by task 63:\n kasan_save_stack+0x30/0x50\n kasan_save_track+0x14/0x30\n __kasan_kmalloc+0x7f/0x90\n __kmalloc_noprof+0x246/0x6f0\n iavf_watchdog_task+0x28fc/0x3230\n process_one_work+0x7fd/0x1420\n worker_thread+0x4d1/0xd40\n kthread+0x344/0x660\n ret_from_fork+0x249/0x320\n ret_from_fork_asm+0x1a/0x30\n\n The buggy address belongs to the object at ffff888102c50100\n which belongs to the cache kmalloc-64 of size 64\n The buggy address is located 0 bytes to the right of\n allocated 52-byte region [ffff888102c50100, ffff888102c50134)\n\n The buggy address belongs to the physical page:\n page: refcount:0 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x102c50\n flags: 0x200000000000000(node=0|zone=2)\n page_type: f5(slab)\n raw: 0200000000000000 ffff8881000418c0 dead000000000122 0000000000000000\n raw: 0000000000000000 0000000080200020 00000000f5000000 0000000000000000\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n ffff888102c50000: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n ffff888102c50080: 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc fc\n \u0026gt;ffff888102c50100: 00 00 00 00 00 00 04 fc fc fc fc fc fc fc fc fc\n ^\n ffff888102c50180: 00 00 00 00 00 00 00 00 fc fc fc fc fc fc fc fc\n ffff888102c50200: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc(CVE-2025-71087)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer\n\nInitialize the eb.vma array with values of 0 when the eb structure is\nfirst set up. In particular, this sets the eb-\u0026gt;vma[i].vma pointers to\nNULL, simplifying cleanup and getting rid of the bug described below.\n\nDuring the execution of eb_lookup_vmas(), the eb-\u0026gt;vma array is\nsuccessively filled up with struct eb_vma objects. This process includes\ncalling eb_add_vma(), which might fail; however, even in the event of\nfailure, eb-\u0026gt;vma[i].vma is set for the currently processed buffer.\n\nIf eb_add_vma() fails, eb_lookup_vmas() returns with an error, which\nprompts a call to eb_release_vmas() to clean up the mess. Since\neb_lookup_vmas() might fail during processing any (possibly not first)\nbuffer, eb_release_vmas() checks whether a buffer\u0026apos;s vma is NULL to know\nat what point did the lookup function fail.\n\nIn eb_lookup_vmas(), eb-\u0026gt;vma[i].vma is set to NULL if either the helper\nfunction eb_lookup_vma() or eb_validate_vma() fails. eb-\u0026gt;vma[i+1].vma is\nset to NULL in case i915_gem_object_userptr_submit_init() fails; the\ncurrent one needs to be cleaned up by eb_release_vmas() at this point,\nso the next one is set. If eb_add_vma() fails, neither the current nor\nthe next vma is set to NULL, which is a source of a NULL deref bug\ndescribed in the issue linked in the Closes tag.\n\nWhen entering eb_lookup_vmas(), the vma pointers are set to the slab\npoison value, instead of NULL. This doesn\u0026apos;t matter for the actual\nlookup, since it gets overwritten anyway, however the eb_release_vmas()\nfunction only recognizes NULL as the stopping value, hence the pointers\nare being set to NULL as they go in case of intermediate failure. This\npatch changes the approach to filling them all with NULL at the start\ninstead, rather than handling that manually during failure.\n\n(cherry picked from commit 08889b706d4f0b8d2352b7ca29c2d8df4d0787cd)(CVE-2025-71130)\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\nbtrfs: fix deadlock in wait_current_trans() due to ignored transaction type\n\nWhen wait_current_trans() is called during start_transaction(), it\ncurrently waits for a blocked transaction without considering whether\nthe given transaction type actually needs to wait for that particular\ntransaction state. The btrfs_blocked_trans_types[] array already defines\nwhich transaction types should wait for which transaction states, but\nthis check was missing in wait_current_trans().\n\nThis can lead to a deadlock scenario involving two transactions and\npending ordered extents:\n\n 1. Transaction A is in TRANS_STATE_COMMIT_DOING state\n\n 2. A worker processing an ordered extent calls start_transaction()\n with TRANS_JOIN\n\n 3. join_transaction() returns -EBUSY because Transaction A is in\n TRANS_STATE_COMMIT_DOING\n\n 4. Transaction A moves to TRANS_STATE_UNBLOCKED and completes\n\n 5. A new Transaction B is created (TRANS_STATE_RUNNING)\n\n 6. The ordered extent from step 2 is added to Transaction B\u0026apos;s\n pending ordered extents\n\n 7. Transaction B immediately starts commit by another task and\n enters TRANS_STATE_COMMIT_START\n\n 8. The worker finally reaches wait_current_trans(), sees Transaction B\n in TRANS_STATE_COMMIT_START (a blocked state), and waits\n unconditionally\n\n 9. However, TRANS_JOIN should NOT wait for TRANS_STATE_COMMIT_START\n according to btrfs_blocked_trans_types[]\n\n 10. Transaction B is waiting for pending ordered extents to complete\n\n 11. Deadlock: Transaction B waits for ordered extent, ordered extent\n waits for Transaction B\n\nThis can be illustrated by the following call stacks:\n CPU0 CPU1\n btrfs_finish_ordered_io()\n start_transaction(TRANS_JOIN)\n join_transaction()\n # -EBUSY (Transaction A is\n # TRANS_STATE_COMMIT_DOING)\n # Transaction A completes\n # Transaction B created\n # ordered extent added to\n # Transaction B\u0026apos;s pending list\n btrfs_commit_transaction()\n # Transaction B enters\n # TRANS_STATE_COMMIT_START\n # waiting for pending ordered\n # extents\n wait_current_trans()\n # waits for Transaction B\n # (should not wait!)\n\nTask bstore_kv_sync in btrfs_commit_transaction waiting for ordered\nextents:\n\n __schedule+0x2e7/0x8a0\n schedule+0x64/0xe0\n btrfs_commit_transaction+0xbf7/0xda0 [btrfs]\n btrfs_sync_file+0x342/0x4d0 [btrfs]\n __x64_sys_fdatasync+0x4b/0x80\n do_syscall_64+0x33/0x40\n entry_SYSCALL_64_after_hwframe+0x44/0xa9\n\nTask kworker in wait_current_trans waiting for transaction commit:\n\n Workqueue: btrfs-syno_nocow btrfs_work_helper [btrfs]\n __schedule+0x2e7/0x8a0\n schedule+0x64/0xe0\n wait_current_trans+0xb0/0x110 [btrfs]\n start_transaction+0x346/0x5b0 [btrfs]\n btrfs_finish_ordered_io.isra.0+0x49b/0x9c0 [btrfs]\n btrfs_work_helper+0xe8/0x350 [btrfs]\n process_one_work+0x1d3/0x3c0\n worker_thread+0x4d/0x3e0\n kthread+0x12d/0x150\n ret_from_fork+0x1f/0x30\n\nFix this by passing the transaction type to wait_current_trans() and\nchecking btrfs_blocked_trans_types[cur_trans-\u0026gt;state] against the given\ntype before deciding to wait. This ensures that transaction types which\nare allowed to join during certain blocked states will not unnecessarily\nwait and cause deadlocks.(CVE-2025-71194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmacvlan: fix possible UAF in macvlan_forward_source()\n\nAdd RCU protection on (struct macvlan_source_entry)-\u0026gt;vlan.\n\nWhenever macvlan_hash_del_source() is called, we must clear\nentry-\u0026gt;vlan pointer before RCU grace period starts.\n\nThis allows macvlan_forward_source() to skip over\nentries queued for freeing.\n\nNote that macvlan_dev are already RCU protected, as they\nare embedded in a standard netdev (netdev_priv(ndev)).\n\nhttps: //lore.kernel.org/netdev/(CVE-2026-23001)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT 8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n \u0026lt;IRQ\u0026gt;\n __dump_stack (lib/dump_stack.c:95)\n dump_stack_lvl (lib/dump_stack.c:123)\n dump_stack (lib/dump_stack.c:130)\n spin_dump (kernel/locking/spinlock_debug.c:71)\n do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n __free_frozen_pages (mm/page_alloc.c:2973)\n ___free_pages (mm/page_alloc.c:5295)\n __free_pages (mm/page_alloc.c:5334)\n tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n ? rcu_core (kernel/rcu/tree.c:?)\n rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n rcu_core_si (kernel/rcu/tree.c:2879)\n handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n irq_exit_rcu (kernel/softirq.c:741)\n sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n \u0026lt;/IRQ\u0026gt;\n \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n free_pcppages_bulk (mm/page_alloc.c:1494)\n drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n __drain_all_pages (mm/page_alloc.c:2731)\n drain_all_pages (mm/page_alloc.c:2747)\n kcompactd (mm/compaction.c:3115)\n kthread (kernel/kthread.c:465)\n ? __cfi_kcompactd (mm/compaction.c:3166)\n ? __cfi_kthread (kernel/kthread.c:412)\n ret_from_fork (arch/x86/kernel/process.c:164)\n ? __cfi_kthread (kernel/kthread.c:412)\n ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock. The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback. However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op. Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;). The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized. Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: Enforce that teql can only be used as root qdisc\n\nDesign intent of teql is that it is only supposed to be used as root qdisc.\nWe need to check for that constraint.\n\nAlthough not important, I will describe the scenario that unearthed this\nissue for the curious.\n\nGangMin Kim \u0026lt;(CVE-2026-23074)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/hugetlb: fix hugetlb_pmd_shared()\n\nPatch series \u0026quot;mm/hugetlb: fixes for PMD table sharing (incl. using\nmmu_gather)\u0026quot;, v3.\n\nOne functional fix, one performance regression fix, and two related\ncomment fixes.\n\nI cleaned up my prototype I recently shared [1] for the performance fix,\ndeferring most of the cleanups I had in the prototype to a later point. \nWhile doing that I identified the other things.\n\nThe goal of this patch set is to be backported to stable trees \u0026quot;fairly\u0026quot;\neasily. At least patch #1 and #4.\n\nPatch #1 fixes hugetlb_pmd_shared() not detecting any sharing\nPatch #2 + #3 are simple comment fixes that patch #4 interacts with.\nPatch #4 is a fix for the reported performance regression due to excessive\nIPI broadcasts during fork()+exit().\n\nThe last patch is all about TLB flushes, IPIs and mmu_gather.\nRead: complicated\n\nThere are plenty of cleanups in the future to be had + one reasonable\noptimization on x86. But that\u0026apos;s all out of scope for this series.\n\nRuntime tested, with a focus on fixing the performance regression using\nthe original reproducer [2] on x86.\n\n\nThis patch (of 4):\n\nWe switched from (wrongly) using the page count to an independent shared\ncount. Now, shared page tables have a refcount of 1 (excluding\nspeculative references) and instead use ptdesc-\u0026gt;pt_share_count to identify\nsharing.\n\nWe didn\u0026apos;t convert hugetlb_pmd_shared(), so right now, we would never\ndetect a shared PMD table as such, because sharing/unsharing no longer\ntouches the refcount of a PMD table.\n\nPage migration, like mbind() or migrate_pages() would allow for migrating\nfolios mapped into such shared PMD tables, even though the folios are not\nexclusive. In smaps we would account them as \u0026quot;private\u0026quot; although they are\n\u0026quot;shared\u0026quot;, and we would be wrongly setting the PM_MMAP_EXCLUSIVE in the\npagemap interface.\n\nFix it by properly using ptdesc_pmd_is_shared() in hugetlb_pmd_shared().(CVE-2026-23100)\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\ntcp: secure_seq: add back ports to TS offset\n\nThis reverts 28ee1b746f49 (\u0026quot;secure_seq: downgrade to per-host timestamp offsets\u0026quot;)\n\ntcp_tw_recycle went away in 2017.\n\nZhouyan Deng reported off-path TCP source port leakage via\nSYN cookie side-channel that can be fixed in multiple ways.\n\nOne of them is to bring back TCP ports in TS offset randomization.\n\nAs a bonus, we perform a single siphash() computation\nto provide both an ISN and a TS offset.(CVE-2026-23247)\n\nIn the Linux kernel, a vulnerability exists in the AppArmor module\u0026apos;s unpack_pdb function. The vulnerability occurs due to failure to validate that DFA start states are within bounds, which can lead to out-of-bound reads. An attacker can exploit this vulnerability through specially crafted policy files, potentially leading to information disclosure or system crashes.(CVE-2026-23269)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: unconditionally bump set-\u0026gt;nelems before insertion\n\nIn case that the set is full, a new element gets published then removed\nwithout waiting for the RCU grace period, while RCU reader can be\nwalking over it already.\n\nTo address this issue, add the element transaction even if set is full,\nbut toggle the set_full flag to report -ENFILE so the abort path safely\nunwinds the set to its previous state.\n\nAs for element updates, decrement set-\u0026gt;nelems to restore it.\n\nA simpler fix is to call synchronize_rcu() in the error path.\nHowever, with a large batch adding elements to already maxed-out set,\nthis could cause noticeable slowdown of such batches.(CVE-2026-23272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: kaweth: validate USB endpoints\n\nThe kaweth driver should validate that the device it is probing has the\nproper number and types of USB endpoints it is expecting before it binds\nto it. If a malicious device were to not have the same urbs the driver\nwill crash later on when it blindly accesses these endpoints.(CVE-2026-23312)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sched: avoid qdisc_reset_all_tx_gt() vs dequeue race for lockless qdiscs\n\nWhen shrinking the number of real tx queues,\nnetif_set_real_num_tx_queues() calls qdisc_reset_all_tx_gt() to flush\nqdiscs for queues which will no longer be used.\n\nqdisc_reset_all_tx_gt() currently serializes qdisc_reset() with\nqdisc_lock(). However, for lockless qdiscs, the dequeue path is\nserialized by qdisc_run_begin/end() using qdisc-\u0026gt;seqlock instead, so\nqdisc_reset() can run concurrently with __qdisc_run() and free skbs\nwhile they are still being dequeued, leading to UAF.\n\nThis can easily be reproduced on e.g. virtio-net by imposing heavy\ntraffic while frequently changing the number of queue pairs:\n\n iperf3 -ub0 -c $peer -t 0 \u0026amp;\n while :; do\n ethtool -L eth0 combined 1\n ethtool -L eth0 combined 2\n done\n\nWith KASAN enabled, this leads to reports like:\n\n BUG: KASAN: slab-use-after-free in __qdisc_run+0x133f/0x1760\n ...\n Call Trace:\n \u0026lt;TASK\u0026gt;\n ...\n __qdisc_run+0x133f/0x1760\n __dev_queue_xmit+0x248f/0x3550\n ip_finish_output2+0xa42/0x2110\n ip_output+0x1a7/0x410\n ip_send_skb+0x2e6/0x480\n udp_send_skb+0xb0a/0x1590\n udp_sendmsg+0x13c9/0x1fc0\n ...\n \u0026lt;/TASK\u0026gt;\n\n Allocated by task 1270 on cpu 5 at 44.558414s:\n ...\n alloc_skb_with_frags+0x84/0x7c0\n sock_alloc_send_pskb+0x69a/0x830\n __ip_append_data+0x1b86/0x48c0\n ip_make_skb+0x1e8/0x2b0\n udp_sendmsg+0x13a6/0x1fc0\n ...\n\n Freed by task 1306 on cpu 3 at 44.558445s:\n ...\n kmem_cache_free+0x117/0x5e0\n pfifo_fast_reset+0x14d/0x580\n qdisc_reset+0x9e/0x5f0\n netif_set_real_num_tx_queues+0x303/0x840\n virtnet_set_channels+0x1bf/0x260 [virtio_net]\n ethnl_set_channels+0x684/0xae0\n ethnl_default_set_doit+0x31a/0x890\n ...\n\nSerialize qdisc_reset_all_tx_gt() against the lockless dequeue path by\ntaking qdisc-\u0026gt;seqlock for TCQ_F_NOLOCK qdiscs, matching the\nserialization model already used by dev_reset_queue().\n\nAdditionally clear QDISC_STATE_NON_EMPTY after reset so the qdisc state\nreflects an empty queue, avoiding needless re-scheduling.(CVE-2026-23340)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: act_ife: Fix metalist update behavior\n\nWhenever an ife action replace changes the metalist, instead of\nreplacing the old data on the metalist, the current ife code is appending\nthe new metadata. Aside from being innapropriate behavior, this may lead\nto an unbounded addition of metadata to the metalist which might cause an\nout of bounds error when running the encode op:\n\n[ 138.423369][ C1] ==================================================================\n[ 138.424317][ C1] BUG: KASAN: slab-out-of-bounds in ife_tlv_meta_encode (net/ife/ife.c:168)\n[ 138.424906][ C1] Write of size 4 at addr ffff8880077f4ffe by task ife_out_out_bou/255\n[ 138.425778][ C1] CPU: 1 UID: 0 PID: 255 Comm: ife_out_out_bou Not tainted 7.0.0-rc1-00169-gfbdfa8da05b6 #624 PREEMPT(full)\n[ 138.425795][ C1] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011\n[ 138.425800][ C1] Call Trace:\n[ 138.425804][ C1] \u0026lt;IRQ\u0026gt;\n[ 138.425808][ C1] dump_stack_lvl (lib/dump_stack.c:122)\n[ 138.425828][ C1] print_report (mm/kasan/report.c:379 mm/kasan/report.c:482)\n[ 138.425839][ C1] ? srso_alias_return_thunk (arch/x86/lib/retpoline.S:221)\n[ 138.425844][ C1] ? __virt_addr_valid (./arch/x86/include/asm/preempt.h:95 (discriminator 1) ./include/linux/rcupdate.h:975 (discriminator 1) ./include/linux/mmzone.h:2207 (discriminator 1) arch/x86/mm/physaddr.c:54 (discriminator 1))\n[ 138.425853][ C1] ? ife_tlv_meta_encode (net/ife/ife.c:168)\n[ 138.425859][ C1] kasan_report (mm/kasan/report.c:221 mm/kasan/report.c:597)\n[ 138.425868][ C1] ? ife_tlv_meta_encode (net/ife/ife.c:168)\n[ 138.425878][ C1] kasan_check_range (mm/kasan/generic.c:186 (discriminator 1) mm/kasan/generic.c:200 (discriminator 1))\n[ 138.425884][ C1] __asan_memset (mm/kasan/shadow.c:84 (discriminator 2))\n[ 138.425889][ C1] ife_tlv_meta_encode (net/ife/ife.c:168)\n[ 138.425893][ C1] ? ife_tlv_meta_encode (net/ife/ife.c:171)\n[ 138.425898][ C1] ? srso_alias_return_thunk (arch/x86/lib/retpoline.S:221)\n[ 138.425903][ C1] ife_encode_meta_u16 (net/sched/act_ife.c:57)\n[ 138.425910][ C1] ? __pfx_do_raw_spin_lock (kernel/locking/spinlock_debug.c:114)\n[ 138.425916][ C1] ? __asan_memcpy (mm/kasan/shadow.c:105 (discriminator 3))\n[ 138.425921][ C1] ? __pfx_ife_encode_meta_u16 (net/sched/act_ife.c:45)\n[ 138.425927][ C1] ? srso_alias_return_thunk (arch/x86/lib/retpoline.S:221)\n[ 138.425931][ C1] tcf_ife_act (net/sched/act_ife.c:847 net/sched/act_ife.c:879)\n\nTo solve this issue, fix the replace behavior by adding the metalist to\nthe ife rcu data structure.(CVE-2026-23378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: Fix memory leak in ice_set_ringparam()\n\nIn ice_set_ringparam, tx_rings and xdp_rings are allocated before\nrx_rings. If the allocation of rx_rings fails, the code jumps to\nthe done label leaking both tx_rings and xdp_rings. Furthermore, if\nthe setup of an individual Rx ring fails during the loop, the code jumps\nto the free_tx label which releases tx_rings but leaks xdp_rings.\n\nFix this by introducing a free_xdp label and updating the error paths to\nensure both xdp_rings and tx_rings are properly freed if rx_rings\nallocation or setup fails.\n\nCompile tested only. Issue found using a prototype static analysis tool\nand code review.(CVE-2026-23389)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix side-effect bug in match_char() macro usage\n\nThe match_char() macro evaluates its character parameter multiple\ntimes when traversing differential encoding chains. When invoked\nwith *str++, the string pointer advances on each iteration of the\ninner do-while loop, causing the DFA to check different characters\nat each iteration and therefore skip input characters.\nThis results in out-of-bounds reads when the pointer advances past\nthe input buffer boundary.\n\n[ 94.984676] ==================================================================\n[ 94.985301] BUG: KASAN: slab-out-of-bounds in aa_dfa_match+0x5ae/0x760\n[ 94.985655] Read of size 1 at addr ffff888100342000 by task file/976\n\n[ 94.986319] CPU: 7 UID: 1000 PID: 976 Comm: file Not tainted 6.19.0-rc7-next-20260127 #1 PREEMPT(lazy)\n[ 94.986322] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[ 94.986329] Call Trace:\n[ 94.986341] \u0026lt;TASK\u0026gt;\n[ 94.986347] dump_stack_lvl+0x5e/0x80\n[ 94.986374] print_report+0xc8/0x270\n[ 94.986384] ? aa_dfa_match+0x5ae/0x760\n[ 94.986388] kasan_report+0x118/0x150\n[ 94.986401] ? aa_dfa_match+0x5ae/0x760\n[ 94.986405] aa_dfa_match+0x5ae/0x760\n[ 94.986408] __aa_path_perm+0x131/0x400\n[ 94.986418] aa_path_perm+0x219/0x2f0\n[ 94.986424] apparmor_file_open+0x345/0x570\n[ 94.986431] security_file_open+0x5c/0x140\n[ 94.986442] do_dentry_open+0x2f6/0x1120\n[ 94.986450] vfs_open+0x38/0x2b0\n[ 94.986453] ? may_open+0x1e2/0x2b0\n[ 94.986466] path_openat+0x231b/0x2b30\n[ 94.986469] ? __x64_sys_openat+0xf8/0x130\n[ 94.986477] do_file_open+0x19d/0x360\n[ 94.986487] do_sys_openat2+0x98/0x100\n[ 94.986491] __x64_sys_openat+0xf8/0x130\n[ 94.986499] do_syscall_64+0x8e/0x660\n[ 94.986515] ? count_memcg_events+0x15f/0x3c0\n[ 94.986526] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 94.986540] ? handle_mm_fault+0x1639/0x1ef0\n[ 94.986551] ? vma_start_read+0xf0/0x320\n[ 94.986558] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 94.986561] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 94.986563] ? fpregs_assert_state_consistent+0x50/0xe0\n[ 94.986572] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 94.986574] ? arch_exit_to_user_mode_prepare+0x9/0xb0\n[ 94.986587] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 94.986588] ? irqentry_exit+0x3c/0x590\n[ 94.986595] entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[ 94.986597] RIP: 0033:0x7fda4a79c3ea\n\nFix by extracting the character value before invoking match_char,\nensuring single evaluation per outer loop.(CVE-2026-23406)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\napparmor: fix missing bounds check on DEFAULT table in verify_dfa()\n\nThe verify_dfa() function only checks DEFAULT_TABLE bounds when the state\nis not differentially encoded.\n\nWhen the verification loop traverses the differential encoding chain,\nit reads k = DEFAULT_TABLE[j] and uses k as an array index without\nvalidation. A malformed DFA with DEFAULT_TABLE[j] \u0026gt;= state_count,\ntherefore, causes both out-of-bounds reads and writes.\n\n[ 57.179855] ==================================================================\n[ 57.180549] BUG: KASAN: slab-out-of-bounds in verify_dfa+0x59a/0x660\n[ 57.180904] Read of size 4 at addr ffff888100eadec4 by task su/993\n\n[ 57.181554] CPU: 1 UID: 0 PID: 993 Comm: su Not tainted 6.19.0-rc7-next-20260127 #1 PREEMPT(lazy)\n[ 57.181558] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[ 57.181563] Call Trace:\n[ 57.181572] \u0026lt;TASK\u0026gt;\n[ 57.181577] dump_stack_lvl+0x5e/0x80\n[ 57.181596] print_report+0xc8/0x270\n[ 57.181605] ? verify_dfa+0x59a/0x660\n[ 57.181608] kasan_report+0x118/0x150\n[ 57.181620] ? verify_dfa+0x59a/0x660\n[ 57.181623] verify_dfa+0x59a/0x660\n[ 57.181627] aa_dfa_unpack+0x1610/0x1740\n[ 57.181629] ? __kmalloc_cache_noprof+0x1d0/0x470\n[ 57.181640] unpack_pdb+0x86d/0x46b0\n[ 57.181647] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 57.181653] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 57.181656] ? aa_unpack_nameX+0x1a8/0x300\n[ 57.181659] aa_unpack+0x20b0/0x4c30\n[ 57.181662] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 57.181664] ? stack_depot_save_flags+0x33/0x700\n[ 57.181681] ? kasan_save_track+0x4f/0x80\n[ 57.181683] ? kasan_save_track+0x3e/0x80\n[ 57.181686] ? __kasan_kmalloc+0x93/0xb0\n[ 57.181688] ? __kvmalloc_node_noprof+0x44a/0x780\n[ 57.181693] ? aa_simple_write_to_buffer+0x54/0x130\n[ 57.181697] ? policy_update+0x154/0x330\n[ 57.181704] aa_replace_profiles+0x15a/0x1dd0\n[ 57.181707] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 57.181710] ? __kvmalloc_node_noprof+0x44a/0x780\n[ 57.181712] ? aa_loaddata_alloc+0x77/0x140\n[ 57.181715] ? srso_alias_return_thunk+0x5/0xfbef5\n[ 57.181717] ? _copy_from_user+0x2a/0x70\n[ 57.181730] policy_update+0x17a/0x330\n[ 57.181733] profile_replace+0x153/0x1a0\n[ 57.181735] ? rw_verify_area+0x93/0x2d0\n[ 57.181740] vfs_write+0x235/0xab0\n[ 57.181745] ksys_write+0xb0/0x170\n[ 57.181748] do_syscall_64+0x8e/0x660\n[ 57.181762] entry_SYSCALL_64_after_hwframe+0x76/0x7e\n[ 57.181765] RIP: 0033:0x7f6192792eb2\n\nRemove the MATCH_FLAG_DIFF_ENCODE condition to validate all DEFAULT_TABLE\nentries unconditionally.(CVE-2026-23407)\n\nA race condition vulnerability exists in the AppArmor security module of the Linux kernel, leading to a use-after-free issue. This vulnerability can be triggered when an attacker simultaneously opens rawdata files and removes an associated AppArmor profile. Since rawdata inodes are not refcounted, there is a time window during profile removal where the i_private pointer may reference freed memory, causing the system to access freed memory regions. This can result in program crashes, unexpected value usage, or arbitrary code execution, threatening the confidentiality, integrity, and availability of the system.(CVE-2026-23410)\n\nA vulnerability exists in the AppArmor security module of the Linux kernel when handling the i_private field of the inode structure. AppArmor was putting the reference to i_private data on its end after removing the original entry from the file system. However the inode can and does live beyond that point and it is possible that some of the fs callback functions will be invoked after the reference has been put, which results in a race between freeing the data and accessing it through the fs. While the rawdata/loaddata is the most likely candidate to fail the race, as it has the fewest references. If properly crafted it might be possible to trigger a race for the other types stored in i_private. This vulnerability could allow a local attacker to bypass AppArmor\u0026apos;s access control policies through a specially crafted request, leading to privilege escalation and impacting system confidentiality, integrity, and availability.(CVE-2026-23411)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp_tunnel: fix NULL deref caused by udp_sock_create6 when CONFIG_IPV6=n\n\nWhen CONFIG_IPV6 is disabled, the udp_sock_create6() function returns 0\n(success) without actually creating a socket. Callers such as\nfou_create() then proceed to dereference the uninitialized socket\npointer, resulting in a NULL pointer dereference.\n\nThe captured NULL deref crash:\n BUG: kernel NULL pointer dereference, address: 0000000000000018\n RIP: 0010:fou_nl_add_doit (net/ipv4/fou_core.c:590 net/ipv4/fou_core.c:764)\n [...]\n Call Trace:\n \u0026lt;TASK\u0026gt;\n genl_family_rcv_msg_doit.constprop.0 (net/netlink/genetlink.c:1114)\n genl_rcv_msg (net/netlink/genetlink.c:1194 net/netlink/genetlink.c:1209)\n [...]\n netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n genl_rcv (net/netlink/genetlink.c:1219)\n netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n netlink_sendmsg (net/netlink/af_netlink.c:1894)\n __sock_sendmsg (net/socket.c:727 (discriminator 1) net/socket.c:742 (discriminator 1))\n __sys_sendto (./include/linux/file.h:62 (discriminator 1) ./include/linux/file.h:83 (discriminator 1) net/socket.c:2183 (discriminator 1))\n __x64_sys_sendto (net/socket.c:2213 (discriminator 1) net/socket.c:2209 (discriminator 1) net/socket.c:2209 (discriminator 1))\n do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1))\n entry_SYSCALL_64_after_hwframe (net/arch/x86/entry/entry_64.S:130)\n\nThis patch makes udp_sock_create6 return -EPFNOSUPPORT instead, so\ncallers correctly take their error paths. There is only one caller of\nthe vulnerable function and only privileged users can trigger it.(CVE-2026-23439)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix race condition during IPSec ESN update\n\nIn IPSec full offload mode, the device reports an ESN (Extended\nSequence Number) wrap event to the driver. The driver validates this\nevent by querying the IPSec ASO and checking that the esn_event_arm\nfield is 0x0, which indicates an event has occurred. After handling\nthe event, the driver must re-arm the context by setting esn_event_arm\nback to 0x1.\n\nA race condition exists in this handling path. After validating the\nevent, the driver calls mlx5_accel_esp_modify_xfrm() to update the\nkernel\u0026apos;s xfrm state. This function temporarily releases and\nre-acquires the xfrm state lock.\n\nSo, need to acknowledge the event first by setting esn_event_arm to\n0x1. This prevents the driver from reprocessing the same ESN update if\nthe hardware sends events for other reason. Since the next ESN update\nonly occurs after nearly 2^31 packets are received, there\u0026apos;s no risk of\nmissing an update, as it will happen long after this handling has\nfinished.\n\nProcessing the event twice causes the ESN high-order bits (esn_msb) to\nbe incremented incorrectly. The driver then programs the hardware with\nthis invalid ESN state, which leads to anti-replay failures and a\ncomplete halt of IPSec traffic.\n\nFix this by re-arming the ESN event immediately after it is validated,\nbefore calling mlx5_accel_esp_modify_xfrm(). This ensures that any\nspurious, duplicate events are correctly ignored, closing the race\nwindow.(CVE-2026-23440)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Prevent concurrent access to IPSec ASO context\n\nThe query or updating IPSec offload object is through Access ASO WQE.\nThe driver uses a single mlx5e_ipsec_aso struct for each PF, which\ncontains a shared DMA-mapped context for all ASO operations.\n\nA race condition exists because the ASO spinlock is released before\nthe hardware has finished processing WQE. If a second operation is\ninitiated immediately after, it overwrites the shared context in the\nDMA area.\n\nWhen the first operation\u0026apos;s completion is processed later, it reads\nthis corrupted context, leading to unexpected behavior and incorrect\nresults.\n\nThis commit fixes the race by introducing a private context within\neach IPSec offload object. The shared ASO context is now copied to\nthis private context while the ASO spinlock is held. Subsequent\nprocessing uses this saved, per-object context, ensuring its integrity\nis maintained.(CVE-2026-23441)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mac80211: always free skb on ieee80211_tx_prepare_skb() failure\n\nieee80211_tx_prepare_skb() has three error paths, but only two of them\nfree the skb. The first error path (ieee80211_tx_prepare() returning\nTX_DROP) does not free it, while invoke_tx_handlers() failure and the\nfragmentation check both do.\n\nAdd kfree_skb() to the first error path so all three are consistent,\nand remove the now-redundant frees in callers (ath9k, mt76,\nmac80211_hwsim) to avoid double-free.\n\nDocument the skb ownership guarantee in the function\u0026apos;s kdoc.(CVE-2026-23444)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check\n\ncdc_ncm_rx_verify_ndp16() validates that the NDP header and its DPE\nentries fit within the skb. The first check correctly accounts for\nndpoffset:\n\n if ((ndpoffset + sizeof(struct usb_cdc_ncm_ndp16)) \u0026gt; skb_in-\u0026gt;len)\n\nbut the second check omits it:\n\n if ((sizeof(struct usb_cdc_ncm_ndp16) +\n ret * (sizeof(struct usb_cdc_ncm_dpe16))) \u0026gt; skb_in-\u0026gt;len)\n\nThis validates the DPE array size against the total skb length as if\nthe NDP were at offset 0, rather than at ndpoffset. When the NDP is\nplaced near the end of the NTB (large wNdpIndex), the DPE entries can\nextend past the skb data buffer even though the check passes.\ncdc_ncm_rx_fixup() then reads out-of-bounds memory when iterating\nthe DPE array.\n\nAdd ndpoffset to the nframes bounds check and use struct_size_t() to\nexpress the NDP-plus-DPE-array size more clearly.(CVE-2026-23448)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/smc: fix NULL dereference and UAF in smc_tcp_syn_recv_sock()\n\nSyzkaller reported a panic in smc_tcp_syn_recv_sock() [1].\n\nsmc_tcp_syn_recv_sock() is called in the TCP receive path\n(softirq) via icsk_af_ops-\u0026gt;syn_recv_sock on the clcsock (TCP\nlistening socket). It reads sk_user_data to get the smc_sock\npointer. However, when the SMC listen socket is being closed\nconcurrently, smc_close_active() sets clcsock-\u0026gt;sk_user_data\nto NULL under sk_callback_lock, and then the smc_sock itself\ncan be freed via sock_put() in smc_release().\n\nThis leads to two issues:\n\n1) NULL pointer dereference: sk_user_data is NULL when\n accessed.\n2) Use-after-free: sk_user_data is read as non-NULL, but the\n smc_sock is freed before its fields (e.g., queued_smc_hs,\n ori_af_ops) are accessed.\n\nThe race window looks like this (the syzkaller crash [1]\ntriggers via the SYN cookie path: tcp_get_cookie_sock() -\u0026gt;\nsmc_tcp_syn_recv_sock(), but the normal tcp_check_req() path\nhas the same race):\n\n CPU A (softirq) CPU B (process ctx)\n\n tcp_v4_rcv()\n TCP_NEW_SYN_RECV:\n sk = req-\u0026gt;rsk_listener\n sock_hold(sk)\n /* No lock on listener */\n smc_close_active():\n write_lock_bh(cb_lock)\n sk_user_data = NULL\n write_unlock_bh(cb_lock)\n ...\n smc_clcsock_release()\n sock_put(smc-\u0026gt;sk) x2\n -\u0026gt; smc_sock freed!\n tcp_check_req()\n smc_tcp_syn_recv_sock():\n smc = user_data(sk)\n -\u0026gt; NULL or dangling\n smc-\u0026gt;queued_smc_hs\n -\u0026gt; crash!\n\nNote that the clcsock and smc_sock are two independent objects\nwith separate refcounts. TCP stack holds a reference on the\nclcsock, which keeps it alive, but this does NOT prevent the\nsmc_sock from being freed.\n\nFix this by using RCU and refcount_inc_not_zero() to safely\naccess smc_sock. Since smc_tcp_syn_recv_sock() is called in\nthe TCP three-way handshake path, taking read_lock_bh on\nsk_callback_lock is too heavy and would not survive a SYN\nflood attack. Using rcu_read_lock() is much more lightweight.\n\n- Set SOCK_RCU_FREE on the SMC listen socket so that\n smc_sock freeing is deferred until after the RCU grace\n period. This guarantees the memory is still valid when\n accessed inside rcu_read_lock().\n- Use rcu_read_lock() to protect reading sk_user_data.\n- Use refcount_inc_not_zero(\u0026amp;smc-\u0026gt;sk.sk_refcnt) to pin the\n smc_sock. If the refcount has already reached zero (close\n path completed), it returns false and we bail out safely.\n\nNote: smc_hs_congested() has a similar lockless read of\nsk_user_data without rcu_read_lock(), but it only checks for\nNULL and accesses the global smc_hs_wq, never dereferencing\nany smc_sock field, so it is not affected.\n\nReproducer was verified with mdelay injection and smc_run,\nthe issue no longer occurs with this patch applied.\n\n[1] https://syzkaller.appspot.com/bug?extid=827ae2bfb3a3529333e9(CVE-2026-23450)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPM: runtime: Fix a race condition related to device removal\n\nThe following code in pm_runtime_work() may dereference the dev-\u0026gt;parent\npointer after the parent device has been freed:\n\n\t/* Maybe the parent is now able to suspend. */\n\tif (parent \u0026amp;\u0026amp; !parent-\u0026gt;power.ignore_children) {\n\t\tspin_unlock(\u0026amp;dev-\u0026gt;power.lock);\n\n\t\tspin_lock(\u0026amp;parent-\u0026gt;power.lock);\n\t\trpm_idle(parent, RPM_ASYNC);\n\t\tspin_unlock(\u0026amp;parent-\u0026gt;power.lock);\n\n\t\tspin_lock(\u0026amp;dev-\u0026gt;power.lock);\n\t}\n\nFix this by inserting a flush_work() call in pm_runtime_remove().\n\nWithout this patch blktest block/001 triggers the following complaint\nsporadically:\n\nBUG: KASAN: slab-use-after-free in lock_acquire+0x70/0x160\nRead of size 1 at addr ffff88812bef7198 by task kworker/u553:1/3081\nWorkqueue: pm pm_runtime_work\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x61/0x80\n print_address_description.constprop.0+0x8b/0x310\n print_report+0xfd/0x1d7\n kasan_report+0xd8/0x1d0\n __kasan_check_byte+0x42/0x60\n lock_acquire.part.0+0x38/0x230\n lock_acquire+0x70/0x160\n _raw_spin_lock+0x36/0x50\n rpm_suspend+0xc6a/0xfe0\n rpm_idle+0x578/0x770\n pm_runtime_work+0xee/0x120\n process_one_work+0xde3/0x1410\n worker_thread+0x5eb/0xfe0\n kthread+0x37b/0x480\n ret_from_fork+0x6cb/0x920\n ret_from_fork_asm+0x11/0x20\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 4314:\n kasan_save_stack+0x2a/0x50\n kasan_save_track+0x18/0x40\n kasan_save_alloc_info+0x3d/0x50\n __kasan_kmalloc+0xa0/0xb0\n __kmalloc_noprof+0x311/0x990\n scsi_alloc_target+0x122/0xb60 [scsi_mod]\n __scsi_scan_target+0x101/0x460 [scsi_mod]\n scsi_scan_channel+0x179/0x1c0 [scsi_mod]\n scsi_scan_host_selected+0x259/0x2d0 [scsi_mod]\n store_scan+0x2d2/0x390 [scsi_mod]\n dev_attr_store+0x43/0x80\n sysfs_kf_write+0xde/0x140\n kernfs_fop_write_iter+0x3ef/0x670\n vfs_write+0x506/0x1470\n ksys_write+0xfd/0x230\n __x64_sys_write+0x76/0xc0\n x64_sys_call+0x213/0x1810\n do_syscall_64+0xee/0xfc0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nFreed by task 4314:\n kasan_save_stack+0x2a/0x50\n kasan_save_track+0x18/0x40\n kasan_save_free_info+0x3f/0x50\n __kasan_slab_free+0x67/0x80\n kfree+0x225/0x6c0\n scsi_target_dev_release+0x3d/0x60 [scsi_mod]\n device_release+0xa3/0x220\n kobject_cleanup+0x105/0x3a0\n kobject_put+0x72/0xd0\n put_device+0x17/0x20\n scsi_device_dev_release+0xacf/0x12c0 [scsi_mod]\n device_release+0xa3/0x220\n kobject_cleanup+0x105/0x3a0\n kobject_put+0x72/0xd0\n put_device+0x17/0x20\n scsi_device_put+0x7f/0xc0 [scsi_mod]\n sdev_store_delete+0xa5/0x120 [scsi_mod]\n dev_attr_store+0x43/0x80\n sysfs_kf_write+0xde/0x140\n kernfs_fop_write_iter+0x3ef/0x670\n vfs_write+0x506/0x1470\n ksys_write+0xfd/0x230\n __x64_sys_write+0x76/0xc0\n x64_sys_call+0x213/0x1810(CVE-2026-23452)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user\n\nAfter commit ab4eedb790ca (\u0026quot;Bluetooth: L2CAP: Fix corrupted list in\nhci_chan_del\u0026quot;), l2cap_conn_del() uses conn-\u0026gt;lock to protect access to\nconn-\u0026gt;users. However, l2cap_register_user() and l2cap_unregister_user()\ndon\u0026apos;t use conn-\u0026gt;lock, creating a race condition where these functions can\naccess conn-\u0026gt;users and conn-\u0026gt;hchan concurrently with l2cap_conn_del().\n\nThis can lead to use-after-free and list corruption bugs, as reported\nby syzbot.\n\nFix this by changing l2cap_register_user() and l2cap_unregister_user()\nto use conn-\u0026gt;lock instead of hci_dev_lock(), ensuring consistent locking\nfor the l2cap_conn structure.(CVE-2026-23461)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2026-23473)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspi: fix statistics allocation\n\nThe controller per-cpu statistics is not allocated until after the\ncontroller has been registered with driver core, which leaves a window\nwhere accessing the sysfs attributes can trigger a NULL-pointer\ndereference.\n\nFix this by moving the statistics allocation to controller allocation\nwhile tying its lifetime to that of the controller (rather than using\nimplicit devres).(CVE-2026-23475)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix krb5 mount with username option\n\nCustomer reported that some of their krb5 mounts were failing against\na single server as the client was trying to mount the shares with\nwrong credentials. It turned out the client was reusing SMB session\nfrom first mount to try mounting the other shares, even though a\ndifferent username= option had been specified to the other mounts.\n\nBy using username mount option along with sec=krb5 to search for\nprincipals from keytab is supported by cifs.upcall(8) since\ncifs-utils-4.8. So fix this by matching username mount option in\nmatch_session() even with Kerberos.\n\nFor example, the second mount below should fail with -ENOKEY as there\nis no \u0026apos;foobar\u0026apos; principal in keytab (/etc/krb5.keytab). The client\nends up reusing SMB session from first mount to perform the second\none, which is wrong.\n\n```\n$ ktutil\nktutil: add_entry -password -p testuser -k 1 -e aes256-cts\nPassword for (CVE-2026-31392)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/rmap: fix incorrect pte restoration for lazyfree folios\n\nWe batch unmap anonymous lazyfree folios by folio_unmap_pte_batch. If the\nbatch has a mix of writable and non-writable bits, we may end up setting\nthe entire batch writable. Fix this by respecting writable bit during\nbatching.\n\nAlthough on a successful unmap of a lazyfree folio, the soft-dirty bit is\nlost, preserve it on pte restoration by respecting the bit during\nbatching, to make the fix consistent w.r.t both writable bit and\nsoft-dirty bit.\n\nI was able to write the below reproducer and crash the kernel. \nExplanation of reproducer (set 64K mTHP to always):\n\nFault in a 64K large folio. Split the VMA at mid-point with\nMADV_DONTFORK. fork() - parent points to the folio with 8 writable ptes\nand 8 non-writable ptes. Merge the VMAs with MADV_DOFORK so that\nfolio_unmap_pte_batch() can determine all the 16 ptes as a batch. Do\nMADV_FREE on the range to mark the folio as lazyfree. Write to the memory\nto dirty the pte, eventually rmap will dirty the folio. Then trigger\nreclaim, we will hit the pte restoration path, and the kernel will crash\nwith the trace given below.\n\nThe BUG happens at:\n\n\tBUG_ON(atomic_inc_return(\u0026amp;ptc-\u0026gt;anon_map_count) \u0026gt; 1 \u0026amp;\u0026amp; rw);\n\nThe code path is asking for anonymous page to be mapped writable into the\npagetable. The BUG_ON() firing implies that such a writable page has been\nmapped into the pagetables of more than one process, which breaks\nanonymous memory/CoW semantics.\n\n[ 21.134473] kernel BUG at mm/page_table_check.c:118!\n[ 21.134497] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP\n[ 21.135917] Modules linked in:\n[ 21.136085] CPU: 1 UID: 0 PID: 1735 Comm: dup-lazyfree Not tainted 7.0.0-rc1-00116-g018018a17770 #1028 PREEMPT\n[ 21.136858] Hardware name: linux,dummy-virt (DT)\n[ 21.137019] pstate: 21400005 (nzCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--)\n[ 21.137308] pc : page_table_check_set+0x28c/0x2a8\n[ 21.137607] lr : page_table_check_set+0x134/0x2a8\n[ 21.137885] sp : ffff80008a3b3340\n[ 21.138124] x29: ffff80008a3b3340 x28: fffffdffc3d14400 x27: ffffd1a55e03d000\n[ 21.138623] x26: 0040000000000040 x25: ffffd1a55f7dd000 x24: 0000000000000001\n[ 21.139045] x23: 0000000000000001 x22: 0000000000000001 x21: ffffd1a55f217f30\n[ 21.139629] x20: 0000000000134521 x19: 0000000000134519 x18: 005c43e000040000\n[ 21.140027] x17: 0001400000000000 x16: 0001700000000000 x15: 000000000000ffff\n[ 21.140578] x14: 000000000000000c x13: 005c006000000000 x12: 0000000000000020\n[ 21.140828] x11: 0000000000000000 x10: 005c000000000000 x9 : ffffd1a55c079ee0\n[ 21.141077] x8 : 0000000000000001 x7 : 005c03e000040000 x6 : 000000004000ffff\n[ 21.141490] x5 : ffff00017fffce00 x4 : 0000000000000001 x3 : 0000000000000002\n[ 21.141741] x2 : 0000000000134510 x1 : 0000000000000000 x0 : ffff0000c08228c0\n[ 21.141991] Call trace:\n[ 21.142093] page_table_check_set+0x28c/0x2a8 (P)\n[ 21.142265] __page_table_check_ptes_set+0x144/0x1e8\n[ 21.142441] __set_ptes_anysz.constprop.0+0x160/0x1a8\n[ 21.142766] contpte_set_ptes+0xe8/0x140\n[ 21.142907] try_to_unmap_one+0x10c4/0x10d0\n[ 21.143177] rmap_walk_anon+0x100/0x250\n[ 21.143315] try_to_unmap+0xa0/0xc8\n[ 21.143441] shrink_folio_list+0x59c/0x18a8\n[ 21.143759] shrink_lruvec+0x664/0xbf0\n[ 21.144043] shrink_node+0x218/0x878\n[ 21.144285] __node_reclaim.constprop.0+0x98/0x338\n[ 21.144763] user_proactive_reclaim+0x2a4/0x340\n[ 21.145056] reclaim_store+0x3c/0x60\n[ 21.145216] dev_attr_store+0x20/0x40\n[ 21.145585] sysfs_kf_write+0x84/0xa8\n[ 21.145835] kernfs_fop_write_iter+0x130/0x1c8\n[ 21.145994] vfs_write+0x2b8/0x368\n[ 21.146119] ksys_write+0x70/0x110\n[ 21.146240] __arm64_sys_write+0x24/0x38\n[ 21.146380] invoke_syscall+0x50/0x120\n[ 21.146513] el0_svc_common.constprop.0+0x48/0xf8\n[ 21.146679] do_el0_svc+0x28/0x40\n[ 21.146798] el0_svc+0x34/0x110\n[ 21.146926] el0t\n---truncated---(CVE-2026-31398)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvdimm/bus: Fix potential use after free in asynchronous initialization\n\nDingisoul with KASAN reports a use after free if device_add() fails in\nnd_async_device_register().\n\nCommit b6eae0f61db2 (\u0026quot;libnvdimm: Hold reference on parent while\nscheduling async init\u0026quot;) correctly added a reference on the parent device\nto be held until asynchronous initialization was complete. However, if\ndevice_add() results in an allocation failure the ref count of the\ndevice drops to 0 prior to the parent pointer being accessed. Thus\nresulting in use after free.\n\nThe bug bot AI correctly identified the fix. Save a reference to the\nparent pointer to be used to drop the parent reference regardless of the\noutcome of device_add().(CVE-2026-31399)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsunrpc: fix cache_request leak in cache_release\n\nWhen a reader\u0026apos;s file descriptor is closed while in the middle of reading\na cache_request (rp-\u0026gt;offset != 0), cache_release() decrements the\nrequest\u0026apos;s readers count but never checks whether it should free the\nrequest.\n\nIn cache_read(), when readers drops to 0 and CACHE_PENDING is clear, the\ncache_request is removed from the queue and freed along with its buffer\nand cache_head reference. cache_release() lacks this cleanup.\n\nThe only other path that frees requests with readers == 0 is\ncache_dequeue(), but it runs only when CACHE_PENDING transitions from\nset to clear. If that transition already happened while readers was\nstill non-zero, cache_dequeue() will have skipped the request, and no\nsubsequent call will clean it up.\n\nAdd the same cleanup logic from cache_read() to cache_release(): after\ndecrementing readers, check if it reached 0 with CACHE_PENDING clear,\nand if so, dequeue and free the cache_request.(CVE-2026-31400)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Hold net reference for the lifetime of /proc/fs/nfs/exports fd\n\nThe /proc/fs/nfs/exports proc entry is created at module init\nand persists for the module\u0026apos;s lifetime. exports_proc_open()\ncaptures the caller\u0026apos;s current network namespace and stores\nits svc_export_cache in seq-\u0026gt;private, but takes no reference\non the namespace. If the namespace is subsequently torn down\n(e.g. container destruction after the opener does setns() to a\ndifferent namespace), nfsd_net_exit() calls nfsd_export_shutdown()\nwhich frees the cache. Subsequent reads on the still-open fd\ndereference the freed cache_detail, walking a freed hash table.\n\nHold a reference on the struct net for the lifetime of the open\nfile descriptor. This prevents nfsd_net_exit() from running --\nand thus prevents nfsd_export_shutdown() from freeing the cache\n-- while any exports fd is open. cache_detail already stores\nits net pointer (cd-\u0026gt;net, set by cache_create_net()), so\nexports_release() can retrieve it without additional per-file\nstorage.(CVE-2026-31403)\n\nIn the Linux kernel, the Bluetooth SCO module\u0026apos;s sco_recv_frame() function contains a use-after-free vulnerability. The function reads conn-\u0026gt;sk under sco_conn_lock() but immediately releases the lock without holding a reference to the socket. A concurrent close() operation can free the socket between the lock release and the subsequent sk-\u0026gt;sk_state access, resulting in a use-after-free vulnerability. Other functions in the same file (sco_sock_timeout(), sco_conn_del()) correctly use sco_sock_hold() to safely hold references under the lock. The vulnerability is fixed by using sco_sock_hold() to acquire a reference before releasing the lock and adding sock_put() on all exit paths.(CVE-2026-31408)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_fw: fix NULL pointer dereference on shared blocks\n\nThe old-method path in fw_classify() calls tcf_block_q() and\ndereferences q-\u0026gt;handle. Shared blocks leave block-\u0026gt;q NULL, causing a\nNULL deref when an empty cls_fw filter is attached to a shared block\nand a packet with a nonzero major skb mark is classified.\n\nReject the configuration in fw_change() when the old method (no\nTCA_OPTIONS) is used on a shared block, since fw_classify()\u0026apos;s\nold-method path needs block-\u0026gt;q which is NULL for shared blocks.\n\nThe fixed null-ptr-deref calling stack:\n KASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]\n RIP: 0010:fw_classify (net/sched/cls_fw.c:81)\n Call Trace:\n tcf_classify (./include/net/tc_wrapper.h:197 net/sched/cls_api.c:1764 net/sched/cls_api.c:1860)\n tc_run (net/core/dev.c:4401)\n __dev_queue_xmit (net/core/dev.c:4535 net/core/dev.c:4790)(CVE-2026-31421)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_flow: fix NULL pointer dereference on shared blocks\n\nflow_change() calls tcf_block_q() and dereferences q-\u0026gt;handle to derive\na default baseclass. Shared blocks leave block-\u0026gt;q NULL, causing a NULL\nderef when a flow filter without a fully qualified baseclass is created\non a shared block.\n\nCheck tcf_block_shared() before accessing block-\u0026gt;q and return -EINVAL\nfor shared blocks. This avoids the null-deref shown below:\n\n=======================================================================\nKASAN: null-ptr-deref in range [0x0000000000000038-0x000000000000003f]\nRIP: 0010:flow_change (net/sched/cls_flow.c:508)\nCall Trace:\n tc_new_tfilter (net/sched/cls_api.c:2432)\n rtnetlink_rcv_msg (net/core/rtnetlink.c:6980)\n [...]\n=======================================================================(CVE-2026-31422)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPI: EC: clean up handlers on probe failure in acpi_ec_setup()\n\nWhen ec_install_handlers() returns -EPROBE_DEFER on reduced-hardware\nplatforms, it has already started the EC and installed the address\nspace handler with the struct acpi_ec pointer as handler context.\nHowever, acpi_ec_setup() propagates the error without any cleanup.\n\nThe caller acpi_ec_add() then frees the struct acpi_ec for non-boot\ninstances, leaving a dangling handler context in ACPICA.\n\nAny subsequent AML evaluation that accesses an EC OpRegion field\ndispatches into acpi_ec_space_handler() with the freed pointer,\ncausing a use-after-free:\n\n BUG: KASAN: slab-use-after-free in mutex_lock (kernel/locking/mutex.c:289)\n Write of size 8 at addr ffff88800721de38 by task init/1\n Call Trace:\n \u0026lt;TASK\u0026gt;\n mutex_lock (kernel/locking/mutex.c:289)\n acpi_ec_space_handler (drivers/acpi/ec.c:1362)\n acpi_ev_address_space_dispatch (drivers/acpi/acpica/evregion.c:293)\n acpi_ex_access_region (drivers/acpi/acpica/exfldio.c:246)\n acpi_ex_field_datum_io (drivers/acpi/acpica/exfldio.c:509)\n acpi_ex_extract_from_field (drivers/acpi/acpica/exfldio.c:700)\n acpi_ex_read_data_from_field (drivers/acpi/acpica/exfield.c:327)\n acpi_ex_resolve_node_to_value (drivers/acpi/acpica/exresolv.c:392)\n \u0026lt;/TASK\u0026gt;\n\n Allocated by task 1:\n acpi_ec_alloc (drivers/acpi/ec.c:1424)\n acpi_ec_add (drivers/acpi/ec.c:1692)\n\n Freed by task 1:\n kfree (mm/slub.c:6876)\n acpi_ec_add (drivers/acpi/ec.c:1751)\n\nThe bug triggers on reduced-hardware EC platforms (ec-\u0026gt;gpe \u0026lt; 0)\nwhen the GPIO IRQ provider defers probing. Once the stale handler\nexists, any unprivileged sysfs read that causes AML to touch an\nEC OpRegion (battery, thermal, backlight) exercises the dangling\npointer.\n\nFix this by calling ec_remove_handlers() in the error path of\nacpi_ec_setup() before clearing first_ec. ec_remove_handlers()\nchecks each EC_FLAGS_* bit before acting, so it is safe to call\nregardless of how far ec_install_handlers() progressed:\n\n -ENODEV (handler not installed): only calls acpi_ec_stop()\n -EPROBE_DEFER (handler installed): removes handler, stops EC(CVE-2026-31426)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: skb: fix cross-cache free of KFENCE-allocated skb head\n\nSKB_SMALL_HEAD_CACHE_SIZE is intentionally set to a non-power-of-2\nvalue (e.g. 704 on x86_64) to avoid collisions with generic kmalloc\nbucket sizes. This ensures that skb_kfree_head() can reliably use\nskb_end_offset to distinguish skb heads allocated from\nskb_small_head_cache vs. generic kmalloc caches.\n\nHowever, when KFENCE is enabled, kfence_ksize() returns the exact\nrequested allocation size instead of the slab bucket size. If a caller\n(e.g. bpf_test_init) allocates skb head data via kzalloc() and the\nrequested size happens to equal SKB_SMALL_HEAD_CACHE_SIZE, then\nslab_build_skb() -\u0026gt; ksize() returns that exact value. After subtracting\nskb_shared_info overhead, skb_end_offset ends up matching\nSKB_SMALL_HEAD_HEADROOM, causing skb_kfree_head() to incorrectly free\nthe object to skb_small_head_cache instead of back to the original\nkmalloc cache, resulting in a slab cross-cache free:\n\n kmem_cache_free(skbuff_small_head): Wrong slab cache. Expected\n skbuff_small_head but got kmalloc-1k\n\nFix this by always calling kfree(head) in skb_kfree_head(). This keeps\nthe free path generic and avoids allocator-specific misclassification\nfor KFENCE objects.(CVE-2026-31429)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nX.509: Fix out-of-bounds access when parsing extensions\n\nLeo reports an out-of-bounds access when parsing a certificate with\nempty Basic Constraints or Key Usage extension because the first byte of\nthe extension is read before checking its length. Fix it.\n\nThe bug can be triggered by an unprivileged user by submitting a\nspecially crafted certificate to the kernel through the keyrings(7) API.\nLeo has demonstrated this with a proof-of-concept program responsibly\ndisclosed off-list.(CVE-2026-31430)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix memory leak when a wq is reset\n\nidxd_wq_disable_cleanup() which is called from the reset path for a\nworkqueue, sets the wq type to NONE, which for other parts of the\ndriver mean that the wq is empty (all its resources were released).\n\nOnly set the wq type to NONE after its resources are released.(CVE-2026-31441)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix possible invalid memory access after FLR\n\nIn the case that the first Function Level Reset (FLR) concludes\ncorrectly, but in the second FLR the scratch area for the saved\nconfiguration cannot be allocated, it\u0026apos;s possible for a invalid memory\naccess to happen.\n\nAlways set the deallocated scratch area to NULL after FLR completes.(CVE-2026-31442)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix use-after-free in update_super_work when racing with umount\n\nCommit b98535d09179 (\u0026quot;ext4: fix bug_on in start_this_handle during umount\nfilesystem\u0026quot;) moved ext4_unregister_sysfs() before flushing s_sb_upd_work\nto prevent new error work from being queued via /proc/fs/ext4/xx/mb_groups\nreads during unmount. However, this introduced a use-after-free because\nupdate_super_work calls ext4_notify_error_sysfs() -\u0026gt; sysfs_notify() which\naccesses the kobject\u0026apos;s kernfs_node after it has been freed by kobject_del()\nin ext4_unregister_sysfs():\n\n update_super_work ext4_put_super\n ----------------- --------------\n ext4_unregister_sysfs(sb)\n kobject_del(\u0026amp;sbi-\u0026gt;s_kobj)\n __kobject_del()\n sysfs_remove_dir()\n kobj-\u0026gt;sd = NULL\n sysfs_put(sd)\n kernfs_put() // RCU free\n ext4_notify_error_sysfs(sbi)\n sysfs_notify(\u0026amp;sbi-\u0026gt;s_kobj)\n kn = kobj-\u0026gt;sd // stale pointer\n kernfs_get(kn) // UAF on freed kernfs_node\n ext4_journal_destroy()\n flush_work(\u0026amp;sbi-\u0026gt;s_sb_upd_work)\n\nInstead of reordering the teardown sequence, fix this by making\next4_notify_error_sysfs() detect that sysfs has already been torn down\nby checking s_kobj.state_in_sysfs, and skipping the sysfs_notify() call\nin that case. A dedicated mutex (s_error_notify_mutex) serializes\next4_notify_error_sysfs() against kobject_del() in ext4_unregister_sysfs()\nto prevent TOCTOU races where the kobject could be deleted between the\nstate_in_sysfs check and the sysfs_notify() call.(CVE-2026-31446)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: validate p_idx bounds in ext4_ext_correct_indexes\n\next4_ext_correct_indexes() walks up the extent tree correcting\nindex entries when the first extent in a leaf is modified. Before\naccessing path[k].p_idx-\u0026gt;ei_block, there is no validation that\np_idx falls within the valid range of index entries for that\nlevel.\n\nIf the on-disk extent header contains a corrupted or crafted\neh_entries value, p_idx can point past the end of the allocated\nbuffer, causing a slab-out-of-bounds read.\n\nFix this by validating path[k].p_idx against EXT_LAST_INDEX() at\nboth access sites: before the while loop and inside it. Return\n-EFSCORRUPTED if the index pointer is out of range, consistent\nwith how other bounds violations are handled in the ext4 extent\ntree code.(CVE-2026-31449)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: publish jinode after initialization\n\next4_inode_attach_jinode() publishes ei-\u0026gt;jinode to concurrent users.\nIt used to set ei-\u0026gt;jinode before jbd2_journal_init_jbd_inode(),\nallowing a reader to observe a non-NULL jinode with i_vfs_inode\nstill unset.\n\nThe fast commit flush path can then pass this jinode to\njbd2_wait_inode_data(), which dereferences i_vfs_inode-\u0026gt;i_mapping and\nmay crash.\n\nBelow is the crash I observe:\n```\nBUG: unable to handle page fault for address: 000000010beb47f4\nPGD 110e51067 P4D 110e51067 PUD 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014\nRIP: 0010:xas_find_marked+0x3d/0x2e0\nCode: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f \u0026lt;49\u0026gt; 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02\nRSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246\nRAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003\nRDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10\nRBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec\nR10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000\nR13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88\nFS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0\nPKRU: 55555554\nCall Trace:\n\u0026lt;TASK\u0026gt;\nfilemap_get_folios_tag+0x87/0x2a0\n__filemap_fdatawait_range+0x5f/0xd0\n? srso_alias_return_thunk+0x5/0xfbef5\n? __schedule+0x3e7/0x10c0\n? srso_alias_return_thunk+0x5/0xfbef5\n? srso_alias_return_thunk+0x5/0xfbef5\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\n? cap_safe_nice+0x37/0x70\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\nfilemap_fdatawait_range_keep_errors+0x12/0x40\next4_fc_commit+0x697/0x8b0\n? ext4_file_write_iter+0x64b/0x950\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\n? srso_alias_return_thunk+0x5/0xfbef5\n? vfs_write+0x356/0x480\n? srso_alias_return_thunk+0x5/0xfbef5\n? preempt_count_sub+0x5f/0x80\next4_sync_file+0xf7/0x370\ndo_fsync+0x3b/0x80\n? syscall_trace_enter+0x108/0x1d0\n__x64_sys_fdatasync+0x16/0x20\ndo_syscall_64+0x62/0x2c0\nentry_SYSCALL_64_after_hwframe+0x76/0x7e\n...\n```\n\nFix this by initializing the jbd2_inode first.\nUse smp_wmb() and WRITE_ONCE() to publish ei-\u0026gt;jinode after\ninitialization. Readers use READ_ONCE() to fetch the pointer.(CVE-2026-31450)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: replace BUG_ON with proper error handling in ext4_read_inline_folio\n\nReplace BUG_ON() with proper error handling when inline data size\nexceeds PAGE_SIZE. This prevents kernel panic and allows the system to\ncontinue running while properly reporting the filesystem corruption.\n\nThe error is logged via ext4_error_inode(), the buffer head is released\nto prevent memory leak, and -EFSCORRUPTED is returned to indicate\nfilesystem corruption.(CVE-2026-31451)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: convert inline data to extents when truncate exceeds inline size\n\nAdd a check in ext4_setattr() to convert files from inline data storage\nto extent-based storage when truncate() grows the file size beyond the\ninline capacity. This prevents the filesystem from entering an\ninconsistent state where the inline data flag is set but the file size\nexceeds what can be stored inline.\n\nWithout this fix, the following sequence causes a kernel BUG_ON():\n\n1. Mount filesystem with inode that has inline flag set and small size\n2. truncate(file, 50MB) - grows size but inline flag remains set\n3. sendfile() attempts to write data\n4. ext4_write_inline_data() hits BUG_ON(write_size \u0026gt; inline_capacity)\n\nThe crash occurs because ext4_write_inline_data() expects inline storage\nto accommodate the write, but the actual inline capacity (~60 bytes for\ni_block + ~96 bytes for xattrs) is far smaller than the file size and\nwrite request.\n\nThe fix checks if the new size from setattr exceeds the inode\u0026apos;s actual\ninline capacity (EXT4_I(inode)-\u0026gt;i_inline_size) and converts the file to\nextent-based storage before proceeding with the size change.\n\nThis addresses the root cause by ensuring the inline data flag and file\nsize remain consistent during truncate operations.(CVE-2026-31452)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: add GFP_NOIO in the bio completion if needed\n\nThe bio completion path in the process context (e.g. dm-verity)\nwill directly call into decompression rather than trigger another\nworkqueue context for minimal scheduling latencies, which can\nthen call vm_map_ram() with GFP_KERNEL.\n\nDue to insufficient memory, vm_map_ram() may generate memory\nswapping I/O, which can cause submit_bio_wait to deadlock\nin some scenarios.\n\nTrimmed down the call stack, as follows:\n\nf2fs_submit_read_io\n submit_bio //bio_list is initialized.\n mmc_blk_mq_recovery\n z_erofs_endio\n vm_map_ram\n __pte_alloc_kernel\n __alloc_pages_direct_reclaim\n shrink_folio_list\n __swap_writepage\n submit_bio_wait //bio_list is non-NULL, hang!!!\n\nUse memalloc_noio_{save,restore}() to wrap up this path.(CVE-2026-31467)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvirtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false\n\nA UAF issue occurs when the virtio_net driver is configured with napi_tx=N\nand the device\u0026apos;s IFF_XMIT_DST_RELEASE flag is cleared\n(e.g., during the configuration of tc route filter rules).\n\nWhen IFF_XMIT_DST_RELEASE is removed from the net_device, the network stack\nexpects the driver to hold the reference to skb-\u0026gt;dst until the packet\nis fully transmitted and freed. In virtio_net with napi_tx=N,\nskbs may remain in the virtio transmit ring for an extended period.\n\nIf the network namespace is destroyed while these skbs are still pending,\nthe corresponding dst_ops structure has freed. When a subsequent packet\nis transmitted, free_old_xmit() is triggered to clean up old skbs.\nIt then calls dst_release() on the skb associated with the stale dst_entry.\nSince the dst_ops (referenced by the dst_entry) has already been freed,\na UAF kernel paging request occurs.\n\nfix it by adds skb_dst_drop(skb) in start_xmit to explicitly release\nthe dst reference before the skb is queued in virtio_net.\n\nCall Trace:\n Unable to handle kernel paging request at virtual address ffff80007e150000\n CPU: 2 UID: 0 PID: 6236 Comm: ping Kdump: loaded Not tainted 7.0.0-rc1+ #6 PREEMPT\n ...\n percpu_counter_add_batch+0x3c/0x158 lib/percpu_counter.c:98 (P)\n dst_release+0xe0/0x110 net/core/dst.c:177\n skb_release_head_state+0xe8/0x108 net/core/skbuff.c:1177\n sk_skb_reason_drop+0x54/0x2d8 net/core/skbuff.c:1255\n dev_kfree_skb_any_reason+0x64/0x78 net/core/dev.c:3469\n napi_consume_skb+0x1c4/0x3a0 net/core/skbuff.c:1527\n __free_old_xmit+0x164/0x230 drivers/net/virtio_net.c:611 [virtio_net]\n free_old_xmit drivers/net/virtio_net.c:1081 [virtio_net]\n start_xmit+0x7c/0x530 drivers/net/virtio_net.c:3329 [virtio_net]\n ...\n\nReproduction Steps:\nNETDEV=\u0026quot;enp3s0\u0026quot;\n\nconfig_qdisc_route_filter() {\n tc qdisc del dev $NETDEV root\n tc qdisc add dev $NETDEV root handle 1: prio\n tc filter add dev $NETDEV parent 1:0 \\\n\tprotocol ip prio 100 route to 100 flowid 1:1\n ip route add 192.168.1.100/32 dev $NETDEV realm 100\n}\n\ntest_ns() {\n ip netns add testns\n ip link set $NETDEV netns testns\n ip netns exec testns ifconfig $NETDEV 10.0.32.46/24\n ip netns exec testns ping -c 1 10.0.32.1\n ip netns del testns\n}\n\nconfig_qdisc_route_filter\n\ntest_ns\nsleep 2\ntest_ns(CVE-2026-31469)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nspi: use generic driver_override infrastructure\n\nWhen a driver is probed through __driver_attach(), the bus\u0026apos; match()\ncallback is called without the device lock held, thus accessing the\ndriver_override field without a lock, which can cause a UAF.\n\nFix this by using the driver-core driver_override infrastructure taking\ncare of proper locking internally.\n\nNote that calling match() from __driver_attach() without the device lock\nheld is intentional. [1]\n\nAlso note that we do not enable the driver_override feature of struct\nbus_type, as SPI - in contrast to most other buses - passes \u0026quot;\u0026quot; to\nsysfs_emit() when the driver_override pointer is NULL. Thus, printing\n\u0026quot;\\n\u0026quot; instead of \u0026quot;(null)\\n\u0026quot;.(CVE-2026-31487)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: use netlink policy range checks\n\nReplace manual range and mask validations with netlink policy\nannotations in ctnetlink code paths, so that the netlink core rejects\ninvalid values early and can generate extack errors.\n\n- CTA_PROTOINFO_TCP_STATE: reject values \u0026gt; TCP_CONNTRACK_SYN_SENT2 at\n policy level, removing the manual \u0026gt;= TCP_CONNTRACK_MAX check.\n- CTA_PROTOINFO_TCP_WSCALE_ORIGINAL/REPLY: reject values \u0026gt; TCP_MAX_WSCALE\n (14). The normal TCP option parsing path already clamps to this value,\n but the ctnetlink path accepted 0-255, causing undefined behavior when\n used as a u32 shift count.\n- CTA_FILTER_ORIG_FLAGS/REPLY_FLAGS: use NLA_POLICY_MASK with\n CTA_FILTER_F_ALL, removing the manual mask checks.\n- CTA_EXPECT_FLAGS: use NLA_POLICY_MASK with NF_CT_EXPECT_MASK, adding\n a new mask define grouping all valid expect flags.\n\nExtracted from a broader nf-next patch by Florian Westphal, scoped to\nctnetlink for the fixes tree.(CVE-2026-31495)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conntrack_expect: skip expectations in other netns via proc\n\nSkip expectations that do not reside in this netns.\n\nSimilar to e77e6ff502ea (\u0026quot;netfilter: conntrack: do not dump other netns\u0026apos;s\nconntrack entries via proc\u0026quot;).(CVE-2026-31496)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop\n\nl2cap_config_req() processes CONFIG_REQ for channels in BT_CONNECTED\nstate to support L2CAP reconfiguration (e.g. MTU changes). However,\nsince both CONF_INPUT_DONE and CONF_OUTPUT_DONE are already set from\nthe initial configuration, the reconfiguration path falls through to\nl2cap_ertm_init(), which re-initializes tx_q, srej_q, srej_list, and\nretrans_list without freeing the previous allocations and sets\nchan-\u0026gt;sdu to NULL without freeing the existing skb. This leaks all\npreviously allocated ERTM resources.\n\nAdditionally, l2cap_parse_conf_req() does not validate the minimum\nvalue of remote_mps derived from the RFC max_pdu_size option. A zero\nvalue propagates to l2cap_segment_sdu() where pdu_len becomes zero,\ncausing the while loop to never terminate since len is never\ndecremented, exhausting all available memory.\n\nFix the double-init by skipping l2cap_ertm_init() and\nl2cap_chan_ready() when the channel is already in BT_CONNECTED state,\nwhile still allowing the reconfiguration parameters to be updated\nthrough l2cap_parse_conf_req(). Also add a pdu_len zero check in\nl2cap_segment_sdu() as a safeguard.(CVE-2026-31498)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix deadlock in l2cap_conn_del()\n\nl2cap_conn_del() calls cancel_delayed_work_sync() for both info_timer\nand id_addr_timer while holding conn-\u0026gt;lock. However, the work functions\nl2cap_info_timeout() and l2cap_conn_update_id_addr() both acquire\nconn-\u0026gt;lock, creating a potential AB-BA deadlock if the work is already\nexecuting when l2cap_conn_del() takes the lock.\n\nMove the work cancellations before acquiring conn-\u0026gt;lock and use\ndisable_delayed_work_sync() to additionally prevent the works from\nbeing rearmed after cancellation, consistent with the pattern used in\nhci_conn_del().(CVE-2026-31499)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niavf: fix out-of-bounds writes in iavf_get_ethtool_stats()\n\niavf incorrectly uses real_num_tx_queues for ETH_SS_STATS. Since the\nvalue could change in runtime, we should use num_tx_queues instead.\n\nMoreover iavf_get_ethtool_stats() uses num_active_queues while\niavf_get_sset_count() and iavf_get_stat_strings() use\nreal_num_tx_queues, which triggers out-of-bounds writes when we do\n\u0026quot;ethtool -L\u0026quot; and \u0026quot;ethtool -S\u0026quot; simultaneously [1].\n\nFor example when we change channels from 1 to 8, Thread 3 could be\nscheduled before Thread 2, and out-of-bounds writes could be triggered\nin Thread 3:\n\nThread 1 (ethtool -L) Thread 2 (work) Thread 3 (ethtool -S)\niavf_set_channels()\n...\niavf_alloc_queues()\n-\u0026gt; num_active_queues = 8\niavf_schedule_finish_config()\n iavf_get_sset_count()\n real_num_tx_queues: 1\n -\u0026gt; buffer for 1 queue\n iavf_get_ethtool_stats()\n num_active_queues: 8\n -\u0026gt; out-of-bounds!\n iavf_finish_config()\n -\u0026gt; real_num_tx_queues = 8\n\nUse immutable num_tx_queues in all related functions to avoid the issue.\n\n[1]\n BUG: KASAN: vmalloc-out-of-bounds in iavf_add_one_ethtool_stat+0x200/0x270\n Write of size 8 at addr ffffc900031c9080 by task ethtool/5800\n\n CPU: 1 UID: 0 PID: 5800 Comm: ethtool Not tainted 6.19.0-enjuk-08403-g8137e3db7f1c #241 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x6f/0xb0\n print_report+0x170/0x4f3\n kasan_report+0xe1/0x180\n iavf_add_one_ethtool_stat+0x200/0x270\n iavf_get_ethtool_stats+0x14c/0x2e0\n __dev_ethtool+0x3d0c/0x5830\n dev_ethtool+0x12d/0x270\n dev_ioctl+0x53c/0xe30\n sock_do_ioctl+0x1a9/0x270\n sock_ioctl+0x3d4/0x5e0\n __x64_sys_ioctl+0x137/0x1c0\n do_syscall_64+0xf3/0x690\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n RIP: 0033:0x7f7da0e6e36d\n ...\n \u0026lt;/TASK\u0026gt;\n\n The buggy address belongs to a 1-page vmalloc region starting at 0xffffc900031c9000 allocated at __dev_ethtool+0x3cc9/0x5830\n The buggy address belongs to the physical page: page: refcount:1 mapcount:0 mapping:0000000000000000\n index:0xffff88813a013de0 pfn:0x13a013\n flags: 0x200000000000000(node=0|zone=2)\n raw: 0200000000000000 0000000000000000 dead000000000122 0000000000000000\n raw: ffff88813a013de0 0000000000000000 00000001ffffffff 0000000000000000\n page dumped because: kasan: bad access detected\n\n Memory state around the buggy address:\n ffffc900031c8f80: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n ffffc900031c9000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00\n \u0026gt;ffffc900031c9080: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n ^\n ffffc900031c9100: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8\n ffffc900031c9180: f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8(CVE-2026-31505)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb\n\nBefore using sk pointer, check if it is null.\n\nFix the following:\n\n KASAN: null-ptr-deref in range [0x0000000000000260-0x0000000000000267]\n CPU: 0 UID: 0 PID: 5985 Comm: kworker/0:5 Not tainted 7.0.0-rc4-00029-ga989fde763f4 #1 PREEMPT(full)\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.17.0-9.fc43 06/10/2025\n Workqueue: events l2cap_info_timeout\n RIP: 0010:kasan_byte_accessible+0x12/0x30\n Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df \u0026lt;0f\u0026gt; b6 04 07 3c 08 0f 92 c0 c3 cc cce\n veth0_macvtap: entered promiscuous mode\n RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202\n RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001\n RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c\n RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000\n R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000\n R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001\n FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00005582615a5008 CR3: 000000007007e000 CR4: 0000000000752ef0\n PKRU: 55555554\n Call Trace:\n \u0026lt;TASK\u0026gt;\n __kasan_check_byte+0x12/0x40\n lock_acquire+0x79/0x2e0\n lock_sock_nested+0x48/0x100\n ? l2cap_sock_ready_cb+0x46/0x160\n l2cap_sock_ready_cb+0x46/0x160\n l2cap_conn_start+0x779/0xff0\n ? __pfx_l2cap_conn_start+0x10/0x10\n ? l2cap_info_timeout+0x60/0xa0\n ? __pfx___mutex_lock+0x10/0x10\n l2cap_info_timeout+0x68/0xa0\n ? process_scheduled_works+0xa8d/0x18c0\n process_scheduled_works+0xb6e/0x18c0\n ? __pfx_process_scheduled_works+0x10/0x10\n ? assign_work+0x3d5/0x5e0\n worker_thread+0xa53/0xfc0\n kthread+0x388/0x470\n ? __pfx_worker_thread+0x10/0x10\n ? __pfx_kthread+0x10/0x10\n ret_from_fork+0x51e/0xb90\n ? __pfx_ret_from_fork+0x10/0x10\n veth1_macvtap: entered promiscuous mode\n ? __switch_to+0xc7d/0x1450\n ? __pfx_kthread+0x10/0x10\n ret_from_fork_asm+0x1a/0x30\n \u0026lt;/TASK\u0026gt;\n Modules linked in:\n ---[ end trace 0000000000000000 ]---\n batman_adv: batadv0: Interface activated: batadv_slave_0\n batman_adv: batadv0: Interface activated: batadv_slave_1\n netdevsim netdevsim7 netdevsim0: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim1: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim2: set [1, 0] type 2 family 0 port 6081 - 0\n netdevsim netdevsim7 netdevsim3: set [1, 0] type 2 family 0 port 6081 - 0\n RIP: 0010:kasan_byte_accessible+0x12/0x30\n Code: 79 ff ff ff 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 40 d6 48 c1 ef 03 48 b8 00 00 00 00 00 fc ff df \u0026lt;0f\u0026gt; b6 04 07 3c 08 0f 92 c0 c3 cc cce\n ieee80211 phy39: Selected rate control algorithm \u0026apos;minstrel_ht\u0026apos;\n RSP: 0018:ffffc90006e0f808 EFLAGS: 00010202\n RAX: dffffc0000000000 RBX: ffffffff89746018 RCX: 0000000080000001\n RDX: 0000000000000000 RSI: ffffffff89746018 RDI: 000000000000004c\n RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000\n R10: dffffc0000000000 R11: ffffffff8aae3e70 R12: 0000000000000000\n R13: 0000000000000260 R14: 0000000000000260 R15: 0000000000000001\n FS: 0000000000000000(0000) GS:ffff8880983c2000(0000) knlGS:0000000000000000\n CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 00007f7e16139e9c CR3: 000000000e74e000 CR4: 0000000000752ef0\n PKRU: 55555554\n Kernel panic - not syncing: Fatal exception(CVE-2026-31510)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix dangling pointer on mgmt_add_adv_patterns_monitor_complete\n\nThis fixes the condition checking so mgmt_pending_valid is executed\nwhenever status != -ECANCELED otherwise calling mgmt_pending_free(cmd)\nwould kfree(cmd) without unlinking it from the list first, leaving a\ndangling pointer. Any subsequent list traversal (e.g.,\nmgmt_pending_foreach during __mgmt_power_off, or another\nmgmt_pending_valid call) would dereference freed memory.(CVE-2026-31511)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Validate PDU length before reading SDU length in l2cap_ecred_data_rcv()\n\nl2cap_ecred_data_rcv() reads the SDU length field from skb-\u0026gt;data using\nget_unaligned_le16() without first verifying that skb contains at least\nL2CAP_SDULEN_SIZE (2) bytes. When skb-\u0026gt;len is less than 2, this reads\npast the valid data in the skb.\n\nThe ERTM reassembly path correctly calls pskb_may_pull() before reading\nthe SDU length (l2cap_reassemble_sdu, L2CAP_SAR_START case). Apply the\nsame validation to the Enhanced Credit Based Flow Control data path.(CVE-2026-31512)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: prevent policy_hthresh.work from racing with netns teardown\n\nA XFRM_MSG_NEWSPDINFO request can queue the per-net work item\npolicy_hthresh.work onto the system workqueue.\n\nThe queued callback, xfrm_hash_rebuild(), retrieves the enclosing\nstruct net via container_of(). If the net namespace is torn down\nbefore that work runs, the associated struct net may already have\nbeen freed, and xfrm_hash_rebuild() may then dereference stale memory.\n\nxfrm_policy_fini() already flushes policy_hash_work during teardown,\nbut it does not synchronize policy_hthresh.work.\n\nSynchronize policy_hthresh.work in xfrm_policy_fini() as well, so the\nqueued work cannot outlive the net namespace teardown and access a\nfreed struct net.(CVE-2026-31516)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nesp: fix skb leak with espintcp and async crypto\n\nWhen the TX queue for espintcp is full, esp_output_tail_tcp will\nreturn an error and not free the skb, because with synchronous crypto,\nthe common xfrm output code will drop the packet for us.\n\nWith async crypto (esp_output_done), we need to drop the skb when\nesp_output_tail_tcp returns an error.(CVE-2026-31518)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix undefined behavior in interpreter sdiv/smod for INT_MIN\n\nThe BPF interpreter\u0026apos;s signed 32-bit division and modulo handlers use\nthe kernel abs() macro on s32 operands. The abs() macro documentation\n(include/linux/math.h) explicitly states the result is undefined when\nthe input is the type minimum. When DST contains S32_MIN (0x80000000),\nabs((s32)DST) triggers undefined behavior and returns S32_MIN unchanged\non arm64/x86. This value is then sign-extended to u64 as\n0xFFFFFFFF80000000, causing do_div() to compute the wrong result.\n\nThe verifier\u0026apos;s abstract interpretation (scalar32_min_max_sdiv) computes\nthe mathematically correct result for range tracking, creating a\nverifier/interpreter mismatch that can be exploited for out-of-bounds\nmap value access.\n\nIntroduce abs_s32() which handles S32_MIN correctly by casting to u32\nbefore negating, avoiding signed overflow entirely. Replace all 8\nabs((s32)...) call sites in the interpreter\u0026apos;s sdiv32/smod32 handlers.\n\ns32 is the only affected case -- the s64 division/modulo handlers do\nnot use abs().(CVE-2026-31525)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf: Make sure to use pmu_ctx-\u0026gt;pmu for groups\n\nOliver reported that x86_pmu_del() ended up doing an out-of-bound memory access\nwhen group_sched_in() fails and needs to roll back.\n\nThis *should* be handled by the transaction callbacks, but he found that when\nthe group leader is a software event, the transaction handlers of the wrong PMU\nare used. Despite the move_group case in perf_event_open() and group_sched_in()\nusing pmu_ctx-\u0026gt;pmu.\n\nTurns out, inherit uses event-\u0026gt;pmu to clone the events, effectively undoing the\nmove_group case for all inherited contexts. Fix this by also making inherit use\npmu_ctx-\u0026gt;pmu, ensuring all inherited counters end up in the same pmu context.\n\nSimilarly, __perf_event_read() should use equally use pmu_ctx-\u0026gt;pmu for the\ngroup case.(CVE-2026-31528)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: nexthop: allocate skb dynamically in rtm_get_nexthop()\n\nWhen querying a nexthop object via RTM_GETNEXTHOP, the kernel currently\nallocates a fixed-size skb using NLMSG_GOODSIZE. While sufficient for\nsingle nexthops and small Equal-Cost Multi-Path groups, this fixed\nallocation fails for large nexthop groups like 512 nexthops.\n\nThis results in the following warning splat:\n\n WARNING: net/ipv4/nexthop.c:3395 at rtm_get_nexthop+0x176/0x1c0, CPU#20: rep/4608\n [...]\n RIP: 0010:rtm_get_nexthop (net/ipv4/nexthop.c:3395)\n [...]\n Call Trace:\n \u0026lt;TASK\u0026gt;\n rtnetlink_rcv_msg (net/core/rtnetlink.c:6989)\n netlink_rcv_skb (net/netlink/af_netlink.c:2550)\n netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)\n netlink_sendmsg (net/netlink/af_netlink.c:1894)\n ____sys_sendmsg (net/socket.c:721 net/socket.c:736 net/socket.c:2585)\n ___sys_sendmsg (net/socket.c:2641)\n __sys_sendmsg (net/socket.c:2671)\n do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)\n entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n \u0026lt;/TASK\u0026gt;\n\nFix this by allocating the size dynamically using nh_nlmsg_size() and\nusing nlmsg_new(), this is consistent with nexthop_notify() behavior. In\naddition, adjust nh_nlmsg_size_grp() so it calculates the size needed\nbased on flags passed. While at it, also add the size of NHA_FDB for\nnexthop group size calculation as it was missing too.\n\nThis cannot be reproduced via iproute2 as the group size is currently\nlimited and the command fails as follows:\n\naddattr_l ERROR: message exceeded bound of 1048(CVE-2026-31531)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: raw: fix ro-\u0026gt;uniq use-after-free in raw_rcv()\n\nraw_release() unregisters raw CAN receive filters via can_rx_unregister(),\nbut receiver deletion is deferred with call_rcu(). This leaves a window\nwhere raw_rcv() may still be running in an RCU read-side critical section\nafter raw_release() frees ro-\u0026gt;uniq, leading to a use-after-free of the\npercpu uniq storage.\n\nMove free_percpu(ro-\u0026gt;uniq) out of raw_release() and into a raw-specific\nsocket destructor. can_rx_unregister() takes an extra reference to the\nsocket and only drops it from the RCU callback, so freeing uniq from\nsk_destruct ensures the percpu area is not released until the relevant\ncallbacks have drained.\n\n[mkl: applied manually](CVE-2026-31532)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/tls: fix use-after-free in -EBUSY error path of tls_do_encryption\n\nThe -EBUSY handling in tls_do_encryption(), introduced by commit\n859054147318 (\u0026quot;net: tls: handle backlogging of crypto requests\u0026quot;), has\na use-after-free due to double cleanup of encrypt_pending and the\nscatterlist entry.\n\nWhen crypto_aead_encrypt() returns -EBUSY, the request is enqueued to\nthe cryptd backlog and the async callback tls_encrypt_done() will be\ninvoked upon completion. That callback unconditionally restores the\nscatterlist entry (sge-\u0026gt;offset, sge-\u0026gt;length) and decrements\nctx-\u0026gt;encrypt_pending. However, if tls_encrypt_async_wait() returns an\nerror, the synchronous error path in tls_do_encryption() performs the\nsame cleanup again, double-decrementing encrypt_pending and\ndouble-restoring the scatterlist.\n\nThe double-decrement corrupts the encrypt_pending sentinel (initialized\nto 1), making tls_encrypt_async_wait() permanently skip the wait for\npending async callbacks. A subsequent sendmsg can then free the\ntls_rec via bpf_exec_tx_verdict() while a cryptd callback is still\npending, resulting in a use-after-free when the callback fires on the\nfreed record.\n\nFix this by skipping the synchronous cleanup when the -EBUSY async\nwait returns an error, since the callback has already handled\nencrypt_pending and sge restoration.(CVE-2026-31533)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/i915/gt: Check set_default_submission() before deferencing\n\nWhen the i915 driver firmware binaries are not present, the\nset_default_submission pointer is not set. This pointer is\ndereferenced during suspend anyways.\n\nAdd a check to make sure it is set before dereferencing.\n\n[ 23.289926] PM: suspend entry (deep)\n[ 23.293558] Filesystems sync: 0.000 seconds\n[ 23.298010] Freezing user space processes\n[ 23.302771] Freezing user space processes completed (elapsed 0.000 seconds)\n[ 23.309766] OOM killer disabled.\n[ 23.313027] Freezing remaining freezable tasks\n[ 23.318540] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)\n[ 23.342038] serial 00:05: disabled\n[ 23.345719] serial 00:02: disabled\n[ 23.349342] serial 00:01: disabled\n[ 23.353782] sd 0:0:0:0: [sda] Synchronizing SCSI cache\n[ 23.358993] sd 1:0:0:0: [sdb] Synchronizing SCSI cache\n[ 23.361635] ata1.00: Entering standby power mode\n[ 23.368863] ata2.00: Entering standby power mode\n[ 23.445187] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[ 23.452194] #PF: supervisor instruction fetch in kernel mode\n[ 23.457896] #PF: error_code(0x0010) - not-present page\n[ 23.463065] PGD 0 P4D 0\n[ 23.465640] Oops: Oops: 0010 [#1] SMP NOPTI\n[ 23.469869] CPU: 8 UID: 0 PID: 211 Comm: kworker/u48:18 Tainted: G S W 6.19.0-rc4-00020-gf0b9d8eb98df #10 PREEMPT(voluntary)\n[ 23.482512] Tainted: [S]=CPU_OUT_OF_SPEC, [W]=WARN\n[ 23.496511] Workqueue: async async_run_entry_fn\n[ 23.501087] RIP: 0010:0x0\n[ 23.503755] Code: Unable to access opcode bytes at 0xffffffffffffffd6.\n[ 23.510324] RSP: 0018:ffffb4a60065fca8 EFLAGS: 00010246\n[ 23.515592] RAX: 0000000000000000 RBX: ffff9f428290e000 RCX: 000000000000000f\n[ 23.522765] RDX: 0000000000000000 RSI: 0000000000000282 RDI: ffff9f428290e000\n[ 23.529937] RBP: ffff9f4282907070 R08: ffff9f4281130428 R09: 00000000ffffffff\n[ 23.537111] R10: 0000000000000000 R11: 0000000000000001 R12: ffff9f42829070f8\n[ 23.544284] R13: ffff9f4282906028 R14: ffff9f4282900000 R15: ffff9f4282906b68\n[ 23.551457] FS: 0000000000000000(0000) GS:ffff9f466b2cf000(0000) knlGS:0000000000000000\n[ 23.559588] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 23.565365] CR2: ffffffffffffffd6 CR3: 000000031c230001 CR4: 0000000000f70ef0\n[ 23.572539] PKRU: 55555554\n[ 23.575281] Call Trace:\n[ 23.577770] \u0026lt;TASK\u0026gt;\n[ 23.579905] intel_engines_reset_default_submission+0x42/0x60\n[ 23.585695] __intel_gt_unset_wedged+0x191/0x200\n[ 23.590360] intel_gt_unset_wedged+0x20/0x40\n[ 23.594675] gt_sanitize+0x15e/0x170\n[ 23.598290] i915_gem_suspend_late+0x6b/0x180\n[ 23.602692] i915_drm_suspend_late+0x35/0xf0\n[ 23.607008] ? __pfx_pci_pm_suspend_late+0x10/0x10\n[ 23.611843] dpm_run_callback+0x78/0x1c0\n[ 23.615817] device_suspend_late+0xde/0x2e0\n[ 23.620037] async_suspend_late+0x18/0x30\n[ 23.624082] async_run_entry_fn+0x25/0xa0\n[ 23.628129] process_one_work+0x15b/0x380\n[ 23.632182] worker_thread+0x2a5/0x3c0\n[ 23.635973] ? __pfx_worker_thread+0x10/0x10\n[ 23.640279] kthread+0xf6/0x1f0\n[ 23.643464] ? __pfx_kthread+0x10/0x10\n[ 23.647263] ? __pfx_kthread+0x10/0x10\n[ 23.651045] ret_from_fork+0x131/0x190\n[ 23.654837] ? __pfx_kthread+0x10/0x10\n[ 23.658634] ret_from_fork_asm+0x1a/0x30\n[ 23.662597] \u0026lt;/TASK\u0026gt;\n[ 23.664826] Modules linked in:\n[ 23.667914] CR2: 0000000000000000\n[ 23.671271] ------------[ cut here ]------------\n\n(cherry picked from commit daa199abc3d3d1740c9e3a2c3e9216ae5b447cad)(CVE-2026-31540)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/platform/uv: Handle deconfigured sockets\n\nWhen a socket is deconfigured, it\u0026apos;s mapped to SOCK_EMPTY (0xffff). This causes\na panic while allocating UV hub info structures.\n\nFix this by using NUMA_NO_NODE, allowing UV hub info structures to be\nallocated on valid nodes.(CVE-2026-31542)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: bonding: fix NULL deref in bond_debug_rlb_hash_show\n\nrlb_clear_slave intentionally keeps RLB hash-table entries on\nthe rx_hashtbl_used_head list with slave set to NULL when no\nreplacement slave is available. However, bond_debug_rlb_hash_show\nvisites client_info-\u0026gt;slave without checking if it\u0026apos;s NULL.\n\nOther used-list iterators in bond_alb.c already handle this NULL-slave\nstate safely:\n\n- rlb_update_client returns early on !client_info-\u0026gt;slave\n- rlb_req_update_slave_clients, rlb_clear_slave, and rlb_rebalance\ncompare slave values before visiting\n- lb_req_update_subnet_clients continues if slave is NULL\n\nThe following NULL deref crash can be trigger in\nbond_debug_rlb_hash_show:\n\n[ 1.289791] BUG: kernel NULL pointer dereference, address: 0000000000000000\n[ 1.292058] RIP: 0010:bond_debug_rlb_hash_show (drivers/net/bonding/bond_debugfs.c:41)\n[ 1.293101] RSP: 0018:ffffc900004a7d00 EFLAGS: 00010286\n[ 1.293333] RAX: 0000000000000000 RBX: ffff888102b48200 RCX: ffff888102b48204\n[ 1.293631] RDX: ffff888102b48200 RSI: ffffffff839daad5 RDI: ffff888102815078\n[ 1.293924] RBP: ffff888102815078 R08: ffff888102b4820e R09: 0000000000000000\n[ 1.294267] R10: 0000000000000000 R11: 0000000000000000 R12: ffff888100f929c0\n[ 1.294564] R13: ffff888100f92a00 R14: 0000000000000001 R15: ffffc900004a7ed8\n[ 1.294864] FS: 0000000001395380(0000) GS:ffff888196e75000(0000) knlGS:0000000000000000\n[ 1.295239] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[ 1.295480] CR2: 0000000000000000 CR3: 0000000102adc004 CR4: 0000000000772ef0\n[ 1.295897] Call Trace:\n[ 1.296134] seq_read_iter (fs/seq_file.c:231)\n[ 1.296341] seq_read (fs/seq_file.c:164)\n[ 1.296493] full_proxy_read (fs/debugfs/file.c:378 (discriminator 1))\n[ 1.296658] vfs_read (fs/read_write.c:572)\n[ 1.296981] ksys_read (fs/read_write.c:717)\n[ 1.297132] do_syscall_64 (arch/x86/entry/syscall_64.c:63 (discriminator 1) arch/x86/entry/syscall_64.c:94 (discriminator 1))\n[ 1.297325] entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130)\n\nAdd a NULL check and print \u0026quot;(none)\u0026quot; for entries with no assigned slave.(CVE-2026-31546)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Clear stale exiting pointer in futex_lock_pi() retry path\n\nFuzzying/stressing futexes triggered:\n\n WARNING: kernel/futex/core.c:825 at wait_for_owner_exiting+0x7a/0x80, CPU#11: futex_lock_pi_s/524\n\nWhen futex_lock_pi_atomic() sees the owner is exiting, it returns -EBUSY\nand stores a refcounted task pointer in \u0026apos;exiting\u0026apos;.\n\nAfter wait_for_owner_exiting() consumes that reference, the local pointer\nis never reset to nil. Upon a retry, if futex_lock_pi_atomic() returns a\ndifferent error, the bogus pointer is passed to wait_for_owner_exiting().\n\n CPU0\t\t\t CPU1\t\t CPU2\n futex_lock_pi(uaddr)\n // acquires the PI futex\n exit()\n futex_cleanup_begin()\n futex_state = EXITING;\n\t\t\t futex_lock_pi(uaddr)\n\t\t\t futex_lock_pi_atomic()\n\t\t\t\t attach_to_pi_owner()\n\t\t\t\t // observes EXITING\n\t\t\t\t *exiting = owner; // takes ref\n\t\t\t\t return -EBUSY\n\t\t\t wait_for_owner_exiting(-EBUSY, owner)\n\t\t\t\t put_task_struct(); // drops ref\n\t\t\t // exiting still points to owner\n\t\t\t goto retry;\n\t\t\t futex_lock_pi_atomic()\n\t\t\t\t lock_pi_update_atomic()\n\t\t\t\t cmpxchg(uaddr)\n\t\t\t\t\t*uaddr ^= WAITERS // whatever\n\t\t\t\t // value changed\n\t\t\t\t return -EAGAIN;\n\t\t\t wait_for_owner_exiting(-EAGAIN, exiting) // stale\n\t\t\t\t WARN_ON_ONCE(exiting)\n\nFix this by resetting upon retry, essentially aligning it with requeue_pi.(CVE-2026-31555)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix fence put before wait in amdgpu_amdkfd_submit_ib\n\namdgpu_amdkfd_submit_ib() submits a GPU job and gets a fence\nfrom amdgpu_ib_schedule(). This fence is used to wait for job\ncompletion.\n\nCurrently, the code drops the fence reference using dma_fence_put()\nbefore calling dma_fence_wait().\n\nIf dma_fence_put() releases the last reference, the fence may be\nfreed before dma_fence_wait() is called. This can lead to a\nuse-after-free.\n\nFix this by waiting on the fence first and releasing the reference\nonly after dma_fence_wait() completes.\n\nFixes the below:\ndrivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:697 amdgpu_amdkfd_submit_ib() warn: passing freed memory \u0026apos;f\u0026apos; (line 696)\n\n(cherry picked from commit 8b9e5259adc385b61a6590a13b82ae0ac2bd3482)(CVE-2026-31566)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncan: gw: fix OOB heap access in cgw_csum_crc8_rel()\n\ncgw_csum_crc8_rel() correctly computes bounds-safe indices via calc_idx():\n\n int from = calc_idx(crc8-\u0026gt;from_idx, cf-\u0026gt;len);\n int to = calc_idx(crc8-\u0026gt;to_idx, cf-\u0026gt;len);\n int res = calc_idx(crc8-\u0026gt;result_idx, cf-\u0026gt;len);\n\n if (from \u0026lt; 0 || to \u0026lt; 0 || res \u0026lt; 0)\n return;\n\nHowever, the loop and the result write then use the raw s8 fields directly\ninstead of the computed variables:\n\n for (i = crc8-\u0026gt;from_idx; ...) /* BUG: raw negative index */\n cf-\u0026gt;data[crc8-\u0026gt;result_idx] = ...; /* BUG: raw negative index */\n\nWith from_idx = to_idx = result_idx = -64 on a 64-byte CAN FD frame,\ncalc_idx(-64, 64) = 0 so the guard passes, but the loop iterates with\ni = -64, reading cf-\u0026gt;data[-64], and the write goes to cf-\u0026gt;data[-64].\nThis write might end up to 56 (7.0-rc) or 40 (\u0026lt;= 6.19) bytes before the\nstart of the canfd_frame on the heap.\n\nThe companion function cgw_csum_xor_rel() uses `from`/`to`/`res`\ncorrectly throughout; fix cgw_csum_crc8_rel() to match.\n\nConfirmed with KASAN on linux-7.0-rc2:\n BUG: KASAN: slab-out-of-bounds in cgw_csum_crc8_rel+0x515/0x5b0\n Read of size 1 at addr ffff8880076619c8 by task poc_cgw_oob/62\n\nTo configure the can-gw crc8 checksums CAP_NET_ADMIN is needed.(CVE-2026-31570)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION\n\nDrop the WARN in sev_pin_memory() on npages overflowing an int, as the\nWARN is comically trivially to trigger from userspace, e.g. by doing:\n\n struct kvm_enc_region range = {\n .addr = 0,\n .size = -1ul,\n };\n\n __vm_ioctl(vm, KVM_MEMORY_ENCRYPT_REG_REGION, \u0026amp;range);\n\nNote, the checks in sev_mem_enc_register_region() that presumably exist to\nverify the incoming address+size are completely worthless, as both \u0026quot;addr\u0026quot;\nand \u0026quot;size\u0026quot; are u64s and SEV is 64-bit only, i.e. they _can\u0026apos;t_ be greater\nthan ULONG_MAX. That wart will be cleaned up in the near future.\n\n\tif (range-\u0026gt;addr \u0026gt; ULONG_MAX || range-\u0026gt;size \u0026gt; ULONG_MAX)\n\t\treturn -EINVAL;\n\nOpportunistically add a comment to explain why the code calculates the\nnumber of pages the \u0026quot;hard\u0026quot; way, e.g. instead of just shifting @ulen.(CVE-2026-31590)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: endpoint: pci-epf-vntb: Stop cmd_handler work in epf_ntb_epc_cleanup\n\nDisable the delayed work before clearing BAR mappings and doorbells to\navoid running the handler after resources have been torn down.\n\n Unable to handle kernel paging request at virtual address ffff800083f46004\n [...]\n Internal error: Oops: 0000000096000007 [#1] SMP\n [...]\n Call trace:\n epf_ntb_cmd_handler+0x54/0x200 [pci_epf_vntb] (P)\n process_one_work+0x154/0x3b0\n worker_thread+0x2c8/0x400\n kthread+0x148/0x210\n ret_from_fork+0x10/0x20(CVE-2026-31595)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU: Fix FPDSS on Zen1\n\nZen1\u0026apos;s hardware divider can leave, under certain circumstances, partial\nresults from previous operations. Those results can be leaked by\nanother, attacker thread.\n\nFix that with a chicken bit.(CVE-2026-31628)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nrxrpc: proc: size address buffers for %pISpc output\n\nThe AF_RXRPC procfs helpers format local and remote socket addresses into\nfixed 50-byte stack buffers with \u0026quot;%pISpc\u0026quot;.\n\nThat is too small for the longest current-tree IPv6-with-port form the\nformatter can produce. In lib/vsprintf.c, the compressed IPv6 path uses a\ndotted-quad tail not only for v4mapped addresses, but also for ISATAP\naddresses via ipv6_addr_is_isatap().\n\nAs a result, a case such as\n\n [ffff:ffff:ffff:ffff:0:5efe:255.255.255.255]:65535\n\nis possible with the current formatter. That is 50 visible characters, so\n51 bytes including the trailing NUL, which does not fit in the existing\nchar[50] buffers used by net/rxrpc/proc.c.\n\nSize the buffers from the formatter\u0026apos;s maximum textual form and switch the\ncall sites to scnprintf().\n\nChanges since v1:\n- correct the changelog to cite the actual maximum current-tree case\n explicitly\n- frame the proof around the ISATAP formatting path instead of the earlier\n mapped-v4 example(CVE-2026-31630)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmmc: vub300: fix NULL-deref on disconnect\n\nMake sure to deregister the controller before dropping the reference to\nthe driver data on disconnect to avoid NULL-pointer dereferences or\nuse-after-free.(CVE-2026-31651)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: fix use-after-free in timeout object destroy\n\nnft_ct_timeout_obj_destroy() frees the timeout object with kfree()\nimmediately after nf_ct_untimeout(), without waiting for an RCU grace\nperiod. Concurrent packet processing on other CPUs may still hold\nRCU-protected references to the timeout object obtained via\nrcu_dereference() in nf_ct_timeout_data().\n\nAdd an rcu_head to struct nf_ct_timeout and use kfree_rcu() to defer\nfreeing until after an RCU grace period, matching the approach already\nused in nfnetlink_cttimeout.c.\n\nKASAN report:\n BUG: KASAN: slab-use-after-free in nf_conntrack_tcp_packet+0x1381/0x29d0\n Read of size 4 at addr ffff8881035fe19c by task exploit/80\n\n Call Trace:\n nf_conntrack_tcp_packet+0x1381/0x29d0\n nf_conntrack_in+0x612/0x8b0\n nf_hook_slow+0x70/0x100\n __ip_local_out+0x1b2/0x210\n tcp_sendmsg_locked+0x722/0x1580\n __sys_sendto+0x2d8/0x320\n\n Allocated by task 75:\n nft_ct_timeout_obj_init+0xf6/0x290\n nft_obj_init+0x107/0x1b0\n nf_tables_newobj+0x680/0x9c0\n nfnetlink_rcv_batch+0xc29/0xe00\n\n Freed by task 26:\n nft_obj_destroy+0x3f/0xa0\n nf_tables_trans_destroy_work+0x51c/0x5c0\n process_one_work+0x2c4/0x5a0(CVE-2026-31665)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: uinput - fix circular locking dependency with ff-core\n\nA lockdep circular locking dependency warning can be triggered\nreproducibly when using a force-feedback gamepad with uinput (for\nexample, playing ELDEN RING under Wine with a Flydigi Vader 5\ncontroller):\n\n ff-\u0026gt;mutex -\u0026gt; udev-\u0026gt;mutex -\u0026gt; input_mutex -\u0026gt; dev-\u0026gt;mutex -\u0026gt; ff-\u0026gt;mutex\n\nThe cycle is caused by four lock acquisition paths:\n\n1. ff upload: input_ff_upload() holds ff-\u0026gt;mutex and calls\n uinput_dev_upload_effect() -\u0026gt; uinput_request_submit() -\u0026gt;\n uinput_request_send(), which acquires udev-\u0026gt;mutex.\n\n2. device create: uinput_ioctl_handler() holds udev-\u0026gt;mutex and calls\n uinput_create_device() -\u0026gt; input_register_device(), which acquires\n input_mutex.\n\n3. device register: input_register_device() holds input_mutex and\n calls kbd_connect() -\u0026gt; input_register_handle(), which acquires\n dev-\u0026gt;mutex.\n\n4. evdev release: evdev_release() calls input_flush_device() under\n dev-\u0026gt;mutex, which calls input_ff_flush() acquiring ff-\u0026gt;mutex.\n\nFix this by introducing a new state_lock spinlock to protect\nudev-\u0026gt;state and udev-\u0026gt;dev access in uinput_request_send() instead of\nacquiring udev-\u0026gt;mutex. The function only needs to atomically check\ndevice state and queue an input event into the ring buffer via\nuinput_dev_event() -- both operations are safe under a spinlock\n(ktime_get_ts64() and wake_up_interruptible() do not sleep). This\nbreaks the ff-\u0026gt;mutex -\u0026gt; udev-\u0026gt;mutex link since a spinlock is a leaf in\nthe lock ordering and cannot form cycles with mutexes.\n\nTo keep state transitions visible to uinput_request_send(), protect\nwrites to udev-\u0026gt;state in uinput_create_device() and\nuinput_destroy_device() with the same state_lock spinlock.\n\nAdditionally, move init_completion(\u0026amp;request-\u0026gt;done) from\nuinput_request_send() to uinput_request_submit() before\nuinput_request_reserve_slot(). Once the slot is allocated,\nuinput_flush_requests() may call complete() on it at any time from\nthe destroy path, so the completion must be initialised before the\nrequest becomes visible.\n\nLock ordering after the fix:\n\n ff-\u0026gt;mutex -\u0026gt; state_lock (spinlock, leaf)\n udev-\u0026gt;mutex -\u0026gt; state_lock (spinlock, leaf)\n udev-\u0026gt;mutex -\u0026gt; input_mutex -\u0026gt; dev-\u0026gt;mutex -\u0026gt; ff-\u0026gt;mutex (no back-edge)(CVE-2026-31667)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_netem: fix out-of-bounds access in packet corruption\n\nIn netem_enqueue(), the packet corruption logic uses\nget_random_u32_below(skb_headlen(skb)) to select an index for\nmodifying skb-\u0026gt;data. When an AF_PACKET TX_RING sends fully non-linear\npackets over an IPIP tunnel, skb_headlen(skb) evaluates to 0.\n\nPassing 0 to get_random_u32_below() takes the variable-ceil slow path\nwhich returns an unconstrained 32-bit random integer. Using this\nunconstrained value as an offset into skb-\u0026gt;data results in an\nout-of-bounds memory access.\n\nFix this by verifying skb_headlen(skb) is non-zero before attempting\nto corrupt the linear data area. Fully non-linear packets will silently\nbypass the corruption logic.(CVE-2026-31675)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af_alg - limit RX SG extraction by receive buffer budget\n\nMake af_alg_get_rsgl() limit each RX scatterlist extraction to the\nremaining receive buffer budget.\n\naf_alg_get_rsgl() currently uses af_alg_readable() only as a gate\nbefore extracting data into the RX scatterlist. Limit each extraction\nto the remaining af_alg_rcvbuf(sk) budget so that receive-side\naccounting matches the amount of data attached to the request.\n\nIf skcipher cannot obtain enough RX space for at least one chunk while\nmore data remains to be processed, reject the recvmsg call instead of\nrounding the request length down to zero.(CVE-2026-31677)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nopenvswitch: defer tunnel netdev_put to RCU release\n\novs_netdev_tunnel_destroy() may run after NETDEV_UNREGISTER already\ndetached the device. Dropping the netdev reference in destroy can race\nwith concurrent readers that still observe vport-\u0026gt;dev.\n\nDo not release vport-\u0026gt;dev in ovs_netdev_tunnel_destroy(). Instead, let\nvport_netdev_free() drop the reference from the RCU callback, matching\nthe non-tunnel destroy path and avoiding additional synchronization\nunder RTNL.(CVE-2026-31678)\n\nIn the Linux kernel, a memory out-of-bounds access vulnerability exists in the act_csum module\u0026apos;s tcf_csum_act() function when processing nested VLAN headers. When an skb still carries in-payload VLAN tags, the function walks nested VLAN headers directly from skb-\u0026gt;data. The current code reads vlan-\u0026gt;h_vlan_encapsulated_proto and then pulls VLAN_HLEN bytes without first ensuring that the full VLAN header is present in the linear area. If only part of an inner VLAN header is linearized, accessing h_vlan_encapsulated_proto reads past the linear area, and the following skb_pull(VLAN_HLEN) may violate skb invariants.(CVE-2026-31684)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ip6t_eui64: reject invalid MAC header for all packets\n\n`eui64_mt6()` derives a modified EUI-64 from the Ethernet source address\nand compares it with the low 64 bits of the IPv6 source address.\n\nThe existing guard only rejects an invalid MAC header when\n`par-\u0026gt;fragoff != 0`. For packets with `par-\u0026gt;fragoff == 0`, `eui64_mt6()`\ncan still reach `eth_hdr(skb)` even when the MAC header is not valid.\n\nFix this by removing the `par-\u0026gt;fragoff != 0` condition so that packets\nwith an invalid MAC header are rejected before accessing `eth_hdr(skb)`.(CVE-2026-31685)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nEDAC/mc: Fix error path ordering in edac_mc_alloc()\n\nWhen the mci-\u0026gt;pvt_info allocation in edac_mc_alloc() fails, the error path\nwill call put_device() which will end up calling the device\u0026apos;s release\nfunction.\n\nHowever, the init ordering is wrong such that device_initialize() happens\n*after* the failed allocation and thus the device itself and the release\nfunction pointer are not initialized yet when they\u0026apos;re called:\n\n MCE: In-kernel MCE decoding enabled.\n ------------[ cut here ]------------\n kobject: \u0026apos;(null)\u0026apos;: is not initialized, yet kobject_put() is being called.\n WARNING: lib/kobject.c:734 at kobject_put, CPU#22: systemd-udevd\n CPU: 22 UID: 0 PID: 538 Comm: systemd-udevd Not tainted 7.0.0-rc1+ #2 PREEMPT(full)\n RIP: 0010:kobject_put\n Call Trace:\n \u0026lt;TASK\u0026gt;\n edac_mc_alloc+0xbe/0xe0 [edac_core]\n amd64_edac_init+0x7a4/0xff0 [amd64_edac]\n ? __pfx_amd64_edac_init+0x10/0x10 [amd64_edac]\n do_one_initcall\n ...\n\nReorder the calling sequence so that the device is initialized and thus the\nrelease function pointer is properly set before it can be used.\n\nThis was found by Claude while reviewing another EDAC patch.(CVE-2026-31689)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy ID to userspace if PSP command failed\n\nWhen retrieving the ID for the CPU, don\u0026apos;t attempt to copy the ID blob to\nuserspace if the firmware command failed. If the failure was due to an\ninvalid length, i.e. the userspace buffer+length was too small, copying\nthe number of bytes _firmware_ requires will overflow the kernel-allocated\nbuffer and leak data to userspace.\n\n BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n Read of size 64 at addr ffff8881867f5960 by task syz.0.906/24388\n\n CPU: 130 UID: 0 PID: 24388 Comm: syz.0.906 Tainted: G U O 7.0.0-smp-DEV #28 PREEMPTLAZY\n Tainted: [U]=USER, [O]=OOT_MODULE\n Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n print_address_description ../mm/kasan/report.c:378 [inline]\n print_report+0xbc/0x260 ../mm/kasan/report.c:482\n kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n check_region_inline ../mm/kasan/generic.c:-1 [inline]\n kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n copy_to_user ../include/linux/uaccess.h:236 [inline]\n sev_ioctl_do_get_id2+0x361/0x490 ../drivers/crypto/ccp/sev-dev.c:2222\n sev_ioctl+0x25f/0x490 ../drivers/crypto/ccp/sev-dev.c:2575\n vfs_ioctl ../fs/ioctl.c:51 [inline]\n __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31697)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy PDH cert to userspace if PSP command failed\n\nWhen retrieving the PDH cert, don\u0026apos;t attempt to copy the blobs to userspace\nif the firmware command failed. If the failure was due to an invalid\nlength, i.e. the userspace buffer+length was too small, copying the number\nof bytes _firmware_ requires will overflow the kernel-allocated buffer and\nleak data to userspace.\n\n BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n Read of size 2084 at addr ffff8885c4ab8aa0 by task syz.0.186/21033\n\n CPU: 51 UID: 0 PID: 21033 Comm: syz.0.186 Tainted: G U O 7.0.0-smp-DEV #28 PREEMPTLAZY\n Tainted: [U]=USER, [O]=OOT_MODULE\n Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.84.12-0 11/17/2025\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n print_address_description ../mm/kasan/report.c:378 [inline]\n print_report+0xbc/0x260 ../mm/kasan/report.c:482\n kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n check_region_inline ../mm/kasan/generic.c:-1 [inline]\n kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n copy_to_user ../include/linux/uaccess.h:236 [inline]\n sev_ioctl_do_pdh_export+0x3d3/0x7c0 ../drivers/crypto/ccp/sev-dev.c:2347\n sev_ioctl+0x2a2/0x490 ../drivers/crypto/ccp/sev-dev.c:2568\n vfs_ioctl ../fs/ioctl.c:51 [inline]\n __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31698)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: ccp: Don\u0026apos;t attempt to copy CSR to userspace if PSP command failed\n\nWhen retrieving the PEK CSR, don\u0026apos;t attempt to copy the blob to userspace\nif the firmware command failed. If the failure was due to an invalid\nlength, i.e. the userspace buffer+length was too small, copying the number\nof bytes _firmware_ requires will overflow the kernel-allocated buffer and\nleak data to userspace.\n\n BUG: KASAN: slab-out-of-bounds in instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n BUG: KASAN: slab-out-of-bounds in _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n BUG: KASAN: slab-out-of-bounds in _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n Read of size 2084 at addr ffff898144612e20 by task syz.9.219/21405\n\n CPU: 14 UID: 0 PID: 21405 Comm: syz.9.219 Tainted: G U O 7.0.0-smp-DEV #28 PREEMPTLAZY\n Tainted: [U]=USER, [O]=OOT_MODULE\n Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 12.62.0-0 11/19/2025\n Call Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xc5/0x110 ../lib/dump_stack.c:120\n print_address_description ../mm/kasan/report.c:378 [inline]\n print_report+0xbc/0x260 ../mm/kasan/report.c:482\n kasan_report+0xa2/0xe0 ../mm/kasan/report.c:595\n check_region_inline ../mm/kasan/generic.c:-1 [inline]\n kasan_check_range+0x264/0x2c0 ../mm/kasan/generic.c:200\n instrument_copy_to_user ../include/linux/instrumented.h:129 [inline]\n _inline_copy_to_user ../include/linux/uaccess.h:205 [inline]\n _copy_to_user+0x66/0xa0 ../lib/usercopy.c:26\n copy_to_user ../include/linux/uaccess.h:236 [inline]\n sev_ioctl_do_pek_csr+0x31f/0x590 ../drivers/crypto/ccp/sev-dev.c:1872\n sev_ioctl+0x3a4/0x490 ../drivers/crypto/ccp/sev-dev.c:2562\n vfs_ioctl ../fs/ioctl.c:51 [inline]\n __do_sys_ioctl ../fs/ioctl.c:597 [inline]\n __se_sys_ioctl+0x11d/0x1b0 ../fs/ioctl.c:583\n do_syscall_x64 ../arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xe0/0x800 ../arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n \u0026lt;/TASK\u0026gt;\n\nWARN if the driver says the command succeeded, but the firmware error code\nsays otherwise, as __sev_do_cmd_locked() is expected to return -EIO on any\nfirwmware error.(CVE-2026-31699)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path\n\nsmb2_ioctl_query_info() has two response-copy branches: PASSTHRU_FSCTL\nand the default QUERY_INFO path. The QUERY_INFO branch clamps\nqi.input_buffer_length to the server-reported OutputBufferLength and then\ncopies qi.input_buffer_length bytes from qi_rsp-\u0026gt;Buffer to userspace, but\nit never verifies that the flexible-array payload actually fits within\nrsp_iov[1].iov_len.\n\nA malicious server can return OutputBufferLength larger than the actual\nQUERY_INFO response, causing copy_to_user() to walk past the response\nbuffer and expose adjacent kernel heap to userspace.\n\nGuard the QUERY_INFO copy with a bounds check on the actual Buffer\npayload. Use struct_size(qi_rsp, Buffer, qi.input_buffer_length)\nrather than an open-coded addition so the guard cannot overflow on\n32-bit builds.(CVE-2026-31708)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvxlan: validate ND option lengths in vxlan_na_create\n\nvxlan_na_create() walks ND options according to option-provided\nlengths. A malformed option can make the parser advance beyond the\ncomputed option span or use a too-short source LLADDR option payload.\n\nValidate option lengths against the remaining NS option area before\nadvancing, and only read source LLADDR when the option is large enough\nfor an Ethernet address.(CVE-2026-31738)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbridge: br_nd_send: validate ND option lengths\n\nbr_nd_send() walks ND options according to option-provided lengths.\nA malformed option can make the parser advance beyond the computed\noption span or use a too-short source LLADDR option payload.\n\nValidate option lengths against the remaining NS option area before\nadvancing, and only read source LLADDR when the option is large enough\nfor an Ethernet address.(CVE-2026-31752)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: gadget: fix NULL pointer dereference in ep_queue\n\nWhen the gadget endpoint is disabled or not yet configured, the ep-\u0026gt;desc\npointer can be NULL. This leads to a NULL pointer dereference when\n__cdns3_gadget_ep_queue() is called, causing a kernel crash.\n\nAdd a check to return -ESHUTDOWN if ep-\u0026gt;desc is NULL, which is the\nstandard return code for unconfigured endpoints.\n\nThis prevents potential crashes when ep_queue is called on endpoints\nthat are not ready.(CVE-2026-31755)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: move wake reason storage into validated event handlers\n\nhci_store_wake_reason() is called from hci_event_packet() immediately\nafter stripping the HCI event header but before hci_event_func()\nenforces the per-event minimum payload length from hci_ev_table.\nThis means a short HCI event frame can reach bacpy() before any bounds\ncheck runs.\n\nRather than duplicating skb parsing and per-event length checks inside\nhci_store_wake_reason(), move wake-address storage into the individual\nevent handlers after their existing event-length validation has\nsucceeded. Convert hci_store_wake_reason() into a small helper that only\nstores an already-validated bdaddr while the caller holds hci_dev_lock().\nUse the same helper after hci_event_func() with a NULL address to\npreserve the existing unexpected-wake fallback semantics when no\nvalidated event handler records a wake address.\n\nAnnotate the helper with __must_hold(\u0026amp;hdev-\u0026gt;lock) and add\nlockdep_assert_held(\u0026amp;hdev-\u0026gt;lock) so future call paths keep the lock\ncontract explicit.\n\nCall the helper from hci_conn_request_evt(), hci_conn_complete_evt(),\nhci_sync_conn_complete_evt(), le_conn_complete_evt(),\nhci_le_adv_report_evt(), hci_le_ext_adv_report_evt(),\nhci_le_direct_adv_report_evt(), hci_le_pa_sync_established_evt(), and\nhci_le_past_received_evt().(CVE-2026-31771)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: SMP: derive legacy responder STK authentication from MITM state\n\nThe legacy responder path in smp_random() currently labels the stored\nSTK as authenticated whenever pending_sec_level is BT_SECURITY_HIGH.\nThat reflects what the local service requested, not what the pairing\nflow actually achieved.\n\nFor Just Works/Confirm legacy pairing, SMP_FLAG_MITM_AUTH stays clear\nand the resulting STK should remain unauthenticated even if the local\nside requested HIGH security. Use the established MITM state when\nstoring the responder STK so the key metadata matches the pairing result.\n\nThis also keeps the legacy path aligned with the Secure Connections code,\nwhich already treats JUST_WORKS/JUST_CFM as unauthenticated.(CVE-2026-31773)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: iwlwifi: mvm: fix potential out-of-bounds read in iwl_mvm_nd_match_info_handler()\n\nThe memcpy function assumes the dynamic array notif-\u0026gt;matches is at least\nas large as the number of bytes to copy. Otherwise, results-\u0026gt;matches may\ncontain unwanted data. To guarantee safety, extend the validation in one\nof the checks to ensure sufficient packet length.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2026-31779)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ioc32: stop speculation on the drm_compat_ioctl path\n\nThe drm compat ioctl path takes a user controlled pointer, and then\ndereferences it into a table of function pointers, the signature method\nof spectre problems. Fix this up by calling array_index_nospec() on the\nindex to the function pointer list.(CVE-2026-31781)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: validate LTK enc_size on load\n\nLoad Long Term Keys stores the user-provided enc_size and later uses\nit to size fixed-size stack operations when replying to LE LTK\nrequests. An enc_size larger than the 16-byte key buffer can therefore\noverflow the reply stack buffer.\n\nReject oversized enc_size values while validating the management LTK\nrecord so invalid keys never reach the stored key state.(CVE-2026-43020)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: use skb_header_pointer() for TCPv4 GSO frag_off check\n\nSyzbot reported a KMSAN uninit-value warning in gso_features_check()\ncalled from netif_skb_features() [1].\n\ngso_features_check() reads iph-\u0026gt;frag_off to decide whether to clear\nmangleid_features. Accessing the IPv4 header via ip_hdr()/inner_ip_hdr()\ncan rely on skb header offsets that are not always safe for direct\ndereference on packets injected from PF_PACKET paths.\n\nUse skb_header_pointer() for the TCPv4 frag_off check so the header read\nis robust whether data is already linear or needs copying.\n\n[1] https://syzkaller.appspot.com/bug?extid=1543a7d954d9c6d00407(CVE-2026-43036)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipv6: ndisc: fix ndisc_ra_useropt to initialize nduseropt_padX fields to zero to prevent an info-leak\n\nWhen processing Router Advertisements with user options the kernel\nbuilds an RTM_NEWNDUSEROPT netlink message. The nduseroptmsg struct\nhas three padding fields that are never zeroed and can leak kernel data\n\nThe fix is simple, just zeroes the padding fields.(CVE-2026-43040)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: af-alg - fix NULL pointer dereference in scatterwalk\n\nThe AF_ALG interface fails to unmark the end of a Scatter/Gather List (SGL)\nwhen chaining a new af_alg_tsgl structure. If a sendmsg() fills an SGL\nexactly to MAX_SGL_ENTS, the last entry is marked as the end. A subsequent\nsendmsg() allocates a new SGL and chains it, but fails to clear the end\nmarker on the previous SGL\u0026apos;s last data entry.\n\nThis causes the crypto scatterwalk to hit a premature end, returning NULL\non sg_next() and leading to a kernel panic during dereference.\n\nFix this by explicitly unmarking the end of the previous SGL when\nperforming sg_chain() in af_alg_alloc_tsgl().(CVE-2026-43043)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nserial: 8250: Fix TX deadlock when using DMA\n\n`dmaengine_terminate_async` does not guarantee that the\n`__dma_tx_complete` callback will run. The callback is currently the\nonly place where `dma-\u0026gt;tx_running` gets cleared. If the transaction is\ncanceled and the callback never runs, then `dma-\u0026gt;tx_running` will never\nget cleared and we will never schedule new TX DMA transactions again.\n\nThis change makes it so we clear `dma-\u0026gt;tx_running` after we terminate\nthe DMA transaction. This is \u0026quot;safe\u0026quot; because `serial8250_tx_dma_flush`\nis holding the UART port lock. The first thing the callback does is also\ngrab the UART port lock, so access to `dma-\u0026gt;tx_running` is serialized.(CVE-2026-43061)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: idxd: Fix not releasing workqueue on .release()\n\nThe workqueue associated with an DSA/IAA device is not released when\nthe object is freed.(CVE-2026-43064)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel/uncore: Skip discovery table for offline dies\n\nThis warning can be triggered if NUMA is disabled and the system\nboots with fewer CPUs than the number of CPUs in die 0.\n\nWARNING: CPU: 9 PID: 7257 at uncore.c:1157 uncore_pci_pmu_register+0x136/0x160 [intel_uncore]\n\nCurrently, the discovery table continues to be parsed even if all CPUs\nin the associated die are offline. This can lead to an array overflow\nat \u0026quot;pmu-\u0026gt;boxes[die] = box\u0026quot; in uncore_pci_pmu_register(), which may\ntrigger the warning above or cause other issues.(CVE-2026-43079)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: icmp: fix null-ptr-deref in icmp_build_probe()\n\nipv6_stub-\u0026gt;ipv6_dev_find() may return ERR_PTR(-EAFNOSUPPORT) when the\nIPv6 stack is not active (CONFIG_IPV6=m and not loaded), and passing\nthis error pointer to dev_hold() will cause a kernel crash with\nnull-ptr-deref.\n\nInstead, silently discard the request. RFC 8335 does not appear to\ndefine a specific response for the case where an IPv6 interface\nidentifier is syntactically valid but the implementation cannot perform\nthe lookup at runtime, and silently dropping the request may safer than\nmisreporting \u0026quot;No Such Interface\u0026quot;.(CVE-2026-43099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npowerpc/smp: Add check for kcalloc() failure in parse_thread_groups()\n\nAs kcalloc() may fail, check its return value to avoid a NULL pointer\ndereference when passing it to of_property_read_u32_array().(CVE-2026-43148)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: enable basic endpoint checking\n\npegasus_probe() fills URBs with hardcoded endpoint pipes without\nverifying the endpoint descriptors:\n\n - usb_rcvbulkpipe(dev, 1) for RX data\n - usb_sndbulkpipe(dev, 2) for TX data\n - usb_rcvintpipe(dev, 3) for status interrupts\n\nA malformed USB device can present these endpoints with transfer types\nthat differ from what the driver assumes.\n\nAdd a pegasus_usb_ep enum for endpoint numbers, replacing magic\nconstants throughout. Add usb_check_bulk_endpoints() and\nusb_check_int_endpoints() calls before any resource allocation to\nverify endpoint types before use, rejecting devices with mismatched\ndescriptors at probe time, and avoid triggering assertion.\n\nSimilar fix to\n- commit 90b7f2961798 (\u0026quot;net: usb: rtl8150: enable basic endpoint checking\u0026quot;)\n- commit 9e7021d2aeae (\u0026quot;net: usb: catc: enable basic endpoint checking\u0026quot;)(CVE-2026-43156)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd/bitmap: fix GPF in write_page caused by resize race\n\nA General Protection Fault occurs in write_page() during array resize:\nRIP: 0010:write_page+0x22b/0x3c0 [md_mod]\n\nThis is a use-after-free race between bitmap_daemon_work() and\n__bitmap_resize(). The daemon iterates over `bitmap-\u0026gt;storage.filemap`\nwithout locking, while the resize path frees that storage via\nmd_bitmap_file_unmap(). `quiesce()` does not stop the md thread,\nallowing concurrent access to freed pages.\n\nFix by holding `mddev-\u0026gt;bitmap_info.mutex` during the bitmap update.(CVE-2026-43163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: ioam: fix heap buffer overflow in __ioam6_fill_trace_data()\n\nOn the receive path, __ioam6_fill_trace_data() uses trace-\u0026gt;nodelen\nto decide how much data to write for each node. It trusts this field\nas-is from the incoming packet, with no consistency check against\ntrace-\u0026gt;type (the 24-bit field that tells which data items are\npresent). A crafted packet can set nodelen=0 while setting type bits\n0-21, causing the function to write ~100 bytes past the allocated\nregion (into skb_shared_info), which corrupts adjacent heap memory\nand leads to a kernel panic.\n\nAdd a shared helper ioam6_trace_compute_nodelen() in ioam6.c to\nderive the expected nodelen from the type field, and use it:\n\n - in ioam6_iptunnel.c (send path, existing validation) to replace\n the open-coded computation;\n - in exthdrs.c (receive path, ipv6_hop_ioam) to drop packets whose\n nodelen is inconsistent with the type field, before any data is\n written.\n\nPer RFC 9197, bits 12-21 are each short (4-octet) fields, so they\nare included in IOAM6_MASK_SHORT_FIELDS (changed from 0xff100000 to\n0xff1ffc00).(CVE-2026-43186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: Make cpumask_of_node() robust against NUMA_NO_NODE\n\nThe arch definition of cpumask_of_node() cannot handle NUMA_NO_NODE -\nwhich is a valid index - so add a check for this.(CVE-2026-43212)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/kexec: add a sanity check on previous kernel\u0026apos;s ima kexec buffer\n\nWhen the second-stage kernel is booted via kexec with a limiting command\nline such as \u0026quot;mem=\u0026lt;size\u0026gt;\u0026quot;, the physical range that contains the carried\nover IMA measurement list may fall outside the truncated RAM leading to a\nkernel panic.\n\n BUG: unable to handle page fault for address: ffff97793ff47000\n RIP: ima_restore_measurement_list+0xdc/0x45a\n #PF: error_code(0x0000) – not-present page\n\nOther architectures already validate the range with page_is_ram(), as done\nin commit cbf9c4b9617b (\u0026quot;of: check previous kernel\u0026apos;s ima-kexec-buffer\nagainst memory bounds\u0026quot;) do a similar check on x86.\n\nWithout carrying the measurement list across kexec, the attestation\nwould fail.(CVE-2026-43240)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: fiemap page fault fix\n\nIn gfs2_fiemap(), we are calling iomap_fiemap() while holding the inode\nglock. This can lead to recursive glock taking if the fiemap buffer is\nmemory mapped to the same inode and accessing it triggers a page fault.\n\nFix by disabling page faults for iomap_fiemap() and faulting in the\nbuffer by hand if necessary.\n\nFixes xfstest generic/742.(CVE-2026-43262)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: supply snapshot context in ceph_zero_partial_object()\n\nThe ceph_zero_partial_object function was missing proper snapshot\ncontext for its OSD write operations, which could lead to data\ninconsistencies in snapshots.\n\nReproducer:\n../src/vstart.sh --new -x --localhost --bluestore\n./bin/ceph auth caps client.fs_a mds \u0026apos;allow rwps fsname=a\u0026apos; mon \u0026apos;allow r fsname=a\u0026apos; osd \u0026apos;allow rw tag cephfs data=a\u0026apos;\nmount -t ceph (CVE-2026-43273)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: move ext4_percpu_param_init() before ext4_mb_init()\n\nWhen running `kvm-xfstests -c ext4/1k -C 1 generic/383` with the\n`DOUBLE_CHECK` macro defined, the following panic is triggered:\n\n==================================================================\nEXT4-fs error (device vdc): ext4_validate_block_bitmap:423:\n comm mount: bg 0: bad block bitmap checksum\nBUG: unable to handle page fault for address: ff110000fa2cc000\nPGD 3e01067 P4D 3e02067 PUD 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 0 UID: 0 PID: 2386 Comm: mount Tainted: G W\n 6.18.0-gba65a4e7120a-dirty #1152 PREEMPT(none)\nRIP: 0010:percpu_counter_add_batch+0x13/0xa0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_mark_group_bitmap_corrupted+0xcb/0xe0\n ext4_validate_block_bitmap+0x2a1/0x2f0\n ext4_read_block_bitmap+0x33/0x50\n mb_group_bb_bitmap_alloc+0x33/0x80\n ext4_mb_add_groupinfo+0x190/0x250\n ext4_mb_init_backend+0x87/0x290\n ext4_mb_init+0x456/0x640\n __ext4_fill_super+0x1072/0x1680\n ext4_fill_super+0xd3/0x280\n get_tree_bdev_flags+0x132/0x1d0\n vfs_get_tree+0x29/0xd0\n vfs_cmd_create+0x59/0xe0\n __do_sys_fsconfig+0x4f6/0x6b0\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n==================================================================\n\nThis issue can be reproduced using the following commands:\n mkfs.ext4 -F -q -b 1024 /dev/sda 5G\n tune2fs -O quota,project /dev/sda\n mount /dev/sda /tmp/test\n\nWith DOUBLE_CHECK defined, mb_group_bb_bitmap_alloc() reads\nand validates the block bitmap. When the validation fails,\next4_mark_group_bitmap_corrupted() attempts to update\nsbi-\u0026gt;s_freeclusters_counter. However, this percpu_counter has not been\ninitialized yet at this point, which leads to the panic described above.\n\nFix this by moving the execution of ext4_percpu_param_init() to occur\nbefore ext4_mb_init(), ensuring the per-CPU counters are initialized\nbefore they are used.(CVE-2026-43288)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/vmalloc: prevent RCU stalls in kasan_release_vmalloc_node\n\nWhen CONFIG_PAGE_OWNER is enabled, freeing KASAN shadow pages during\nvmalloc cleanup triggers expensive stack unwinding that acquires RCU read\nlocks. Processing a large purge_list without rescheduling can cause the\ntask to hold CPU for extended periods (10+ seconds), leading to RCU stalls\nand potential OOM conditions.\n\nThe issue manifests in purge_vmap_node() -\u0026gt; kasan_release_vmalloc_node()\nwhere iterating through hundreds or thousands of vmap_area entries and\nfreeing their associated shadow pages causes:\n\n rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:\n rcu: Tasks blocked on level-0 rcu_node (CPUs 0-1): P6229/1:b..l\n ...\n task:kworker/0:17 state:R running task stack:28840 pid:6229\n ...\n kasan_release_vmalloc_node+0x1ba/0xad0 mm/vmalloc.c:2299\n purge_vmap_node+0x1ba/0xad0 mm/vmalloc.c:2299\n\nEach call to kasan_release_vmalloc() can free many pages, and with\npage_owner tracking, each free triggers save_stack() which performs stack\nunwinding under RCU read lock. Without yielding, this creates an\nunbounded RCU critical section.\n\nAdd periodic cond_resched() calls within the loop to allow:\n- RCU grace periods to complete\n- Other tasks to run\n- Scheduler to preempt when needed\n\nThe fix uses need_resched() for immediate response under load, with a\nbatch count of 32 as a guaranteed upper bound to prevent worst-case stalls\neven under light load.(CVE-2026-43292)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: ipa: fix event ring index not programmed for IPA v5.0+\n\nFor IPA v5.0+, the event ring index field moved from CH_C_CNTXT_0 to\nCH_C_CNTXT_1. The v5.0 register definition intended to define this\nfield in the CH_C_CNTXT_1 fmask array but used the old identifier of\nERINDEX instead of CH_ERINDEX.\n\nWithout a valid event ring, GSI channels could never signal transfer\ncompletions. This caused gsi_channel_trans_quiesce() to block\nforever in wait_for_completion().\n\nAt least for IPA v5.2 this resolves an issue seen where runtime\nsuspend, system suspend, and remoteproc stop all hanged forever. It\nalso meant the IPA data path was completely non functional.(CVE-2026-43345)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/kbuf: check if target buffer list is still legacy on recycle\n\nThere\u0026apos;s a gap between when the buffer was grabbed and when it\npotentially gets recycled, where if the list is empty, someone could\u0026apos;ve\nupgraded it to a ring provided type. This can happen if the request\nis forced via io-wq. The legacy recycling is missing checking if the\nbuffer_list still exists, and if it\u0026apos;s of the correct type. Add those\nchecks.(CVE-2026-43366)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in process_message_header()\n\nIf the message frame is (maliciously) corrupted in a way that the\nlength of the control segment ends up being less than the size of the\nmessage header or a different frame is made to look like a message\nframe, out-of-bounds reads may ensue in process_message_header().\n\nPerform an explicit bounds check before decoding the message header.(CVE-2026-43406)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix memory leaks in ceph_mdsc_build_path()\n\nAdd __putname() calls to error code paths that did not free the \u0026quot;path\u0026quot;\npointer obtained by __getname(). If ownership of this pointer is not\npassed to the caller via path_info.path, the function must free it\nbefore returning.(CVE-2026-43419)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: class: cdc-wdm: fix reordering issue in read code path\n\nQuoting the bug report:\n\nDue to compiler optimization or CPU out-of-order execution, the\ndesc-\u0026gt;length update can be reordered before the memmove. If this\nhappens, wdm_read() can see the new length and call copy_to_user() on\nuninitialized memory. This also violates LKMM data race rules [1].\n\nFix it by using WRITE_ONCE and memory barriers.(CVE-2026-43427)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nUSB: core: Limit the length of unkillable synchronous timeouts\n\nThe usb_control_msg(), usb_bulk_msg(), and usb_interrupt_msg() APIs in\nusbcore allow unlimited timeout durations. And since they use\nuninterruptible waits, this leaves open the possibility of hanging a\ntask for an indefinitely long time, with no way to kill it short of\nunplugging the target device.\n\nTo prevent this sort of problem, enforce a maximum limit on the length\nof these unkillable timeouts. The limit chosen here, somewhat\narbitrarily, is 60 seconds. On many systems (although not all) this\nis short enough to avoid triggering the kernel\u0026apos;s hung-task detector.\n\nIn addition, clear up the ambiguity of negative timeout values by\ntreating them the same as 0, i.e., using the maximum allowed timeout.(CVE-2026-43428)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: Fix deadlock between devlink lock and esw-\u0026gt;wq\n\nesw-\u0026gt;work_queue executes esw_functions_changed_event_handler -\u0026gt;\nesw_vfs_changed_event_handler and acquires the devlink lock.\n\n.eswitch_mode_set (acquires devlink lock in devlink_nl_pre_doit) -\u0026gt;\nmlx5_devlink_eswitch_mode_set -\u0026gt; mlx5_eswitch_disable_locked -\u0026gt;\nmlx5_eswitch_event_handler_unregister -\u0026gt; flush_workqueue deadlocks\nwhen esw_vfs_changed_event_handler executes.\n\nFix that by no longer flushing the work to avoid the deadlock, and using\na generation counter to keep track of work relevance. This avoids an old\nhandler manipulating an esw that has undergone one or more mode changes:\n- the counter is incremented in mlx5_eswitch_event_handler_unregister.\n- the counter is read and passed to the ephemeral mlx5_host_work struct.\n- the work handler takes the devlink lock and bails out if the current\n generation is different than the one it was scheduled to operate on.\n- mlx5_eswitch_cleanup does the final draining before destroying the wq.\n\nNo longer flushing the workqueue has the side effect of maybe no longer\ncancelling pending vport_change_handler work items, but that\u0026apos;s ok since\nthose are disabled elsewhere:\n- mlx5_eswitch_disable_locked disables the vport eq notifier.\n- mlx5_esw_vport_disable disarms the HW EQ notification and marks\n vport-\u0026gt;enabled under state_lock to false to prevent pending vport\n handler from doing anything.\n- mlx5_eswitch_cleanup destroys the workqueue and makes sure all events\n are disabled/finished.(CVE-2026-43468)\n\nIn the Linux kernel, the following vulnerability has been resolved: crypto: pcrypt - Fix handling of MAY_BACKLOG requests MAY_BACKLOG requests can return EBUSY. Handle them by checking for that value and filtering out EINPROGRESS notifications. The Linux kernel CVE team has assigned CVE-2026-43493 to this issue.(CVE-2026-43493)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: skbuff: propagate shared-frag marker through frag-transfer helpers\n\nTwo frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail\nto propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()-\u0026gt;flags when\nmoving frags from source to destination. __pskb_copy_fclone() defers\nthe rest of the shinfo metadata to skb_copy_header() after copying\nfrag descriptors, but that helper only carries over gso_{size,segs,\ntype} and never touches skb_shinfo()-\u0026gt;flags; skb_shift() moves frag\ndescriptors directly and leaves flags untouched. As a result, the\ndestination skb keeps a reference to the same externally-owned or\npage-cache-backed pages while reporting skb_has_shared_frag() as\nfalse.\n\nThe mismatch is harmful in any in-place writer that uses\nskb_has_shared_frag() to decide whether shared pages must be detoured\nthrough skb_cow_data(). ESP input is one such writer (esp4.c,\nesp6.c), and a single nft \u0026apos;dup to \u0026lt;local\u0026gt;\u0026apos; rule -- or any other\nnf_dup_ipv4() / xt_TEE caller -- is enough to land a pskb_copy()\u0026apos;d\nskb in esp_input() with the marker stripped, letting an unprivileged\nuser write into the page cache of a root-owned read-only file via\nauthencesn-ESN stray writes.\n\nSet SKBFL_SHARED_FRAG on the destination whenever frag descriptors\nwere actually moved from the source. skb_copy() and skb_copy_expand()\nshare skb_copy_header() too but linearize all paged data into freshly\nallocated head storage and emerge with nr_frags == 0, so\nskb_has_shared_frag() returns false on its own; they need no change.\n\nThe same omission exists in skb_gro_receive() and skb_gro_receive_list().\nThe former moves the incoming skb\u0026apos;s frag descriptors into the\naccumulator\u0026apos;s last sub-skb via two paths (a direct frag-move loop and\nthe head_frag + memcpy path); the latter chains the incoming skb whole\nonto p\u0026apos;s frag_list. Downstream skb_segment() reads only\nskb_shinfo(p)-\u0026gt;flags, and skb_segment_list() reuses each sub-skb\u0026apos;s\nshinfo as the nskb -- both p and lp must carry the marker.\n\nThe same omission also exists in tcp_clone_payload(), which builds an\nMTU probe skb by moving frag descriptors from skbs on sk_write_queue\ninto a freshly allocated nskb. The helper falls into the same family\nand warrants the same fix for consistency; no TCP TX-side in-place\nwriter is currently known to reach a user page through this gap, but\na future consumer depending on the marker would regress silently.\n\nThe same omission exists in skb_segment(): the per-iteration flag\nmerge takes only head_skb\u0026apos;s flag, and the inner switch that rebinds\nfrag_skb to list_skb on head_skb-frags exhaustion does not fold the\nnew frag_skb\u0026apos;s flag into nskb. Fold frag_skb\u0026apos;s flag at both sites\nso segments drawing frags from frag_list members carry the marker.(CVE-2026-43503)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: L2CAP: Fix null-ptr-deref in l2cap_sock_state_change_cb()\n\nAdd the same NULL guard already present in\nl2cap_sock_resume_cb() and l2cap_sock_ready_cb().(CVE-2026-45834)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix slab-use-after-free in qd_put\n\nCommit a475c5dd16e5 (\u0026quot;gfs2: Free quota data objects synchronously\u0026quot;)\nstarted freeing quota data objects during filesystem shutdown instead of\nputting them back onto the LRU list, but it failed to remove these\nobjects from the LRU list, causing LRU list corruption. This caused\nuse-after-free when the shrinker (gfs2_qd_shrink_scan) tried to access\nalready-freed objects on the LRU list.\n\nFix this by removing qd objects from the LRU list before freeing them in\nqd_put().\n\nInitial fix from Deepanshu Kartikey \u0026lt;(CVE-2026-45861)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: cdns3: fix role switching during resume\n\nIf the role change while we are suspended, the cdns3 driver switches to the\nnew mode during resume. However, switching to host mode in this context\ncauses a NULL pointer dereference.\n\nThe host role\u0026apos;s start() operation registers a xhci-hcd device, but its\nprobe is deferred while we are in the resume path. The host role\u0026apos;s resume()\noperation assumes the xhci-hcd device is already probed, which is not the\ncase, leading to the dereference. Since the start() operation of the new\nrole is already called, the resume operation can be skipped.\n\nSo skip the resume operation for the new role if a role switch occurs\nduring resume. Once the resume sequence is complete, the xhci-hcd device\ncan be probed in case of host mode.\n\nUnable to handle kernel NULL pointer dereference at virtual address 0000000000000208\nMem abort info:\n...\nData abort info:\n...\n[0000000000000208] pgd=0000000000000000, p4d=0000000000000000\nInternal error: Oops: 0000000096000004 [#1] SMP\nModules linked in:\nCPU: 0 UID: 0 PID: 146 Comm: sh Not tainted\n6.19.0-rc7-00013-g6e64f4aabfae-dirty #135 PREEMPT\nHardware name: Texas Instruments J7200 EVM (DT)\npstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\npc : usb_hcd_is_primary_hcd+0x0/0x1c\nlr : cdns_host_resume+0x24/0x5c\n...\nCall trace:\n usb_hcd_is_primary_hcd+0x0/0x1c (P)\n cdns_resume+0x6c/0xbc\n cdns3_controller_resume.isra.0+0xe8/0x17c\n cdns3_plat_resume+0x18/0x24\n platform_pm_resume+0x2c/0x68\n dpm_run_callback+0x90/0x248\n device_resume+0x100/0x24c\n dpm_resume+0x190/0x2ec\n dpm_resume_end+0x18/0x34\n suspend_devices_and_enter+0x2b0/0xa44\n pm_suspend+0x16c/0x5fc\n state_store+0x80/0xec\n kobj_attr_store+0x18/0x2c\n sysfs_kf_write+0x7c/0x94\n kernfs_fop_write_iter+0x130/0x1dc\n vfs_write+0x240/0x370\n ksys_write+0x70/0x108\n __arm64_sys_write+0x1c/0x28\n invoke_syscall+0x48/0x10c\n el0_svc_common.constprop.0+0x40/0xe0\n do_el0_svc+0x1c/0x28\n el0_svc+0x34/0x108\n el0t_64_sync_handler+0xa0/0xe4\n el0t_64_sync+0x198/0x19c\nCode: 52800003 f9407ca5 d63f00a0 17ffffe4 (f9410401)\n---[ end trace 0000000000000000 ]---(CVE-2026-45911)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: fix inline data read failure for ztailpacking pclusters\n\nCompressed folios for ztailpacking pclusters must be valid before adding\nthese pclusters to I/O chains. Otherwise, z_erofs_decompress_pcluster()\nmay assume they are already valid and then trigger a NULL pointer\ndereference.\n\nIt is somewhat hard to reproduce because the inline data is in the same\nblock as the tail of the compressed indexes, which are usually read just\nbefore. However, it may still happen if a fatal signal arrives while\nread_mapping_folio() is running, as shown below:\n\n erofs: (device dm-1): z_erofs_pcluster_begin: failed to get inline data -4\n Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008\n\n ...\n\n pc : z_erofs_decompress_queue+0x4c8/0xa14\n lr : z_erofs_decompress_queue+0x160/0xa14\n sp : ffffffc08b3eb3a0\n x29: ffffffc08b3eb570 x28: ffffffc08b3eb418 x27: 0000000000001000\n x26: ffffff8086ebdbb8 x25: ffffff8086ebdbb8 x24: 0000000000000001\n x23: 0000000000000008 x22: 00000000fffffffb x21: dead000000000700\n x20: 00000000000015e7 x19: ffffff808babb400 x18: ffffffc089edc098\n x17: 00000000c006287d x16: 00000000c006287d x15: 0000000000000004\n x14: ffffff80ba8f8000 x13: 0000000000000004 x12: 00000006589a77c9\n x11: 0000000000000015 x10: 0000000000000000 x9 : 0000000000000000\n x8 : 0000000000000000 x7 : 0000000000000000 x6 : 000000000000003f\n x5 : 0000000000000040 x4 : ffffffffffffffe0 x3 : 0000000000000020\n x2 : 0000000000000008 x1 : 0000000000000000 x0 : 0000000000000000\n Call trace:\n z_erofs_decompress_queue+0x4c8/0xa14\n z_erofs_runqueue+0x908/0x97c\n z_erofs_read_folio+0x128/0x228\n filemap_read_folio+0x68/0x128\n filemap_get_pages+0x44c/0x8b4\n filemap_read+0x12c/0x5b8\n generic_file_read_iter+0x4c/0x15c\n do_iter_readv_writev+0x188/0x1e0\n vfs_iter_read+0xac/0x1a4\n backing_file_read_iter+0x170/0x34c\n ovl_read_iter+0xf0/0x140\n vfs_read+0x28c/0x344\n ksys_read+0x80/0xf0\n __arm64_sys_read+0x24/0x34\n invoke_syscall+0x60/0x114\n el0_svc_common+0x88/0xe4\n do_el0_svc+0x24/0x30\n el0_svc+0x40/0xa8\n el0t_64_sync_handler+0x70/0xbc\n el0t_64_sync+0x1bc/0x1c0\n\nFix this by reading the inline data before allocating and adding\nthe pclusters to the I/O chains.(CVE-2026-45943)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix memory leak in amdgpu_acpi_enumerate_xcc()\n\nIn amdgpu_acpi_enumerate_xcc(), if amdgpu_acpi_dev_init() returns -ENOMEM,\nthe function returns directly without releasing the allocated xcc_info,\nresulting in a memory leak.\n\nFix this by ensuring that xcc_info is properly freed in the error paths.\n\nCompile tested only. Issue found using a prototype static analysis tool\nand code review.(CVE-2026-45947)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: fix memory leaks in gfs2_fill_super error path\n\nFix two memory leaks in the gfs2_fill_super() error handling path when\ntransitioning a filesystem to read-write mode fails.\n\nFirst leak: kthread objects (thread_struct, task_struct, etc.)\nWhen gfs2_freeze_lock_shared() fails after init_threads() succeeds, the\ncreated kernel threads (logd and quotad) are never destroyed. This\noccurs because the fail_per_node label doesn\u0026apos;t call\ngfs2_destroy_threads().\n\nSecond leak: quota bitmap buffer (8192 bytes)\nWhen gfs2_make_fs_rw() fails after gfs2_quota_init() succeeds but\nbefore other operations complete, the allocated quota bitmap is never\nfreed.\n\nThe fix moves thread cleanup to the fail_per_node label to handle all\nerror paths uniformly. gfs2_destroy_threads() is safe to call\nunconditionally as it checks for NULL pointers. Quota cleanup is added\nin gfs2_make_fs_rw() to properly handle the withdrawal case where\nquota initialization succeeds but the filesystem is then withdrawn.\n\nThread leak backtrace (gfs2_freeze_lock_shared failure):\n unreferenced object 0xffff88801d7bca80 (size 4480):\n copy_process+0x3a1/0x4670 kernel/fork.c:2422\n kernel_clone+0xf3/0x6e0 kernel/fork.c:2779\n kthread_create_on_node+0x100/0x150 kernel/kthread.c:478\n init_threads+0xab/0x350 fs/gfs2/ops_fstype.c:611\n gfs2_fill_super+0xe5c/0x1240 fs/gfs2/ops_fstype.c:1265\n\nQuota leak backtrace (gfs2_make_fs_rw failure):\n unreferenced object 0xffff88812de7c000 (size 8192):\n gfs2_quota_init+0xe5/0x820 fs/gfs2/quota.c:1409\n gfs2_make_fs_rw+0x7a/0xe0 fs/gfs2/super.c:149\n gfs2_fill_super+0xfbb/0x1240 fs/gfs2/ops_fstype.c:1275(CVE-2026-45961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Fix NULL pointer dereference in acpi_ev_address_space_dispatch()\n\nCover a missed execution path with a new check.(CVE-2026-45982)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nerofs: fix unsigned underflow in z_erofs_lz4_handle_overlap()\n\nSome crafted images can have illegal (!partial_decoding \u0026amp;\u0026amp;\nm_llen \u0026lt; m_plen) extents, and the LZ4 inplace decompression path\ncan be wrongly hit, but it cannot handle (outpages \u0026lt; inpages)\nproperly: \u0026quot;outpages - inpages\u0026quot; wraps to a large value and\nthe subsequent rq-\u0026gt;out[] access reads past the decompressed_pages\narray.\n\nHowever, such crafted cases can correctly result in a corruption\nreport in the normal LZ4 non-inplace path.\n\nLet\u0026apos;s add an additional check to fix this for backporting.\n\nReproducible image (base64-encoded gzipped blob):\n\nH4sIAJGR12kCA+3SPUoDQRgG4MkmkkZk8QRbRFIIi9hbpEjrHQI5ghfwCN5BLCzTGtLbBI+g\ndilSJo1CnIm7GEXFxhT6PDDwfrs73/ywIQD/1ePD4r7Ou6ETsrq4mu7XcWfj++Pb58nJU/9i\nPNtbjhan04/9GtX4qVYc814WDqt6FaX5s+ZwXXeq52lndT6IuVvlblytLMvh4Gzwaf90nsvz\n2DF/21+20T/ldgp5s1jXRaN4t/8izsy/OUB6e/Qa79r+JwAAAAAAAL52vQVuGQAAAP6+my1w\nywAAAAAAAADwu14ATsEYtgBQAAA=\n\n$ mount -t erofs -o cache_strategy=disabled foo.erofs /mnt\n$ dd if=/mnt/data of=/dev/null bs=4096 count=1(CVE-2026-45999)\n\nIn the Linux kernel, the following vulnerability has been resolved: ipmi:ssif: Clean up kthread on errors If an error occurs after the ssif kthread is created, but before the main IPMI code starts the ssif interface, the ssif kthread will not be stopped. So make sure the kthread is stopped on an error condition if it is running. The Linux kernel CVE team has assigned CVE-2026-46044 to this issue.(CVE-2026-46044)\n\nIn the Linux kernel, the following vulnerability has been resolved: md/raid5: fix soft lockup in retry_aligned_read() When retry_aligned_read() encounters an overlapped stripe, it releases the stripe via raid5_release_stripe() which puts it on the lockless released_stripes llist. In the next raid5d loop iteration, release_stripe_list() drains the stripe onto handle_list (since STRIPE_HANDLE is set by the original IO), but retry_aligned_read() runs before handle_active_stripes() and removes the stripe from handle_list via find_get_stripe() -\u0026gt; list_del_init(). This prevents handle_stripe() from ever processing the stripe to resolve the overlap, causing an infinite loop and soft lockup. Fix this by using __release_stripe() with temp_inactive_list instead of raid5_release_stripe() in the failure path, so the stripe does not go through the released_stripes llist. This allows raid5d to break out of its loop, and the overlap will be resolved when the stripe is eventually processed by handle_stripe(). The Linux kernel CVE team has assigned CVE-2026-46051 to this issue.(CVE-2026-46051)\n\nIn the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Raise #UD if unhandled VMMCALL isn\u0026apos;t intercepted by L1 Explicitly synthesize a #UD for VMMCALL if L2 is active, L1 does NOT want to intercept VMMCALL, nested_svm_l2_tlb_flush_enabled() is true, and the hypercall is something other than one of the supported Hyper-V hypercalls. When all of the above conditions are met, KVM will intercept VMMCALL but never forward it to L1, i.e. will let L2 make hypercalls as if it were L1. The TLFS says a whole lot of nothing about this scenario, so go with the architectural behavior, which says that VMMCALL #UDs if it\u0026apos;s not intercepted. Opportunistically do a 2-for-1 stub trade by stub-ifying the new API instead of the helpers it uses. The last remaining \u0026quot;single\u0026quot; stub will soon be dropped as well. [sean: rewrite changelog and comment, tag for stable, remove defunct stubs] The Linux kernel CVE team has assigned CVE-2026-46076 to this issue.(CVE-2026-46076)\n\nIn the Linux kernel, the following vulnerability has been resolved: erofs: fix the out-of-bounds nameoff handling for trailing dirents Currently we already have boundary-checks for nameoffs, but the trailing dirents are special since the namelens are calculated with strnlen() with unchecked nameoffs. If a crafted EROFS has a trailing dirent with nameoff \u0026gt;= maxsize, maxsize - nameoff can underflow, causing strnlen() to read past the directory block. nameoff0 should also be verified to be a multiple of `sizeof(struct erofs_dirent)` as well [1]. [1] https://sashiko.dev/#/patchset/20260416063511.3173774-1-hsiangkao%40linux.alibaba.com The Linux kernel CVE team has assigned CVE-2026-46078 to this issue.(CVE-2026-46078)\n\nIn the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Inject #UD for INVLPGA if EFER.SVME=0 INVLPGA should cause a #UD when EFER.SVME is not set. Add a check to properly inject #UD when EFER.SVME=0. [sean: tag for stable@] The Linux kernel CVE team has assigned CVE-2026-46082 to this issue.(CVE-2026-46082)\n\nIn the Linux kernel, the following vulnerability has been resolved: mm/vmalloc: take vmap_purge_lock in shrinker decay_va_pool_node() can be invoked concurrently from two paths: __purge_vmap_area_lazy() when pools are being purged, and the shrinker via vmap_node_shrink_scan(). However, decay_va_pool_node() is not safe to run concurrently, and the shrinker path currently lacks serialization, leading to races and possible leaks. Protect decay_va_pool_node() by taking vmap_purge_lock in the shrinker path to ensure serialization with purge users. The Linux kernel CVE team has assigned CVE-2026-46093 to this issue.(CVE-2026-46093)\n\nIn the Linux kernel, the following vulnerability has been resolved:mm/damon/sysfs-schemes: protect memcg_path kfree() with damon_sysfs_lockPatch series \u0026quot;mm/damon/sysfs-schemes: fix use-after-free for [memcg_]path\u0026quot;.Reads of \u0026apos;memcg_path\u0026apos; and \u0026apos;path\u0026apos; files in DAMON sysfs interface could racewith their writes, results in use-after-free. Fix those.This patch (of 2):damon_sysfs_scheme_filter-\u0026gt;mmecg_path can be read and written by users,via DAMON sysfs memcg_path file. It can also be indirectly read, for theparameters {on,off}line committing to DAMON. The reads for parameterscommitting are protected by damon_sysfs_lock to avoid the sysfs filesbeing destroyed while any of the parameters are being read. But theuser-driven direct reads and writes are not protected by any lock, whilethe write is deallocating the memcg_path-pointing buffer. As a result,the readers could read the already freed buffer (user-after-free). Notethat the user-reads don\u0026apos;t race when the same open file is used by thewriter, due to kernfs\u0026apos;s open file locking. Nonetheless, doing the readsand writes with separate open files would be common. Fix it by protectingboth the user-direct reads and writes with damon_sysfs_lock.(CVE-2026-46121)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt\n\nhci_le_create_big_complete_evt() iterates over BT_BOUND connections for\na BIG handle using a while loop, accessing ev-\u0026gt;bis_handle[i++] on each\niteration. However, there is no check that i stays within ev-\u0026gt;num_bis\nbefore the array access.\n\nWhen a controller sends a LE_Create_BIG_Complete event with fewer\nbis_handle entries than there are BT_BOUND connections for that BIG,\nor with num_bis=0, the loop reads beyond the valid bis_handle[] flex\narray into adjacent heap memory. Since the out-of-bounds values\ntypically exceed HCI_CONN_HANDLE_MAX (0x0EFF), hci_conn_set_handle()\nrejects them and the connection remains in BT_BOUND state. The same\nconnection is then found again by hci_conn_hash_lookup_big_state(),\ncreating an infinite loop with hci_dev_lock held.\n\nFix this by terminating the BIG if in case not all BIS could be setup\nproperly.(CVE-2026-46138)\n\nIn the Linux kernel, vports are used concurrently and protected by RCU, so netdev_put() must happen after the RCU grace period. The rtnl_delete_link() must happen under RTNL and cannot be executed in RCU context. Calling synchronize_net() while holding RTNL is not good for performance and system stability, so calling netdev_put() in RCU call is the right solution. However, when the device is deleted, rtnl_unlock() calls netdev_run_todo() and blocks until all references are gone. In the current code, this means that call_rcu() is never reached, the vport is never freed, and the reference is never released, causing a self-deadlock on device removal. The fix moves the rcu_call() before rtnl_unlock(), so the scheduled RCU callback will be executed when synchronize_net() is called from rtnl_unlock()-\u0026gt;netdev_run_todo() while RTNL itself is already released.(CVE-2026-46165)\n\nIn the Linux kernel\u0026apos;s RISC-V KVM subsystem, when the second kzalloc (host_context.vector.datap) fails in kvm_riscv_vcpu_alloc_vector_context, the first allocation (guest_context.vector.datap) is not freed, causing a memory leak. An attacker can trigger this via ioctl(vm_fd, KVM_CREATE_VCPU), potentially leading to resource exhaustion.(CVE-2026-46171)\n\nIn the Linux kernel, the mlx4_ib_create_srq() function fails to release resources allocated by mlx4_srq_alloc() in error handling paths, leading to a resource leak. An attacker could exploit this vulnerability to cause resource exhaustion or denial of service.(CVE-2026-46178)\n\nIn the Linux kernel, the spi_nor_params_show() function uses sizeof(snor_f_names) to calculate the array length. Since snor_f_names is an array of pointers, sizeof returns the total byte size of the pointer array (element_count sizeof(void )), which on 64-bit systems is 8 times larger than intended. This causes an out-of-bounds read when a flag bit is set that exceeds the actual element count but falls within the inflated byte-size count. The fix replaces sizeof with ARRAY_SIZE to pass the actual number of elements.(CVE-2026-46190)","status":"published","published":"2026-06-05T11:11:31Z","modified":"2026-08-18T01:20:04.171596141Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:46.449097Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2026-23011","title":"CVE-2026-23011 in linux - Patched by Root","description":"Root has patched CVE-2026-23011 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:15:36.42015871Z","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-DEBIAN-12-CVE-2026-23011","title":"CVE-2026-23011 in linux - Patched by Root","description":"Root has patched CVE-2026-23011 in the linux package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-10-18T03:18:11Z","modified":"2026-10-18T04:17:45.340628847Z","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:31.773105Z"},{"id":"ROOT-OS-UBUNTU-2204-CVE-2026-23011","title":"CVE-2026-23011 in linux - Patched by Root","description":"Root has patched CVE-2026-23011 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:15:49.189562913Z","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-2026-23011","title":"CVE-2026-23011 in linux - Patched by Root","description":"Root has patched CVE-2026-23011 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:16:30.194383268Z","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":"UBUNTU-CVE-2026-23011","description":"In the Linux kernel, the following vulnerability has been resolved: ipv4: ip_gre: make ipgre_header() robust Analog to commit db5b4e39c4e6 (\"ip6_gre: make ip6gre_header() robust\") Over the years, syzbot found many ways to crash the kernel in ipgre_header() [1]. This involves team or bonding drivers ability to dynamically change their dev-\u003eneeded_headroom and/or dev-\u003ehard_header_len In this particular crash mld_newpack() allocated an skb with a too small reserve/headroom, and by the time mld_sendpack() was called, syzbot managed to attach an ipgre device. [1] skbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0 kernel BUG at net/core/skbuff.c:213 ! Oops: invalid opcode: 0000 [#1] SMP KASAN PTI CPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Workqueue: mld mld_ifc_work RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213 Call Trace: \u003cTASK\u003e skb_under_panic net/core/skbuff.c:223 [inline] skb_push+0xc3/0xe0 net/core/skbuff.c:2641 ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897 dev_hard_header include/linux/netdevice.h:3436 [inline] neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618 NF_HOOK_COND include/linux/netfilter.h:307 [inline] ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247 NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318 mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855 mld_send_cr net/ipv6/mcast.c:2154 [inline] mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693 process_one_work kernel/workqueue.c:3257 [inline] process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340 worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421 kthread+0x711/0x8a0 kernel/kthread.c:463 ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246","status":"published","published":"2026-01-25T15:15:00Z","modified":"2026-11-12T17:25:27.382153611Z","cvss":[{"version":"4.0","score":5.7,"vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","level":"medium"},{"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-12T18:05:21.867737Z"},{"id":"AZL-77121","title":"CVE-2026-23011 affecting package kernel for versions less than 6.6.126.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\"ip6_gre: make ip6gre_header() robust\")\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u003eneeded_headroom and/or dev-\u003ehard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u003cTASK\u003e\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246","status":"published","published":"2026-01-25T15:15:55Z","modified":"2026-08-28T17:56:21.350459Z","updated_at":"2026-11-02T15:28:09.747541Z"},{"id":"CLSA-2026-1778756832","title":"kernel: Fix of 40 CVEs","description":"- fix: \"vsock: Ignore signal/timeout on connect() if already established {CVE-2025-40248}\"\n- gfs2: Fix possible data races in gfs2_show_options() {CVE-2023-53622}\n- ALSA: 6fire: fix use-after-free on disconnect {CVE-2026-31581}\n- nfnetlink_osf: validate individual option lengths in fingerprints {CVE-2026-23397}\n- netfilter: nfnetlink_osf: avoid OOB read {CVE-2026-23397}\n- Squashfs: check metadata block offset is within range {CVE-2026-23388}\n- scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() {CVE-2026-23216}\n- can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak {CVE-2026-23108}\n- net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag {CVE-2026-23105}\n- ALSA: ctxfi: Fix potential OOB access in audio mixer handling {CVE-2026-23076}\n- net: usb: pegasus: fix memory leak in update_eth_regs_async() {CVE-2026-23021}\n- ipv4: ip_gre: make ipgre_header() robust {CVE-2026-23011}\n- libceph: make decode_pool() more resilient against corrupted osdmaps {CVE-2025-71116}\n- via_wdt: fix critical boot hang due to unnamed resource allocation {CVE-2025-71114}\n- hwmon: (w83791d) Convert macros to functions to avoid TOCTOU {CVE-2025-71111}\n- Bluetooth: btusb: revert use of devm_kzalloc in btusb {CVE-2025-71082}\n- Revert \"fbdev: bitblit: bound-check glyph index in bit_putcs* {CVE-2025-40322}\"\n- driver core: fix potential null-ptr-deref in device_add() {CVE-2023-54321}\n- btrfs: output extra debug info if we failed to find an inline backref {CVE-2023-53672}\n- ring-buffer: Fix deadloop issue on reading trace_pipe {CVE-2023-53668}\n- netfilter: conntrack: Avoid nf_ct_helper_hash uses after free {CVE-2023-53619}\n- ring-buffer: Sync IRQ works before buffer destruction {CVE-2023-53587}\n- net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb {CVE-2023-53548}\n- udf: Do not bother merging very long extents {CVE-2023-53506}\n- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release(CVE-2023-53484)\n- lib: cpu_rmap: Avoid use after free on rmap-\u003eobj array entries {CVE-2023-53484}\n- ext4: remove a BUG_ON in ext4_mb_release_group_pa() {CVE-2023-53450}\n- md/raid10: fix wrong setting of max_corr_read_errors {CVE-2023-53313}\n- platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() {CVE-2022-50521}\n- binfmt_misc: fix shift-out-of-bounds in check_special_flags {CVE-2022-50497}\n- ntb_netdev: Use dev_kfree_skb_any() in interrupt context {CVE-2022-50476}\n- i2c: ismt: use correct length when copy buffer {CVE-2022-50394}\n- misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() {CVE-2022-50349}\n- ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS {CVE-2022-50315}\n- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network {CVE-2022-49865}\n- KVM: x86/mmu: make apf token non-zero to fix bug {CVE-2022-48943}\n- kvm: avoid speculation-based attacks from out-of-range memslot accesses {CVE-2021-47277}\n- scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs() {CVE-2021-47219}\n- scsi: scsi_debug: Fix out-of-bound read in resp_readcap16() {CVE-2021-47191}\n- USB: core: Add routines for endpoint checks in old drivers\n- xen: sync some headers with xen tree\n- squashfs: fix memory leak in squashfs_fill_super {CVE-2025-38415}\n- pptp: fix pptp_xmit() error path {CVE-2025-38574}\n- Revert \"net/sched: sch_hfsc: Ensure inner classes have fsc curve\" {CVE-2023-4623}","status":"published","published":"2026-05-14T19:27:09Z","modified":"2026-10-21T10:47:07.339724149Z","updated_at":"2026-11-02T15:43:44.737408Z"},{"id":"CLSA-2026-1778757276","title":"kernel: Fix of 40 CVEs","description":"- fix: \"vsock: Ignore signal/timeout on connect() if already established {CVE-2025-40248}\"\n- gfs2: Fix possible data races in gfs2_show_options() {CVE-2023-53622}\n- ALSA: 6fire: fix use-after-free on disconnect {CVE-2026-31581}\n- nfnetlink_osf: validate individual option lengths in fingerprints {CVE-2026-23397}\n- netfilter: nfnetlink_osf: avoid OOB read {CVE-2026-23397}\n- Squashfs: check metadata block offset is within range {CVE-2026-23388}\n- scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() {CVE-2026-23216}\n- can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak {CVE-2026-23108}\n- net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag {CVE-2026-23105}\n- ALSA: ctxfi: Fix potential OOB access in audio mixer handling {CVE-2026-23076}\n- net: usb: pegasus: fix memory leak in update_eth_regs_async() {CVE-2026-23021}\n- ipv4: ip_gre: make ipgre_header() robust {CVE-2026-23011}\n- libceph: make decode_pool() more resilient against corrupted osdmaps {CVE-2025-71116}\n- via_wdt: fix critical boot hang due to unnamed resource allocation {CVE-2025-71114}\n- hwmon: (w83791d) Convert macros to functions to avoid TOCTOU {CVE-2025-71111}\n- Bluetooth: btusb: revert use of devm_kzalloc in btusb {CVE-2025-71082}\n- Revert \"fbdev: bitblit: bound-check glyph index in bit_putcs* {CVE-2025-40322}\"\n- driver core: fix potential null-ptr-deref in device_add() {CVE-2023-54321}\n- btrfs: output extra debug info if we failed to find an inline backref {CVE-2023-53672}\n- ring-buffer: Fix deadloop issue on reading trace_pipe {CVE-2023-53668}\n- netfilter: conntrack: Avoid nf_ct_helper_hash uses after free {CVE-2023-53619}\n- ring-buffer: Sync IRQ works before buffer destruction {CVE-2023-53587}\n- net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb {CVE-2023-53548}\n- udf: Do not bother merging very long extents {CVE-2023-53506}\n- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release(CVE-2023-53484)\n- lib: cpu_rmap: Avoid use after free on rmap-\u003eobj array entries {CVE-2023-53484}\n- ext4: remove a BUG_ON in ext4_mb_release_group_pa() {CVE-2023-53450}\n- md/raid10: fix wrong setting of max_corr_read_errors {CVE-2023-53313}\n- platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() {CVE-2022-50521}\n- binfmt_misc: fix shift-out-of-bounds in check_special_flags {CVE-2022-50497}\n- ntb_netdev: Use dev_kfree_skb_any() in interrupt context {CVE-2022-50476}\n- i2c: ismt: use correct length when copy buffer {CVE-2022-50394}\n- misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() {CVE-2022-50349}\n- ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS {CVE-2022-50315}\n- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network {CVE-2022-49865}\n- KVM: x86/mmu: make apf token non-zero to fix bug {CVE-2022-48943}\n- kvm: avoid speculation-based attacks from out-of-range memslot accesses {CVE-2021-47277}\n- scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs() {CVE-2021-47219}\n- scsi: scsi_debug: Fix out-of-bound read in resp_readcap16() {CVE-2021-47191}\n- USB: core: Add routines for endpoint checks in old drivers\n- xen: sync some headers with xen tree\n- squashfs: fix memory leak in squashfs_fill_super {CVE-2025-38415}\n- pptp: fix pptp_xmit() error path {CVE-2025-38574}\n- Revert \"net/sched: sch_hfsc: Ensure inner classes have fsc curve\" {CVE-2023-4623}","status":"published","published":"2026-05-14T18:35:16Z","modified":"2026-10-21T10:48:13.014147274Z","updated_at":"2026-11-02T15:43:44.737408Z"},{"id":"CLSA-2026-1778759582","title":"kernel: Fix of 40 CVEs","description":"- fix: \"vsock: Ignore signal/timeout on connect() if already established {CVE-2025-40248}\"\n- gfs2: Fix possible data races in gfs2_show_options() {CVE-2023-53622}\n- ALSA: 6fire: fix use-after-free on disconnect {CVE-2026-31581}\n- nfnetlink_osf: validate individual option lengths in fingerprints {CVE-2026-23397}\n- netfilter: nfnetlink_osf: avoid OOB read {CVE-2026-23397}\n- Squashfs: check metadata block offset is within range {CVE-2026-23388}\n- scsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count() {CVE-2026-23216}\n- can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak {CVE-2026-23108}\n- net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag {CVE-2026-23105}\n- ALSA: ctxfi: Fix potential OOB access in audio mixer handling {CVE-2026-23076}\n- net: usb: pegasus: fix memory leak in update_eth_regs_async() {CVE-2026-23021}\n- ipv4: ip_gre: make ipgre_header() robust {CVE-2026-23011}\n- libceph: make decode_pool() more resilient against corrupted osdmaps {CVE-2025-71116}\n- via_wdt: fix critical boot hang due to unnamed resource allocation {CVE-2025-71114}\n- hwmon: (w83791d) Convert macros to functions to avoid TOCTOU {CVE-2025-71111}\n- Bluetooth: btusb: revert use of devm_kzalloc in btusb {CVE-2025-71082}\n- Revert \"fbdev: bitblit: bound-check glyph index in bit_putcs* {CVE-2025-40322}\"\n- driver core: fix potential null-ptr-deref in device_add() {CVE-2023-54321}\n- btrfs: output extra debug info if we failed to find an inline backref {CVE-2023-53672}\n- ring-buffer: Fix deadloop issue on reading trace_pipe {CVE-2023-53668}\n- netfilter: conntrack: Avoid nf_ct_helper_hash uses after free {CVE-2023-53619}\n- ring-buffer: Sync IRQ works before buffer destruction {CVE-2023-53587}\n- net: usbnet: Fix WARNING in usbnet_start_xmit/usb_submit_urb {CVE-2023-53548}\n- udf: Do not bother merging very long extents {CVE-2023-53506}\n- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release(CVE-2023-53484)\n- lib: cpu_rmap: Avoid use after free on rmap-\u003eobj array entries {CVE-2023-53484}\n- ext4: remove a BUG_ON in ext4_mb_release_group_pa() {CVE-2023-53450}\n- md/raid10: fix wrong setting of max_corr_read_errors {CVE-2023-53313}\n- platform/x86: mxm-wmi: fix memleak in mxm_wmi_call_mx[ds|mx]() {CVE-2022-50521}\n- binfmt_misc: fix shift-out-of-bounds in check_special_flags {CVE-2022-50497}\n- ntb_netdev: Use dev_kfree_skb_any() in interrupt context {CVE-2022-50476}\n- i2c: ismt: use correct length when copy buffer {CVE-2022-50394}\n- misc: tifm: fix possible memory leak in tifm_7xx1_switch_media() {CVE-2022-50349}\n- ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS {CVE-2022-50315}\n- ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network {CVE-2022-49865}\n- KVM: x86/mmu: make apf token non-zero to fix bug {CVE-2022-48943}\n- kvm: avoid speculation-based attacks from out-of-range memslot accesses {CVE-2021-47277}\n- scsi: scsi_debug: Fix out-of-bound read in resp_report_tgtpgs() {CVE-2021-47219}\n- scsi: scsi_debug: Fix out-of-bound read in resp_readcap16() {CVE-2021-47191}\n- USB: core: Add routines for endpoint checks in old drivers\n- xen: sync some headers with xen tree\n- squashfs: fix memory leak in squashfs_fill_super {CVE-2025-38415}\n- pptp: fix pptp_xmit() error path {CVE-2025-38574}\n- Revert \"net/sched: sch_hfsc: Ensure inner classes have fsc curve\" {CVE-2023-4623}","status":"published","published":"2026-05-14T19:26:23Z","modified":"2026-10-21T10:48:18.570732074Z","updated_at":"2026-11-02T15:43:44.737408Z"},{"id":"CLSA-2026-1779987841","title":"kernel: Fix of 110 CVEs","description":"- smb: client: reject userspace cifs.spnego descriptions\n- mlxsw: spectrum_acl_tcam: Fix possible use-after-free during rehash {CVE-2024-35854}\n- cifs: Fix memory leak when build ntlmssp negotiate blob failed {CVE-2022-50372}\n- scsi: lpfc: Check kzalloc() in lpfc_sli4_cgn_params_read() {CVE-2023-53038}\n- drm/amd/display: Do not set DRR on pipe Commit {CVE-2023-53042}\n- tcp: fix skb_copy_ubufs() vs BIG TCP {CVE-2023-53669}\n- clk: Fix clk_core_get NULL dereference {CVE-2024-27038}\n- drm/amd/display: Check null pointers before using dc-\u003eclk_mgr {CVE-2024-49907}\n- bpf: reject unhashed sockets in bpf_sk_assign {CVE-2023-53585}\n- driver core: fix resource leak in device_add() {CVE-2023-53594}\n- wifi: ath9k: hif_usb: fix memory leak of remain_skbs {CVE-2023-53641}\n- wifi: ath9k: verify the expected usb_endpoints are present {CVE-2022-50297}\n- drm/amd/display: Fix potential null-deref in dm_resume {CVE-2022-50535}\n- ext4: don't allow journal inode to have encrypt flag {CVE-2022-50277}\n- tls: get psock ref after taking rxlock to avoid leak {CVE-2024-35908}\n- cpumap: Zero-initialise xdp_rxq_info struct before running XDP program {CVE-2024-27431}\n- bpf: Guard stack limits against 32bit overflow {CVE-2023-52676}\n- can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible() {CVE-2021-47457}\n- serial: core: fix transmit-buffer reset and memleak {CVE-2021-47527}\n- cpufreq: exit() callback is optional {CVE-2024-38615}\n- ext4: fix mb_cache_entry's e_refcnt leak in ext4_xattr_block_cache_find() {CVE-2024-39276}\n- tcp: defer shutdown(SEND_SHUTDOWN) for TCP_SYN_RECV sockets {CVE-2024-36905}\n- wifi: nl80211: reject iftype change with mesh ID change {CVE-2024-27410}\n- tcp: do not accept ACK of bytes we never sent {CVE-2023-52881}\n- crypto: pcrypt - Fix hungtask for PADATA_RESET {CVE-2023-52813}\n- net/mlx5: Properly link new fs rules into the tree {CVE-2024-35960}\n- usb: ulpi: fix memory leak on ulpi_register() error paths\n- usb: ulpi: fix double free in ulpi_register_interface() error path {CVE-2026-31759}\n- wifi: ath11k: fix htt pktlog locking {CVE-2023-52800}\n- net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute {CVE-2025-21653}\n- calipso: fix memory leak in netlbl_calipso_add_pass() {CVE-2023-52698}\n- wifi: iwlwifi: mvm: avoid NULL pointer dereference {CVE-2024-49929}\n- ext4: update orig_path in ext4_find_extent() {CVE-2024-49881}\n- drm/vmwgfx: Fix a deadlock in dma buf fence polling {CVE-2024-43863}\n- RDMA/restrack: Fix potential invalid address access {CVE-2024-42080}\n- net: can: j1939: Initialize unused data in j1939_send_one() {CVE-2024-42076}\n- nfsd: clear acl_access/acl_default after releasing them {CVE-2025-21796}\n- rtc: pl031: fix rtc features null pointer dereference {CVE-2022-49273}\n- net: veth: clear GRO when clearing XDP even when down {CVE-2024-26803}\n- coresight: cti: Fix hang in cti_disable_hw() {CVE-2022-50491}\n- scsi: qla2xxx: Fix deletion race condition {CVE-2023-53615}\n- iw_cxgb4: Fix potential NULL dereference in c4iw_fill_res_cm_id_entry() {CVE-2023-53476}\n- scsi: qla2xxx: Fix potential NULL pointer dereference {CVE-2023-53451}\n- usb: ucsi_acpi: Increase the command completion timeout {CVE-2023-53168}\n- drivers: base: dd: fix memory leak with using debugfs_lookup() {CVE-2023-53390}\n- USB: fix memory leak with using debugfs_lookup() {CVE-2023-53359}\n- PM: domains: fix memory leak with using debugfs_lookup() {CVE-2023-53202}\n- drm/client: Fix memory leak in drm_client_modeset_probe {CVE-2023-53288}\n- drivers: base: component: fix memory leak with using debugfs_lookup() {CVE-2023-53409}\n- USB: uhci: fix memory leak with using debugfs_lookup() {CVE-2023-53197}\n- media: uvcvideo: Handle cameras with invalid descriptors {CVE-2023-53437}\n- arm64: csum: Fix OoB access in IP checksum code for negative lengths {CVE-2023-53726}\n- bnxt: Do not read past the end of test names {CVE-2023-53010}\n- dax: make sure inodes are flushed before destroy cache {CVE-2022-49220}\n- cifs: Fix oops due to uncleared server-\u003esmbd_conn in reconnect {CVE-2023-53006}\n- net: flow_dissector: use DEBUG_NET_WARN_ON_ONCE {CVE-2024-42321}\n- PCI: Fix use-after-free of slot-\u003ebus on hot remove {CVE-2024-53194}\n- net/ipv6: release expired exception dst cached in socket {CVE-2024-56644}\n- net: sched: fix ordering of qlen adjustment {CVE-2024-53164}\n- watch_queue: Fix NULL dereference in error cleanup {CVE-2022-49257}\n- lz4: fix LZ4_decompress_safe_partial read out of bound {CVE-2022-49078}\n- vmxnet3: disable rx data ring on dma allocation failure {CVE-2024-40923}\n- ALSA: hda: intel-sdw-acpi: fix usage of device_get_named_child_node() {CVE-2024-36955}\n- Bluetooth: hci_{ldisc,serdev}: check percpu_init_rwsem() failure {CVE-2022-50374}\n- drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag {CVE-2024-35817}\n- dm snapshot: fix lockup in dm_exception_table_exit {CVE-2024-35805}\n- nouveau: fix instmem race condition around ptr stores {CVE-2024-26984}\n- wireguard: netlink: access device through ctx instead of peer {CVE-2024-26950}\n- drm/i915/gt: Reset queue_priority_hint on parking {CVE-2024-26937}\n- netfilter: nft_set_pipapo: do not free live element {CVE-2024-26924}\n- dmaengine: fix NULL pointer in channel unregistration function {CVE-2023-52492}\n- PCI/PM: Drain runtime-idle callbacks before driver removal {CVE-2024-35809}\n- nvme-fc: do not wait in vain when unloading module {CVE-2024-26846}\n- netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp {CVE-2026-31427}\n- phylib: fix potential use-after-free {CVE-2022-48754}\n- mm/filemap: skip to create PMD-sized page cache if needed {CVE-2024-41031}\n- VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host() {CVE-2024-35944}\n- mlxsw: spectrum_acl_tcam: Fix incorrect list API usage {CVE-2024-36006}\n- wifi: ath11k: decrease MHI channel buffer length to 8KB {CVE-2024-35938}\n- dyndbg: fix old BUG_ON in \u003econtrol parser {CVE-2024-35947}\n- ALSA: core: Fix NULL module pointer assignment at card init {CVE-2024-38605}\n- wifi: iwlwifi: mvm: rfi: fix potential response leaks {CVE-2024-35912}\n- x86/fpu: Keep xfd_state in sync with MSR_IA32_XFD {CVE-2024-35801}\n- ipv6: avoid overflows in ip6_datagram_send_ctl() {CVE-2026-31415}\n- wifi: mac80211: don't return unset power in ieee80211_get_tx_power() {CVE-2023-52832}\n- i2c: core: Run atomic i2c xfer when !preemptible {CVE-2023-52791}\n- mmc: sdio: fix possible resource leaks in some error paths {CVE-2023-52730}\n- protect the fetch of -\u003efd[fd] in do_dup2() from mispredictions {CVE-2024-42265}\n- wifi: mac80211: fix potential sta-link leak {CVE-2024-35838}\n- octeontx2-af: avoid off-by-one read from userspace {CVE-2024-36957}\n- xen-netfront: Add missing skb_mark_for_recycle {CVE-2024-27393}\n- net: hns3: do not allow call hns3_nic_net_open repeatedly {CVE-2021-47400}\n- HID: sony: Fix a potential memory leak in sony_probe() {CVE-2023-52529}\n- netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD {CVE-2026-31428}\n- mm/gup: fix gup_pud_range() for dax {CVE-2022-48986}\n- drm/virtio: Fix GEM handle creation UAF {CVE-2022-48899}\n- ipv4: ip_gre: make ipgre_header() robust {CVE-2026-23011}\n- ACPI: processor_idle: Fix memory leak in acpi_processor_power_exit() {CVE-2024-26894}\n- RDMA/umad: Reject negative data_len in ib_umad_write {CVE-2026-23243}\n- HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure {CVE-2026-43049}\n- usb: class: cdc-wdm: fix reordering issue in read code path {CVE-2026-43427}\n- bpf, cpumap: Make sure kthread is running before map update returns {CVE-2023-53577}\n- wifi: mac80211: check tdls flag in ieee80211_tdls_oper {CVE-2026-43052}\n- net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks {CVE-2026-23270}\n- net/sched: act_ct: fix skb leak and crash on ooo frags {CVE-2023-52610}\n- Bluetooth: L2CAP: Fix user-after-free {CVE-2022-50386}\n- mm/mempolicy: fix memory leak in set_mempolicy_home_node system call {CVE-2022-50391}\n- mm/kasan: fix double free for kasan pXds {CVE-2026-31686}\n- ext4: convert inline data to extents when truncate exceeds inline size {CVE-2026-31452}\n- nfsd: fix heap overflow in NFSv4.0 LOCK replay cache {CVE-2026-31402}\n- dax: Fix dax_mapping_release() use after free {CVE-2023-53613}","status":"published","published":"2026-10-21T04:54:54Z","modified":"2026-10-26T09:43:34.161502175Z","updated_at":"2026-11-02T15:43:45.090939Z"},{"id":"CLSA-2026-1780052998","title":"kernel: Fix of 102 CVEs","description":"- smb: client: reject userspace cifs.spnego descriptions\n- usb: ulpi: fix memory leak on ulpi_register() error paths\n- usb: ulpi: fix double free in ulpi_register_interface() error path {CVE-2026-31759}\n- mptcp: consolidate suboption status {CVE-2025-21707}\n- blktrace: fix __this_cpu_read/write in preemptible context {CVE-2026-23374}\n- espintcp: remove encap socket caching to avoid reference leak {CVE-2025-38097}\n- net: usb: asix: validate PHY address before use {CVE-2025-71094}\n- driver: iio: add missing checks on iio_info's callback access {CVE-2024-46715}\n- net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts {CVE-2026-22997}\n- crypto: af_alg - Set merge to zero early in af_alg_sendmsg {CVE-2025-39931}\n- bonding: fix use-after-free due to enslave fail after slave array update {CVE-2026-23171}\n- Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT {CVE-2025-38335}\n- spi: spi-fsl-lpspi: fix teardown order issue (UAF) {CVE-2026-31485}\n- mm/smaps: fix race between smaps_hugetlb_range and migration {CVE-2025-39754}\n- vxlan: Fix NPD in {arp,neigh}_reduce() when using nexthop objects {CVE-2025-39850}\n- mm/userfaultfd: fix hugetlb fault mutex hash calculation {CVE-2026-31575}\n- RDMA/irdma: Initialize free_qp completion before using it {CVE-2026-31492}\n- calipso: Don't call calipso functions for AF_INET sk. {CVE-2025-38147}\n- mm/ksm: fix flag-dropping behavior in ksm_madvise {CVE-2025-40040}\n- espintcp: fix skb leaks {CVE-2025-38057}\n- net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize {CVE-2023-53667}\n- memcg: fix soft lockup in the OOM process {CVE-2024-57977}\n- futex: Clear stale exiting pointer in futex_lock_pi() retry path {CVE-2026-31555}\n- trace_events_hist: add check for return value of 'create_hist_field' {CVE-2023-53005}\n- dm-verity: disable recursive forward error correction {CVE-2025-71161}\n- Bluetooth: L2CAP: Fix accepting multiple L2CAP_ECRED_CONN_REQ {CVE-2026-23395}\n- vfs: Don't evict inode under the inode lru traversing context {CVE-2024-45003}\n- ipvs: fix uninit-value for saddr in do_output_route4 {CVE-2025-37961}\n- sctp: add mutual exclusion in proc_sctp_do_udp_port() {CVE-2025-22062}\n- net: phy: leds: fix memory leak {CVE-2025-37989}\n- x86/cpu/hygon: Add missing resctrl_cpu_detect() in bsp_init helper {CVE-2025-39681}\n- tls: Use __sk_dst_get() and dst_dev_rcu() in get_netdev_for_sock(). {CVE-2025-40149}\n- netfilter: ctnetlink: remove refcounting in expectation dumpers {CVE-2025-39764}\n- sctp: sysctl: auth_enable: avoid using current-\u003ensproxy {CVE-2025-21638}\n- kobject: Add sanity check for kset-\u003ekobj.ktype in kset_register() {CVE-2023-53480}\n- io_uring: check if iowq is killed before queuing {CVE-2024-56709}\n- netfilter: x_tables: fix percpu counter block leak on error path when creating new netns {CVE-2023-53200}\n- ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed {CVE-2023-53481}\n- udf: Do not update file length for failed writes to inline files {CVE-2023-53295}\n- bpf: Forget ranges when refining tnum after JSET {CVE-2025-39748}\n- perf/core: Exit early on perf_mmap() fail {CVE-2025-38565}\n- misc: vmw_balloon: fix memory leak with using debugfs_lookup() {CVE-2023-53279}\n- can: bcm: bcm_tx_setup(): fix KMSAN uninit-value in vfs_write {CVE-2023-53344}\n- tracing: Fix race issue between cpu buffer write and swap {CVE-2023-53368}\n- KVM: x86: Acquire SRCU in KVM_GET_MP_STATE to protect guest memory accesses {CVE-2025-23141}\n- io_uring/tctx: work around xa_store() allocation error issue {CVE-2024-56584}\n- objtool: Fix memory leak in create_static_call_sections() {CVE-2023-53423}\n- net: bcmgenet: Add a check for oversized packets {CVE-2023-53535}\n- ext4: remove a BUG_ON in ext4_mb_release_group_pa() {CVE-2023-53450}\n- PM: EM: fix memory leak with using debugfs_lookup() {CVE-2023-53411}\n- ALSA: usb-audio: Use correct version for UAC3 header validation {CVE-2026-23318}\n- watchdog: Fix kmemleak in watchdog_cdev_register {CVE-2023-53234}\n- nfsd: fix heap overflow in NFSv4.0 LOCK replay cache {CVE-2026-31402}\n- libceph: reset sparse-read state in osd_fault() {CVE-2026-23136}\n- ppp: fix race conditions in ppp_fill_forward_path {CVE-2025-39673}\n- platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks {CVE-2025-38412}\n- perf: Revert to requiring CAP_SYS_ADMIN for uprobes {CVE-2025-38466}\n- can: isotp: fix potential CAN frame reception race in isotp_rcv() {CVE-2022-48830}\n- net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute {CVE-2025-21653}\n- HID: ignore non-functional sensor in HP 5MP Camera {CVE-2025-21992}\n- smb: client: Avoid race in open_cached_dir with lease breaks {CVE-2025-37954}\n- net/mlx5e: Avoid WARN_ON when configuring MQPRIO with HTB offload enabled {CVE-2025-38039}\n- smb: Log an error when close_all_cached_dirs fails {CVE-2025-38321}\n- rxrpc: Fix bug due to prealloc collision {CVE-2025-38544}\n- ASoC: SOF: Intel: hda: Use devm_kstrdup() to avoid memleak. {CVE-2025-38438}\n- net: stmmac: Fix accessing freed irq affinity_hint {CVE-2025-23155}\n- perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init {CVE-2025-37878}\n- bpf: Fix deadlock between rcu_tasks_trace and event_mutex. {CVE-2025-37884}\n- tracing: Free error logs of tracing instances {CVE-2023-53375}\n- loop: Avoid updating block size under exclusive owner {CVE-2025-38709}\n- netfilter: ctnetlink: use netlink policy range checks {CVE-2026-31495}\n- ceph: fix deadlock or deadcode of misusing dget() {CVE-2023-52583}\n- net/sched: Only allow act_ct to bind to clsact/ingress qdiscs and shared blocks {CVE-2026-23270}\n- ip6_gre: make ip6gre_header() robust {CVE-2025-71098}\n- hwmon: (w83791d) Convert macros to functions to avoid TOCTOU {CVE-2025-71111}\n- crypto: seqiv - Do not use req-\u003eiv after crypto_aead_encrypt {CVE-2025-71131}\n- rocker: fix memory leak in rocker_world_port_post_fini() {CVE-2026-23164}\n- bonding: provide a net pointer to __skb_flow_dissect() {CVE-2026-23119}\n- l2tp: avoid one data-race in l2tp_tunnel_del_work() {CVE-2026-23120}\n- can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak {CVE-2026-23108}\n- leds: led-class: Only Add LED to leds_list when it is fully ready {CVE-2026-23101}\n- regmap: Fix race condition in hwspinlock irqsave routine {CVE-2026-23071}\n- cifs: Fix memory and information leak in smb3_reconfigure() {CVE-2025-71151}\n- ipv4: ip_gre: make ipgre_header() robust {CVE-2026-23011}\n- NFSv4/pNFS: Fix a race to wake on NFS_LAYOUT_DRAIN {CVE-2025-38393}\n- nvme-pci: fix freeing of the HMB descriptor table {CVE-2024-56756}\n- spi: imx: Don't skip cleanup in remove's error path {CVE-2023-53225}\n- ring-buffer: Fix a race between readers and resize checks {CVE-2024-38601}\n- i3c: Use i3cdev-\u003edesc-\u003einfo instead of calling i3c_device_get_info() to avoid deadlock {CVE-2024-43098}\n- can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open {CVE-2024-46791}\n- ftrace: Fix regression with module command in stack_trace_filter {CVE-2024-56569}\n- leds: class: Protect brightness_show() with led_cdev-\u003eled_access mutex {CVE-2024-56587}\n- bpf, sockmap: Several fixes to bpf_msg_pop_data {CVE-2024-56720}\n- sctp: sysctl: cookie_hmac_alg: avoid using current-\u003ensproxy {CVE-2025-21640}\n- sctp: sysctl: rto_min/max: avoid using current-\u003ensproxy {CVE-2025-21639}\n- ACPI: APEI: send SIGBUS to current task if synchronous memory error not recovered {CVE-2025-39763}\n- cxgb4: fix memory leak in cxgb4_init_ethtool_filters() error path {CVE-2025-37788}\n- net: clear the dst when changing skb protocol {CVE-2025-38192}\n- bpf: Fix kmemleak warning for percpu hashmap {CVE-2025-37807}\n- drm/amdkfd: debugfs hang_hws skip GPU with MES {CVE-2025-37853}\n- RDMA/mlx5: Fix a race for an ODP MR which leads to CQE with error {CVE-2025-21732}\n- PCI: vmd: Make vmd_dev::cfg_lock a raw_spinlock_t type {CVE-2025-23161}\n- PCI: Fix reference leak in pci_register_host_bridge() {CVE-2025-37836}\n- ALSA: caiaq: fix stack out-of-bounds read in init_card {CVE-2026-31778}","status":"published","published":"2026-07-28T12:08:13Z","modified":"2026-10-26T09:43:17.296034292Z","updated_at":"2026-11-02T15:43:45.090939Z"},{"id":"CLSA-2026-1783791022","title":"Fix of 64 CVEs","description":" * CVE-2026-31607\n - usbip: validate number_of_packets in usbip_pack_ret_submit()\n {CVE-2026-31607}\n * CVE-2026-31527\n - driver core: platform: use generic driver_override infrastructure\n {CVE-2026-31527}\n * CVE-2026-43493\n - crypto: pcrypt - Fix handling of MAY_BACKLOG requests {CVE-2026-43493}\n * CVE-2026-43038\n - ipv6: icmp: clear skb2-\u003ecb[] in ip6_err_gen_icmpv6_unreach()\n {CVE-2026-43038}\n * CVE-2026-43037\n - ip6_tunnel: clear skb2-\u003ecb[] in ip4ip6_err() {CVE-2026-43037}\n * CVE-2026-23083\n - fou: Don't allow 0 for FOU_ATTR_IPPROTO. {CVE-2026-23083}\n * CVE-2024-57982\n - xfrm: state: fix out-of-bounds read during lookup {CVE-2024-57982}\n * CVE-2024-50115\n - KVM: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memory\n {CVE-2024-50115}\n * CVE-2026-53166\n - futex/requeue: Prevent NULL pointer dereference in remove_waiter() on\n self-deadlock {CVE-2026-53166}\n * CVE-2026-43499\n - rtmutex: Use waiter::task instead of current in remove_waiter()\n {CVE-2026-43499}\n * CVE-2023-6546\n - tty: n_gsm: fix the UAF caused by race condition in gsm_cleanup_mux\n {CVE-2023-6546}\n * CVE-2023-53510\n - scsi: ufs: core: Fix handling of lrbp-\u003ecmd {CVE-2023-53510}\n * CVE-2023-53286\n - RDMA/mlx5: Return the firmware result upon destroying QP/RQ\n {CVE-2023-53286}\n * CVE-2023-53259\n - VMCI: check context-\u003enotify_page after call to get_user_pages_fast() to\n avoid GPF {CVE-2023-53259}\n * CVE-2026-31500\n - Bluetooth: btintel: serialize btintel_hw_error() with hci_req_sync_lock\n {CVE-2026-31500}\n * CVE-2023-52916\n - media: aspeed: Fix memory overwrite if timing is 1600x900 {CVE-2023-52916}\n * CVE-2022-50021\n - ext4: block range must be validated before use in ext4_mb_clear_bb()\n {CVE-2022-50021}\n * CVE-2022-49799\n - tracing: Fix wild-memory-access in register_synth_event() {CVE-2022-49799}\n * CVE-2022-49234\n - net: dsa: Avoid cross-chip syncing of VLAN filtering {CVE-2022-49234}\n * CVE-2022-48744\n - net/mlx5e: Avoid field-overflowing memcpy() {CVE-2022-48744}\n * CVE-2026-23164\n - rocker: fix memory leak in rocker_world_port_post_fini() {CVE-2026-23164}\n * CVE-2026-23150\n - nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame(). {CVE-2026-23150}\n * CVE-2026-23133\n - wifi: ath10k: fix dma_free_coherent() pointer {CVE-2026-23133}\n * CVE-2026-23121\n - mISDN: annotate data-race around dev-\u003ework {CVE-2026-23121}\n * CVE-2026-23108\n - can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak\n {CVE-2026-23108}\n * CVE-2026-23103\n - ipvlan: Make the addrs_lock be per port {CVE-2026-23103}\n * CVE-2026-23101\n - leds: led-class: Only Add LED to leds_list when it is fully ready\n {CVE-2026-23101}\n * CVE-2026-23095\n - gue: Fix skb memleak with inner IP protocol 0. {CVE-2026-23095}\n * CVE-2026-23084\n - be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list\n {CVE-2026-23084}\n * CVE-2026-23080\n - can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak\n {CVE-2026-23080}\n * CVE-2026-23071\n - regmap: Fix race condition in hwspinlock irqsave routine {CVE-2026-23071}\n * CVE-2026-23058\n - can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak\n {CVE-2026-23058}\n * CVE-2026-23038\n - pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n {CVE-2026-23038}\n * CVE-2026-23011\n - ipv4: ip_gre: make ipgre_header() robust {CVE-2026-23011}\n * CVE-2026-23003\n - ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n {CVE-2026-23003}\n * CVE-2025-71194\n - btrfs: fix deadlock in wait_current_trans() due to ignored transaction\n type {CVE-2025-71194}\n * CVE-2026-31417\n - net/x25: Fix overflow when accumulating packets {CVE-2026-31417}\n * CVE-2026-31396\n - net: macb: fix use-after-free access to PTP clock {CVE-2026-31396}\n * CVE-2025-68769\n - f2fs: fix return value of f2fs_recover_fsync_data() {CVE-2025-68769}\n * CVE-2025-68289\n - usb: gadget: f_eem: Fix memory leak in eem_unwrap {CVE-2025-68289}\n * Miscellaneous upstream changes\n - xen/privcmd: fix double free via VMA splitting\n - net: do not delay dst_entries_add() in dst_release()\n - drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer\n - drm/amd/pm: Fix negative array index read\n - drm/amd/display: Check link_index before accessing dc-\u003elinks[]\n - xfs: don't walk off the end of a directory data block\n - wifi: cfg80211: check A-MSDU format more carefully\n - smb: client: fix potential UAF in cifs_stats_proc_write()\n - f2fs: fix to tag gcing flag on page during block migration\n - ipv4: ip_tunnel: Fix suspicious RCU usage warning in ip_tunnel_find()\n - drivers core: Use sysfs_emit for shared_cpu_map_show and\n shared_cpu_list_show\n * Bump ABI 5.4.0-235","status":"published","published":"2026-10-21T11:48:19Z","modified":"2026-10-26T09:43:13.060674852Z","updated_at":"2026-11-02T15:43:46.151924Z"},{"id":"CVE-2026-23011","title":"ipv4: ip_gre: make ipgre_header() robust","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\"ip6_gre: make ip6gre_header() robust\")\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u003eneeded_headroom and/or dev-\u003ehard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u003cTASK\u003e\n skb_under_panic net/core/skbuff.c:223 [inline]\n skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n dev_hard_header include/linux/netdevice.h:3436 [inline]\n neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n mld_send_cr net/ipv6/mcast.c:2154 [inline]\n mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n process_one_work kernel/workqueue.c:3257 [inline]\n process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n kthread+0x711/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246","status":"published","published":"2026-01-25T14:36:24.455Z","modified":"2026-11-11T02:30:47.257425168Z","updated_at":"2026-11-11T11:06:42.235392Z"},{"id":"DLA-4475-1","title":"linux - security update","status":"published","published":"2026-02-10T00:00:00Z","modified":"2026-02-10T18:30:13.794366Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"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":"openSUSE-SU-2026:20287-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 and SL MIxro 6.2 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-40147: blk-throttle: fix access race during throttle policy activation (bsc#1253344).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68211: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item (bsc#1255319).\n- CVE-2025-68218: nvme-multipath: fix lockdep WARN due to partition scan work (bsc#1255245).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68341: veth: reduce XDP no_direct return section to fix race (bsc#1255506).\n- CVE-2025-68348: block: fix memory leak in __blkdev_issue_zero_pages (bsc#1255694).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68356: gfs2: Prevent recursive memory reclaim (bsc#1255593).\n- CVE-2025-68359: btrfs: fix double free of qgroup record after failure to add delayed ref head (bsc#1255542).\n- CVE-2025-68360: wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks (bsc#1255536).\n- CVE-2025-68361: erofs: limit the level of fs stacking for file-backed mounts (bsc#1255526).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68368: md: init bioset in mddev_init (bsc#1255527).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68374: md: fix rcu protection in md_wakeup_thread (bsc#1255530).\n- CVE-2025-68376: coresight: ETR: Fix ETR buffer use-after-free issue (bsc#1255529).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68735: drm/panthor: Prevent potential UAF in group creation (bsc#1255811).\n- CVE-2025-68741: scsi: qla2xxx: Fix improper freeing of purex item (bsc#1255703).\n- CVE-2025-68743: mshv: Fix create memory region overlap check (bsc#1255708).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68784: xfs: fix a UAF problem in xattr repair (bsc#1256793).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68792: tpm2-sessions: Fix out of range indexing in name_size (bsc#1256656).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68799: caif: fix integer underflow in cffrml_receive() (bsc#1256643).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: NFSD: NFSv4 file creation neglects setting ACL (bsc#1256770).\n- CVE-2025-68811: svcrdma: use rc_pageoff for memcpy byte offset (bsc#1256677).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-68821: fuse: fix readahead reclaim deadlock (bsc#1256667).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71080: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT (bsc#1256608).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71126: mptcp: avoid deadlock on fallback while reinjecting (bsc#1256755).\n- CVE-2025-71132: smc91x: fix broken irq-context in PREEMPT_RT (bsc#1256737).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" (bsc#1256760).\n- CVE-2025-71148: net/handshake: restore destructor on submit failure (bsc#1257159).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71156: gve: defer interrupt enabling until NAPI registration (bsc#1257167).\n- CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() (bsc#1257168).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22981: idpf: detach and close netdevs while handling a reset (bsc#1257225).\n- CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag (bsc#1257179).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22986: gpiolib: fix race condition for gdev-\u003esrcu (bsc#1257276).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- Add bugnumber to an existing hv_netvsc change (bsc#1257473).\n- Fix locking issue introduced by a CVE backport (bsc#1256975 bsc#1254977).\n- Update config files: disable CONFIG_DEVPORT for arm64 (bsc#1256792)\n- arm64: Update config files. Disable DEVPORT (bsc#1256792)\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- btrfs: pass fs_info to btrfs_delete_ref_head() (git-fixes).\n- btrfs: scrub: always update btrfs_scrub_progress::last_physical (git-fixes).\n- bus: fsl-mc: Constify fsl_mc_device_match() (jsc#PED-10906 git-fixes).\n- drm/imagination: Wait for FW trace update command completion (git-fixes).\n- drm/msm/a6xx: fix bogus hwcg register updates (git-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- libbpf: Fix -Wdiscarded-qualifiers under C23 (bsc#1257309).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1254447 bsc#1253087).\n- net: mana: Fix incorrect speed reported by debugfs (bsc#1255232).\n- net: mana: Support HW link state events (bsc#1253049).\n- nfsd: adjust WARN_ON_ONCE in revoke_delegation (bsc#1257015).\n- nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl() (git-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- sched/fair: Disable scheduler feature NEXT_BUDDY (bsc#1255459).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256864).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256864).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests: net: fib-onlink-tests: Convert to use namespaces by default (bsc#1255346).\n- slimbus: core: Constify slim_eaddr_equal() (jsc#PED-10906 git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748,bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- tsm-mr: Add TVM Measurement Register support (bsc#1257504).\n- tsm-mr: Add tsm-mr sample code (bsc#1257504).\n- virt: tdx-guest: Expose TDX MRs as sysfs attributes (bsc#1257504).\n- virt: tdx-guest: Refactor and streamline TDREPORT generation (bsc#1257504).\n- virt: tdx-guest: Transition to scoped_cond_guard for mutex operations (bsc#1257504).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- x86/tdx: Add tdx_mcall_extend_rtmr() interface (bsc#1257504).\n- x86/tdx: tdx_mcall_get_report0: Return -EBUSY on TDCALL_OPERAND_BUSY error (bsc#1257504).\n","status":"published","published":"2026-02-27T13:03:55Z","modified":"2026-03-23T04:54:50.07576Z","updated_at":"2026-11-02T16:58:41.463445Z"},{"id":"SUSE-SU-2026:0447-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-54013: interconnect: Fix locking for runpm vs reclaim (bsc#1256280).\n- CVE-2025-39880: libceph: fix invalid accesses to ceph_connection_v1_info (bsc#1250388).\n- CVE-2025-40238: net/mlx5: Fix IPsec cleanup over MPV device (bsc#1254871).\n- CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields (bsc#1254852).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).\n- CVE-2025-40328: smb: client: fix potential UAF in smb2_close_cached_fid() (bsc#1254624).\n- CVE-2025-40350: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ (bsc#1255260).\n- CVE-2025-40355: sysfs: check visibility before changing group attribute ownership (bsc#1255261).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68171: x86/fpu: Ensure XFD state on signal delivery (bsc#1255255).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68215: ice: fix PTP cleanup on driver removal in error path (bsc#1255226).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68284: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() (bsc#1255377).\n- CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68301: net: atlantic: fix fragment overflow handling in RX path (bsc#1255120).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68327: usb: renesas_usbhs: Fix synchronous external abort on unbind (bsc#1255488).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68363: bpf: Check skb-\u003etransport_header is set in bpf_skb_check_mtu (bsc#1255552).\n- CVE-2025-68365: fs/ntfs3: Initialize allocated memory before use (bsc#1255548).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68727: ntfs3: Fix uninit buffer allocated by __getname() (bsc#1255568).\n- CVE-2025-68728: ntfs3: fix uninit memory after failed mi_read in mi_format_new (bsc#1255539).\n- CVE-2025-68733: smack: fix bug: unprivileged task can create labels (bsc#1255615).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: nfsd: set security label during create operations (bsc#1256770).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71080: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT (bsc#1256608).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix 'UBSAN: shift-out-of-bounds error' (bsc#1256760).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71156: gve: defer interrupt enabling until NAPI registration (bsc#1257167).\n- CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() (bsc#1257168).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: ctxfi: Fix potential OOB access in audio mixer handling (stable-fixes).\n- ALSA: scarlett2: Fix buffer overflow in config retrieval (git-fixes).\n- ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (git-fixes).\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- ALSA: usb: Increase volume range that triggers a warning (git-fixes).\n- ASoC: amd: yc: Add quirk for Honor MagicBook X16 2025 (stable-fixes).\n- ASoC: codecs: wsa881x: Drop unused version readout (stable-fixes).\n- ASoC: codecs: wsa881x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa883x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa884x: fix codec initialisation (git-fixes).\n- ASoC: fsl_sai: Add missing registers to cache default (stable-fixes).\n- ASoC: fsl: imx-card: Do not force slot width to sample width (git-fixes).\n- ASoC: Intel: sof_es8336: fix headphone GPIO logic inversion (git-fixes).\n- ASoC: tlv320adcx140: fix null pointer (git-fixes).\n- ASoC: tlv320adcx140: fix word length (git-fixes).\n- ata: libata: Add cpr_log to ata_dev_print_features() early return (git-fixes).\n- Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work (git-fixes).\n- Bluetooth: MGMT: Fix memory leak in set_ssp_complete (git-fixes).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bs-upload-kernel: Fix cve branch uploads.\n- btrfs: do not strictly require dirty metadata threshold for metadata writepages (stable-fixes).\n- can: ctucanfd: fix SSP_SRC in cases when bit-rate is higher than 1 MBit (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: etas_es58x: allow partial RX URB allocation to succeed (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): fix error message (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error (git-fixes).\n- can: j1939: make j1939_session_activate() fail if device is no longer registered (stable-fixes).\n- can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak (git-fixes).\n- cifs: add new field to track the last access time of cfid (git-fixes).\n- cifs: after disabling multichannel, mark tcon for reconnect (git-fixes).\n- cifs: avoid redundant calls to disable multichannel (git-fixes).\n- cifs: cifs_pick_channel should try selecting active channels (git-fixes).\n- cifs: deal with the channel loading lag while picking channels (git-fixes).\n- cifs: dns resolution is needed only for primary channel (git-fixes).\n- cifs: do not disable interface polling on failure (git-fixes).\n- cifs: do not search for channel if server is terminating (git-fixes).\n- cifs: fix a pending undercount of srv_count (git-fixes).\n- cifs: Fix copy offload to flush destination region (bsc#1252511).\n- cifs: Fix flushing, invalidation and file size with copy_file_range() (bsc#1252511).\n- cifs: fix lock ordering while disabling multichannel (git-fixes).\n- cifs: fix stray unlock in cifs_chan_skip_or_disable (git-fixes).\n- cifs: fix use after free for iface while disabling secondary channels (git-fixes).\n- cifs: handle servers that still advertise multichannel after disabling (git-fixes).\n- cifs: handle when server starts supporting multichannel (git-fixes).\n- cifs: handle when server stops supporting multichannel (git-fixes).\n- cifs: make cifs_chan_update_iface() a void function (git-fixes).\n- cifs: make sure server interfaces are requested only for SMB3+ (git-fixes).\n- cifs: make sure that channel scaling is done only once (git-fixes).\n- cifs: reconnect worker should take reference on server struct unconditionally (git-fixes).\n- cifs: reset connections for all channels when reconnect requested (git-fixes).\n- cifs: reset iface weights when we cannot find a candidate (git-fixes).\n- cifs: serialize other channels when query server interfaces is pending (git-fixes).\n- cifs: update dstaddr whenever channel iface is updated (git-fixes).\n- comedi: dmm32at: serialize use of paged registers (git-fixes).\n- comedi: fix divide-by-zero in comedi_buf_munge() (stable-fixes).\n- comedi: Fix getting range information for subdevices 16 to 255 (git-fixes).\n- cpuset: fix warning when disabling remote partition (bsc#1256794).\n- crypto: authencesn - reject too-short AAD (assoclen\u003c8) to match ESP/ESN spec (git-fixes).\n- dmaengine: apple-admac: Add 'apple,t8103-admac' compatible (git-fixes).\n- dmaengine: at_hdmac: fix device leak on of_dma_xlate() (git-fixes).\n- dmaengine: bcm-sba-raid: fix device leak on probe (git-fixes).\n- dmaengine: dw: dmamux: fix OF node leak on route allocation failure (git-fixes).\n- dmaengine: idxd: fix device leaks on compat bind and unbind (git-fixes).\n- dmaengine: lpc18xx-dmamux: fix device leak on route allocation (git-fixes).\n- dmaengine: omap-dma: fix dma_pool resource leak in error paths (git-fixes).\n- dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config() (git-fixes).\n- dmaengine: sh: rz-dmac: Fix rz_dmac_terminate_all() (git-fixes).\n- dmaengine: tegra-adma: Fix use-after-free (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on dra7x route allocation (git-fixes).\n- dmaengine: ti: k3-udma: fix device leak on udma lookup (git-fixes).\n- dmaengine: xilinx_dma: Fix uninitialized addr_width when 'xlnx,addrwidth' property is missing (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap max_register (git-fixes).\n- dpll: fix device-id-get and pin-id-get to return errors properly (git-fixes).\n- dpll: fix return value check for kmemdup (git-fixes).\n- dpll: indent DPLL option type by a tab (git-fixes).\n- dpll: Prevent duplicate registrations (git-fixes).\n- dpll: spec: add missing module-name and clock-id to pin-get reply (git-fixes).\n- drm/amd: Clean up kfd node on surprise disconnect (stable-fixes).\n- drm/amd/display: Apply e4479aecf658 to dml (stable-fixes).\n- drm/amd/display: Bump the HDMI clock to 340MHz (stable-fixes).\n- drm/amd/display: Fix DP no audio issue (stable-fixes).\n- drm/amd/display: Initialise backlight level values from hw (git-fixes).\n- drm/amd/display: Respect user's CONFIG_FRAME_WARN more for dml files (stable-fixes).\n- drm/amd/display: shrink struct members (stable-fixes).\n- drm/amd/pm: Don't clear SI SMC table when setting power limit (git-fixes).\n- drm/amd/pm: fix race in power state check before mutex lock (git-fixes).\n- drm/amd/pm: fix smu overdrive data type wrong issue on smu 14.0.2 (git-fixes).\n- drm/amd/pm: Workaround SI powertune issue on Radeon 430 (v2) (git-fixes).\n- drm/amdgpu: Fix cond_exec handling in amdgpu_ib_schedule() (git-fixes).\n- drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove (git-fixes).\n- drm/amdgpu: Fix query for VPE block_type and ip_count (stable-fixes).\n- drm/amdgpu: remove frame cntl for gfx v12 (stable-fixes).\n- drm/amdkfd: fix a memory leak in device_queue_manager_init() (git-fixes).\n- drm/amdkfd: Fix improper NULL termination of queue restore SMI event string (stable-fixes).\n- drm/imagination: Wait for FW trace update command completion (git-fixes).\n- drm/imx/tve: fix probe device leak (git-fixes).\n- drm/msm/a6xx: fix bogus hwcg register updates (git-fixes).\n- drm/nouveau: add missing DCB connector types (git-fixes).\n- drm/nouveau: implement missing DCB connector types; gracefully handle unknown connectors (git-fixes).\n- drm/nouveau/disp: Set drm_mode_config_funcs.atomic_(check|commit) (stable-fixes).\n- drm/nouveau/disp/nv50-: Set lock_core in curs507a_prepare (git-fixes).\n- drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel (git-fixes).\n- drm/radeon: Remove __counted_by from ClockInfoArray.clockInfo[] (stable-fixes).\n- drm/vmwgfx: Fix an error return check in vmw_compat_shader_add() (git-fixes).\n- drm/vmwgfx: Merge vmw_bo_release and vmw_bo_free functions (git-fixes).\n- exfat: check return value of sb_min_blocksize in exfat_read_boot_sector (git-fixes).\n- exfat: fix remount failure in different process environments (git-fixes).\n- gpio: omap: do not register driver in probe() (git-fixes).\n- gpio: pca953x: Add support for level-triggered interrupts (stable-fixes).\n- gpio: pca953x: fix wrong error probe return value (git-fixes).\n- gpio: pca953x: handle short interrupt pulses on PCAL devices (git-fixes).\n- gpio: pca953x: Utilise dev_err_probe() where it makes sense (stable-fixes).\n- gpio: pca953x: Utilise temporary variable for struct device (stable-fixes).\n- gpio: rockchip: Stop calling pinctrl for set_direction (git-fixes).\n- HID: usbhid: paper over wrong bNumDescriptor field (stable-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- iio: accel: iis328dq: fix gain values (git-fixes).\n- iio: adc: ad7280a: handle spi_setup() errors in probe() (git-fixes).\n- iio: adc: ad9467: fix ad9434 vref mask (git-fixes).\n- iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver (git-fixes).\n- iio: dac: ad5686: add AD5695R to ad5686_chip_info_tbl (git-fixes).\n- iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection (git-fixes).\n- Input: i8042 - add quirk for ASUS Zenbook UX425QA_UM425QA (stable-fixes).\n- Input: i8042 - add quirks for MECHREVO Wujie 15X Pro (stable-fixes).\n- intel_th: fix device leak on output open() (git-fixes).\n- leds: led-class: Only Add LED to leds_list when it is fully ready (git-fixes).\n- lib/crypto: aes: Fix missing MMU protection for AES S-box (git-fixes).\n- mei: me: add nova lake point S DID (stable-fixes).\n- mei: me: add wildcat lake P DID (stable-fixes).\n- mISDN: annotate data-race around dev-\u003ework (git-fixes).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1253087).\n- mmc: rtsx_pci_sdmmc: implement sdmmc_card_busy function (git-fixes).\n- mmc: sdhci-of-dwcmshc: Prevent illegal clock reduction in HS200/HS400 mode (git-fixes).\n- net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts (git-fixes).\n- net: hv_netvsc: reject RSS hash key programming without RX indirection table (bsc#1257473).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (git-fixes).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (git-fixes).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (git-fixes).\n- net: tcp: allow zero-window ACK update the window (bsc#1254767).\n- net: usb: dm9601: remove broken SR9700 support (git-fixes).\n- net: wwan: t7xx: fix potential skb-\u003efrags overflow in RX path (git-fixes).\n- nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame() (git-fixes).\n- nfc: nci: Fix race between rfkill and nci_unregister_device() (git-fixes).\n- NFS: Fix up the automount fs_context to use the correct cred (git-fixes).\n- nfsd: Drop the client reference in client_states_open() (git-fixes).\n- NFSD: Fix permission check for read access to executable-only files (git-fixes).\n- NFSD: use correct reservation type in nfsd4_scsi_fence_client (git-fixes).\n- NFSD/blocklayout: Fix minlength check in proc_layoutget (git-fixes).\n- NFSv4: ensure the open stateid seqid doesn't go backwards (git-fixes).\n- nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl() (git-fixes).\n- nvmet-auth: update sc_c in host response (git-fixes).\n- nvmet-auth: update sc_c in target host hash calculation (git-fixes).\n- of: fix reference count leak in of_alias_scan() (git-fixes).\n- of: platform: Use default match table for /firmware (git-fixes).\n- phy: freescale: imx8m-pcie: assert phy reset during power on (stable-fixes).\n- phy: rockchip: inno-usb2: fix communication disruption in gadget mode (git-fixes).\n- phy: rockchip: inno-usb2: fix disconnection in gadget mode (git-fixes).\n- phy: stm32-usphyc: Fix off by one in probe() (git-fixes).\n- phy: tegra: xusb: Explicitly configure HS_DISCON_LEVEL to 0x7 (git-fixes).\n- platform/x86: hp-bioscfg: Fix automatic module loading (git-fixes).\n- platform/x86: hp-bioscfg: Fix kernel panic in GET_INSTANCE_ID macro (git-fixes).\n- platform/x86: hp-bioscfg: Fix kobject warnings for empty attribute names (git-fixes).\n- platform/x86/amd: Fix memory leak in wbrf_record() (git-fixes).\n- pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() (git-fixes).\n- powercap: fix race condition in register_control_type() (stable-fixes).\n- powercap: fix sscanf() error return value handling (stable-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- RDMA/mana_ib: Access remote atomic for MRs (git-fixes).\n- RDMA/mana_ib: add additional port counters (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: add support of multiple ports (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (git-fixes).\n- regmap: Fix race condition in hwspinlock irqsave routine (git-fixes).\n- sched: Increase sched_tick_remote timeout (bsc#1254510).\n- sched/rt: Skip group schedulable check with rt_group_sched=0 (bsc#1256568).\n- scripts: obsapi: Support URL trailing / in oscrc.\n- scripts: teaapi: Add paging.\n- scripts: uploader: Fix no change condition for _maintainership.json.\n- scripts: uploader: Handle missing upstream in is_pr_open.\n- scripts/python/git_sort/git_sort.yaml: add cifs for-next repository.\n- scrits: teaapi: Add list_repos.\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256861).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256861).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256863).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256863).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256863).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256863).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256863).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256863).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256863).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256863).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256863).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256863).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256863).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256863).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests: net: fib-onlink-tests: Convert to use namespaces by default (bsc#1255346).\n- selftests/bpf: Fix flaky bpf_cookie selftest (git-fixes).\n- serial: 8250_pci: Fix broken RS485 for F81504/508/512 (git-fixes).\n- slimbus: core: fix device reference leak on report present (git-fixes).\n- slimbus: core: fix OF node leak on registration failure (git-fixes).\n- slimbus: core: fix of_slim_get_device() kernel doc (git-fixes).\n- slimbus: core: fix runtime PM imbalance on report present (git-fixes).\n- smb: change return type of cached_dir_lease_break() to bool (git-fixes).\n- smb: client: ensure open_cached_dir_by_dentry() only returns valid cfid (git-fixes).\n- smb: client: fix cifs_pick_channel when channel needs reconnect (git-fixes).\n- smb: client: fix warning when reconnecting channel (git-fixes).\n- smb: client: introduce close_cached_dir_locked() (git-fixes).\n- smb: client: remove unused fid_lock (git-fixes).\n- smb: client: short-circuit in open_cached_dir_by_dentry() if !dentry (git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- smb3: add missing null server pointer check (git-fixes).\n- spi: spi-sprd-adi: Fix double free in probe error path (git-fixes).\n- spi: sprd-adi: switch to use spi_alloc_host() (stable-fixes).\n- spi: sprd: adi: Use devm_register_restart_handler() (stable-fixes).\n- svcrdma: return 0 on success from svc_rdma_copy_inline_range (git-fixes).\n- uacce: ensure safe queue release with state management (git-fixes).\n- uacce: fix cdev handling in the cleanup path (git-fixes).\n- uacce: fix isolate sysfs check condition (git-fixes).\n- uacce: implement mremap in uacce_vm_ops to return -EPERM (git-fixes).\n- usb: core: add USB_QUIRK_NO_BOS for devices that hang on BOS descriptor (stable-fixes).\n- usb: dwc3: Check for USB4 IP_NAME (stable-fixes).\n- USB: OHCI/UHCI: Add soft dependencies on ehci_platform (stable-fixes).\n- USB: serial: ftdi_sio: add support for PICAXE AXE027 cable (stable-fixes).\n- USB: serial: option: add Telit LE910 MBIM composition (stable-fixes).\n- usbnet: limit max_mtu based on device's hard_mtu (git-fixes).\n- w1: fix redundant counter decrement in w1_attach_slave_device() (git-fixes).\n- w1: therm: Fix off-by-one buffer overflow in alarms_store (git-fixes).\n- wifi: ath10k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: ath12k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: mac80211: correctly decode TTLM with default link map (git-fixes).\n- wifi: mac80211: don't perform DA check on S1G beacon (git-fixes).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- wifi: rsi: Fix memory corruption due to not set vif driver data size (git-fixes).\n- x86: make page fault handling disable interrupts properly (git-fixes).\n- x86/microcode: Fix Entrysign revision check for Zen1/Naples (bsc#1256528).\n- x86/microcode/AMD: Add more known models to entry sign checking (bsc#1256528).\n- x86/microcode/AMD: Add some forgotten models to the SHA check (bsc#1256528).\n- x86/microcode/AMD: Add TSA microcode SHAs (bsc#1256528).\n- x86/microcode/AMD: Add Zen5 model 0x44, stepping 0x1 minrev (bsc#1256528).\n- x86/microcode/AMD: Clean the cache if update did not load microcode (bsc#1256528).\n- x86/microcode/AMD: Extend the SHA check to Zen5, block loading of any unreleased standalone Zen5 microcode patches (bsc#1256528).\n- x86/microcode/AMD: Fix __apply_microcode_amd()'s return value (bsc#1256528).\n- x86/microcode/AMD: Fix Entrysign revision check for Zen5/Strix Halo (bsc#1256528).\n- x86/microcode/AMD: Limit Entrysign signature checking to known generations (bsc#1256528).\n- x86/microcode/AMD: Load only SHA256-checksummed patches (bsc#1256528).\n- x86/microcode/AMD: Use sha256() instead of init/update/final (bsc#1256528).\n","status":"published","published":"2026-02-11T14:05:07Z","modified":"2026-03-23T04:52:15.717412Z","updated_at":"2026-11-02T15:54:00.846737Z"},{"id":"SUSE-SU-2026:0472-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 Azure kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-54013: interconnect: Fix locking for runpm vs reclaim (bsc#1256280).\n- CVE-2025-39880: libceph: fix invalid accesses to ceph_connection_v1_info (bsc#1250388).\n- CVE-2025-40238: net/mlx5: Fix IPsec cleanup over MPV device (bsc#1254871).\n- CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields (bsc#1254852).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).\n- CVE-2025-40328: smb: client: fix potential UAF in smb2_close_cached_fid() (bsc#1254624).\n- CVE-2025-40350: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ (bsc#1255260).\n- CVE-2025-40355: sysfs: check visibility before changing group attribute ownership (bsc#1255261).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68171: x86/fpu: Ensure XFD state on signal delivery (bsc#1255255).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68215: ice: fix PTP cleanup on driver removal in error path (bsc#1255226).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68284: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() (bsc#1255377).\n- CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68301: net: atlantic: fix fragment overflow handling in RX path (bsc#1255120).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68327: usb: renesas_usbhs: Fix synchronous external abort on unbind (bsc#1255488).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68363: bpf: Check skb-\u003etransport_header is set in bpf_skb_check_mtu (bsc#1255552).\n- CVE-2025-68365: fs/ntfs3: Initialize allocated memory before use (bsc#1255548).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68727: ntfs3: Fix uninit buffer allocated by __getname() (bsc#1255568).\n- CVE-2025-68728: ntfs3: fix uninit memory after failed mi_read in mi_format_new (bsc#1255539).\n- CVE-2025-68733: smack: fix bug: unprivileged task can create labels (bsc#1255615).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: nfsd: set security label during create operations (bsc#1256770).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71080: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT (bsc#1256608).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix 'UBSAN: shift-out-of-bounds error' (bsc#1256760).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71156: gve: defer interrupt enabling until NAPI registration (bsc#1257167).\n- CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() (bsc#1257168).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: ctxfi: Fix potential OOB access in audio mixer handling (stable-fixes).\n- ALSA: scarlett2: Fix buffer overflow in config retrieval (git-fixes).\n- ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (git-fixes).\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- ALSA: usb: Increase volume range that triggers a warning (git-fixes).\n- ASoC: amd: yc: Add quirk for Honor MagicBook X16 2025 (stable-fixes).\n- ASoC: codecs: wsa881x: Drop unused version readout (stable-fixes).\n- ASoC: codecs: wsa881x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa883x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa884x: fix codec initialisation (git-fixes).\n- ASoC: fsl_sai: Add missing registers to cache default (stable-fixes).\n- ASoC: fsl: imx-card: Do not force slot width to sample width (git-fixes).\n- ASoC: Intel: sof_es8336: fix headphone GPIO logic inversion (git-fixes).\n- ASoC: tlv320adcx140: fix null pointer (git-fixes).\n- ASoC: tlv320adcx140: fix word length (git-fixes).\n- ata: libata: Add cpr_log to ata_dev_print_features() early return (git-fixes).\n- Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work (git-fixes).\n- Bluetooth: MGMT: Fix memory leak in set_ssp_complete (git-fixes).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bs-upload-kernel: Fix cve branch uploads.\n- btrfs: do not strictly require dirty metadata threshold for metadata writepages (stable-fixes).\n- can: ctucanfd: fix SSP_SRC in cases when bit-rate is higher than 1 MBit (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: etas_es58x: allow partial RX URB allocation to succeed (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): fix error message (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error (git-fixes).\n- can: j1939: make j1939_session_activate() fail if device is no longer registered (stable-fixes).\n- can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak (git-fixes).\n- cifs: add new field to track the last access time of cfid (git-fixes).\n- cifs: after disabling multichannel, mark tcon for reconnect (git-fixes).\n- cifs: avoid redundant calls to disable multichannel (git-fixes).\n- cifs: cifs_pick_channel should try selecting active channels (git-fixes).\n- cifs: deal with the channel loading lag while picking channels (git-fixes).\n- cifs: dns resolution is needed only for primary channel (git-fixes).\n- cifs: do not disable interface polling on failure (git-fixes).\n- cifs: do not search for channel if server is terminating (git-fixes).\n- cifs: fix a pending undercount of srv_count (git-fixes).\n- cifs: Fix copy offload to flush destination region (bsc#1252511).\n- cifs: Fix flushing, invalidation and file size with copy_file_range() (bsc#1252511).\n- cifs: fix lock ordering while disabling multichannel (git-fixes).\n- cifs: fix stray unlock in cifs_chan_skip_or_disable (git-fixes).\n- cifs: fix use after free for iface while disabling secondary channels (git-fixes).\n- cifs: handle servers that still advertise multichannel after disabling (git-fixes).\n- cifs: handle when server starts supporting multichannel (git-fixes).\n- cifs: handle when server stops supporting multichannel (git-fixes).\n- cifs: make cifs_chan_update_iface() a void function (git-fixes).\n- cifs: make sure server interfaces are requested only for SMB3+ (git-fixes).\n- cifs: make sure that channel scaling is done only once (git-fixes).\n- cifs: reconnect worker should take reference on server struct unconditionally (git-fixes).\n- cifs: reset connections for all channels when reconnect requested (git-fixes).\n- cifs: reset iface weights when we cannot find a candidate (git-fixes).\n- cifs: serialize other channels when query server interfaces is pending (git-fixes).\n- cifs: update dstaddr whenever channel iface is updated (git-fixes).\n- comedi: dmm32at: serialize use of paged registers (git-fixes).\n- comedi: fix divide-by-zero in comedi_buf_munge() (stable-fixes).\n- comedi: Fix getting range information for subdevices 16 to 255 (git-fixes).\n- cpuset: fix warning when disabling remote partition (bsc#1256794).\n- crypto: authencesn - reject too-short AAD (assoclen\u003c8) to match ESP/ESN spec (git-fixes).\n- dmaengine: apple-admac: Add 'apple,t8103-admac' compatible (git-fixes).\n- dmaengine: at_hdmac: fix device leak on of_dma_xlate() (git-fixes).\n- dmaengine: bcm-sba-raid: fix device leak on probe (git-fixes).\n- dmaengine: dw: dmamux: fix OF node leak on route allocation failure (git-fixes).\n- dmaengine: idxd: fix device leaks on compat bind and unbind (git-fixes).\n- dmaengine: lpc18xx-dmamux: fix device leak on route allocation (git-fixes).\n- dmaengine: omap-dma: fix dma_pool resource leak in error paths (git-fixes).\n- dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config() (git-fixes).\n- dmaengine: sh: rz-dmac: Fix rz_dmac_terminate_all() (git-fixes).\n- dmaengine: tegra-adma: Fix use-after-free (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on dra7x route allocation (git-fixes).\n- dmaengine: ti: k3-udma: fix device leak on udma lookup (git-fixes).\n- dmaengine: xilinx_dma: Fix uninitialized addr_width when 'xlnx,addrwidth' property is missing (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap max_register (git-fixes).\n- dpll: fix device-id-get and pin-id-get to return errors properly (git-fixes).\n- dpll: fix return value check for kmemdup (git-fixes).\n- dpll: indent DPLL option type by a tab (git-fixes).\n- dpll: Prevent duplicate registrations (git-fixes).\n- dpll: spec: add missing module-name and clock-id to pin-get reply (git-fixes).\n- drm/amd: Clean up kfd node on surprise disconnect (stable-fixes).\n- drm/amd/display: Apply e4479aecf658 to dml (stable-fixes).\n- drm/amd/display: Bump the HDMI clock to 340MHz (stable-fixes).\n- drm/amd/display: Fix DP no audio issue (stable-fixes).\n- drm/amd/display: Initialise backlight level values from hw (git-fixes).\n- drm/amd/display: Respect user's CONFIG_FRAME_WARN more for dml files (stable-fixes).\n- drm/amd/display: shrink struct members (stable-fixes).\n- drm/amd/pm: Don't clear SI SMC table when setting power limit (git-fixes).\n- drm/amd/pm: fix race in power state check before mutex lock (git-fixes).\n- drm/amd/pm: fix smu overdrive data type wrong issue on smu 14.0.2 (git-fixes).\n- drm/amd/pm: Workaround SI powertune issue on Radeon 430 (v2) (git-fixes).\n- drm/amdgpu: Fix cond_exec handling in amdgpu_ib_schedule() (git-fixes).\n- drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove (git-fixes).\n- drm/amdgpu: Fix query for VPE block_type and ip_count (stable-fixes).\n- drm/amdgpu: remove frame cntl for gfx v12 (stable-fixes).\n- drm/amdkfd: fix a memory leak in device_queue_manager_init() (git-fixes).\n- drm/amdkfd: Fix improper NULL termination of queue restore SMI event string (stable-fixes).\n- drm/imagination: Wait for FW trace update command completion (git-fixes).\n- drm/imx/tve: fix probe device leak (git-fixes).\n- drm/msm/a6xx: fix bogus hwcg register updates (git-fixes).\n- drm/nouveau: add missing DCB connector types (git-fixes).\n- drm/nouveau: implement missing DCB connector types; gracefully handle unknown connectors (git-fixes).\n- drm/nouveau/disp: Set drm_mode_config_funcs.atomic_(check|commit) (stable-fixes).\n- drm/nouveau/disp/nv50-: Set lock_core in curs507a_prepare (git-fixes).\n- drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel (git-fixes).\n- drm/radeon: Remove __counted_by from ClockInfoArray.clockInfo[] (stable-fixes).\n- drm/vmwgfx: Fix an error return check in vmw_compat_shader_add() (git-fixes).\n- drm/vmwgfx: Merge vmw_bo_release and vmw_bo_free functions (git-fixes).\n- exfat: check return value of sb_min_blocksize in exfat_read_boot_sector (git-fixes).\n- exfat: fix remount failure in different process environments (git-fixes).\n- gpio: omap: do not register driver in probe() (git-fixes).\n- gpio: pca953x: Add support for level-triggered interrupts (stable-fixes).\n- gpio: pca953x: fix wrong error probe return value (git-fixes).\n- gpio: pca953x: handle short interrupt pulses on PCAL devices (git-fixes).\n- gpio: pca953x: Utilise dev_err_probe() where it makes sense (stable-fixes).\n- gpio: pca953x: Utilise temporary variable for struct device (stable-fixes).\n- gpio: rockchip: Stop calling pinctrl for set_direction (git-fixes).\n- HID: usbhid: paper over wrong bNumDescriptor field (stable-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- iio: accel: iis328dq: fix gain values (git-fixes).\n- iio: adc: ad7280a: handle spi_setup() errors in probe() (git-fixes).\n- iio: adc: ad9467: fix ad9434 vref mask (git-fixes).\n- iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver (git-fixes).\n- iio: dac: ad5686: add AD5695R to ad5686_chip_info_tbl (git-fixes).\n- iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection (git-fixes).\n- Input: i8042 - add quirk for ASUS Zenbook UX425QA_UM425QA (stable-fixes).\n- Input: i8042 - add quirks for MECHREVO Wujie 15X Pro (stable-fixes).\n- intel_th: fix device leak on output open() (git-fixes).\n- leds: led-class: Only Add LED to leds_list when it is fully ready (git-fixes).\n- lib/crypto: aes: Fix missing MMU protection for AES S-box (git-fixes).\n- mei: me: add nova lake point S DID (stable-fixes).\n- mei: me: add wildcat lake P DID (stable-fixes).\n- mISDN: annotate data-race around dev-\u003ework (git-fixes).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1253087).\n- mmc: rtsx_pci_sdmmc: implement sdmmc_card_busy function (git-fixes).\n- mmc: sdhci-of-dwcmshc: Prevent illegal clock reduction in HS200/HS400 mode (git-fixes).\n- net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts (git-fixes).\n- net: hv_netvsc: reject RSS hash key programming without RX indirection table (bsc#1257473).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (git-fixes).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (git-fixes).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (git-fixes).\n- net: tcp: allow zero-window ACK update the window (bsc#1254767).\n- net: usb: dm9601: remove broken SR9700 support (git-fixes).\n- net: wwan: t7xx: fix potential skb-\u003efrags overflow in RX path (git-fixes).\n- nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame() (git-fixes).\n- nfc: nci: Fix race between rfkill and nci_unregister_device() (git-fixes).\n- NFS: Fix up the automount fs_context to use the correct cred (git-fixes).\n- nfsd: Drop the client reference in client_states_open() (git-fixes).\n- NFSD: Fix permission check for read access to executable-only files (git-fixes).\n- NFSD: use correct reservation type in nfsd4_scsi_fence_client (git-fixes).\n- NFSD/blocklayout: Fix minlength check in proc_layoutget (git-fixes).\n- NFSv4: ensure the open stateid seqid doesn't go backwards (git-fixes).\n- nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl() (git-fixes).\n- nvmet-auth: update sc_c in host response (git-fixes).\n- nvmet-auth: update sc_c in target host hash calculation (git-fixes).\n- of: fix reference count leak in of_alias_scan() (git-fixes).\n- of: platform: Use default match table for /firmware (git-fixes).\n- phy: freescale: imx8m-pcie: assert phy reset during power on (stable-fixes).\n- phy: rockchip: inno-usb2: fix communication disruption in gadget mode (git-fixes).\n- phy: rockchip: inno-usb2: fix disconnection in gadget mode (git-fixes).\n- phy: stm32-usphyc: Fix off by one in probe() (git-fixes).\n- phy: tegra: xusb: Explicitly configure HS_DISCON_LEVEL to 0x7 (git-fixes).\n- platform/x86: hp-bioscfg: Fix automatic module loading (git-fixes).\n- platform/x86: hp-bioscfg: Fix kernel panic in GET_INSTANCE_ID macro (git-fixes).\n- platform/x86: hp-bioscfg: Fix kobject warnings for empty attribute names (git-fixes).\n- platform/x86/amd: Fix memory leak in wbrf_record() (git-fixes).\n- pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() (git-fixes).\n- powercap: fix race condition in register_control_type() (stable-fixes).\n- powercap: fix sscanf() error return value handling (stable-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- RDMA/mana_ib: Access remote atomic for MRs (git-fixes).\n- RDMA/mana_ib: add additional port counters (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: add support of multiple ports (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (git-fixes).\n- regmap: Fix race condition in hwspinlock irqsave routine (git-fixes).\n- sched: Increase sched_tick_remote timeout (bsc#1254510).\n- sched/rt: Skip group schedulable check with rt_group_sched=0 (bsc#1256568).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256861).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256861).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256863).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256863).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256863).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256863).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256863).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256863).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256863).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256863).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256863).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256863).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256863).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256863).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests: net: fib-onlink-tests: Convert to use namespaces by default (bsc#1255346).\n- selftests/bpf: Fix flaky bpf_cookie selftest (git-fixes).\n- serial: 8250_pci: Fix broken RS485 for F81504/508/512 (git-fixes).\n- slimbus: core: fix device reference leak on report present (git-fixes).\n- slimbus: core: fix OF node leak on registration failure (git-fixes).\n- slimbus: core: fix of_slim_get_device() kernel doc (git-fixes).\n- slimbus: core: fix runtime PM imbalance on report present (git-fixes).\n- smb: change return type of cached_dir_lease_break() to bool (git-fixes).\n- smb: client: ensure open_cached_dir_by_dentry() only returns valid cfid (git-fixes).\n- smb: client: fix cifs_pick_channel when channel needs reconnect (git-fixes).\n- smb: client: fix warning when reconnecting channel (git-fixes).\n- smb: client: introduce close_cached_dir_locked() (git-fixes).\n- smb: client: remove unused fid_lock (git-fixes).\n- smb: client: short-circuit in open_cached_dir_by_dentry() if !dentry (git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- smb3: add missing null server pointer check (git-fixes).\n- spi: spi-sprd-adi: Fix double free in probe error path (git-fixes).\n- spi: sprd-adi: switch to use spi_alloc_host() (stable-fixes).\n- spi: sprd: adi: Use devm_register_restart_handler() (stable-fixes).\n- svcrdma: return 0 on success from svc_rdma_copy_inline_range (git-fixes).\n- uacce: ensure safe queue release with state management (git-fixes).\n- uacce: fix cdev handling in the cleanup path (git-fixes).\n- uacce: fix isolate sysfs check condition (git-fixes).\n- uacce: implement mremap in uacce_vm_ops to return -EPERM (git-fixes).\n- usb: core: add USB_QUIRK_NO_BOS for devices that hang on BOS descriptor (stable-fixes).\n- usb: dwc3: Check for USB4 IP_NAME (stable-fixes).\n- USB: OHCI/UHCI: Add soft dependencies on ehci_platform (stable-fixes).\n- USB: serial: ftdi_sio: add support for PICAXE AXE027 cable (stable-fixes).\n- USB: serial: option: add Telit LE910 MBIM composition (stable-fixes).\n- usbnet: limit max_mtu based on device's hard_mtu (git-fixes).\n- w1: fix redundant counter decrement in w1_attach_slave_device() (git-fixes).\n- w1: therm: Fix off-by-one buffer overflow in alarms_store (git-fixes).\n- wifi: ath10k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: ath12k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: mac80211: correctly decode TTLM with default link map (git-fixes).\n- wifi: mac80211: don't perform DA check on S1G beacon (git-fixes).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- wifi: rsi: Fix memory corruption due to not set vif driver data size (git-fixes).\n- x86: make page fault handling disable interrupts properly (git-fixes).\n- x86/microcode: Fix Entrysign revision check for Zen1/Naples (bsc#1256528).\n- x86/microcode/AMD: Add more known models to entry sign checking (bsc#1256528).\n- x86/microcode/AMD: Add some forgotten models to the SHA check (bsc#1256528).\n- x86/microcode/AMD: Add TSA microcode SHAs (bsc#1256528).\n- x86/microcode/AMD: Add Zen5 model 0x44, stepping 0x1 minrev (bsc#1256528).\n- x86/microcode/AMD: Clean the cache if update did not load microcode (bsc#1256528).\n- x86/microcode/AMD: Extend the SHA check to Zen5, block loading of any unreleased standalone Zen5 microcode patches (bsc#1256528).\n- x86/microcode/AMD: Fix __apply_microcode_amd()'s return value (bsc#1256528).\n- x86/microcode/AMD: Fix Entrysign revision check for Zen5/Strix Halo (bsc#1256528).\n- x86/microcode/AMD: Limit Entrysign signature checking to known generations (bsc#1256528).\n- x86/microcode/AMD: Load only SHA256-checksummed patches (bsc#1256528).\n- x86/microcode/AMD: Use sha256() instead of init/update/final (bsc#1256528).\n","status":"published","published":"2026-02-12T11:26:05Z","modified":"2026-03-23T04:52:16.396939Z","updated_at":"2026-11-02T15:54:00.846737Z"},{"id":"SUSE-SU-2026:0473-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 12 SP5 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2022-50347: mmc: rtsx_usb_sdmmc: fix return value check of mmc_add_host() (bsc#1249928).\n- CVE-2022-50580: blk-throttle: prevent overflow while calculating wait time (bsc#1252542).\n- CVE-2022-50676: net: rds: don't hold sock lock when cancelling work from rds_tcp_reset_callbacks() (bsc#1254689).\n- CVE-2022-50697: mrp: introduce active flags to prevent UAF when applicant uninit (bsc#1255594).\n- CVE-2022-50709: wifi: ath9k: avoid uninit memory read in ath9k_htc_rx_msg() (bsc#1255565).\n- CVE-2022-50716: wifi: ar5523: Fix use-after-free on ar5523_cmd() timed out (bsc#1255839).\n- CVE-2022-50717: nvmet-tcp: add bounds check on Transfer Tag (bsc#1255844).\n- CVE-2022-50719: ALSA: line6: fix stack overflow in line6_midi_transmit (bsc#1255939).\n- CVE-2022-50740: wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs() (bsc#1256155).\n- CVE-2022-50744: scsi: lpfc: Fix hard lockup when reading the rx_monitor from debugfs (bsc#1256165).\n- CVE-2022-50749: acct: fix potential integer overflow in encode_comp_t() (bsc#1256191).\n- CVE-2022-50751: configfs: fix possible memory leak in configfs_create_dir() (bsc#1256184).\n- CVE-2022-50760: drm/amdgpu: Fix PCI device refcount leak in amdgpu_atrm_get_bios() (bsc#1255983).\n- CVE-2022-50770: ocfs2: fix memory leak in ocfs2_mount_volume() (bsc#1256221).\n- CVE-2022-50777: net: phy: xgmiitorgmii: Fix refcount leak in xgmiitorgmii_probe (bsc#1256320).\n- CVE-2022-50780: net: fix UAF issue in nfqnl_nf_hook_drop() when ops_init() failed (bsc#1256305).\n- CVE-2022-50782: ext4: fix bug_on in __es_tree_search caused by bad quota inode (bsc#1256282).\n- CVE-2022-50786: media: s5p-mfc: Clear workbit to handle error condition (bsc#1256258).\n- CVE-2022-50816: ipv6: ensure sane device mtu in tunnels (bsc#1256038).\n- CVE-2022-50834: nfc: Fix potential resource leaks (bsc#1256219).\n- CVE-2022-50865: tcp: fix a signed-integer-overflow bug in tcp_add_backlog() (bsc#1256168).\n- CVE-2022-50868: hwrng: amd - Fix PCI device refcount leak (bsc#1256386).\n- CVE-2022-50880: wifi: ath10k: add peer map clean up for peer delete in ath10k_sta_state() (bsc#1256132).\n- CVE-2022-50881: ath9k: Fix typo in function name (bsc#1256130).\n- CVE-2022-50884: drm: Prevent drm_copy_field() to attempt copying a NULL pointer (bsc#1256127).\n- CVE-2022-50885: RDMA/rxe: Fix NULL-ptr-deref in rxe_qp_do_cleanup() when socket create failed (bsc#1256122).\n- CVE-2022-50887: regulator: core: fix unbalanced of node refcount in regulator_dev_lookup() (bsc#1256125).\n- CVE-2023-50756: nvme-pci: fix mempool alloc size (bsc#1256216).\n- CVE-2023-53685: tun: Fix memory leak for detached NAPI queue (bsc#1251770).\n- CVE-2023-53747: vc_screen: reload load of struct vc_data pointer in vcs_write() to avoid UAF (bsc#1254572).\n- CVE-2023-53751: cifs: fix potential use-after-free bugs in TCP_Server_Info::hostname (bsc#1254986).\n- CVE-2023-53825: kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg() (bsc#1254707).\n- CVE-2023-53853: netlink: annotate accesses to nlk-\u003ecb_running (bsc#1254673).\n- CVE-2023-53863: netlink: do not hard code device address lenth in fdb dumps (bsc#1254657).\n- CVE-2023-53992: wifi: cfg80211: ocb: don't leave if not joined (bsc#1256058).\n- CVE-2023-54012: net: fix stack overflow when LRO is disabled for virtual interfaces (bsc#1255571).\n- CVE-2023-54047: drm/rockchip: dw_hdmi: cleanup drm encoder during unbind (bsc#1256398).\n- CVE-2023-54048: RDMA/bnxt_re: Prevent handling any completions after qp destroy (bsc#1256395).\n- CVE-2023-54067: btrfs: fix race when deleting free space root from the dirty cow roots list (bsc#1256369).\n- CVE-2023-54111: pinctrl: rockchip: Fix refcount leak in rockchip_pinctrl_parse_groups (bsc#1256149).\n- CVE-2023-54112: kcm: Fix memory leak in error path of kcm_sendmsg() (bsc#1256354).\n- CVE-2023-54118: serial: sc16is7xx: setup GPIO controller later in probe (bsc#1256131).\n- CVE-2023-54121: btrfs: fix incorrect splitting in btrfs_drop_extent_map_range (bsc#1256267).\n- CVE-2023-54134: autofs: fix memory leak of waitqueues in autofs_catatonic_mode (bsc#1256106).\n- CVE-2023-54198: tty: fix out-of-bounds access in tty_driver_lookup_tty() (bsc#1255970).\n- CVE-2023-54202: drm/i915: fix race condition UAF in i915_perf_add_config_ioctl (bsc#1255880).\n- CVE-2023-54207: HID: uclogic: Correct devm device reference for hidinput input_dev name (bsc#1255961).\n- CVE-2023-54218: sock: Make sock-\u003esk_stamp thread-safe (bsc#1256229).\n- CVE-2023-54230: amba: bus: fix refcount leak (bsc#1255925).\n- CVE-2023-54243: netfilter: ebtables: fix table blob use-after-free (bsc#1255908).\n- CVE-2023-54265: ipv6: Fix an uninit variable access bug in __ip6_make_skb() (bsc#1255874).\n- CVE-2023-54274: RDMA/srpt: Add a check for valid 'mad_agent' pointer (bsc#1255905).\n- CVE-2023-54282: media: tuners: qt1010: replace BUG_ON with a regular error (bsc#1255810).\n- CVE-2023-54287: tty: serial: imx: disable Ageing Timer interrupt request irq (bsc#1255804).\n- CVE-2023-54311: ext4: fix deadlock when converting an inline directory in nojournal mode (bsc#1255773).\n- CVE-2023-54321: driver core: fix potential null-ptr-deref in device_add() (bsc#1255762).\n- CVE-2024-41007: tcp: use signed arithmetic in tcp_rtx_probe0_timed_out() (bsc#1227863).\n- CVE-2025-40115: scsi: mpt3sas: Fix crash in transport port remove by using ioc_info() (bsc#1253318).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).\n- CVE-2025-40271: fs/proc: fix uaf in proc_readdir_de() (bsc#1255297).\n- CVE-2025-40323: fbcon: Set fb_display[i]-\u003emode to NULL when the mode is released (bsc#1255094).\n- CVE-2025-40339: drm/amdgpu: fix nullptr err of vm_handle_moved (bsc#1255428).\n- CVE-2025-40345: usb: storage: sddr55: Reject out-of-bound new_pba (bsc#1255279).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68190: drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked() (bsc#1255131).\n- CVE-2025-68192: net: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup (bsc#1255246).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68264: ext4: refresh inline data size before write operations (bsc#1255380).\n- CVE-2025-68286: drm/amd/display: Check NULL before accessing (bsc#1255351).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68303: platform/x86: intel: punit_ipc: fix memory corruption (bsc#1255122).\n- CVE-2025-68305: Bluetooth: hci_sock: Prevent race in socket write iter and sock bind (bsc#1255169).\n- CVE-2025-68312: usbnet: Prevents free active kevent (bsc#1255171).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68354: regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex (bsc#1255553).\n- CVE-2025-68362: wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb() (bsc#1255611).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68740: ima: Handle error code returned by ima_filter_rule_match() (bsc#1255812).\n- CVE-2025-68757: drm/vgem-fence: Fix potential deadlock on release (bsc#1255943).\n- CVE-2025-68767: hfsplus: Verify inode mode when loading from disk (bsc#1256580).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68774: hfsplus: fix missing hfs_bnode_get() in __hfs_bnode_create (bsc#1256585).\n- CVE-2025-68783: ALSA: usb-mixer: us16x08: validate meter packet indices (bsc#1256650).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68797: char: applicom: fix NULL pointer dereference in ac_ioctl (bsc#1256660).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71082: Bluetooth: btusb: revert use of devm_kzalloc in btusb (bsc#1256611).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71108: usb: typec: ucsi: Handle incorrect num_connectors capability (bsc#1256774).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71119: powerpc/kexec: Enable SMT before waking offline CPUs (bsc#1205462).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2026-22976: net_sched: qfq: Fix double list add in class with netem as child qdisc (bsc#1257035).\n- CVE-2026-22978: wifi: avoid kernel-infoleak from struct iw_point (bsc#1257227).\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23001: macvlan: Use 'hash' iterators to simplify code (bsc#1257232).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- RDMA/rxe: Fix the error caused by qp-\u003esk (bsc#1256122).\n- RDMA/srpt: Fix disabling device management (bsc#1255905).\n- RDMA/srpt: Fix handling of SR-IOV and iWARP ports (bsc#1255905).\n- configfs: factor dirent removal into helpers (bsc#1256184).\n- drm/amdgpu: Remove explicit wait after VM validate (bsc#1255428).\n- drm/amdgpu: update mappings not managed by KFD (bsc#1255428).\n- hwrng: amd - Convert PCIBIOS_* return codes to errnos (bsc#1256386).\n- nvmet-tcp: Fix NULL dereference when a connect data comes in h2cdata pdu (bsc#1255844).\n","status":"published","published":"2026-02-12T11:26:33Z","modified":"2026-03-23T04:50:25.397341Z","updated_at":"2026-11-02T15:54:00.846737Z"},{"id":"SUSE-SU-2026:0587-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 RT kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-54013: interconnect: Fix locking for runpm vs reclaim (bsc#1256280).\n- CVE-2025-39880: libceph: fix invalid accesses to ceph_connection_v1_info (bsc#1250388).\n- CVE-2025-40238: net/mlx5: Fix IPsec cleanup over MPV device (bsc#1254871).\n- CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields (bsc#1254852).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).\n- CVE-2025-40328: smb: client: fix potential UAF in smb2_close_cached_fid() (bsc#1254624).\n- CVE-2025-40350: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ (bsc#1255260).\n- CVE-2025-40355: sysfs: check visibility before changing group attribute ownership (bsc#1255261).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68171: x86/fpu: Ensure XFD state on signal delivery (bsc#1255255).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68215: ice: fix PTP cleanup on driver removal in error path (bsc#1255226).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68284: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() (bsc#1255377).\n- CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68301: net: atlantic: fix fragment overflow handling in RX path (bsc#1255120).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68327: usb: renesas_usbhs: Fix synchronous external abort on unbind (bsc#1255488).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68363: bpf: Check skb-\u003etransport_header is set in bpf_skb_check_mtu (bsc#1255552).\n- CVE-2025-68365: fs/ntfs3: Initialize allocated memory before use (bsc#1255548).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68727: ntfs3: Fix uninit buffer allocated by __getname() (bsc#1255568).\n- CVE-2025-68728: ntfs3: fix uninit memory after failed mi_read in mi_format_new (bsc#1255539).\n- CVE-2025-68733: smack: fix bug: unprivileged task can create labels (bsc#1255615).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: nfsd: set security label during create operations (bsc#1256770).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change\n (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71080: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT (bsc#1256608).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix 'UBSAN: shift-out-of-bounds error' (bsc#1256760).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71156: gve: defer interrupt enabling until NAPI registration (bsc#1257167).\n- CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() (bsc#1257168).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: ctxfi: Fix potential OOB access in audio mixer handling (stable-fixes).\n- ALSA: scarlett2: Fix buffer overflow in config retrieval (git-fixes).\n- ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (git-fixes).\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- ALSA: usb: Increase volume range that triggers a warning (git-fixes).\n- ASoC: Intel: sof_es8336: fix headphone GPIO logic inversion (git-fixes).\n- ASoC: amd: yc: Add quirk for Honor MagicBook X16 2025 (stable-fixes).\n- ASoC: codecs: wsa881x: Drop unused version readout (stable-fixes).\n- ASoC: codecs: wsa881x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa883x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa884x: fix codec initialisation (git-fixes).\n- ASoC: fsl: imx-card: Do not force slot width to sample width (git-fixes).\n- ASoC: fsl_sai: Add missing registers to cache default (stable-fixes).\n- ASoC: tlv320adcx140: fix null pointer (git-fixes).\n- ASoC: tlv320adcx140: fix word length (git-fixes).\n- Bluetooth: MGMT: Fix memory leak in set_ssp_complete (git-fixes).\n- Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work (git-fixes).\n- HID: usbhid: paper over wrong bNumDescriptor field (stable-fixes).\n- Input: i8042 - add quirk for ASUS Zenbook UX425QA_UM425QA (stable-fixes).\n- Input: i8042 - add quirks for MECHREVO Wujie 15X Pro (stable-fixes).\n- NFS: Fix up the automount fs_context to use the correct cred (git-fixes).\n- NFSD/blocklayout: Fix minlength check in proc_layoutget (git-fixes).\n- NFSD: Fix permission check for read access to executable-only files (git-fixes).\n- NFSD: use correct reservation type in nfsd4_scsi_fence_client (git-fixes).\n- NFSv4: ensure the open stateid seqid doesn't go backwards (git-fixes).\n- RDMA/mana_ib: Access remote atomic for MRs (git-fixes).\n- RDMA/mana_ib: Add device statistics support (git-fixes).\n- RDMA/mana_ib: Add port statistics support (git-fixes).\n- RDMA/mana_ib: Add support of 4M, 1G, and 2G pages (git-fixes).\n- RDMA/mana_ib: Add support of mana_ib for RNIC and ETH nic (git-fixes).\n- RDMA/mana_ib: Allow registration of DMA-mapped memory in PDs (git-fixes).\n- RDMA/mana_ib: Create and destroy UD/GSI QP (git-fixes).\n- RDMA/mana_ib: Drain send wrs of GSI QP (git-fixes).\n- RDMA/mana_ib: Extend modify QP (git-fixes).\n- RDMA/mana_ib: Fix error code in probe() (git-fixes).\n- RDMA/mana_ib: Fix integer overflow during queue creation (git-fixes).\n- RDMA/mana_ib: Handle net event for pointing to the current netdev (bsc#1256690).\n- RDMA/mana_ib: Implement DMABUF MR support (git-fixes).\n- RDMA/mana_ib: Query feature_flags bitmask from FW (git-fixes).\n- RDMA/mana_ib: UD/GSI QP creation for kernel (git-fixes).\n- RDMA/mana_ib: UD/GSI work requests (git-fixes).\n- RDMA/mana_ib: Use safer allocation function() (git-fixes).\n- RDMA/mana_ib: add additional port counters (git-fixes).\n- RDMA/mana_ib: add support of multiple ports (git-fixes).\n- RDMA/mana_ib: check cqe length for kernel CQs (git-fixes).\n- RDMA/mana_ib: create kernel-level CQs (git-fixes).\n- RDMA/mana_ib: create/destroy AH (git-fixes).\n- RDMA/mana_ib: extend mana QP table (git-fixes).\n- RDMA/mana_ib: helpers to allocate kernel queues (git-fixes).\n- RDMA/mana_ib: implement get_dma_mr (git-fixes).\n- RDMA/mana_ib: implement req_notify_cq (git-fixes).\n- RDMA/mana_ib: indicate CM support (git-fixes).\n- RDMA/mana_ib: polling of CQs for GSI/UD (git-fixes).\n- RDMA/mana_ib: request error CQEs when supported (git-fixes).\n- RDMA/mana_ib: support of the zero based MRs (git-fixes).\n- RDMA/mana_ib: unify mana_ib functions to support any gdma device (git-fixes).\n- Revert 'nfc/nci: Add the inconsistency check between the input data length and count' (git-fixes).\n- USB: OHCI/UHCI: Add soft dependencies on ehci_platform (stable-fixes).\n- USB: serial: ftdi_sio: add support for PICAXE AXE027 cable (stable-fixes).\n- USB: serial: option: add Telit LE910 MBIM composition (stable-fixes).\n- ata: libata: Add cpr_log to ata_dev_print_features() early return (git-fixes).\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- bs-upload-kernel: Fix cve branch uploads.\n- btrfs: do not strictly require dirty metadata threshold for metadata writepages (stable-fixes).\n- can: ctucanfd: fix SSP_SRC in cases when bit-rate is higher than 1 MBit (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: etas_es58x: allow partial RX URB allocation to succeed (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): fix error message (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error (git-fixes).\n- can: j1939: make j1939_session_activate() fail if device is no longer registered (stable-fixes).\n- can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak (git-fixes).\n- cifs: Fix copy offload to flush destination region (bsc#1252511).\n- cifs: Fix flushing, invalidation and file size with copy_file_range() (bsc#1252511).\n- cifs: add new field to track the last access time of cfid (git-fixes).\n- cifs: after disabling multichannel, mark tcon for reconnect (git-fixes).\n- cifs: avoid redundant calls to disable multichannel (git-fixes).\n- cifs: cifs_pick_channel should try selecting active channels (git-fixes).\n- cifs: deal with the channel loading lag while picking channels (git-fixes).\n- cifs: dns resolution is needed only for primary channel (git-fixes).\n- cifs: do not disable interface polling on failure (git-fixes).\n- cifs: do not search for channel if server is terminating (git-fixes).\n- cifs: fix a pending undercount of srv_count (git-fixes).\n- cifs: fix lock ordering while disabling multichannel (git-fixes).\n- cifs: fix stray unlock in cifs_chan_skip_or_disable (git-fixes).\n- cifs: fix use after free for iface while disabling secondary channels (git-fixes).\n- cifs: handle servers that still advertise multichannel after disabling (git-fixes).\n- cifs: handle when server starts supporting multichannel (git-fixes).\n- cifs: handle when server stops supporting multichannel (git-fixes).\n- cifs: make cifs_chan_update_iface() a void function (git-fixes).\n- cifs: make sure server interfaces are requested only for SMB3+ (git-fixes).\n- cifs: make sure that channel scaling is done only once (git-fixes).\n- cifs: reconnect worker should take reference on server struct unconditionally (git-fixes).\n- cifs: reset connections for all channels when reconnect requested (git-fixes).\n- cifs: reset iface weights when we cannot find a candidate (git-fixes).\n- cifs: serialize other channels when query server interfaces is pending (git-fixes).\n- cifs: update dstaddr whenever channel iface is updated (git-fixes).\n- comedi: Fix getting range information for subdevices 16 to 255 (git-fixes).\n- comedi: dmm32at: serialize use of paged registers (git-fixes).\n- comedi: fix divide-by-zero in comedi_buf_munge() (stable-fixes).\n- cpuset: fix warning when disabling remote partition (bsc#1256794).\n- crypto: authencesn - reject too-short AAD (assoclen\u003c8) to match ESP/ESN spec (git-fixes).\n- dmaengine: apple-admac: Add 'apple,t8103-admac' compatible (git-fixes).\n- dmaengine: at_hdmac: fix device leak on of_dma_xlate() (git-fixes).\n- dmaengine: bcm-sba-raid: fix device leak on probe (git-fixes).\n- dmaengine: dw: dmamux: fix OF node leak on route allocation failure (git-fixes).\n- dmaengine: idxd: fix device leaks on compat bind and unbind (git-fixes).\n- dmaengine: lpc18xx-dmamux: fix device leak on route allocation (git-fixes).\n- dmaengine: omap-dma: fix dma_pool resource leak in error paths (git-fixes).\n- dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config() (git-fixes).\n- dmaengine: sh: rz-dmac: Fix rz_dmac_terminate_all() (git-fixes).\n- dmaengine: tegra-adma: Fix use-after-free (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on dra7x route allocation (git-fixes).\n- dmaengine: ti: k3-udma: fix device leak on udma lookup (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap max_register (git-fixes).\n- dmaengine: xilinx_dma: Fix uninitialized addr_width when 'xlnx,addrwidth' property is missing (git-fixes).\n- dpll: Prevent duplicate registrations (git-fixes).\n- dpll: fix device-id-get and pin-id-get to return errors properly (git-fixes).\n- dpll: fix return value check for kmemdup (git-fixes).\n- dpll: indent DPLL option type by a tab (git-fixes).\n- dpll: spec: add missing module-name and clock-id to pin-get reply (git-fixes).\n- drm/amd/display: Apply e4479aecf658 to dml (stable-fixes).\n- drm/amd/display: Bump the HDMI clock to 340MHz (stable-fixes).\n- drm/amd/display: Fix DP no audio issue (stable-fixes).\n- drm/amd/display: Initialise backlight level values from hw (git-fixes).\n- drm/amd/display: Respect user's CONFIG_FRAME_WARN more for dml files (stable-fixes).\n- drm/amd/display: shrink struct members (stable-fixes).\n- drm/amd/pm: Don't clear SI SMC table when setting power limit (git-fixes).\n- drm/amd/pm: Workaround SI powertune issue on Radeon 430 (v2) (git-fixes).\n- drm/amd/pm: fix race in power state check before mutex lock (git-fixes).\n- drm/amd/pm: fix smu overdrive data type wrong issue on smu 14.0.2 (git-fixes).\n- drm/amd: Clean up kfd node on surprise disconnect (stable-fixes).\n- drm/amdgpu: Fix cond_exec handling in amdgpu_ib_schedule() (git-fixes).\n- drm/amdgpu: Fix query for VPE block_type and ip_count (stable-fixes).\n- drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove (git-fixes).\n- drm/amdgpu: remove frame cntl for gfx v12 (stable-fixes).\n- drm/amdkfd: Fix improper NULL termination of queue restore SMI event string (stable-fixes).\n- drm/amdkfd: fix a memory leak in device_queue_manager_init() (git-fixes).\n- drm/imagination: Wait for FW trace update command completion (git-fixes).\n- drm/imx/tve: fix probe device leak (git-fixes).\n- drm/msm/a6xx: fix bogus hwcg register updates (git-fixes).\n- drm/nouveau/disp/nv50-: Set lock_core in curs507a_prepare (git-fixes).\n- drm/nouveau/disp: Set drm_mode_config_funcs.atomic_(check|commit) (stable-fixes).\n- drm/nouveau: add missing DCB connector types (git-fixes).\n- drm/nouveau: implement missing DCB connector types; gracefully handle unknown connectors (git-fixes).\n- drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel (git-fixes).\n- drm/radeon: Remove __counted_by from ClockInfoArray.clockInfo[] (stable-fixes).\n- drm/vmwgfx: Fix an error return check in vmw_compat_shader_add() (git-fixes).\n- drm/vmwgfx: Merge vmw_bo_release and vmw_bo_free functions (git-fixes).\n- exfat: check return value of sb_min_blocksize in exfat_read_boot_sector (git-fixes).\n- exfat: fix remount failure in different process environments (git-fixes).\n- gpio: omap: do not register driver in probe() (git-fixes).\n- gpio: pca953x: Add support for level-triggered interrupts (stable-fixes).\n- gpio: pca953x: Utilise dev_err_probe() where it makes sense (stable-fixes).\n- gpio: pca953x: Utilise temporary variable for struct device (stable-fixes).\n- gpio: pca953x: fix wrong error probe return value (git-fixes).\n- gpio: pca953x: handle short interrupt pulses on PCAL devices (git-fixes).\n- gpio: rockchip: Stop calling pinctrl for set_direction (git-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- iio: accel: iis328dq: fix gain values (git-fixes).\n- iio: adc: ad7280a: handle spi_setup() errors in probe() (git-fixes).\n- iio: adc: ad9467: fix ad9434 vref mask (git-fixes).\n- iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver (git-fixes).\n- iio: dac: ad5686: add AD5695R to ad5686_chip_info_tbl (git-fixes).\n- iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection (git-fixes).\n- intel_th: fix device leak on output open() (git-fixes).\n- leds: led-class: Only Add LED to leds_list when it is fully ready (git-fixes).\n- lib/crypto: aes: Fix missing MMU protection for AES S-box (git-fixes).\n- mISDN: annotate data-race around dev-\u003ework (git-fixes).\n- mei: me: add nova lake point S DID (stable-fixes).\n- mei: me: add wildcat lake P DID (stable-fixes).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1253087 bsc#1254447).\n- mmc: rtsx_pci_sdmmc: implement sdmmc_card_busy function (git-fixes).\n- mmc: sdhci-of-dwcmshc: Prevent illegal clock reduction in HS200/HS400 mode (git-fixes).\n- net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts (git-fixes).\n- net: hv_netvsc: reject RSS hash key programming without RX indirection table (bsc#1257473).\n- net: mana: Add metadata support for xdp mode (git-fixes).\n- net: mana: Add standard counter rx_missed_errors (git-fixes).\n- net: mana: Add support for auxiliary device servicing events (git-fixes).\n- net: mana: Change the function signature of mana_get_primary_netdev_rcu (bsc#1256690).\n- net: mana: Drop TX skb on post_work_request failure and unmap resources (git-fixes).\n- net: mana: Fix use-after-free in reset service rescan path (git-fixes).\n- net: mana: Fix warnings for missing export.h header inclusion (git-fixes).\n- net: mana: Handle Reset Request from MANA NIC (git-fixes).\n- net: mana: Handle SKB if TX SGEs exceed hardware limit (git-fixes).\n- net: mana: Handle hardware recovery events when probing the device (git-fixes).\n- net: mana: Handle unsupported HWC commands (git-fixes).\n- net: mana: Move hardware counter stats from per-port to per-VF context (git-fixes).\n- net: mana: Probe rdma device in mana driver (git-fixes).\n- net: mana: Reduce waiting time if HWC not responding (git-fixes).\n- net: mana: fix spelling for mana_gd_deregiser_irq() (git-fixes).\n- net: tcp: allow zero-window ACK update the window (bsc#1254767).\n- net: usb: dm9601: remove broken SR9700 support (git-fixes).\n- net: wwan: t7xx: fix potential skb-\u003efrags overflow in RX path (git-fixes).\n- nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame() (git-fixes).\n- nfc: nci: Fix race between rfkill and nci_unregister_device() (git-fixes).\n- nfsd: Drop the client reference in client_states_open() (git-fixes).\n- nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl() (git-fixes).\n- nvmet-auth: update sc_c in host response (git-fixes).\n- nvmet-auth: update sc_c in target host hash calculation (git-fixes).\n- of: fix reference count leak in of_alias_scan() (git-fixes).\n- of: platform: Use default match table for /firmware (git-fixes).\n- phy: freescale: imx8m-pcie: assert phy reset during power on (stable-fixes).\n- phy: rockchip: inno-usb2: fix communication disruption in gadget mode (git-fixes).\n- phy: rockchip: inno-usb2: fix disconnection in gadget mode (git-fixes).\n- phy: stm32-usphyc: Fix off by one in probe() (git-fixes).\n- phy: tegra: xusb: Explicitly configure HS_DISCON_LEVEL to 0x7 (git-fixes).\n- platform/x86/amd: Fix memory leak in wbrf_record() (git-fixes).\n- platform/x86: hp-bioscfg: Fix automatic module loading (git-fixes).\n- platform/x86: hp-bioscfg: Fix kernel panic in GET_INSTANCE_ID macro (git-fixes).\n- platform/x86: hp-bioscfg: Fix kobject warnings for empty attribute names (git-fixes).\n- pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() (git-fixes).\n- powercap: fix race condition in register_control_type() (stable-fixes).\n- powercap: fix sscanf() error return value handling (stable-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- regmap: Fix race condition in hwspinlock irqsave routine (git-fixes).\n- sched/rt: Skip group schedulable check with rt_group_sched=0 (bsc#1256568).\n- sched: Increase sched_tick_remote timeout (bsc#1254510).\n- scripts/python/git_sort/git_sort.yaml: add cifs for-next repository.\n- scripts: obsapi: Support URL trailing / in oscrc.\n- scripts: teaapi: Add paging.\n- scripts: uploader: Fix no change condition for _maintainership.json.\n- scripts: uploader: Handle missing upstream in is_pr_open.\n- scrits: teaapi: Add list_repos.\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256861).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256861).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256863).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256863).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256863).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256863).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256863).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256863).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256863).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256863).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256863).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256863).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256863).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256863).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests/bpf: Fix flaky bpf_cookie selftest (git-fixes).\n- selftests: net: fib-onlink-tests: Convert to use namespaces by default (bsc#1255346).\n- serial: 8250_pci: Fix broken RS485 for F81504/508/512 (git-fixes).\n- slimbus: core: fix OF node leak on registration failure (git-fixes).\n- slimbus: core: fix device reference leak on report present (git-fixes).\n- slimbus: core: fix of_slim_get_device() kernel doc (git-fixes).\n- slimbus: core: fix runtime PM imbalance on report present (git-fixes).\n- smb3: add missing null server pointer check (git-fixes).\n- smb: change return type of cached_dir_lease_break() to bool (git-fixes).\n- smb: client: ensure open_cached_dir_by_dentry() only returns valid cfid (git-fixes).\n- smb: client: fix cifs_pick_channel when channel needs reconnect (git-fixes).\n- smb: client: fix warning when reconnecting channel (git-fixes).\n- smb: client: introduce close_cached_dir_locked() (git-fixes).\n- smb: client: remove unused fid_lock (git-fixes).\n- smb: client: short-circuit in open_cached_dir_by_dentry() if !dentry (git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748 bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- spi: spi-sprd-adi: Fix double free in probe error path (git-fixes).\n- spi: sprd-adi: switch to use spi_alloc_host() (stable-fixes).\n- spi: sprd: adi: Use devm_register_restart_handler() (stable-fixes).\n- svcrdma: return 0 on success from svc_rdma_copy_inline_range (git-fixes).\n- uacce: ensure safe queue release with state management (git-fixes).\n- uacce: fix cdev handling in the cleanup path (git-fixes).\n- uacce: fix isolate sysfs check condition (git-fixes).\n- uacce: implement mremap in uacce_vm_ops to return -EPERM (git-fixes).\n- usb: core: add USB_QUIRK_NO_BOS for devices that hang on BOS descriptor (stable-fixes).\n- usb: dwc3: Check for USB4 IP_NAME (stable-fixes).\n- usbnet: limit max_mtu based on device's hard_mtu (git-fixes).\n- w1: fix redundant counter decrement in w1_attach_slave_device() (git-fixes).\n- w1: therm: Fix off-by-one buffer overflow in alarms_store (git-fixes).\n- wifi: ath10k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: ath12k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: mac80211: correctly decode TTLM with default link map (git-fixes).\n- wifi: mac80211: don't perform DA check on S1G beacon (git-fixes).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- wifi: rsi: Fix memory corruption due to not set vif driver data size (git-fixes).\n- x86/microcode/AMD: Add TSA microcode SHAs (bsc#1256528).\n- x86/microcode/AMD: Add Zen5 model 0x44, stepping 0x1 minrev (bsc#1256528).\n- x86/microcode/AMD: Add more known models to entry sign checking (bsc#1256528).\n- x86/microcode/AMD: Add some forgotten models to the SHA check (bsc#1256528).\n- x86/microcode/AMD: Clean the cache if update did not load microcode (bsc#1256528).\n- x86/microcode/AMD: Extend the SHA check to Zen5, block loading of any unreleased standalone Zen5 microcode patches\n (bsc#1256528).\n- x86/microcode/AMD: Fix Entrysign revision check for Zen5/Strix Halo (bsc#1256528).\n- x86/microcode/AMD: Fix __apply_microcode_amd()'s return value (bsc#1256528).\n- x86/microcode/AMD: Limit Entrysign signature checking to known generations (bsc#1256528).\n- x86/microcode/AMD: Load only SHA256-checksummed patches (bsc#1256528).\n- x86/microcode/AMD: Use sha256() instead of init/update/final (bsc#1256528).\n- x86/microcode: Fix Entrysign revision check for Zen1/Naples (bsc#1256528).\n- x86: make page fault handling disable interrupts properly (git-fixes).\n","status":"published","published":"2026-02-20T10:04:28Z","modified":"2026-03-23T04:52:23.385245Z","updated_at":"2026-11-02T15:54:00.846737Z"},{"id":"SUSE-SU-2026:20477-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and Micro 6.1 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-54013: interconnect: Fix locking for runpm vs reclaim (bsc#1256280).\n- CVE-2025-38321: smb: Log an error when close_all_cached_dirs fails (bsc#1246328).\n- CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).\n- CVE-2025-39880: libceph: fix invalid accesses to ceph_connection_v1_info (bsc#1250388).\n- CVE-2025-39890: wifi: ath12k: fix memory leak in ath12k_service_ready_ext_event (bsc#1250334).\n- CVE-2025-39977: futex: Prevent use-after-free during requeue-PI (bsc#1252046).\n- CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).\n- CVE-2025-40024: vhost: Take a reference on the task in struct vhost_task (bsc#1252686).\n- CVE-2025-40033: remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable() (bsc#1252824).\n- CVE-2025-40042: tracing: Fix race condition in kprobe initialization causing NULL pointer dereference (bsc#1252861).\n- CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).\n- CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).\n- CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).\n- CVE-2025-40123: bpf: Enforce expected_attach_type for tailcall compatibility (bsc#1253365).\n- CVE-2025-40134: dm: fix NULL pointer dereference in __dm_suspend() (bsc#1253386).\n- CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).\n- CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).\n- CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).\n- CVE-2025-40160: xen/events: Cleanup find_virq() return codes (bsc#1253400).\n- CVE-2025-40167: ext4: detect invalid INLINE_DATA + EXTENTS flag combination (bsc#1253458).\n- CVE-2025-40170: net: use dst_dev_rcu() in sk_setup_caps() (bsc#1253413).\n- CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).\n- CVE-2025-40179: ext4: verify orphan file size is not too big (bsc#1253442).\n- CVE-2025-40187: net/sctp: fix a null dereference in sctp_disposition sctp_sf_do_5_1D_ce() (bsc#1253647).\n- CVE-2025-40190: ext4: guard against EA inode refcount underflow in xattr update (bsc#1253623).\n- CVE-2025-40215: kABI: xfrm: delete x-\u003etunnel as we delete x (bsc#1254959).\n- CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).\n- CVE-2025-40231: vsock: fix lock inversion in vsock_assign_transport() (bsc#1254815).\n- CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).\n- CVE-2025-40238: net/mlx5: Fix IPsec cleanup over MPV device (bsc#1254871).\n- CVE-2025-40240: sctp: avoid NULL dereference when chunk data buffer is missing (bsc#1254869).\n- CVE-2025-40242: gfs2: Fix unlikely race in gdlm_put_lock (bsc#1255075).\n- CVE-2025-40248: vsock: Ignore signal/timeout on connect() if already established (bsc#1254864).\n- CVE-2025-40250: net/mlx5: Clean up only new IRQ glue on request_irq() failure (bsc#1254854).\n- CVE-2025-40251: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (bsc#1254856).\n- CVE-2025-40252: net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end() (bsc#1254849).\n- CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields (bsc#1254852).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40258: mptcp: fix race condition in mptcp_schedule_work() (bsc#1254843).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).\n- CVE-2025-40268: cifs: client: fix memory leak in smb3_fs_context_parse_param (bsc#1255082).\n- CVE-2025-40271: fs/proc: fix uaf in proc_readdir_de() (bsc#1255297).\n- CVE-2025-40274: KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying (bsc#1254830).\n- CVE-2025-40278: net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak (bsc#1254825).\n- CVE-2025-40279: net: sched: act_connmark: initialize struct tc_ife to fix kernel leak (bsc#1254846).\n- CVE-2025-40280: tipc: Fix use-after-free in tipc_mon_reinit_self() (bsc#1254847).\n- CVE-2025-40287: exfat: fix improper check of dentry.stream.valid_size (bsc#1255030).\n- CVE-2025-40289: drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM (bsc#1255042).\n- CVE-2025-40292: virtio-net: fix received length check in big packets (bsc#1255175).\n- CVE-2025-40293: iommufd: Don't overflow during division for dirty tracking (bsc#1255179).\n- CVE-2025-40297: net: bridge: fix use-after-free due to MST port state bypass (bsc#1255187).\n- CVE-2025-40307: exfat: validate cluster allocation bits of the allocation bitmap (bsc#1255039).\n- CVE-2025-40319: bpf: Sync pending IRQ work before freeing ring buffer (bsc#1254794).\n- CVE-2025-40328: smb: client: fix potential UAF in smb2_close_cached_fid() (bsc#1254624).\n- CVE-2025-40331: sctp: Prevent TOCTOU out-of-bounds write (bsc#1254615).\n- CVE-2025-40337: net: stmmac: Correctly handle Rx checksum offload errors (bsc#1255081).\n- CVE-2025-40338: ASoC: Intel: avs: Do not share the name pointer between components (bsc#1255273).\n- CVE-2025-40339: drm/amdgpu: fix nullptr err of vm_handle_moved (bsc#1255428).\n- CVE-2025-40346: arch_topology: Fix incorrect error check in topology_parse_cpu_capacity() (bsc#1255318).\n- CVE-2025-40350: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ (bsc#1255260).\n- CVE-2025-40355: sysfs: check visibility before changing group attribute ownership (bsc#1255261).\n- CVE-2025-40360: drm/sysfb: Do not dereference NULL pointer in plane reset (bsc#1255095).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68171: x86/fpu: Ensure XFD state on signal delivery (bsc#1255255).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68190: drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked() (bsc#1255131).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68201: drm/amdgpu: remove two invalid BUG_ON()s (bsc#1255136).\n- CVE-2025-68204: pmdomain: arm: scmi: Fix genpd leak on provider registration failure (bsc#1255224).\n- CVE-2025-68206: netfilter: nft_ct: add seqadj extension for natted connections (bsc#1255142).\n- CVE-2025-68208: bpf: account for current allocated stack depth in widen_imprecise_scalars() (bsc#1255227).\n- CVE-2025-68209: mlx5: Fix default values in create CQ (bsc#1255230).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68230: drm/amdgpu: fix gpu page fault after hibernation on PF passthrough (bsc#1255134).\n- CVE-2025-68239: binfmt_misc: restore write access before closing files opened by open_exec() (bsc#1255272).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68255: staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing (bsc#1255395).\n- CVE-2025-68259: KVM: SVM: Don't skip unrelated instruction if INT3/INTO is replaced (bsc#1255199).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68264: ext4: refresh inline data size before write operations (bsc#1255380).\n- CVE-2025-68284: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() (bsc#1255377).\n- CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68301: net: atlantic: fix fragment overflow handling in RX path (bsc#1255120).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68327: usb: renesas_usbhs: Fix synchronous external abort on unbind (bsc#1255488).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68340: team: Move team device type change at the end of team_port_add (bsc#1255507).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68363: bpf: Check skb-\u003etransport_header is set in bpf_skb_check_mtu (bsc#1255552).\n- CVE-2025-68365: fs/ntfs3: Initialize allocated memory before use (bsc#1255548).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68378: bpf: Refactor stack map trace depth calculation into helper function (bsc#1255614).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68727: ntfs3: Fix uninit buffer allocated by __getname() (bsc#1255568).\n- CVE-2025-68728: ntfs3: fix uninit memory after failed mi_read in mi_format_new (bsc#1255539).\n- CVE-2025-68733: smack: fix bug: unprivileged task can create labels (bsc#1255615).\n- CVE-2025-68742: bpf: Improve program stats run-time calculation (bsc#1255707).\n- CVE-2025-68744: bpf: Free special fields when update [lru_,]percpu_hash maps (bsc#1255709).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: nfsd: set security label during create operations (bsc#1256770).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" (bsc#1256760).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- Disable CONFIG_CPU5_WDT The cpu5wdt driver doesn't implement a\n proper watchdog interface and has many code issues. It only handles\n obscure and obsolete hardware. Stop building and supporting this driver\n (jsc#PED-14062).\n- Update config files (jsc#PED-12554 jsc#PED-6996\n bsc#1243677 ltc#213602 bsc#1243678 ltc#213596)\n CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY=y\n CONFIG_INTEGRITY_CA_MACHINE_KEYRING_MAX=y\n- Update config files: disable CONFIG_DEVPORT for arm64 (bsc#1256792)\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- cifs: Fix copy offload to flush destination region (bsc#1252511).\n- cifs: Fix flushing, invalidation and file size with copy_file_range() (bsc#1252511).\n- cifs: Fix uncached read into ITER_KVEC iterator (bsc#1245449).\n- cifs: make cifs_chan_update_iface() a void function (git-fixes).\n- cifs: update dstaddr whenever channel iface is updated (git-fixes).\n- cpuidle: menu: Use residency threshold in polling state override decisions (bsc#1255026).\n- dm: fix queue start/stop imbalance under suspend/load/resume races (bsc#1253386)\n- drm/amdgpu: update mappings not managed by KFD (bsc#1255428)\n- ext4: use optimized mballoc scanning regardless of inode format (bsc#1254378).\n- ext4: wait for ongoing I/O to complete before freeing blocks (bsc#1256366).\n- fs: dlm: allow to F_SETLKW getting interrupted (bsc#1255025).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- media: atomisp: Prefix firmware paths with \"intel/ipu/\" (bsc#1252973).\n- media: atomisp: Remove firmware_name module parameter (bsc#1252973).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1254447 bsc#1253087).\n- net: hv_netvsc: reject RSS hash key programming without RX indirection table (bsc#1257473).\n- net: tcp: allow zero-window ACK update the window (bsc#1254767).\n- net: usb: pegasus: fix memory leak in update_eth_regs_async() (git-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event\n handling (bsc#1253262 ltc#216029).\n- powerpc/kexec: Enable SMT before waking offline CPUs (bsc#1214285\n bsc#1205462 ltc#200161 ltc#200588 git-fixes bsc#1253739 ltc#211493\n bsc#1254244 ltc#216496).\n- sched: Increase sched_tick_remote timeout (bsc#1254510).\n- scsi: lpfc: Add capability to register Platform Name ID to fabric (bsc#1254119).\n- scsi: lpfc: Allow support for BB credit recovery in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Ensure unregistration of rpis for received PLOGIs (bsc#1254119).\n- scsi: lpfc: Fix leaked ndlp krefs when in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI (bsc#1254119).\n- scsi: lpfc: Modify kref handling for Fabric Controller ndlps (bsc#1254119).\n- scsi: lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb() (bsc#1254119).\n- scsi: lpfc: Revise discovery related function headers and comments (bsc#1254119).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256861).\n- scsi: lpfc: Update lpfc version to 14.4.0.12 (bsc#1254119).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256861).\n- scsi: lpfc: Update various NPIV diagnostic log messaging (bsc#1254119).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256863).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256863).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256863).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256863).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256863).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256863).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256863).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256863).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256863).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256863).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256863).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256863).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748,bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- soc/tegra: fuse: speedo-tegra210: Update speedo IDs (git-fixes).\n- spi: tegra210-quad: Check hardware status on timeout (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (bsc#1253155)\n- spi: tegra210-quad: Refactor error handling into helper functions (bsc#1253155)\n- spi: tegra210-quad: Update dummy sequence configuration (git-fixes)\n- supported.conf: Mark lan 743x supported (jsc#PED-14571)\n- tracing: Fix access to trace_event_file (bsc#1254373).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- x86/microcode/AMD: Add TSA microcode SHAs (bsc#1256528).\n- x86/microcode/AMD: Add Zen5 model 0x44, stepping 0x1 minrev (bsc#1256528).\n- x86/microcode/AMD: Add more known models to entry sign checking (bsc#1256528).\n- x86/microcode/AMD: Add some forgotten models to the SHA check (bsc#1256528).\n- x86/microcode/AMD: Clean the cache if update did not load microcode (bsc#1256528).\n- x86/microcode/AMD: Extend the SHA check to Zen5, block loading of any\n unreleased standalone Zen5 microcode patches (bsc#1256528).\n- x86/microcode/AMD: Fix Entrysign revision check for Zen5/Strix Halo (bsc#1256528).\n- x86/microcode/AMD: Fix __apply_microcode_amd()'s return value (bsc#1256528).\n- x86/microcode/AMD: Limit Entrysign signature checking to known generations (bsc#1256528).\n- x86/microcode/AMD: Load only SHA256-checksummed patches (bsc#1256528).\n- x86/microcode/AMD: Select which microcode patch to load (bsc#1256528).\n- x86/microcode/AMD: Use sha256() instead of init/update/final (bsc#1256528).\n- x86/microcode: Fix Entrysign revision check for Zen1/Naples (bsc#1256528).\n","status":"published","published":"2026-02-24T10:42:46Z","modified":"2026-03-23T04:52:59.338344Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20498-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and Micro 6.1 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2023-54013: interconnect: Fix locking for runpm vs reclaim (bsc#1256280).\n- CVE-2025-38321: smb: Log an error when close_all_cached_dirs fails (bsc#1246328).\n- CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).\n- CVE-2025-39880: libceph: fix invalid accesses to ceph_connection_v1_info (bsc#1250388).\n- CVE-2025-39890: wifi: ath12k: fix memory leak in ath12k_service_ready_ext_event (bsc#1250334).\n- CVE-2025-39977: futex: Prevent use-after-free during requeue-PI (bsc#1252046).\n- CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).\n- CVE-2025-40024: vhost: Take a reference on the task in struct vhost_task (bsc#1252686).\n- CVE-2025-40033: remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable() (bsc#1252824).\n- CVE-2025-40042: tracing: Fix race condition in kprobe initialization causing NULL pointer dereference (bsc#1252861).\n- CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).\n- CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).\n- CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).\n- CVE-2025-40123: bpf: Enforce expected_attach_type for tailcall compatibility (bsc#1253365).\n- CVE-2025-40134: dm: fix NULL pointer dereference in __dm_suspend() (bsc#1253386).\n- CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).\n- CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).\n- CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).\n- CVE-2025-40160: xen/events: Cleanup find_virq() return codes (bsc#1253400).\n- CVE-2025-40167: ext4: detect invalid INLINE_DATA + EXTENTS flag combination (bsc#1253458).\n- CVE-2025-40170: net: use dst_dev_rcu() in sk_setup_caps() (bsc#1253413).\n- CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).\n- CVE-2025-40179: ext4: verify orphan file size is not too big (bsc#1253442).\n- CVE-2025-40187: net/sctp: fix a null dereference in sctp_disposition sctp_sf_do_5_1D_ce() (bsc#1253647).\n- CVE-2025-40190: ext4: guard against EA inode refcount underflow in xattr update (bsc#1253623).\n- CVE-2025-40215: kABI: xfrm: delete x-\u003etunnel as we delete x (bsc#1254959).\n- CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).\n- CVE-2025-40231: vsock: fix lock inversion in vsock_assign_transport() (bsc#1254815).\n- CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).\n- CVE-2025-40238: net/mlx5: Fix IPsec cleanup over MPV device (bsc#1254871).\n- CVE-2025-40240: sctp: avoid NULL dereference when chunk data buffer is missing (bsc#1254869).\n- CVE-2025-40242: gfs2: Fix unlikely race in gdlm_put_lock (bsc#1255075).\n- CVE-2025-40248: vsock: Ignore signal/timeout on connect() if already established (bsc#1254864).\n- CVE-2025-40250: net/mlx5: Clean up only new IRQ glue on request_irq() failure (bsc#1254854).\n- CVE-2025-40251: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (bsc#1254856).\n- CVE-2025-40252: net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end() (bsc#1254849).\n- CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields (bsc#1254852).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40258: mptcp: fix race condition in mptcp_schedule_work() (bsc#1254843).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).\n- CVE-2025-40268: cifs: client: fix memory leak in smb3_fs_context_parse_param (bsc#1255082).\n- CVE-2025-40271: fs/proc: fix uaf in proc_readdir_de() (bsc#1255297).\n- CVE-2025-40274: KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying (bsc#1254830).\n- CVE-2025-40278: net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak (bsc#1254825).\n- CVE-2025-40279: net: sched: act_connmark: initialize struct tc_ife to fix kernel leak (bsc#1254846).\n- CVE-2025-40280: tipc: Fix use-after-free in tipc_mon_reinit_self() (bsc#1254847).\n- CVE-2025-40287: exfat: fix improper check of dentry.stream.valid_size (bsc#1255030).\n- CVE-2025-40289: drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM (bsc#1255042).\n- CVE-2025-40292: virtio-net: fix received length check in big packets (bsc#1255175).\n- CVE-2025-40293: iommufd: Don't overflow during division for dirty tracking (bsc#1255179).\n- CVE-2025-40297: net: bridge: fix use-after-free due to MST port state bypass (bsc#1255187).\n- CVE-2025-40307: exfat: validate cluster allocation bits of the allocation bitmap (bsc#1255039).\n- CVE-2025-40319: bpf: Sync pending IRQ work before freeing ring buffer (bsc#1254794).\n- CVE-2025-40328: smb: client: fix potential UAF in smb2_close_cached_fid() (bsc#1254624).\n- CVE-2025-40331: sctp: Prevent TOCTOU out-of-bounds write (bsc#1254615).\n- CVE-2025-40337: net: stmmac: Correctly handle Rx checksum offload errors (bsc#1255081).\n- CVE-2025-40338: ASoC: Intel: avs: Do not share the name pointer between components (bsc#1255273).\n- CVE-2025-40339: drm/amdgpu: fix nullptr err of vm_handle_moved (bsc#1255428).\n- CVE-2025-40346: arch_topology: Fix incorrect error check in topology_parse_cpu_capacity() (bsc#1255318).\n- CVE-2025-40350: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ (bsc#1255260).\n- CVE-2025-40355: sysfs: check visibility before changing group attribute ownership (bsc#1255261).\n- CVE-2025-40360: drm/sysfb: Do not dereference NULL pointer in plane reset (bsc#1255095).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68171: x86/fpu: Ensure XFD state on signal delivery (bsc#1255255).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68190: drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked() (bsc#1255131).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68201: drm/amdgpu: remove two invalid BUG_ON()s (bsc#1255136).\n- CVE-2025-68204: pmdomain: arm: scmi: Fix genpd leak on provider registration failure (bsc#1255224).\n- CVE-2025-68206: netfilter: nft_ct: add seqadj extension for natted connections (bsc#1255142).\n- CVE-2025-68208: bpf: account for current allocated stack depth in widen_imprecise_scalars() (bsc#1255227).\n- CVE-2025-68209: mlx5: Fix default values in create CQ (bsc#1255230).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68230: drm/amdgpu: fix gpu page fault after hibernation on PF passthrough (bsc#1255134).\n- CVE-2025-68239: binfmt_misc: restore write access before closing files opened by open_exec() (bsc#1255272).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68255: staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing (bsc#1255395).\n- CVE-2025-68259: KVM: SVM: Don't skip unrelated instruction if INT3/INTO is replaced (bsc#1255199).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68264: ext4: refresh inline data size before write operations (bsc#1255380).\n- CVE-2025-68284: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() (bsc#1255377).\n- CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68301: net: atlantic: fix fragment overflow handling in RX path (bsc#1255120).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68327: usb: renesas_usbhs: Fix synchronous external abort on unbind (bsc#1255488).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68340: team: Move team device type change at the end of team_port_add (bsc#1255507).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68363: bpf: Check skb-\u003etransport_header is set in bpf_skb_check_mtu (bsc#1255552).\n- CVE-2025-68365: fs/ntfs3: Initialize allocated memory before use (bsc#1255548).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68378: bpf: Refactor stack map trace depth calculation into helper function (bsc#1255614).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68727: ntfs3: Fix uninit buffer allocated by __getname() (bsc#1255568).\n- CVE-2025-68728: ntfs3: fix uninit memory after failed mi_read in mi_format_new (bsc#1255539).\n- CVE-2025-68733: smack: fix bug: unprivileged task can create labels (bsc#1255615).\n- CVE-2025-68742: bpf: Improve program stats run-time calculation (bsc#1255707).\n- CVE-2025-68744: bpf: Free special fields when update [lru_,]percpu_hash maps (bsc#1255709).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: nfsd: set security label during create operations (bsc#1256770).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" (bsc#1256760).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- Disable CONFIG_CPU5_WDT The cpu5wdt driver doesn't implement a\n proper watchdog interface and has many code issues. It only handles\n obscure and obsolete hardware. Stop building and supporting this driver\n (jsc#PED-14062).\n- Update config files (jsc#PED-12554 jsc#PED-6996\n bsc#1243677 ltc#213602 bsc#1243678 ltc#213596)\n CONFIG_IMA_KEYRINGS_PERMIT_SIGNED_BY_BUILTIN_OR_SECONDARY=y\n CONFIG_INTEGRITY_CA_MACHINE_KEYRING_MAX=y\n- Update config files: disable CONFIG_DEVPORT for arm64 (bsc#1256792)\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- cifs: Fix copy offload to flush destination region (bsc#1252511).\n- cifs: Fix flushing, invalidation and file size with copy_file_range() (bsc#1252511).\n- cifs: Fix uncached read into ITER_KVEC iterator (bsc#1245449).\n- cifs: make cifs_chan_update_iface() a void function (git-fixes).\n- cifs: update dstaddr whenever channel iface is updated (git-fixes).\n- cpuidle: menu: Use residency threshold in polling state override decisions (bsc#1255026).\n- dm: fix queue start/stop imbalance under suspend/load/resume races (bsc#1253386)\n- drm/amdgpu: update mappings not managed by KFD (bsc#1255428)\n- ext4: use optimized mballoc scanning regardless of inode format (bsc#1254378).\n- ext4: wait for ongoing I/O to complete before freeing blocks (bsc#1256366).\n- fs: dlm: allow to F_SETLKW getting interrupted (bsc#1255025).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- media: atomisp: Prefix firmware paths with \"intel/ipu/\" (bsc#1252973).\n- media: atomisp: Remove firmware_name module parameter (bsc#1252973).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1254447 bsc#1253087).\n- net: hv_netvsc: reject RSS hash key programming without RX indirection table (bsc#1257473).\n- net: tcp: allow zero-window ACK update the window (bsc#1254767).\n- net: usb: pegasus: fix memory leak in update_eth_regs_async() (git-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event\n handling (bsc#1253262 ltc#216029).\n- powerpc/kexec: Enable SMT before waking offline CPUs (bsc#1214285\n bsc#1205462 ltc#200161 ltc#200588 git-fixes bsc#1253739 ltc#211493\n bsc#1254244 ltc#216496).\n- sched: Increase sched_tick_remote timeout (bsc#1254510).\n- scsi: lpfc: Add capability to register Platform Name ID to fabric (bsc#1254119).\n- scsi: lpfc: Allow support for BB credit recovery in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Ensure unregistration of rpis for received PLOGIs (bsc#1254119).\n- scsi: lpfc: Fix leaked ndlp krefs when in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI (bsc#1254119).\n- scsi: lpfc: Modify kref handling for Fabric Controller ndlps (bsc#1254119).\n- scsi: lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb() (bsc#1254119).\n- scsi: lpfc: Revise discovery related function headers and comments (bsc#1254119).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256861).\n- scsi: lpfc: Update lpfc version to 14.4.0.12 (bsc#1254119).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256861).\n- scsi: lpfc: Update various NPIV diagnostic log messaging (bsc#1254119).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256863).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256863).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256863).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256863).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256863).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256863).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256863).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256863).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256863).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256863).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256863).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256863).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748,bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- soc/tegra: fuse: speedo-tegra210: Update speedo IDs (git-fixes).\n- spi: tegra210-quad: Check hardware status on timeout (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (bsc#1253155)\n- spi: tegra210-quad: Refactor error handling into helper functions (bsc#1253155)\n- spi: tegra210-quad: Update dummy sequence configuration (git-fixes)\n- supported.conf: Mark lan 743x supported (jsc#PED-14571)\n- tracing: Fix access to trace_event_file (bsc#1254373).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- x86/microcode/AMD: Add TSA microcode SHAs (bsc#1256528).\n- x86/microcode/AMD: Add Zen5 model 0x44, stepping 0x1 minrev (bsc#1256528).\n- x86/microcode/AMD: Add more known models to entry sign checking (bsc#1256528).\n- x86/microcode/AMD: Add some forgotten models to the SHA check (bsc#1256528).\n- x86/microcode/AMD: Clean the cache if update did not load microcode (bsc#1256528).\n- x86/microcode/AMD: Extend the SHA check to Zen5, block loading of any\n unreleased standalone Zen5 microcode patches (bsc#1256528).\n- x86/microcode/AMD: Fix Entrysign revision check for Zen5/Strix Halo (bsc#1256528).\n- x86/microcode/AMD: Fix __apply_microcode_amd()'s return value (bsc#1256528).\n- x86/microcode/AMD: Limit Entrysign signature checking to known generations (bsc#1256528).\n- x86/microcode/AMD: Load only SHA256-checksummed patches (bsc#1256528).\n- x86/microcode/AMD: Select which microcode patch to load (bsc#1256528).\n- x86/microcode/AMD: Use sha256() instead of init/update/final (bsc#1256528).\n- x86/microcode: Fix Entrysign revision check for Zen1/Naples (bsc#1256528).\n","status":"published","published":"2026-02-24T09:10:01Z","modified":"2026-03-23T04:53:00.283571Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20555-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 and SL MIxro 6.2 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-40147: blk-throttle: fix access race during throttle policy activation (bsc#1253344).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68211: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item (bsc#1255319).\n- CVE-2025-68218: nvme-multipath: fix lockdep WARN due to partition scan work (bsc#1255245).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68341: veth: reduce XDP no_direct return section to fix race (bsc#1255506).\n- CVE-2025-68348: block: fix memory leak in __blkdev_issue_zero_pages (bsc#1255694).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68356: gfs2: Prevent recursive memory reclaim (bsc#1255593).\n- CVE-2025-68359: btrfs: fix double free of qgroup record after failure to add delayed ref head (bsc#1255542).\n- CVE-2025-68360: wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks (bsc#1255536).\n- CVE-2025-68361: erofs: limit the level of fs stacking for file-backed mounts (bsc#1255526).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68368: md: init bioset in mddev_init (bsc#1255527).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68374: md: fix rcu protection in md_wakeup_thread (bsc#1255530).\n- CVE-2025-68376: coresight: ETR: Fix ETR buffer use-after-free issue (bsc#1255529).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68735: drm/panthor: Prevent potential UAF in group creation (bsc#1255811).\n- CVE-2025-68741: scsi: qla2xxx: Fix improper freeing of purex item (bsc#1255703).\n- CVE-2025-68743: mshv: Fix create memory region overlap check (bsc#1255708).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68784: xfs: fix a UAF problem in xattr repair (bsc#1256793).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68792: tpm2-sessions: Fix out of range indexing in name_size (bsc#1256656).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68799: caif: fix integer underflow in cffrml_receive() (bsc#1256643).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: NFSD: NFSv4 file creation neglects setting ACL (bsc#1256770).\n- CVE-2025-68811: svcrdma: use rc_pageoff for memcpy byte offset (bsc#1256677).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-68821: fuse: fix readahead reclaim deadlock (bsc#1256667).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71080: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT (bsc#1256608).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71126: mptcp: avoid deadlock on fallback while reinjecting (bsc#1256755).\n- CVE-2025-71132: smc91x: fix broken irq-context in PREEMPT_RT (bsc#1256737).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" (bsc#1256760).\n- CVE-2025-71148: net/handshake: restore destructor on submit failure (bsc#1257159).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71156: gve: defer interrupt enabling until NAPI registration (bsc#1257167).\n- CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() (bsc#1257168).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22981: idpf: detach and close netdevs while handling a reset (bsc#1257225).\n- CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag (bsc#1257179).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22986: gpiolib: fix race condition for gdev-\u003esrcu (bsc#1257276).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- Add bugnumber to an existing hv_netvsc change (bsc#1257473).\n- Fix locking issue introduced by a CVE backport (bsc#1256975 bsc#1254977).\n- Update config files: disable CONFIG_DEVPORT for arm64 (bsc#1256792)\n- arm64: Update config files. Disable DEVPORT (bsc#1256792)\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- btrfs: pass fs_info to btrfs_delete_ref_head() (git-fixes).\n- btrfs: scrub: always update btrfs_scrub_progress::last_physical (git-fixes).\n- bus: fsl-mc: Constify fsl_mc_device_match() (jsc#PED-10906 git-fixes).\n- drm/imagination: Wait for FW trace update command completion (git-fixes).\n- drm/msm/a6xx: fix bogus hwcg register updates (git-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- libbpf: Fix -Wdiscarded-qualifiers under C23 (bsc#1257309).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1254447 bsc#1253087).\n- net: mana: Fix incorrect speed reported by debugfs (bsc#1255232).\n- net: mana: Support HW link state events (bsc#1253049).\n- nfsd: adjust WARN_ON_ONCE in revoke_delegation (bsc#1257015).\n- nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl() (git-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- sched/fair: Disable scheduler feature NEXT_BUDDY (bsc#1255459).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256864).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256864).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests: net: fib-onlink-tests: Convert to use namespaces by default (bsc#1255346).\n- slimbus: core: Constify slim_eaddr_equal() (jsc#PED-10906 git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748,bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- tsm-mr: Add TVM Measurement Register support (bsc#1257504).\n- tsm-mr: Add tsm-mr sample code (bsc#1257504).\n- virt: tdx-guest: Expose TDX MRs as sysfs attributes (bsc#1257504).\n- virt: tdx-guest: Refactor and streamline TDREPORT generation (bsc#1257504).\n- virt: tdx-guest: Transition to scoped_cond_guard for mutex operations (bsc#1257504).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- x86/tdx: Add tdx_mcall_extend_rtmr() interface (bsc#1257504).\n- x86/tdx: tdx_mcall_get_report0: Return -EBUSY on TDCALL_OPERAND_BUSY error (bsc#1257504).\n","status":"published","published":"2026-02-27T11:51:02Z","modified":"2026-03-23T04:53:03.624925Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20570-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 and SL MIxro 6.2 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-40147: blk-throttle: fix access race during throttle policy activation (bsc#1253344).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68211: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item (bsc#1255319).\n- CVE-2025-68218: nvme-multipath: fix lockdep WARN due to partition scan work (bsc#1255245).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68341: veth: reduce XDP no_direct return section to fix race (bsc#1255506).\n- CVE-2025-68348: block: fix memory leak in __blkdev_issue_zero_pages (bsc#1255694).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68356: gfs2: Prevent recursive memory reclaim (bsc#1255593).\n- CVE-2025-68359: btrfs: fix double free of qgroup record after failure to add delayed ref head (bsc#1255542).\n- CVE-2025-68360: wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks (bsc#1255536).\n- CVE-2025-68361: erofs: limit the level of fs stacking for file-backed mounts (bsc#1255526).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68368: md: init bioset in mddev_init (bsc#1255527).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68374: md: fix rcu protection in md_wakeup_thread (bsc#1255530).\n- CVE-2025-68376: coresight: ETR: Fix ETR buffer use-after-free issue (bsc#1255529).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68735: drm/panthor: Prevent potential UAF in group creation (bsc#1255811).\n- CVE-2025-68741: scsi: qla2xxx: Fix improper freeing of purex item (bsc#1255703).\n- CVE-2025-68743: mshv: Fix create memory region overlap check (bsc#1255708).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68784: xfs: fix a UAF problem in xattr repair (bsc#1256793).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68792: tpm2-sessions: Fix out of range indexing in name_size (bsc#1256656).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68799: caif: fix integer underflow in cffrml_receive() (bsc#1256643).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: NFSD: NFSv4 file creation neglects setting ACL (bsc#1256770).\n- CVE-2025-68811: svcrdma: use rc_pageoff for memcpy byte offset (bsc#1256677).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-68821: fuse: fix readahead reclaim deadlock (bsc#1256667).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71080: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT (bsc#1256608).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71126: mptcp: avoid deadlock on fallback while reinjecting (bsc#1256755).\n- CVE-2025-71132: smc91x: fix broken irq-context in PREEMPT_RT (bsc#1256737).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" (bsc#1256760).\n- CVE-2025-71148: net/handshake: restore destructor on submit failure (bsc#1257159).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71156: gve: defer interrupt enabling until NAPI registration (bsc#1257167).\n- CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() (bsc#1257168).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22981: idpf: detach and close netdevs while handling a reset (bsc#1257225).\n- CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag (bsc#1257179).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22986: gpiolib: fix race condition for gdev-\u003esrcu (bsc#1257276).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- Add bugnumber to an existing hv_netvsc change (bsc#1257473).\n- Fix locking issue introduced by a CVE backport (bsc#1256975 bsc#1254977).\n- Update config files: disable CONFIG_DEVPORT for arm64 (bsc#1256792)\n- arm64: Update config files. Disable DEVPORT (bsc#1256792)\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- btrfs: pass fs_info to btrfs_delete_ref_head() (git-fixes).\n- btrfs: scrub: always update btrfs_scrub_progress::last_physical (git-fixes).\n- bus: fsl-mc: Constify fsl_mc_device_match() (jsc#PED-10906 git-fixes).\n- drm/imagination: Wait for FW trace update command completion (git-fixes).\n- drm/msm/a6xx: fix bogus hwcg register updates (git-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- libbpf: Fix -Wdiscarded-qualifiers under C23 (bsc#1257309).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1254447 bsc#1253087).\n- net: mana: Fix incorrect speed reported by debugfs (bsc#1255232).\n- net: mana: Support HW link state events (bsc#1253049).\n- nfsd: adjust WARN_ON_ONCE in revoke_delegation (bsc#1257015).\n- nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl() (git-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- sched/fair: Disable scheduler feature NEXT_BUDDY (bsc#1255459).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256864).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256864).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests: net: fib-onlink-tests: Convert to use namespaces by default (bsc#1255346).\n- slimbus: core: Constify slim_eaddr_equal() (jsc#PED-10906 git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748,bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- tsm-mr: Add TVM Measurement Register support (bsc#1257504).\n- tsm-mr: Add tsm-mr sample code (bsc#1257504).\n- virt: tdx-guest: Expose TDX MRs as sysfs attributes (bsc#1257504).\n- virt: tdx-guest: Refactor and streamline TDREPORT generation (bsc#1257504).\n- virt: tdx-guest: Transition to scoped_cond_guard for mutex operations (bsc#1257504).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- x86/tdx: Add tdx_mcall_extend_rtmr() interface (bsc#1257504).\n- x86/tdx: tdx_mcall_get_report0: Return -EBUSY on TDCALL_OPERAND_BUSY error (bsc#1257504).\n","status":"published","published":"2026-02-27T11:23:36Z","modified":"2026-07-09T18:24:04.405573342Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20599-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 and SL MIxro 6.2 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-40147: blk-throttle: fix access race during throttle policy activation (bsc#1253344).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68211: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item (bsc#1255319).\n- CVE-2025-68218: nvme-multipath: fix lockdep WARN due to partition scan work (bsc#1255245).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68341: veth: reduce XDP no_direct return section to fix race (bsc#1255506).\n- CVE-2025-68348: block: fix memory leak in __blkdev_issue_zero_pages (bsc#1255694).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68356: gfs2: Prevent recursive memory reclaim (bsc#1255593).\n- CVE-2025-68359: btrfs: fix double free of qgroup record after failure to add delayed ref head (bsc#1255542).\n- CVE-2025-68360: wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks (bsc#1255536).\n- CVE-2025-68361: erofs: limit the level of fs stacking for file-backed mounts (bsc#1255526).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68368: md: init bioset in mddev_init (bsc#1255527).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68374: md: fix rcu protection in md_wakeup_thread (bsc#1255530).\n- CVE-2025-68376: coresight: ETR: Fix ETR buffer use-after-free issue (bsc#1255529).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68735: drm/panthor: Prevent potential UAF in group creation (bsc#1255811).\n- CVE-2025-68741: scsi: qla2xxx: Fix improper freeing of purex item (bsc#1255703).\n- CVE-2025-68743: mshv: Fix create memory region overlap check (bsc#1255708).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68784: xfs: fix a UAF problem in xattr repair (bsc#1256793).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68792: tpm2-sessions: Fix out of range indexing in name_size (bsc#1256656).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68799: caif: fix integer underflow in cffrml_receive() (bsc#1256643).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: NFSD: NFSv4 file creation neglects setting ACL (bsc#1256770).\n- CVE-2025-68811: svcrdma: use rc_pageoff for memcpy byte offset (bsc#1256677).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-68821: fuse: fix readahead reclaim deadlock (bsc#1256667).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71080: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT (bsc#1256608).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71126: mptcp: avoid deadlock on fallback while reinjecting (bsc#1256755).\n- CVE-2025-71132: smc91x: fix broken irq-context in PREEMPT_RT (bsc#1256737).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" (bsc#1256760).\n- CVE-2025-71148: net/handshake: restore destructor on submit failure (bsc#1257159).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71156: gve: defer interrupt enabling until NAPI registration (bsc#1257167).\n- CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() (bsc#1257168).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22981: idpf: detach and close netdevs while handling a reset (bsc#1257225).\n- CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag (bsc#1257179).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22986: gpiolib: fix race condition for gdev-\u003esrcu (bsc#1257276).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- Add bugnumber to an existing hv_netvsc change (bsc#1257473).\n- Fix locking issue introduced by a CVE backport (bsc#1256975 bsc#1254977).\n- Update config files: disable CONFIG_DEVPORT for arm64 (bsc#1256792)\n- arm64: Update config files. Disable DEVPORT (bsc#1256792)\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- btrfs: pass fs_info to btrfs_delete_ref_head() (git-fixes).\n- btrfs: scrub: always update btrfs_scrub_progress::last_physical (git-fixes).\n- bus: fsl-mc: Constify fsl_mc_device_match() (jsc#PED-10906 git-fixes).\n- drm/imagination: Wait for FW trace update command completion (git-fixes).\n- drm/msm/a6xx: fix bogus hwcg register updates (git-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- libbpf: Fix -Wdiscarded-qualifiers under C23 (bsc#1257309).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1254447 bsc#1253087).\n- net: mana: Fix incorrect speed reported by debugfs (bsc#1255232).\n- net: mana: Support HW link state events (bsc#1253049).\n- nfsd: adjust WARN_ON_ONCE in revoke_delegation (bsc#1257015).\n- nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl() (git-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- sched/fair: Disable scheduler feature NEXT_BUDDY (bsc#1255459).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256864).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256864).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests: net: fib-onlink-tests: Convert to use namespaces by default (bsc#1255346).\n- slimbus: core: Constify slim_eaddr_equal() (jsc#PED-10906 git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748,bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- tsm-mr: Add TVM Measurement Register support (bsc#1257504).\n- tsm-mr: Add tsm-mr sample code (bsc#1257504).\n- virt: tdx-guest: Expose TDX MRs as sysfs attributes (bsc#1257504).\n- virt: tdx-guest: Refactor and streamline TDREPORT generation (bsc#1257504).\n- virt: tdx-guest: Transition to scoped_cond_guard for mutex operations (bsc#1257504).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- x86/tdx: Add tdx_mcall_extend_rtmr() interface (bsc#1257504).\n- x86/tdx: tdx_mcall_get_report0: Return -EBUSY on TDCALL_OPERAND_BUSY error (bsc#1257504).\n","status":"published","published":"2026-02-27T11:51:02Z","modified":"2026-03-23T04:53:04.246765Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20615-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 and SL MIxro 6.2 kernel was updated to fix various security issues\n\nThe following security issues were fixed:\n\n- CVE-2025-40147: blk-throttle: fix access race during throttle policy activation (bsc#1253344).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68211: ksm: use range-walk function to jump over holes in scan_get_next_rmap_item (bsc#1255319).\n- CVE-2025-68218: nvme-multipath: fix lockdep WARN due to partition scan work (bsc#1255245).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68341: veth: reduce XDP no_direct return section to fix race (bsc#1255506).\n- CVE-2025-68348: block: fix memory leak in __blkdev_issue_zero_pages (bsc#1255694).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68356: gfs2: Prevent recursive memory reclaim (bsc#1255593).\n- CVE-2025-68359: btrfs: fix double free of qgroup record after failure to add delayed ref head (bsc#1255542).\n- CVE-2025-68360: wifi: mt76: wed: use proper wed reference in mt76 wed driver callabacks (bsc#1255536).\n- CVE-2025-68361: erofs: limit the level of fs stacking for file-backed mounts (bsc#1255526).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68368: md: init bioset in mddev_init (bsc#1255527).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68374: md: fix rcu protection in md_wakeup_thread (bsc#1255530).\n- CVE-2025-68376: coresight: ETR: Fix ETR buffer use-after-free issue (bsc#1255529).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68735: drm/panthor: Prevent potential UAF in group creation (bsc#1255811).\n- CVE-2025-68741: scsi: qla2xxx: Fix improper freeing of purex item (bsc#1255703).\n- CVE-2025-68743: mshv: Fix create memory region overlap check (bsc#1255708).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68784: xfs: fix a UAF problem in xattr repair (bsc#1256793).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68792: tpm2-sessions: Fix out of range indexing in name_size (bsc#1256656).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68799: caif: fix integer underflow in cffrml_receive() (bsc#1256643).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: NFSD: NFSv4 file creation neglects setting ACL (bsc#1256770).\n- CVE-2025-68811: svcrdma: use rc_pageoff for memcpy byte offset (bsc#1256677).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-68821: fuse: fix readahead reclaim deadlock (bsc#1256667).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71080: ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT (bsc#1256608).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71098: ip6_gre: make ip6gre_header() robust (bsc#1256591).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71126: mptcp: avoid deadlock on fallback while reinjecting (bsc#1256755).\n- CVE-2025-71132: smc91x: fix broken irq-context in PREEMPT_RT (bsc#1256737).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" (bsc#1256760).\n- CVE-2025-71148: net/handshake: restore destructor on submit failure (bsc#1257159).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71156: gve: defer interrupt enabling until NAPI registration (bsc#1257167).\n- CVE-2025-71157: RDMA/core: always drop device refcount in ib_del_sub_device_and_put() (bsc#1257168).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22981: idpf: detach and close netdevs while handling a reset (bsc#1257225).\n- CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag (bsc#1257179).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22986: gpiolib: fix race condition for gdev-\u003esrcu (bsc#1257276).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22993: idpf: Fix RSS LUT NULL pointer crash on early ethtool operations (bsc#1257180).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: fix possible UAF in macvlan_forward_source() (bsc#1257232).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- Add bugnumber to an existing hv_netvsc change (bsc#1257473).\n- Fix locking issue introduced by a CVE backport (bsc#1256975 bsc#1254977).\n- Update config files: disable CONFIG_DEVPORT for arm64 (bsc#1256792)\n- arm64: Update config files. Disable DEVPORT (bsc#1256792)\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- btrfs: pass fs_info to btrfs_delete_ref_head() (git-fixes).\n- btrfs: scrub: always update btrfs_scrub_progress::last_physical (git-fixes).\n- bus: fsl-mc: Constify fsl_mc_device_match() (jsc#PED-10906 git-fixes).\n- drm/imagination: Wait for FW trace update command completion (git-fixes).\n- drm/msm/a6xx: fix bogus hwcg register updates (git-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- libbpf: Fix -Wdiscarded-qualifiers under C23 (bsc#1257309).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1254447 bsc#1253087).\n- net: mana: Fix incorrect speed reported by debugfs (bsc#1255232).\n- net: mana: Support HW link state events (bsc#1253049).\n- nfsd: adjust WARN_ON_ONCE in revoke_delegation (bsc#1257015).\n- nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl() (git-fixes).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- sched/fair: Disable scheduler feature NEXT_BUDDY (bsc#1255459).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256864).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256864).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256865 bsc#1256867 jsc#PED-14156).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests: net: fib-onlink-tests: Convert to use namespaces by default (bsc#1255346).\n- slimbus: core: Constify slim_eaddr_equal() (jsc#PED-10906 git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748,bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- tsm-mr: Add TVM Measurement Register support (bsc#1257504).\n- tsm-mr: Add tsm-mr sample code (bsc#1257504).\n- virt: tdx-guest: Expose TDX MRs as sysfs attributes (bsc#1257504).\n- virt: tdx-guest: Refactor and streamline TDREPORT generation (bsc#1257504).\n- virt: tdx-guest: Transition to scoped_cond_guard for mutex operations (bsc#1257504).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- x86/tdx: Add tdx_mcall_extend_rtmr() interface (bsc#1257504).\n- x86/tdx: tdx_mcall_get_report0: Return -EBUSY on TDCALL_OPERAND_BUSY error (bsc#1257504).\n","status":"published","published":"2026-02-27T11:32:45Z","modified":"2026-03-23T04:53:05.307414Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20845-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-53817: crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() (bsc#1254992).\n- CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue (bsc#1243055).\n- CVE-2025-38321: smb: Log an error when close_all_cached_dirs fails (bsc#1246328).\n- CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).\n- CVE-2025-39748: bpf: Forget ranges when refining tnum after JSET (bsc#1249587).\n- CVE-2025-39880: libceph: fix invalid accesses to ceph_connection_v1_info (bsc#1250388).\n- CVE-2025-39890: wifi: ath12k: fix memory leak in ath12k_service_ready_ext_event (bsc#1250334).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-39977: futex: Prevent use-after-free during requeue-PI (bsc#1252046).\n- CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).\n- CVE-2025-40024: vhost: Take a reference on the task in struct vhost_task (bsc#1252686).\n- CVE-2025-40033: remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable() (bsc#1252824).\n- CVE-2025-40042: tracing: Fix race condition in kprobe initialization causing NULL pointer dereference (bsc#1252861).\n- CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).\n- CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40123: bpf: Enforce expected_attach_type for tailcall compatibility (bsc#1253365).\n- CVE-2025-40134: dm: fix NULL pointer dereference in __dm_suspend() (bsc#1253386).\n- CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).\n- CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).\n- CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).\n- CVE-2025-40160: xen/events: Cleanup find_virq() return codes (bsc#1253400).\n- CVE-2025-40167: ext4: detect invalid INLINE_DATA + EXTENTS flag combination (bsc#1253458).\n- CVE-2025-40170: net: use dst_dev_rcu() in sk_setup_caps() (bsc#1253413).\n- CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).\n- CVE-2025-40179: ext4: verify orphan file size is not too big (bsc#1253442).\n- CVE-2025-40187: net/sctp: fix a null dereference in sctp_disposition sctp_sf_do_5_1D_ce() (bsc#1253647).\n- CVE-2025-40190: ext4: guard against EA inode refcount underflow in xattr update (bsc#1253623).\n- CVE-2025-40192: Revert \"ipmi: fix msg stack when IPMI is disconnected\" (bsc#1253622).\n- CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).\n- CVE-2025-40231: vsock: fix lock inversion in vsock_assign_transport() (bsc#1254815).\n- CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).\n- CVE-2025-40238: net/mlx5: Fix IPsec cleanup over MPV device (bsc#1254871).\n- CVE-2025-40240: sctp: avoid NULL dereference when chunk data buffer is missing (bsc#1254869).\n- CVE-2025-40242: gfs2: Fix unlikely race in gdlm_put_lock (bsc#1255075).\n- CVE-2025-40248: vsock: Ignore signal/timeout on connect() if already established (bsc#1254864).\n- CVE-2025-40250: net/mlx5: Clean up only new IRQ glue on request_irq() failure (bsc#1254854).\n- CVE-2025-40251: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (bsc#1254856).\n- CVE-2025-40252: net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end() (bsc#1254849).\n- CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields (bsc#1254852).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40258: mptcp: fix race condition in mptcp_schedule_work() (bsc#1254843).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).\n- CVE-2025-40268: cifs: client: fix memory leak in smb3_fs_context_parse_param (bsc#1255082).\n- CVE-2025-40271: fs/proc: fix uaf in proc_readdir_de() (bsc#1255297).\n- CVE-2025-40274: KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying (bsc#1254830).\n- CVE-2025-40278: net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak (bsc#1254825).\n- CVE-2025-40279: net: sched: act_connmark: initialize struct tc_ife to fix kernel leak (bsc#1254846).\n- CVE-2025-40280: tipc: Fix use-after-free in tipc_mon_reinit_self() (bsc#1254847).\n- CVE-2025-40289: drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM (bsc#1255042).\n- CVE-2025-40292: virtio-net: fix received length check in big packets (bsc#1255175).\n- CVE-2025-40293: iommufd: Don't overflow during division for dirty tracking (bsc#1255179).\n- CVE-2025-40297: net: bridge: fix use-after-free due to MST port state bypass (bsc#1255187).\n- CVE-2025-40307: exfat: validate cluster allocation bits of the allocation bitmap (bsc#1255039).\n- CVE-2025-40319: bpf: Sync pending IRQ work before freeing ring buffer (bsc#1254794).\n- CVE-2025-40328: smb: client: fix potential UAF in smb2_close_cached_fid() (bsc#1254624).\n- CVE-2025-40331: sctp: Prevent TOCTOU out-of-bounds write (bsc#1254615).\n- CVE-2025-40338: ASoC: Intel: avs: Do not share the name pointer between components (bsc#1255273).\n- CVE-2025-40339: drm/amdgpu: fix nullptr err of vm_handle_moved (bsc#1255428).\n- CVE-2025-40346: arch_topology: Fix incorrect error check in topology_parse_cpu_capacity() (bsc#1255318).\n- CVE-2025-40350: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ (bsc#1255260).\n- CVE-2025-40355: sysfs: check visibility before changing group attribute ownership (bsc#1255261).\n- CVE-2025-40360: drm/sysfb: Do not dereference NULL pointer in plane reset (bsc#1255095).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68171: x86/fpu: Ensure XFD state on signal delivery (bsc#1255255).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68190: drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked() (bsc#1255131).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68201: drm/amdgpu: remove two invalid BUG_ON()s (bsc#1255136).\n- CVE-2025-68204: pmdomain: arm: scmi: Fix genpd leak on provider registration failure (bsc#1255224).\n- CVE-2025-68206: netfilter: nft_ct: add seqadj extension for natted connections (bsc#1255142).\n- CVE-2025-68208: bpf: account for current allocated stack depth in widen_imprecise_scalars() (bsc#1255227).\n- CVE-2025-68209: mlx5: Fix default values in create CQ (bsc#1255230).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68230: drm/amdgpu: fix gpu page fault after hibernation on PF passthrough (bsc#1255134).\n- CVE-2025-68239: binfmt_misc: restore write access before closing files opened by open_exec() (bsc#1255272).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68255: staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing (bsc#1255395).\n- CVE-2025-68259: KVM: SVM: Don't skip unrelated instruction if INT3/INTO is replaced (bsc#1255199).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68264: ext4: refresh inline data size before write operations (bsc#1255380).\n- CVE-2025-68283: libceph: replace BUG_ON with bounds check for map-\u003emax_osd (bsc#1255379).\n- CVE-2025-68284: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() (bsc#1255377).\n- CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68301: net: atlantic: fix fragment overflow handling in RX path (bsc#1255120).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68327: usb: renesas_usbhs: Fix synchronous external abort on unbind (bsc#1255488).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68340: team: Move team device type change at the end of team_port_add (bsc#1255507).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68363: bpf: Check skb-\u003etransport_header is set in bpf_skb_check_mtu (bsc#1255552).\n- CVE-2025-68365: fs/ntfs3: Initialize allocated memory before use (bsc#1255548).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68374: md: fix rcu protection in md_wakeup_thread (bsc#1255530).\n- CVE-2025-68378: bpf: Refactor stack map trace depth calculation into helper function (bsc#1255614).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68727: ntfs3: Fix uninit buffer allocated by __getname() (bsc#1255568).\n- CVE-2025-68728: ntfs3: fix uninit memory after failed mi_read in mi_format_new (bsc#1255539).\n- CVE-2025-68733: smack: fix bug: unprivileged task can create labels (bsc#1255615).\n- CVE-2025-68736: landlock: Fix handling of disconnected directories (bsc#1255698).\n- CVE-2025-68742: bpf: Improve program stats run-time calculation (bsc#1255707).\n- CVE-2025-68744: bpf: Free special fields when update [lru_,]percpu_hash maps (bsc#1255709).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68778: btrfs: don't log conflicting inode if it's a dir moved in the current transaction (bsc#1256683).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: nfsd: set security label during create operations (bsc#1256770).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71113: crypto: af_alg - zero initialize memory allocated via sock_kmalloc (bsc#1256716).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71126: mptcp: reset fallback status gracefully at disconnect() time (bsc#1256755).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" (bsc#1256760).\n- CVE-2025-71148: net/handshake: restore destructor on submit failure (bsc#1257159).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71184: btrfs: fix NULL dereference on root when tracing inode eviction (bsc#1257635).\n- CVE-2025-71194: btrfs: fix deadlock in wait_current_trans() due to ignored transaction type (bsc#1257687).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag (bsc#1257179).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: Use 'hash' iterators to simplify code (bsc#1257232).\n- CVE-2026-23003: geneve: Fix incorrect inner network header offset when innerprotoinherit is set (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23053: NFS: Fix a deadlock involving nfs_release_folio() (bsc#1257718).\n- CVE-2026-23057: vsock/virtio: Coalesce only linear skb (bsc#1257740).\n- CVE-2026-23060: crypto: authencesn - reject too-short AAD (assoclen\u003c8) to match ESP/ESN spec (bsc#1257735).\n- CVE-2026-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: fou: Don't allow 0 for FOU_ATTR_IPPROTO (bsc#1257745).\n- CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list (bsc#1257830).\n- CVE-2026-23085: irqchip/gic-v3-its: Avoid truncating memory addresses (bsc#1257758).\n- CVE-2026-23086: vsock/virtio: cap TX credit to local buffer size (bsc#1257757).\n- CVE-2026-23089: ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (bsc#1257790).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23102: arm64/fpsimd: signal: Mandate SVE payload for streaming-mode state (bsc#1257772).\n- CVE-2026-23104: ice: fix devlink reload call trace (bsc#1257763).\n- CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag (bsc#1257775).\n- CVE-2026-23107: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA (bsc#1257762).\n- CVE-2026-23110: scsi: core: Wake up the error handler when final completions race against each other (bsc#1257761).\n- CVE-2026-23111: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() (bsc#1258181).\n- CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1258184).\n- CVE-2026-23113: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (bsc#1258278).\n- CVE-2026-23116: pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu (bsc#1258277).\n- CVE-2026-23119: bonding: provide a net pointer to __skb_flow_dissect() (bsc#1258273).\n- CVE-2026-23139: netfilter: nf_conncount: update last_gc only when GC has been performed (bsc#1258304).\n- CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent() (bsc#1258377).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23171: net: bonding: update the slave array for broadcast mode (bsc#1258349).\n- CVE-2026-23173: net/mlx5e: TC, delete flows only for existing peers (bsc#1258520).\n- CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() (bsc#1258394).\n- CVE-2026-23191: ALSA: aloop: Fix racy access at PCM trigger (bsc#1258395).\n- CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd (bsc#1258321).\n- CVE-2026-23208: ALSA: usb-audio: Prevent excessive number of frames (bsc#1258468).\n- CVE-2026-23209: macvlan: fix error recovery in macvlan_common_newlink() (bsc#1258518).\n- CVE-2026-23213: drm/amd/pm: Disable MMIO access during SMU Mode 1 reset (bsc#1258465).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Fix missing PCC check for guaranteed_perf (git-fixes).\n- ACPI: CPPC: Fix remaining for_each_possible_cpu() to use online CPUs (git-fixes).\n- ACPI: PCC: Fix race condition by removing static qualifier (git-fixes).\n- ACPI: PM: Add unused power resource quirk for THUNDEROBOT ZERO (git-fixes).\n- ACPI: processor: Fix NULL-pointer dereference in acpi_processor_errata_piix4() (stable-fixes).\n- ACPI: processor_core: fix map_x2apic_id for amd-pstate on am4 (git-fixes).\n- ACPI: property: Fix fwnode refcount leak in acpi_fwnode_graph_parse_endpoint() (git-fixes).\n- ACPI: property: Use ACPI functions in acpi_graph_get_next_endpoint() only (stable-fixes).\n- ACPICA: Abort AML bytecode execution when executing AML_FATAL_OP (stable-fixes).\n- ACPICA: Avoid walking the Namespace if start_node is NULL (stable-fixes).\n- ACPICA: Fix NULL pointer dereference in acpi_ev_address_space_dispatch() (git-fixes).\n- ALSA: ac97: fix a double free in snd_ac97_controller_register() (git-fixes).\n- ALSA: ctxfi: Fix potential OOB access in audio mixer handling (stable-fixes).\n- ALSA: dice: fix buffer overflow in detect_stream_formats() (git-fixes).\n- ALSA: firewire-motu: add bounds check in put_user loop for DSP events (git-fixes).\n- ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events (git-fixes).\n- ALSA: hda/conexant: Add headset mic fix for MECHREVO Wujie 15X Pro (stable-fixes).\n- ALSA: hda/realtek - fixed speaker no sound (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Inspur S14-G1 (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic for TongFang X6AR55xU (stable-fixes).\n- ALSA: hda/realtek: Really fix headset mic for TongFang X6AR55xU (git-fixes).\n- ALSA: hda/realtek: add HP Laptop 15s-eq1xxx mute LED quirk (stable-fixes).\n- ALSA: hda/realtek: fix right sounds and mute/micmute LEDs for HP machine (stable-fixes).\n- ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_hda_read_acpi() (git-fixes).\n- ALSA: pcmcia: Fix resource leak in snd_pdacf_probe error path (git-fixes).\n- ALSA: scarlett2: Fix buffer overflow in config retrieval (git-fixes).\n- ALSA: uapi: Fix typo in asound.h comment (git-fixes).\n- ALSA: usb-audio: Add DSD quirk for LEAK Stereo 230 (stable-fixes).\n- ALSA: usb-audio: Add iface reset and delay quirk for AB13X USB Audio (stable-fixes).\n- ALSA: usb-audio: Add native DSD quirks for PureAudio DAC series (stable-fixes).\n- ALSA: usb-audio: Add sanity check for OOB writes at silencing (stable-fixes).\n- ALSA: usb-audio: Avoid implicit feedback mode on DIYINHK USB Audio 2.0 (stable-fixes).\n- ALSA: usb-audio: Cap the packet size pre-calculations (git-fixes).\n- ALSA: usb-audio: Check max frame size for implicit feedback mode, too (stable-fixes).\n- ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (git-fixes).\n- ALSA: usb-audio: Remove VALIDATE_RATES quirk for Focusrite devices (git-fixes).\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: Use correct version for UAC3 header validation (git-fixes).\n- ALSA: usb-audio: Use inclusive terms (git-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ALSA: usb-mixer: us16x08: validate meter packet indices (git-fixes).\n- ALSA: usb: Increase volume range that triggers a warning (git-fixes).\n- ALSA: vxpocket: Fix resource leak in vxpocket_probe error path (git-fixes).\n- APEI/GHES: ensure that won't go past CPER allocated record (stable-fixes).\n- ASoC: Intel: catpt: Fix error path in hw_params() (git-fixes).\n- ASoC: Intel: sof_es8336: Add DMI quirk for Huawei BOD-WXX9 (stable-fixes).\n- ASoC: Intel: sof_es8336: fix headphone GPIO logic inversion (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- ASoC: SOF: ipc4-control: Keep the payload size up to date (git-fixes).\n- ASoC: SOF: ipc4-control: Use the correct size for scontrol-\u003eipc_control_data (git-fixes).\n- ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls (git-fixes).\n- ASoC: ak4458: Disable regulator when error happens (git-fixes).\n- ASoC: ak5558: Disable regulator when error happens (git-fixes).\n- ASoC: amd: drop unused Kconfig symbols (git-fixes).\n- ASoC: amd: fix memory leak in acp3x pdm dma ops (git-fixes).\n- ASoC: amd: yc: Add ASUS ExpertBook PM1503CDA to quirks list (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS Vivobook Pro 15X M6501RR (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer TravelMate P216-41-TCO (stable-fixes).\n- ASoC: amd: yc: Add quirk for HP 200 G2a 16 (stable-fixes).\n- ASoC: amd: yc: Add quirk for Honor MagicBook X16 2025 (stable-fixes).\n- ASoC: amd: yc: Fix microphone on ASUS M6500RE (stable-fixes).\n- ASoC: bcm: bcm63xx-pcm-whistler: Check return value of of_dma_configure() (git-fixes).\n- ASoC: codecs: max98390: Check return value of devm_gpiod_get_optional() in max98390_i2c_probe() (stable-fixes).\n- ASoC: codecs: wcd938x: fix OF node leaks on probe failure (git-fixes).\n- ASoC: codecs: wsa881x: Drop unused version readout (stable-fixes).\n- ASoC: codecs: wsa881x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa883x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa884x: fix codec initialisation (git-fixes).\n- ASoC: cs35l45: Corrects ASP_TX5 DAPM widget channel (stable-fixes).\n- ASoC: davinci-evm: Fix reference leak in davinci_evm_probe (stable-fixes).\n- ASoC: fsl: imx-card: Do not force slot width to sample width (git-fixes).\n- ASoC: fsl_sai: Add missing registers to cache default (stable-fixes).\n- ASoC: fsl_xcvr: clear the channel status control memory (git-fixes).\n- ASoC: nau8821: Avoid unnecessary blocking in IRQ handler (stable-fixes).\n- ASoC: nau8821: Cancel delayed work on component remove (git-fixes).\n- ASoC: nau8821: Cancel pending work before suspend (git-fixes).\n- ASoC: nau8821: Consistently clear interrupts before unmasking (git-fixes).\n- ASoC: nau8821: Fixup nau8821_enable_jack_detect() (git-fixes).\n- ASoC: pxa: drop unused Kconfig symbol (git-fixes).\n- ASoC: qcom: q6adm: the the copp device only during last instance (git-fixes).\n- ASoC: qcom: q6apm-dai: set flags to reflect correct operation of appl_ptr (git-fixes).\n- ASoC: qcom: q6asm-dai: perform correct state check before closing (git-fixes).\n- ASoC: qcom: qdsp6: q6asm-dai: set 10 ms period and buffer alignment (git-fixes).\n- ASoC: rockchip: i2s-tdm: Use param rate if not provided by set_sysclk (git-fixes).\n- ASoC: stm32: sai: fix OF node leak on probe (git-fixes).\n- ASoC: stm32: sai: fix clk prepare imbalance on probe failure (git-fixes).\n- ASoC: stm32: sai: fix device leak on probe (git-fixes).\n- ASoC: sun4i-spdif: Add missing kerneldoc fields for sun4i_spdif_quirks (git-fixes).\n- ASoC: sunxi: sun50i-dmic: Add missing check for devm_regmap_init_mmio (stable-fixes).\n- ASoC: tlv320adcx140: Propagate error codes during probe (stable-fixes).\n- ASoC: tlv320adcx140: fix null pointer (git-fixes).\n- ASoC: tlv320adcx140: fix word length (git-fixes).\n- ASoC: wm8962: Add WM8962_ADC_MONOMIX to \"3D Coefficients\" mask (stable-fixes).\n- ASoC: wm8962: Do not report a microphone if it's shorted to ground on plug (stable-fixes).\n- Add dtb-spacemit SpacemiT boards include MilkV-Jupiter, Banana Pi F3 and Orange Pi RV2.\n- Bluetooth: HCI: Fix tracking of advertisement set/instance 0x00 (git-fixes).\n- Bluetooth: L2CAP: Fix invalid response to L2CAP_ECRED_RECONF_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix not checking output MTU is acceptable on L2CAP_ECRED_CONN_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix response to L2CAP_ECRED_CONN_REQ (git-fixes).\n- Bluetooth: MGMT: Fix memory leak in set_ssp_complete (git-fixes).\n- Bluetooth: SMP: Fix not generating mackey and ltk when repairing (git-fixes).\n- Bluetooth: btrtl: Avoid loading the config file on security chips (stable-fixes).\n- Bluetooth: btusb: Add USB ID 7392:e611 for Edimax EW-7611UXB (stable-fixes).\n- Bluetooth: btusb: Add device ID for Realtek RTL8761BU (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3533 for RTL8821CE (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 2b89/6275 for RTL8761BUV (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID for RTL8852CE (stable-fixes).\n- Bluetooth: btusb: revert use of devm_kzalloc in btusb (git-fixes).\n- Bluetooth: hci_conn: Set link_policy on incoming ACL connections (stable-fixes).\n- Bluetooth: hci_conn: use mod_delayed_work for active mode timeout (stable-fixes).\n- Bluetooth: hci_qca: Cleanup on all setup failures (git-fixes).\n- Bluetooth: hci_sock: Prevent race in socket write iter and sock bind (git-fixes).\n- Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work (git-fixes).\n- Documentation/kernel-parameters: fix typo in retbleed= kernel parameter description (git-fixes).\n- Documentation: PCI: endpoint: Fix ntb/vntb copy \u0026 paste errors (git-fixes).\n- Documentation: hid-alps: Fix packet format section headings (git-fixes).\n- Documentation: mailbox: mbox_chan_ops.flush() is optional (git-fixes).\n- Documentation: parport-lowlevel: Separate function listing code blocks (git-fixes).\n- HID: Apply quirk HID_QUIRK_ALWAYS_POLL to Edifier QR30 (2d99:a101) (stable-fixes).\n- HID: apple: Add \"SONiX KN85 Keyboard\" to the list of non-apple keyboards (stable-fixes).\n- HID: apple: Add SONiX AK870 PRO to non_apple_keyboards quirk list (stable-fixes).\n- HID: elecom: Add support for ELECOM HUGE Plus M-HT1MRBK (stable-fixes).\n- HID: elecom: Add support for ELECOM M-XT3URBK (018F) (stable-fixes).\n- HID: hid-input: Extend Elan ignore battery quirk to USB (stable-fixes).\n- HID: hid-pl: handle probe errors (git-fixes).\n- HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report() (stable-fixes).\n- HID: input: map HID_GD_Z to ABS_DISTANCE for stylus/pen (stable-fixes).\n- HID: intel-ish-hid: Reset enum_devices_done before enumeration (stable-fixes).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- HID: logitech-dj: Remove duplicate error logging (git-fixes).\n- HID: logitech-hidpp: Check maxfield in hidpp_get_report_length() (stable-fixes).\n- HID: logitech-hidpp: Do not assume FAP in hidpp_send_message_sync() (git-fixes).\n- HID: magicmouse: Do not crash on missing msc-\u003einput (stable-fixes).\n- HID: multitouch: add MT_QUIRK_STICKY_FINGERS to MT_CLS_VTL (stable-fixes).\n- HID: multitouch: add eGalaxTouch EXC3188 support (stable-fixes).\n- HID: playstation: Add missing check for input_ff_create_memless (git-fixes).\n- HID: playstation: Center initial joystick axes to prevent spurious events (stable-fixes).\n- HID: prodikeys: Check presence of pm-\u003einput_ep82 (stable-fixes).\n- HID: quirks: Add another Chicony HP 5MP Cameras to hid_ignore_list (stable-fixes).\n- HID: quirks: work around VID/PID conflict for appledisplay (git-fixes).\n- HID: usbhid: paper over wrong bNumDescriptor field (stable-fixes).\n- Input: atkbd - skip deactivate for HONOR FMB-P's internal keyboard (git-fixes).\n- Input: cros_ec_keyb - fix an invalid memory access (stable-fixes).\n- Input: goodix - add support for ACPI ID GDIX1003 (stable-fixes).\n- Input: goodix - add support for ACPI ID GDX9110 (stable-fixes).\n- Input: i8042 - add TUXEDO InfinityBook Max Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: i8042 - add quirk for ASUS Zenbook UX425QA_UM425QA (stable-fixes).\n- Input: i8042 - add quirks for MECHREVO Wujie 15X Pro (stable-fixes).\n- Input: stmfts - correct wording for the warning message (git-fixes).\n- Input: stmfts - make comments correct (git-fixes).\n- Input: ti_am335x_tsc - fix off-by-one error in wire_order validation (git-fixes).\n- KEYS: trusted: Fix a memory leak in tpm2_load_cmd (git-fixes).\n- KEYS: trusted_tpm1: Compare HMAC values in constant time (git-fixes).\n- Move upstreamed SCSI patches into sorted section\n- Move upstreamed ath12k patch into sorted section\n- Move upstreamed mm and SCSI patches into sorted section\n- NTB: ntb_transport: Fix too small buffer for debugfs_name (git-fixes).\n- PCI/ACPI: Restrict program_hpx_type2() to AER bits (git-fixes).\n- PCI/IOV: Fix race between SR-IOV enable/disable and hotplug (git-fixes).\n- PCI/MSI: Unmap MSI-X region on error (stable-fixes).\n- PCI/P2PDMA: Release per-CPU pgmap ref when vm_insert_page() fails (git-fixes).\n- PCI/PM: Avoid redundant delays on D3hot-\u003eD3cold (git-fixes).\n- PCI/PM: Reinstate clearing state_saved in legacy and !PM codepaths (git-fixes).\n- PCI/portdrv: Fix potential resource leak (git-fixes).\n- PCI: Add ACS quirk for Pericom PI7C9X2G404 switches [12d8:b404] (git-fixes).\n- PCI: Add ACS quirk for Qualcomm Hamoa \u0026 Glymur (stable-fixes).\n- PCI: Add PCIE_MSG_CODE_ASSERT_INTx message macros (stable-fixes).\n- PCI: Add defines for bridge window indexing (stable-fixes).\n- PCI: Correct PCI_CAP_EXP_ENDPOINT_SIZEOF_V2 value (git-fixes).\n- PCI: Do not attempt to set ExtTag for VFs (git-fixes).\n- PCI: Enable ACS after configuring IOMMU for OF platforms (stable-fixes).\n- PCI: Fix pci_slot_lock () device locking (stable-fixes).\n- PCI: Fix pci_slot_trylock() error handling (git-fixes).\n- PCI: Initialize RCB from pci_configure_device() (git-fixes).\n- PCI: Log bridge info when first enumerating bridge (stable-fixes).\n- PCI: Log bridge windows conditionally (stable-fixes).\n- PCI: Mark 3ware-9650SA Root Port Extended Tags as broken (git-fixes).\n- PCI: Mark ASM1164 SATA controller to avoid bus reset (stable-fixes).\n- PCI: Mark Nvidia GB10 to avoid bus reset (stable-fixes).\n- PCI: Move pci_read_bridge_windows() below individual window accessors (stable-fixes).\n- PCI: Supply bridge device, not secondary bus, to read window details (stable-fixes).\n- PCI: dw-rockchip: Disable BAR 0 and BAR 1 for Root Port (stable-fixes).\n- PCI: dwc: Fix wrong PORT_LOGIC_LTSSM_STATE_MASK definition (git-fixes).\n- PCI: endpoint: Fix swapped parameters in pci_{primary/secondary}_epc_epf_unlink() functions (git-fixes).\n- PCI: keystone: Exit ks_pcie_probe() for invalid mode (git-fixes).\n- PCI: mediatek: Fix IRQ domain leak when MSI allocation fails (git-fixes).\n- PCI: rcar-gen2: Drop ARM dependency from PCI_RCAR_GEN2 (git-fixes).\n- PM: runtime: Do not clear needs_force_resume with enabled runtime PM (git-fixes).\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- PM: sleep: wakeirq: harden dev_pm_clear_wake_irq() against races (git-fixes).\n- PM: wakeup: Handle empty list in wakeup_sources_walk_start() (git-fixes).\n- USB: Fix descriptor count when handling invalid MBIM extended descriptor (git-fixes).\n- USB: OHCI/UHCI: Add soft dependencies on ehci_platform (stable-fixes).\n- USB: lpc32xx_udc: Fix error handling in probe (git-fixes).\n- USB: serial: belkin_sa: fix TIOCMBIS and TIOCMBIC (git-fixes).\n- USB: serial: ftdi_sio: add support for PICAXE AXE027 cable (stable-fixes).\n- USB: serial: ftdi_sio: add support for u-blox EVK-M101 (stable-fixes).\n- USB: serial: ftdi_sio: match on interface number for jtag (stable-fixes).\n- USB: serial: kobil_sct: fix TIOCMBIS and TIOCMBIC (git-fixes).\n- USB: serial: option: add Foxconn T99W760 (stable-fixes).\n- USB: serial: option: add Quectel RG255C (stable-fixes).\n- USB: serial: option: add Telit Cinterion FE910C04 new compositions (stable-fixes).\n- USB: serial: option: add Telit FN920C04 ECM compositions (stable-fixes).\n- USB: serial: option: add Telit FN920C04 RNDIS compositions (stable-fixes).\n- USB: serial: option: add Telit LE910 MBIM composition (stable-fixes).\n- USB: serial: option: add UNISOC UIS7720 (stable-fixes).\n- USB: serial: option: add support for Rolling RW101R-GL (stable-fixes).\n- USB: serial: option: move Telit 0x10c7 composition in the right place (stable-fixes).\n- USB: storage: Remove subclass and protocol overrides from Novatek quirk (git-fixes).\n- Update config files: disable CONFIG_DEVPORT for arm64 (bsc#1256792)\n- Workaround for hybrid git workflow in SLFO 1.0/1.1\n- arm64: zynqmp: Fix usb node drive strength and slew rate (git-fixes)\n- arm64: zynqmp: Revert usb node drive strength and slew rate for (git-fixes)\n- ata: libata: Add cpr_log to ata_dev_print_features() early return (git-fixes).\n- ata: libata: avoid long timeouts on hot-unplugged SATA DAS (stable-fixes).\n- ata: pata_ftide010: Fix some DMA timings (git-fixes).\n- atm/fore200e: Fix possible data race in fore200e_open() (git-fixes).\n- atm: Fix dma_free_coherent() size (git-fixes).\n- atm: fore200e: fix use-after-free in tasklets during device removal (git-fixes).\n- atm: idt77252: Add missing `dma_map_error()` (stable-fixes).\n- auxdisplay: arm-charlcd: fix release_mem_region() size (git-fixes).\n- backlight: led-bl: Add devlink to supplier LEDs (git-fixes).\n- backlight: lp855x: Fix lp855x.h kernel-doc warnings (git-fixes).\n- backlight: qcom-wled: Change PM8950 WLED configurations (git-fixes).\n- backlight: qcom-wled: Support ovp values for PMI8994 (git-fixes).\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- bpf: Reject bpf_timer for PREEMPT_RT (git-fixes).\n- broadcom: b44: prevent uninitialized value usage (git-fixes).\n- bs-upload-kernel: Fix cve branch uploads\n- btrfs: do not strictly require dirty metadata threshold for metadata writepages (stable-fixes).\n- btrfs: make sure extent and csum paths are always released in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: scrub: always update btrfs_scrub_progress::last_physical (git-fixes).\n- bus: fsl-mc: Replace snprintf and sprintf with sysfs_emit in sysfs show functions (stable-fixes).\n- bus: fsl-mc: fix an error handling in fsl_mc_device_add() (git-fixes).\n- bus: fsl-mc: fix use-after-free in driver_override_show() (git-fixes).\n- can: ctucanfd: fix SSP_SRC in cases when bit-rate is higher than 1 MBit (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: etas_es58x: allow partial RX URB allocation to succeed (git-fixes).\n- can: gs_usb: gs_can_open(): fix error handling (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): fix error message (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error (git-fixes).\n- can: gs_usb: gs_usb_xmit_callback(): fix handling of failed transmitted URBs (git-fixes).\n- can: j1939: make j1939_session_activate() fail if device is no longer registered (stable-fixes).\n- can: j1939: make j1939_sk_bind() fail if device is no longer registered (git-fixes).\n- can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: kvaser_usb: leaf: Fix potential infinite loop in command parsers (git-fixes).\n- can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: sja1000: fix max irq loop handling (git-fixes).\n- can: sun4i_can: sun4i_can_interrupt(): fix max irq loop handling (git-fixes).\n- can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak (git-fixes).\n- char: applicom: fix NULL pointer dereference in ac_ioctl (stable-fixes).\n- char: tpm: cr50: Remove IRQF_ONESHOT (stable-fixes).\n- cifs: Fix copy offload to flush destination region (bsc#1252511).\n- cifs: Fix flushing, invalidation and file size with copy_file_range() (bsc#1252511).\n- cifs: Fix uncached read into ITER_KVEC iterator (bsc#1245449).\n- cifs: add new field to track the last access time of cfid (git-fixes).\n- cifs: add xid to query server interface call (git-fixes).\n- cifs: after disabling multichannel, mark tcon for reconnect (git-fixes).\n- cifs: avoid redundant calls to disable multichannel (git-fixes).\n- cifs: cifs_pick_channel should try selecting active channels (git-fixes).\n- cifs: deal with the channel loading lag while picking channels (git-fixes).\n- cifs: dns resolution is needed only for primary channel (git-fixes).\n- cifs: do not disable interface polling on failure (git-fixes).\n- cifs: do not search for channel if server is terminating (git-fixes).\n- cifs: fix a pending undercount of srv_count (git-fixes).\n- cifs: fix lock ordering while disabling multichannel (git-fixes).\n- cifs: fix stray unlock in cifs_chan_skip_or_disable (git-fixes).\n- cifs: fix use after free for iface while disabling secondary channels (git-fixes).\n- cifs: handle servers that still advertise multichannel after disabling (git-fixes).\n- cifs: handle when server starts supporting multichannel (git-fixes).\n- cifs: handle when server stops supporting multichannel (git-fixes).\n- cifs: make cifs_chan_update_iface() a void function (git-fixes).\n- cifs: make sure server interfaces are requested only for SMB3+ (git-fixes).\n- cifs: make sure that channel scaling is done only once (git-fixes).\n- cifs: reconnect worker should take reference on server struct unconditionally (git-fixes).\n- cifs: reset connections for all channels when reconnect requested (git-fixes).\n- cifs: reset iface weights when we cannot find a candidate (git-fixes).\n- cifs: serialize other channels when query server interfaces is pending (git-fixes).\n- cifs: update dstaddr whenever channel iface is updated (git-fixes).\n- clk: clk-apple-nco: Add \"apple,t8103-nco\" compatible (git-fixes).\n- clk: mediatek: Fix error handling in runtime PM setup (git-fixes).\n- clk: meson: g12a: Limit the HDMI PLL OD to /4 (git-fixes).\n- clk: meson: gxbb: Limit the HDMI PLL OD to /4 on GXL/GXM SoCs (git-fixes).\n- clk: qcom: camcc-sm6350: Fix PLL config of PLL2 (git-fixes).\n- clk: qcom: camcc-sm6350: Specify Titan GDSC power domain as a parent to other (git-fixes).\n- clk: qcom: dispcc-sdm845: Enable parents for pixel clocks (git-fixes).\n- clk: qcom: gcc-msm8917: Remove ALWAYS_ON flag from cpp_gdsc (git-fixes).\n- clk: qcom: gcc-msm8953: Remove ALWAYS_ON flag from cpp_gdsc (git-fixes).\n- clk: qcom: gfx3d: add parent to parent request map (git-fixes).\n- clk: qcom: rcg2: compute 2d using duty fraction directly (git-fixes).\n- clk: renesas: cpg-mssr: Add missing 1ms delay into reset toggle callback (git-fixes).\n- clk: renesas: r9a06g032: Fix memory leak in error path (git-fixes).\n- clk: renesas: rzg2l: Fix intin variable size (git-fixes).\n- clk: renesas: rzg2l: Select correct div round macro (git-fixes).\n- clk: tegra: tegra124-emc: Fix potential memory leak in tegra124_clk_register_emc() (git-fixes).\n- clk: tegra: tegra124-emc: fix device leak on set_rate() (git-fixes).\n- clocksource: Print durations for sync check unconditionally (bsc#1241345).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1241345).\n- comedi: Fix getting range information for subdevices 16 to 255 (git-fixes).\n- comedi: c6xdigio: Fix invalid PNP driver unregistration (git-fixes).\n- comedi: check device's attached status in compat ioctls (git-fixes).\n- comedi: dmm32at: serialize use of paged registers (git-fixes).\n- comedi: fix divide-by-zero in comedi_buf_munge() (stable-fixes).\n- comedi: multiq3: sanitize config options in multiq3_attach() (git-fixes).\n- comedi: pcl818: fix null-ptr-deref in pcl818_ai_cancel() (git-fixes).\n- cpufreq: intel_pstate: Check IDA only before MSR_IA32_PERF_CTL writes (git-fixes).\n- cpuidle: menu: Use residency threshold in polling state override decisions (bsc#1255026).\n- crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id (git-fixes).\n- crypto: authenc - Correctly pass EINPROGRESS back up to the caller (git-fixes).\n- crypto: authencesn - reject too-short AAD (assoclen\u0026lt;8) to match ESP/ESN spec (git-fixes).\n- crypto: cavium - fix dma_free_coherent() size (git-fixes).\n- crypto: ccp - Add an S4 restore flow (git-fixes).\n- crypto: ccree - Correctly handle return of sg_nents_for_len (git-fixes).\n- crypto: hisilicon/qm - restore original qos values (git-fixes).\n- crypto: hisilicon/sec2 - support skcipher/aead fallback for hardware queue unavailable (git-fixes).\n- crypto: iaa - Fix incorrect return value in save_iaa_wq() (git-fixes).\n- crypto: iaa - Fix out-of-bounds index in find_empty_iaa_compression_mode (git-fixes).\n- crypto: octeontx - Fix length check to avoid truncation in ucode_load_store (git-fixes).\n- crypto: octeontx - fix dma_free_coherent() size (git-fixes).\n- crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly (git-fixes).\n- crypto: qat - fix duplicate restarting msg during AER error (git-fixes).\n- crypto: qat - fix parameter order used in ICP_QAT_FW_COMN_FLAGS_BUILD (git-fixes).\n- crypto: qat - fix warning on adf_pfvf_pf_proto.c (git-fixes).\n- crypto: rockchip - drop redundant crypto_skcipher_ivsize() calls (git-fixes).\n- crypto: seqiv - Do not use req-\u003eiv after crypto_aead_encrypt (git-fixes).\n- crypto: virtio - Add spinlock protection with virtqueue notification (git-fixes).\n- crypto: virtio - Remove duplicated virtqueue_kick in virtio_crypto_skcipher_crypt_req (git-fixes).\n- device property: Allow secondary lookup in fwnode_get_next_child_node() (git-fixes).\n- dm-integrity: limit MAX_TAG_SIZE to 255 (git-fixes).\n- dm-verity: fix unreliable memory allocation (git-fixes).\n- dm: fix queue start/stop imbalance under suspend/load/resume races (bsc#1253386)\n- dma: dma-axi-dmac: fix SW cyclic transfers (git-fixes).\n- dmaengine: apple-admac: Add \"apple,t8103-admac\" compatible (git-fixes).\n- dmaengine: at_hdmac: fix device leak on of_dma_xlate() (git-fixes).\n- dmaengine: bcm-sba-raid: fix device leak on probe (git-fixes).\n- dmaengine: dw: dmamux: fix OF node leak on route allocation failure (git-fixes).\n- dmaengine: idxd: fix device leaks on compat bind and unbind (git-fixes).\n- dmaengine: lpc18xx-dmamux: fix device leak on route allocation (git-fixes).\n- dmaengine: mediatek: uart-apdma: Fix above 4G addressing TX/RX (git-fixes).\n- dmaengine: omap-dma: fix dma_pool resource leak in error paths (git-fixes).\n- dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config() (git-fixes).\n- dmaengine: sh: rz-dmac: Fix rz_dmac_terminate_all() (git-fixes).\n- dmaengine: sun6i: Choose appropriate burst length under maxburst (stable-fixes).\n- dmaengine: tegra-adma: Fix use-after-free (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on dra7x route allocation (git-fixes).\n- dmaengine: ti: k3-udma: fix device leak on udma lookup (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap max_register (git-fixes).\n- dmaengine: xilinx_dma: Fix uninitialized addr_width when \"xlnx,addrwidth\" property is missing (git-fixes).\n- docs: ABI: sysfs-devices-soc: Fix swapped sample values (git-fixes).\n- docs: fix WARNING document not included in any toctree (stable-fixes).\n- docs: w1: fix w1-netlink invalid URL (git-fixes).\n- dpll: Prevent duplicate registrations (git-fixes).\n- dpll: fix device-id-get and pin-id-get to return errors properly (git-fixes).\n- dpll: fix return value check for kmemdup (git-fixes).\n- dpll: indent DPLL option type by a tab (git-fixes).\n- dpll: spec: add missing module-name and clock-id to pin-get reply (git-fixes).\n- drivers/usb/dwc3: fix PCI parent check (git-fixes).\n- drivers: iio: mpu3050: use dev_err_probe for regulator request (git-fixes).\n- drm/amd/display: Avoid updating surface with the same surface under MPO (stable-fixes).\n- drm/amd/display: Bump the HDMI clock to 340MHz (stable-fixes).\n- drm/amd/display: Check NULL before accessing (stable-fixes).\n- drm/amd/display: Fix DP no audio issue (stable-fixes).\n- drm/amd/display: Fix logical vs bitwise bug in get_embedded_panel_info_v2_1() (git-fixes).\n- drm/amd/display: Increase DPCD read retries (stable-fixes).\n- drm/amd/display: Move sleep into each retry for retrieve_link_cap() (stable-fixes).\n- drm/amd/display: Use GFP_ATOMIC in dc_create_plane_state() (stable-fixes).\n- drm/amd/display: Use same max plane scaling limits for all 64 bpp formats (git-fixes).\n- drm/amd/display: fix wrong color value mapping on MCM shaper LUT (git-fixes).\n- drm/amd/pm: Do not clear SI SMC table when setting power limit (git-fixes).\n- drm/amd/pm: Workaround SI powertune issue on Radeon 430 (v2) (git-fixes).\n- drm/amd/pm: fix race in power state check before mutex lock (git-fixes).\n- drm/amd: Clean up kfd node on surprise disconnect (stable-fixes).\n- drm/amd: Fix hang on amdgpu unload by using pci_dev_is_disconnected() (git-fixes).\n- drm/amdgpu/gfx10: fix wptr reset in KGQ init (stable-fixes).\n- drm/amdgpu/gfx11: fix wptr reset in KGQ init (stable-fixes).\n- drm/amdgpu/soc21: fix xclk for APUs (stable-fixes).\n- drm/amdgpu: Add HAINAN clock adjustment (stable-fixes).\n- drm/amdgpu: Adjust usleep_range in fence wait (stable-fixes).\n- drm/amdgpu: Fix memory leak in amdgpu_acpi_enumerate_xcc() (git-fixes).\n- drm/amdgpu: Fix memory leak in amdgpu_ras_init() (git-fixes).\n- drm/amdgpu: Forward VMID reservation errors (git-fixes).\n- drm/amdgpu: Skip emit de meta data on gfx11 with rs64 enabled (stable-fixes).\n- drm/amdgpu: add missing lock to amdgpu_ttm_access_memory_sdma (git-fixes).\n- drm/amdgpu: add support for HDP IP version 6.1.1 (stable-fixes).\n- drm/amdgpu: avoid a warning in timedout job handler (stable-fixes).\n- drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove (git-fixes).\n- drm/amdgpu: fix cyan_skillfish2 gpu info fw handling (git-fixes).\n- drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify (git-fixes).\n- drm/amdgpu: update mappings not managed by KFD (bsc#1255428)\n- drm/amdkfd: Fix GART PTE for non-4K pagesize in svm_migrate_gart_map() (stable-fixes).\n- drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (stable-fixes).\n- drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 (git-fixes).\n- drm/amdkfd: fix a memory leak in device_queue_manager_init() (git-fixes).\n- drm/amdkfd: fix debug watchpoints for logical devices (stable-fixes).\n- drm/atmel-hlcdc: do not reject the commit if the src rect has fractional parts (stable-fixes).\n- drm/atmel-hlcdc: fix memory leak from the atomic_destroy_state callback (stable-fixes).\n- drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release (stable-fixes).\n- drm/bridge: samsung-dsim: Fix memory leak in error path (git-fixes).\n- drm/bridge: ti-sn65dsi86: Enable HPD polling if IRQ is not used (git-fixes).\n- drm/buddy: Prevent BUG_ON by validating rounded allocation (git-fixes).\n- drm/display/dp_mst: Add protection against 0 vcpi (stable-fixes).\n- drm/gma500: Remove unused helper psb_fbdev_fb_setcolreg() (git-fixes).\n- drm/i915/acpi: free _DSM package when no connectors (git-fixes).\n- drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer (git-fixes).\n- drm/i915/wakeref: clean up INTEL_WAKEREF_PUT_* flag macros (stable-fixes).\n- drm/imx/tve: fix probe device leak (git-fixes).\n- drm/logicvc: Fix device node reference leak in logicvc_drm_config_parse() (git-fixes).\n- drm/mediatek: Fix CCORR mtk_ctm_s31_32_to_s1_n function issue (git-fixes).\n- drm/mediatek: Fix device node reference leak in mtk_dp_dt_parse() (git-fixes).\n- drm/mgag200: Fix big-endian support (git-fixes).\n- drm/mgag200: fix mgag200_bmc_stop_scanout() (git-fixes).\n- drm/msm/a2xx: fix pixel shader start on A225 (git-fixes).\n- drm/msm/a2xx: stop over-complaining about the legacy firmware (git-fixes).\n- drm/msm/a6xx: Fix out of bound IO access in a6xx_get_gmu_registers (git-fixes).\n- drm/msm/a6xx: Flush LRZ cache before PT switch (git-fixes).\n- drm/msm/dpu: Add missing NULL pointer check for pingpong interface (git-fixes).\n- drm/msm/dpu: Remove dead-code in dpu_encoder_helper_reset_mixers() (git-fixes).\n- drm/msm/dpu: fix CMD panels on DPU 1.x - 3.x (git-fixes).\n- drm/nouveau/disp/nv50-: Set lock_core in curs507a_prepare (git-fixes).\n- drm/nouveau/dispnv50: Do not call drm_atomic_get_crtc_state() in prepare_fb (git-fixes).\n- drm/nouveau: add missing DCB connector types (git-fixes).\n- drm/nouveau: implement missing DCB connector types; gracefully handle unknown connectors (git-fixes).\n- drm/nouveau: restrict the flush page to a 32-bit address (git-fixes).\n- drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel (git-fixes).\n- drm/panel: sony-td4353-jdi: Enable prepare_prev_first (git-fixes).\n- drm/pl111: Fix error handling in pl111_amba_probe (git-fixes).\n- drm/radeon: Add HAINAN clock adjustment (stable-fixes).\n- drm/radeon: Remove __counted_by from ClockInfoArray.clockInfo[] (stable-fixes).\n- drm/radeon: delete radeon_fence_process in is_signaled, no deadlock (stable-fixes).\n- drm/tegra: dsi: fix device leak on probe (git-fixes).\n- drm/tegra: hdmi: sor: Fix error: variable ‘j’ set but not used (stable-fixes).\n- drm/tilcdc: request and mapp iomem with devres (stable-fixes).\n- drm/ttm: Avoid NULL pointer deref for evicted BOs (git-fixes).\n- drm/v3d: Set DMA segment size to avoid debug warnings (stable-fixes).\n- drm/vgem-fence: Fix potential deadlock on release (git-fixes).\n- drm/vmwgfx: Fix an error return check in vmw_compat_shader_add() (git-fixes).\n- drm/vmwgfx: Fix invalid kref_put callback in vmw_bo_dirty_release (git-fixes).\n- drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (git-fixes).\n- drm/vmwgfx: Use kref in vmw_bo_dirty (stable-fixes).\n- drm: Account property blob allocations to memcg (stable-fixes).\n- drm: nouveau: Replace sprintf() with sysfs_emit() (git-fixes).\n- drm: sti: fix device leaks at component probe (git-fixes).\n- efi/libstub: Describe missing 'out' parameter in efi_load_initrd (git-fixes).\n- efi/libstub: Fix page table access in 5-level to 4-level paging transition (git-fixes).\n- efi: Fix reservation of unaccepted memory table (git-fixes).\n- efivarfs: fix error propagation in efivar_entry_get() (git-fixes).\n- exfat: add a check for invalid data size (git-fixes).\n- exfat: using hweight instead of internal logic (git-fixes).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- ext4: use optimized mballoc scanning regardless of inode format (bsc#1254378).\n- ext4: wait for ongoing I/O to complete before freeing blocks (bsc#1256366).\n- fbcon: check return value of con2fb_acquire_newinfo() (git-fixes).\n- fbdev: au1200fb: Fix a memory leak in au1200fb_drv_probe() (git-fixes).\n- fbdev: ffb: fix corrupted video output on Sun FFB1 (stable-fixes).\n- fbdev: gbefb: fix to use physical address instead of dma address (stable-fixes).\n- fbdev: of: display_timing: fix refcount leak in of_get_display_timings() (git-fixes).\n- fbdev: pxafb: Fix multiple clamped values in pxafb_adjust_timing (git-fixes).\n- fbdev: rivafb: fix divide error in nv3_arb() (git-fixes).\n- fbdev: smscufx: properly copy ioctl memory to kernelspace (stable-fixes).\n- fbdev: ssd1307fb: fix potential page leak in ssd1307fb_probe() (git-fixes).\n- fbdev: tcx.c fix mem_map to correct smem_start offset (git-fixes).\n- fbdev: vt8500lcdfb: fix missing dma_free_coherent() (git-fixes).\n- firewire: nosy: Fix dma_free_coherent() size (git-fixes).\n- firmware: imx: scu-irq: Init workqueue before request mbox channel (stable-fixes).\n- firmware: imx: scu-irq: fix OF node leak in (git-fixes).\n- firmware: stratix10-svc: Add mutex in stratix10 memory management (git-fixes).\n- firmware: stratix10-svc: fix bug in saving controller data (git-fixes).\n- firmware: stratix10-svc: fix make htmldocs warning for stratix10_svc (git-fixes).\n- fix it87_wdt early reboot by reporting running timer (stable-fixes).\n- fpga: dfl: use subsys_initcall to allow built-in drivers to be added (git-fixes).\n- fpga: of-fpga-region: Fail if any bridge is missing (stable-fixes).\n- fs: dlm: allow to F_SETLKW getting interrupted (bsc#1255025).\n- genalloc.h: fix htmldocs warning (git-fixes).\n- gpio: aspeed-sgpio: Change the macro to support deferred probe (stable-fixes).\n- gpio: omap: do not register driver in probe() (git-fixes).\n- gpio: pca953x: Add support for level-triggered interrupts (stable-fixes).\n- gpio: pca953x: Utilise dev_err_probe() where it makes sense (stable-fixes).\n- gpio: pca953x: Utilise temporary variable for struct device (stable-fixes).\n- gpio: pca953x: fix wrong error probe return value (git-fixes).\n- gpio: pca953x: handle short interrupt pulses on PCAL devices (git-fixes).\n- gpio: pca953x: mask interrupts in irq shutdown (stable-fixes).\n- gpio: rockchip: Stop calling pinctrl for set_direction (git-fixes).\n- gpio: rockchip: mark the GPIO controller as sleeping (git-fixes).\n- gpio: sprd: Change sprd_gpio lock to raw_spin_lock (stable-fixes).\n- gpu: host1x: Fix race in syncpt alloc/free (git-fixes).\n- hwmon: (f71882fg) Add F81968 support (stable-fixes).\n- hwmon: (ibmpex) fix use-after-free in high/low store (git-fixes).\n- hwmon: (max16065) Use READ/WRITE_ONCE to avoid compiler optimization induced race (git-fixes).\n- hwmon: (max16065) Use local variable to avoid TOCTOU (git-fixes).\n- hwmon: (nct6775) Add ASUS Pro WS WRX90E-SAGE SE (stable-fixes).\n- hwmon: (occ) Mark occ_init_attribute() as __printf (git-fixes).\n- hwmon: (tmp401) fix overflow caused by default conversion rate value (git-fixes).\n- hwmon: (w83791d) Convert macros to functions to avoid TOCTOU (git-fixes).\n- hwmon: (w83l786ng) Convert macros to functions to avoid TOCTOU (git-fixes).\n- hwmon: sy7636a: Fix regulator_enable resource leak on error path (git-fixes).\n- i2c: amd-mp2: fix reference leak in MP2 PCI device (git-fixes).\n- i2c: designware: Disable SMBus interrupts to prevent storms from mis-configured firmware (stable-fixes).\n- i2c: i2c.h: fix a bad kernel-doc line (git-fixes).\n- i3c: Move device name assignment after i3c_bus_init (git-fixes).\n- i3c: dw: Initialize spinlock to avoid upsetting lockdep (git-fixes).\n- i3c: fix refcount inconsistency in i3c_master_register (git-fixes).\n- i3c: master: Inherit DMA masks and parameters from parent device (stable-fixes).\n- i3c: master: svc: Initialize 'dev' to NULL in svc_i3c_master_ibi_isr() (stable-fixes).\n- i3c: master: svc: Prevent incomplete IBI transaction (git-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- idr: fix idr_alloc() returning an ID out of range (git-fixes).\n- iio: Use IRQF_NO_THREAD (stable-fixes).\n- iio: accel: bmc150: Fix irq assumption regression (stable-fixes).\n- iio: accel: fix ADXL355 startup race condition (git-fixes).\n- iio: accel: iis328dq: fix gain values (git-fixes).\n- iio: adc: ad7280a: fix ad7280_store_balance_timer() (git-fixes).\n- iio: adc: ad7280a: handle spi_setup() errors in probe() (git-fixes).\n- iio: adc: ad9467: fix ad9434 vref mask (git-fixes).\n- iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver (git-fixes).\n- iio: adc: ti_am335x_adc: Limit step_avg to valid range for gcc complains (stable-fixes).\n- iio: core: Clean up device correctly on iio_device_alloc() failure (git-fixes).\n- iio: core: add missing mutex_destroy in iio_dev_release() (git-fixes).\n- iio: dac: ad5686: add AD5695R to ad5686_chip_info_tbl (git-fixes).\n- iio: gyro: itg3200: Fix unchecked return value in read_raw (git-fixes).\n- iio: imu: st_lsm6dsx: Fix measurement unit for odr struct member (git-fixes).\n- iio: imu: st_lsm6dsx: fix array size for st_lsm6dsx_settings fields (git-fixes).\n- iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection (git-fixes).\n- iio: magnetometer: Remove IRQF_ONESHOT (stable-fixes).\n- iio: sca3000: Fix a resource leak in sca3000_probe() (git-fixes).\n- iio: st_lsm6dsx: Fixed calibrated timestamp calculation (git-fixes).\n- iio:common:ssp_sensors: Fix an error handling path ssp_probe() (git-fixes).\n- ima: Handle error code returned by ima_filter_rule_match() (git-fixes).\n- intel_th: Fix error handling in intel_th_output_open (git-fixes).\n- intel_th: fix device leak on output open() (git-fixes).\n- iomap: account for unaligned end offsets when truncating read range (git-fixes).\n- ipmi: Fix __scan_channels() failing to rescan channels (stable-fixes).\n- ipmi: Fix handling of messages with provided receive message pointer (git-fixes).\n- ipmi: Fix the race between __scan_channels() and deliver_response() (stable-fixes).\n- ipmi: Rework user message limit handling (git-fixes).\n- ipmi: ipmb: initialise event handler read bytes (git-fixes).\n- irqchip/mchp-eic: Fix error code in mchp_eic_domain_alloc() (git-fixes).\n- kABI workaround for HCI_LE_ADV_0 addition (git-fixes).\n- kconfig/mconf: Initialize the default locale at startup (stable-fixes).\n- kconfig/nconf: Initialize the default locale at startup (stable-fixes).\n- kernel-binary: Require libdw in Factory Libdw is required for gendwarfksyms\n- kernel-binary: Support building gendwarfksyms on SLE/Leap 15\n- landlock: Optimize file path walks and prepare for audit support (bsc#1255698).\n- leds: led-class: Only Add LED to leds_list when it is fully ready (git-fixes).\n- leds: leds-lp50xx: Allow LED 0 to be added to module bank (git-fixes).\n- leds: leds-lp50xx: Enable chip before any communication (git-fixes).\n- leds: leds-lp50xx: LP5009 supports 3 modules for a total of 9 LEDs (git-fixes).\n- leds: netxbig: Fix GPIO descriptor leak in error paths (git-fixes).\n- leds: qcom-lpg: Check the return value of regmap_bulk_write() (git-fixes).\n- lib/crypto: aes: Fix missing MMU protection for AES S-box (git-fixes).\n- lib/vsprintf: Check pointer before dereferencing in time_and_date() (git-fixes).\n- mISDN: annotate data-race around dev-\u003ework (git-fixes).\n- mailbox: mailbox-test: Fix debugfs_create_dir error checking (git-fixes).\n- media: TDA1997x: Remove redundant cancel_delayed_work in probe (git-fixes).\n- media: adv7180: fix frame interval in progressive mode (stable-fixes).\n- media: adv7842: Avoid possible out-of-bounds array accesses in adv7842_cp_log_status() (git-fixes).\n- media: amphion: Add a frame flush mode for decoder (stable-fixes).\n- media: amphion: Cancel message work before releasing the VPU core (git-fixes).\n- media: amphion: Clear last_buffer_dequeued flag for DEC_CMD_START (stable-fixes).\n- media: amphion: Make some vpu_v4l2 functions static (stable-fixes).\n- media: amphion: Remove vpu_vb_is_codecconfig (git-fixes).\n- media: atomisp: Prefix firmware paths with \"intel/ipu/\" (bsc#1252973).\n- media: atomisp: Remove firmware_name module parameter (bsc#1252973).\n- media: ccs: Accommodate C-PHY into the calculation (git-fixes).\n- media: ccs: Avoid possible division by zero (git-fixes).\n- media: cec: Fix debugfs leak on bus_register() failure (git-fixes).\n- media: cx23885: Add missing unmap in snd_cx23885_hw_params() (git-fixes).\n- media: cx25821: Add missing unmap in snd_cx25821_hw_params() (git-fixes).\n- media: cx25821: Fix a resource leak in cx25821_dev_setup() (stable-fixes).\n- media: cx88: Add missing unmap in snd_cx88_hw_params() (git-fixes).\n- media: dvb-core: dmxdevfilter must always flush bufs (stable-fixes).\n- media: dvb-core: fix wrong reinitialization of ringbuffer on reopen (git-fixes).\n- media: dvb-net: fix OOB access in ULE extension header tables (git-fixes).\n- media: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg() (git-fixes).\n- media: i2c/tw9903: Fix potential memory leak in tw9903_probe() (git-fixes).\n- media: i2c/tw9906: Fix potential memory leak in tw9906_probe() (git-fixes).\n- media: i2c: ADV7604: Remove redundant cancel_delayed_work in probe (git-fixes).\n- media: i2c: adv7842: Remove redundant cancel_delayed_work in probe (git-fixes).\n- media: i2c: ov5647: Correct minimum VBLANK value (git-fixes).\n- media: i2c: ov5647: Correct pixel array offset (git-fixes).\n- media: i2c: ov5647: Fix PIXEL_RATE value for VGA mode (git-fixes).\n- media: i2c: ov5647: Initialize subdev before controls (git-fixes).\n- media: i2c: ov5647: Sensor should report RAW color space (git-fixes).\n- media: i2c: ov5647: use our own mutex for the ctrl lock (git-fixes).\n- media: msp3400: Avoid possible out-of-bounds array accesses in msp3400c_thread() (git-fixes).\n- media: mtk-mdp: Fix a reference leak bug in mtk_mdp_remove() (git-fixes).\n- media: mtk-mdp: Fix error handling in probe function (git-fixes).\n- media: omap3isp: isp_video_mbus_to_pix/pix_to_mbus fixes (stable-fixes).\n- media: omap3isp: isppreview: always clamp in preview_try_format() (stable-fixes).\n- media: omap3isp: set initial format (stable-fixes).\n- media: pvrusb2: Fix incorrect variable used in trace message (git-fixes).\n- media: pvrusb2: fix URB leak in pvr2_send_request_ex (stable-fixes).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- media: radio-keene: fix memory leak in error path (git-fixes).\n- media: rc: st_rc: Fix reset control resource leak (git-fixes).\n- media: renesas: rcar_drif: fix device node reference leak in rcar_drif_bond_enabled (git-fixes).\n- media: rkisp1: Fix filter mode register configuration (stable-fixes).\n- media: samsung: exynos4-is: fix potential ABBA deadlock on init (git-fixes).\n- media: solo6x10: Check for out of bounds chip_id (stable-fixes).\n- media: uvcvideo: Fix allocation for small frame sizes (git-fixes).\n- media: v4l2-mem2mem: Fix outdated documentation (git-fixes).\n- media: venus: vdec: fix error state assignment for zero bytesused (git-fixes).\n- media: verisilicon: Fix CPU stalls on G2 bus error (git-fixes).\n- media: verisilicon: Protect G2 HEVC decoder against invalid DPB index (git-fixes).\n- media: verisilicon: Store chroma and motion vectors offset (stable-fixes).\n- media: verisilicon: g2: Use common helpers to compute chroma and mv offsets (stable-fixes).\n- media: videobuf2: Fix device reference leak in vb2_dc_alloc error path (git-fixes).\n- media: vidtv: initialize local pointers upon transfer of memory ownership (git-fixes).\n- media: vpif_capture: fix section mismatch (git-fixes).\n- media: vpif_display: fix section mismatch (git-fixes).\n- mei: me: add nova lake point S DID (stable-fixes).\n- mei: me: add wildcat lake P DID (stable-fixes).\n- mfd: altera-sysmgr: Fix device leak on sysmgr regmap lookup (git-fixes).\n- mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure (git-fixes).\n- mfd: core: Add locking around 'mfd_of_node_list' (git-fixes).\n- mfd: da9055: Fix missing regmap_del_irq_chip() in error path (git-fixes).\n- mfd: max77620: Fix potential IRQ chip conflict when probing two devices (git-fixes).\n- mfd: mt6358-irq: Fix missing irq_domain_remove() in error path (git-fixes).\n- mfd: mt6397-irq: Fix missing irq_domain_remove() in error path (git-fixes).\n- mfd: tps6105x: Fix kernel-doc warnings relating to the core struct and tps6105x_mode (git-fixes).\n- mfd: wm8350-core: Use IRQF_ONESHOT (git-fixes).\n- misc: bcm_vk: Fix possible null-pointer dereferences in bcm_vk_read() (stable-fixes).\n- misc: eeprom: Fix EWEN/EWDS/ERAL commands for 93xx56 and 93xx66 (stable-fixes).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1254447 bsc#1253087).\n- mmc: mmci: Fix device_node reference leak in of_get_dml_pipe_index() (git-fixes).\n- mmc: rtsx_pci_sdmmc: implement sdmmc_card_busy function (git-fixes).\n- mmc: rtsx_pci_sdmmc: increase power-on settling delay to 5ms (git-fixes).\n- mmc: sdhci-esdhc-imx: add alternate ARCH_S32 dependency to Kconfig (git-fixes).\n- mmc: sdhci-msm: Avoid early clock doubling during HS400 transition (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Prevent illegal clock reduction in HS200/HS400 mode (git-fixes).\n- most: usb: fix double free on late probe failure (git-fixes).\n- mt76: mt7615: Fix memory leak in mt7615_mcu_wtbl_sta_add() (git-fixes).\n- mtd: lpddr_cmds: fix signed shifts in lpddr_cmds (git-fixes).\n- mtd: maps: pcmciamtd: fix potential memory leak in pcmciamtd_detach() (git-fixes).\n- mtd: nand: relax ECC parameter validation check (git-fixes).\n- mtd: parsers: Fix memory leak in mtd_parser_tplink_safeloader_parse() (git-fixes).\n- mtd: parsers: ofpart: fix OF node refcount leak in parse_fixed_partitions() (git-fixes).\n- mtd: rawnand: cadence: Fix return type of CDMA send-and-wait helper (git-fixes).\n- mtd: rawnand: lpc32xx_slc: fix GPIO descriptor leak on probe error and remove (git-fixes).\n- mtd: rawnand: pl353: Fix software ECC support (git-fixes).\n- mtd: rawnand: renesas: Handle devm_pm_runtime_enable() errors (git-fixes).\n- mtd: spinand: Fix kernel doc (git-fixes).\n- myri10ge: avoid uninitialized variable use (stable-fixes).\n- net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts (git-fixes).\n- net: hv_netvsc: reject RSS hash key programming without RX indirection table (bsc#1257473).\n- net: mdio: aspeed: add dummy read to avoid read-after-write issue (git-fixes).\n- net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write (git-fixes).\n- net: nfc: nci: Fix parameter validation for packet data (git-fixes).\n- net: phy: adin1100: Fix software power-down ready condition (git-fixes).\n- net: phy: mxl-gpy: fix bogus error on USXGMII and integrated PHY (git-fixes).\n- net: phy: mxl-gpy: fix link properties on USXGMII and internal PHYs (git-fixes).\n- net: rose: fix invalid array index in rose_kill_by_device() (git-fixes).\n- net: tcp: allow zero-window ACK update the window (bsc#1254767).\n- net: usb: catc: enable basic endpoint checking (git-fixes).\n- net: usb: dm9601: remove broken SR9700 support (git-fixes).\n- net: usb: kalmia: validate USB endpoints (git-fixes).\n- net: usb: kaweth: remove TX queue manipulation in kaweth_set_rx_mode (git-fixes).\n- net: usb: kaweth: validate USB endpoints (git-fixes).\n- net: usb: lan78xx: scan all MDIO addresses on LAN7801 (git-fixes).\n- net: usb: pegasus: enable basic endpoint checking (git-fixes).\n- net: usb: pegasus: fix memory leak in update_eth_regs_async() (git-fixes).\n- net: usb: r8152: fix transmit queue timeout (stable-fixes).\n- net: usb: rtl8150: fix memory leak on usb_submit_urb() failure (git-fixes).\n- net: usb: sr9700: fix incorrect command used to write single register (git-fixes).\n- net: usb: sr9700: remove code to drive nonexistent multicast filter (stable-fixes).\n- net: usb: sr9700: support devices with virtual driver CD (stable-fixes).\n- net: wan/fsl_ucc_hdlc: Fix dma_free_coherent() in uhdlc_memclean() (git-fixes).\n- net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets (git-fixes).\n- net: wwan: iosm: Fix memory leak in ipc_mux_deinit() (git-fixes).\n- net: wwan: t7xx: fix potential skb-\u003efrags overflow in RX path (git-fixes).\n- nfc: hci: shdlc: Stop timers and work before freeing context (git-fixes).\n- nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame() (git-fixes).\n- nfc: nci: Fix race between rfkill and nci_unregister_device() (git-fixes).\n- nfc: nxp-nci: remove interrupt trigger type (stable-fixes).\n- nfc: pn533: Fix error code in pn533_acr122_poweron_rdr() (git-fixes).\n- nfc: pn533: properly drop the usb interface reference on disconnect (git-fixes).\n- ntb: ntb_hw_switchtec: Fix array-index-out-of-bounds access (stable-fixes).\n- ntb: ntb_hw_switchtec: Fix shift-out-of-bounds for 0 mw lut (stable-fixes).\n- nvme: Use non zero KATO for persistent discovery connections (git-fixes).\n- of: fix reference count leak in of_alias_scan() (git-fixes).\n- of: platform: Use default match table for /firmware (git-fixes).\n- orangefs: fix xattr related buffer overflow.. (git-fixes).\n- phy: broadcom: bcm63xx-usbh: fix section mismatches (git-fixes).\n- phy: freescale: imx8m-pcie: assert phy reset during power on (stable-fixes).\n- phy: fsl-imx8mq-usb: disable bind/unbind platform driver feature (stable-fixes).\n- phy: mvebu-cp110-utmi: fix dr_mode property read from dts (stable-fixes).\n- phy: renesas: rcar-gen3-usb2: Fix an error handling path in rcar_gen3_phy_usb2_probe() (git-fixes).\n- phy: rockchip: inno-usb2: fix communication disruption in gadget mode (git-fixes).\n- phy: rockchip: inno-usb2: fix disconnection in gadget mode (git-fixes).\n- phy: stm32-usphyc: Fix off by one in probe() (git-fixes).\n- phy: tegra: xusb: Explicitly configure HS_DISCON_LEVEL to 0x7 (git-fixes).\n- pinctrl: equilibrium: Fix device node reference leak in pinbank_init() (git-fixes).\n- pinctrl: meson: mark the GPIO controller as sleeping (git-fixes).\n- pinctrl: qcom: lpass-lpi: mark the GPIO controller as sleeping (git-fixes).\n- pinctrl: qcom: msm: Fix deadlock in pinmux configuration (stable-fixes).\n- pinctrl: qcom: sm8250-lpass-lpi: Fix i2s2_data_groups definition (git-fixes).\n- pinctrl: single: Fix PIN_CONFIG_BIAS_DISABLE handling (stable-fixes).\n- pinctrl: single: Fix incorrect type for error return variable (git-fixes).\n- pinctrl: single: fix refcount leak in pcs_add_gpio_func() (git-fixes).\n- pinctrl: stm32: fix hwspinlock resource leak in probe function (git-fixes).\n- platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver (git-fixes).\n- platform/chrome: cros_ec_lightbar: Fix response size initialization (git-fixes).\n- platform/chrome: cros_typec_switch: Do not touch struct fwnode_handle::dev (git-fixes).\n- platform/mellanox: mlxbf-pmc: Remove trailing whitespaces from event names (git-fixes).\n- platform/x86/amd/pmc: Add quirk for MECHREVO Wujie 15X Pro (stable-fixes).\n- platform/x86/amd/pmc: Add spurious_8042 to Xbox Ally (stable-fixes).\n- platform/x86/amd: pmc: Add Lenovo Legion Go 2 to pmc quirk list (stable-fixes).\n- platform/x86/intel/hid: Add Dell Pro Rugged 10/12 tablet to VGBS DMI quirks (stable-fixes).\n- platform/x86: acer-wmi: Ignore backlight event (stable-fixes).\n- platform/x86: asus-wmi: use brightness_set_blocking() for kbd led (git-fixes).\n- platform/x86: classmate-laptop: Add missing NULL pointer checks (stable-fixes).\n- platform/x86: huawei-wmi: add keys for HONOR models (stable-fixes).\n- platform/x86: ibm_rtl: fix EBDA signature search pointer arithmetic (git-fixes).\n- platform/x86: intel: chtwc_int33fe: do not dereference swnode args (git-fixes).\n- platform/x86: intel: punit_ipc: fix memory corruption (git-fixes).\n- platform/x86: intel_telemetry: Fix PSS event register mask (git-fixes).\n- platform/x86: intel_telemetry: Fix swapped arrays in PSS output (git-fixes).\n- platform/x86: msi-laptop: add missing sysfs_remove_group() (git-fixes).\n- platform/x86: panasonic-laptop: Fix sysfs group leak in error path (stable-fixes).\n- platform/x86: toshiba_haps: Fix memory leaks in add/remove routines (git-fixes).\n- power: reset: nvmem-reboot-mode: respect cell size for nvmem_cell_write (git-fixes).\n- power: supply: ab8500: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: act8945a: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: apm_power: only unset own apm_get_power_status (git-fixes).\n- power: supply: bq256xx: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: bq25980: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: bq27xxx: fix wrong errno when bus ops are unsupported (git-fixes).\n- power: supply: cpcap-battery: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: cw2015: Check devm_delayed_work_autocancel() return code (git-fixes).\n- power: supply: goldfish: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: qcom_battmgr: Recognize \"LiP\" as lithium-polymer (git-fixes).\n- power: supply: rt9455: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: rt9467: Prevent using uninitialized local variable in rt9467_set_value_from_ranges() (git-fixes).\n- power: supply: rt9467: Return error on failure in rt9467_set_value_from_ranges() (git-fixes).\n- power: supply: sbs-battery: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: wm831x: Check wm831x_set_bits() return value (git-fixes).\n- power: supply: wm97xx: Fix NULL pointer dereference in power_supply_changed() (git-fixes).\n- powercap: fix race condition in register_control_type() (stable-fixes).\n- powercap: fix sscanf() error return value handling (stable-fixes).\n- powercap: intel_rapl_tpmi: Remove FW_BUG from invalid version check (git-fixes).\n- powerpc/64s/slb: Fix SLB multihit issue during SLB preload (bac#1236022 ltc#211187).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling (bsc#1253262 ltc#216029).\n- powerpc/kexec: Enable SMT before waking offline CPUs (bsc#1214285 bsc#1205462 bsc#1253739 bsc#1254244).\n- pwm: bcm2835: Make sure the channel is enabled after pwm_request() (git-fixes).\n- rapidio: replace rio_free_net() with kfree() in rio_scan_alloc_net() (git-fixes).\n- regmap: Fix race condition in hwspinlock irqsave routine (git-fixes).\n- regmap: maple: free entry on mas_store_gfp() failure (stable-fixes).\n- regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex (git-fixes).\n- regulator: core: disable supply if enabling main regulator fails (git-fixes).\n- regulator: core: fix locking in regulator_resolve_supply() error path (git-fixes).\n- regulator: core: move supply check earlier in set_machine_constraints() (git-fixes).\n- remove a bpf CVE change which is already part of the base kernel\n- remove an Intel CPU model change which is already part of the base kernel\n- reset: fix BIT macro reference (stable-fixes).\n- rpm/mkspec-dtb: add riscv64 dtb-thead subpackage\n- rpmsg: core: fix race in driver_override_show() and use core helper (git-fixes).\n- rpmsg: glink: fix rpmsg device leak (git-fixes).\n- rtc: gamecube: Check the return value of ioremap() (git-fixes).\n- rtc: interface: Alarm race handling should not discard preceding error (git-fixes).\n- rtc: zynqmp: correct frequency value (stable-fixes).\n- sched: Increase sched_tick_remote timeout (bsc#1254510).\n- scripts/python/git_sort/git_sort.yaml: add cifs for-next repository\n- scripts: obsapi: Support URL trailing / in oscrc\n- scripts: teaapi: Add paging\n- scripts: uploader: Fix no change condition for _maintainership.json\n- scripts: uploader: Handle missing upstream in is_pr_open\n- scrits: teaapi: Add list_repos\n- scsi: lpfc: Add capability to register Platform Name ID to fabric (bsc#1254119).\n- scsi: lpfc: Allow support for BB credit recovery in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Ensure unregistration of rpis for received PLOGIs (bsc#1254119).\n- scsi: lpfc: Fix leaked ndlp krefs when in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI (bsc#1254119).\n- scsi: lpfc: Modify kref handling for Fabric Controller ndlps (bsc#1254119).\n- scsi: lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb() (bsc#1254119).\n- scsi: lpfc: Revise discovery related function headers and comments (bsc#1254119).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256861).\n- scsi: lpfc: Update lpfc version to 14.4.0.12 (bsc#1254119).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256861).\n- scsi: lpfc: Update various NPIV diagnostic log messaging (bsc#1254119).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256863).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256863).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256863).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256863).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256863).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256863).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256863).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256863).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256863).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256863).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256863).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256863).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests/bpf: Skip timer cases when bpf_timer is not supported (git-fixes).\n- serial: 8250: 8250_omap.c: Clear DMA RX running status only after DMA termination is done (stable-fixes).\n- serial: 8250_dw: handle clock enable errors in runtime_resume (stable-fixes).\n- serial: 8250_pci: Fix broken RS485 for F81504/508/512 (git-fixes).\n- serial: SH_SCI: improve \"DMA support\" prompt (git-fixes).\n- serial: add support of CPCI cards (stable-fixes).\n- serial: amba-pl011: prefer dma_mapping_error() over explicit address checking (git-fixes).\n- serial: imx: change SERIAL_IMX_CONSOLE to bool (git-fixes).\n- serial: sprd: Return -EPROBE_DEFER when uart clock is not ready (stable-fixes).\n- shrink_slab_memcg: clear_bits of skipped shrinkers (bsc#1256564).\n- slimbus: core: fix OF node leak on registration failure (git-fixes).\n- slimbus: core: fix device reference leak on report present (git-fixes).\n- slimbus: core: fix of_slim_get_device() kernel doc (git-fixes).\n- slimbus: core: fix runtime PM imbalance on report present (git-fixes).\n- slimbus: ngd: Fix reference count leak in qcom_slim_ngd_notify_slaves (git-fixes).\n- smb3: add missing null server pointer check (git-fixes).\n- smb: change return type of cached_dir_lease_break() to bool (git-fixes).\n- smb: client: ensure open_cached_dir_by_dentry() only returns valid cfid (git-fixes).\n- smb: client: fix cifs_pick_channel when channel needs reconnect (git-fixes).\n- smb: client: fix warning when reconnecting channel (git-fixes).\n- smb: client: introduce close_cached_dir_locked() (git-fixes).\n- smb: client: remove unused fid_lock (git-fixes).\n- smb: client: short-circuit in open_cached_dir_by_dentry() if !dentry (git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748,bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- smc91x: fix broken irq-context in PREEMPT_RT (git-fixes).\n- soc/tegra: fuse: speedo-tegra210: Update speedo IDs (git-fixes).\n- soc: amlogic: canvas: fix device leak on lookup (git-fixes).\n- soc: mediatek: svs: Fix memory leak in svs_enable_debug_write() (git-fixes).\n- soc: qcom: cmd-db: Use devm_memremap() to fix memory leak in cmd_db_dev_probe (git-fixes).\n- soc: qcom: ocmem: fix device leak on lookup (git-fixes).\n- soc: qcom: smem: fix hwspinlock resource leak in probe error paths (git-fixes).\n- soc: qcom: smem: handle ENOMEM error during probe (git-fixes).\n- soc: ti: k3-socinfo: Fix regmap leak on probe failure (git-fixes).\n- soc: ti: pruss: Fix double free in pruss_clk_mux_setup() (git-fixes).\n- soundwire: dmi-quirks: add mapping for Avell B.ON (OEM rebranded of NUC15) (stable-fixes).\n- spi-geni-qcom: initialize mode related registers to 0 (stable-fixes).\n- spi-geni-qcom: use xfer-\u003ebits_per_word for can_dma() (stable-fixes).\n- spi: amlogic-spifc-a1: Handle devm_pm_runtime_enable() errors (git-fixes).\n- spi: bcm63xx: drop wrong casts in probe() (git-fixes).\n- spi: bcm63xx: fix premature CS deassertion on RX-only transactions (git-fixes).\n- spi: fsl-cpm: Check length parity before switching to 16 bit mode (git-fixes).\n- spi: imx: keep dma request disabled before dma transfer setup (stable-fixes).\n- spi: spi-mem: Limit octal DTR constraints to octal DTR situations (stable-fixes).\n- spi: spi-mem: Protect dirmap_create() with spi_mem_access_start/end (stable-fixes).\n- spi: spi-sprd-adi: Fix double free in probe error path (git-fixes).\n- spi: sprd-adi: switch to use spi_alloc_host() (stable-fixes).\n- spi: sprd: adi: Use devm_register_restart_handler() (stable-fixes).\n- spi: stm32: fix Overrun issue at \u0026lt; 8bpw (stable-fixes).\n- spi: tegra114: Preserve SPI mode bits in def_command1_reg (git-fixes).\n- spi: tegra210-qspi: Remove cache operations (git-fixes)\n- spi: tegra210-quad: Add support for internal DMA (git-fixes)\n- spi: tegra210-quad: Check hardware status on timeout (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (git-fixes).\n- spi: tegra210-quad: Move curr_xfer read inside spinlock (bsc#1257952)\n- spi: tegra210-quad: Move curr_xfer read inside spinlock (git-fixes).\n- spi: tegra210-quad: Protect curr_xfer assignment in (bsc#1257952)\n- spi: tegra210-quad: Protect curr_xfer assignment in tegra_qspi_setup_transfer_one (git-fixes).\n- spi: tegra210-quad: Protect curr_xfer check in IRQ handler (bsc#1257952)\n- spi: tegra210-quad: Protect curr_xfer check in IRQ handler (git-fixes).\n- spi: tegra210-quad: Protect curr_xfer clearing in (bsc#1257952)\n- spi: tegra210-quad: Protect curr_xfer clearing in tegra_qspi_non_combined_seq_xfer (git-fixes).\n- spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer (bsc#1257952)\n- spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer (git-fixes).\n- spi: tegra210-quad: Refactor error handling into helper functions (bsc#1253155)\n- spi: tegra210-quad: Return IRQ_HANDLED when timeout already processed (bsc#1257952)\n- spi: tegra210-quad: Return IRQ_HANDLED when timeout already processed transfer (git-fixes).\n- spi: tegra210-quad: Update dummy sequence configuration (git-fixes)\n- spi: tegra: Fix a memory leak in tegra_slink_probe() (git-fixes).\n- spi: wpcm-fiu: Fix potential NULL pointer dereference in wpcm_fiu_probe() (git-fixes).\n- spi: wpcm-fiu: Fix uninitialized res (git-fixes).\n- spi: wpcm-fiu: Simplify with dev_err_probe() (stable-fixes).\n- spi: wpcm-fiu: Use devm_platform_ioremap_resource_byname() (stable-fixes).\n- spi: xilinx: increase number of retries before declaring stall (stable-fixes).\n- staging: fbtft: core: fix potential memory leak in fbtft_probe_common() (git-fixes).\n- staging: rtl8723bs: fix memory leak on failure path (stable-fixes).\n- staging: rtl8723bs: fix null dereference in find_network (git-fixes).\n- staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing (stable-fixes).\n- staging: rtl8723bs: fix out-of-bounds read in rtw_get_ie() parser (stable-fixes).\n- supported.conf: Mark lan 743x supported (jsc#PED-14571)\n- thermal: int340x: Fix sysfs group leak on DLVR registration failure (stable-fixes).\n- thunderbolt: Add support for Intel Wildcat Lake (stable-fixes).\n- tools/power cpupower: Reset errno before strtoull() (stable-fixes).\n- tools/power/x86/intel-speed-select: Fix file descriptor leak in isolate_cpus() (git-fixes).\n- tpm: st33zp24: Fix missing cleanup on get_burstcount() error (git-fixes).\n- tpm: tpm_i2c_infineon: Fix locality leak on get_burstcount() failure (git-fixes).\n- tracing: Fix access to trace_event_file (bsc#1254373).\n- uacce: ensure safe queue release with state management (git-fixes).\n- uacce: fix cdev handling in the cleanup path (git-fixes).\n- uacce: fix isolate sysfs check condition (git-fixes).\n- uacce: implement mremap in uacce_vm_ops to return -EPERM (git-fixes).\n- uio: uio_fsl_elbc_gpcm:: Add null pointer check to uio_fsl_elbc_gpcm_probe (git-fixes).\n- usb: bdc: fix sleep during atomic (git-fixes).\n- usb: cdns3: Fix double resource release in cdns3_pci_probe (git-fixes).\n- usb: chaoskey: fix locking for O_NONBLOCK (git-fixes).\n- usb: chipidea: udc: limit usb request length to max 16KB (stable-fixes).\n- usb: core: add USB_QUIRK_NO_BOS for devices that hang on BOS descriptor (stable-fixes).\n- usb: dwc2: disable platform lowlevel hw resources during shutdown (stable-fixes).\n- usb: dwc2: fix hang during shutdown if set as peripheral (git-fixes).\n- usb: dwc2: fix hang during suspend if set as peripheral (git-fixes).\n- usb: dwc2: fix resume failure if dr_mode is host (git-fixes).\n- usb: dwc3: Abort suspend on soft disconnect failure (git-fixes).\n- usb: dwc3: Check for USB4 IP_NAME (stable-fixes).\n- usb: dwc3: Fix race condition between concurrent dwc3_remove_requests() call paths (git-fixes).\n- usb: dwc3: keep susphy enabled during exit to avoid controller faults (git-fixes).\n- usb: dwc3: of-simple: fix clock resource leak in dwc3_of_simple_probe (git-fixes).\n- usb: dwc3: pci: Sort out the Intel device IDs (stable-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -S (stable-fixes).\n- usb: gadget: configfs: Correctly set use_os_string at bind (git-fixes).\n- usb: gadget: f_eem: Fix memory leak in eem_unwrap (git-fixes).\n- usb: gadget: lpc32xx_udc: fix clock imbalance in error path (git-fixes).\n- usb: gadget: renesas_usbf: Handle devm_pm_runtime_enable() errors (git-fixes).\n- usb: gadget: tegra-xudc: Add handling for BLCG_COREPLL_PWRDN (git-fixes).\n- usb: gadget: tegra-xudc: Always reinitialize data toggle when clear halt (git-fixes).\n- usb: ohci-nxp: Use helper function devm_clk_get_enabled() (stable-fixes).\n- usb: ohci-nxp: fix device leak on probe failure (git-fixes).\n- usb: phy: Initialize struct usb_phy list_head (git-fixes).\n- usb: phy: isp1301: fix non-OF device reference imbalance (git-fixes).\n- usb: raw-gadget: cap raw_io transfer length to KMALLOC_MAX_SIZE (git-fixes).\n- usb: raw-gadget: do not limit transfer length (git-fixes).\n- usb: renesas_usbhs: Fix a resource leak in usbhs_pipe_malloc() (git-fixes).\n- usb: storage: Fix memory leak in USB bulk transport (git-fixes).\n- usb: storage: sddr55: Reject out-of-bound new_pba (stable-fixes).\n- usb: typec: tipd: Clear interrupts first (git-fixes).\n- usb: typec: ucsi: Handle incorrect num_connectors capability (stable-fixes).\n- usb: typec: ucsi: psy: Set max current to zero when disconnected (git-fixes).\n- usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer (git-fixes).\n- usb: udc: Add trace event for usb_gadget_set_state (stable-fixes).\n- usb: usb-storage: Maintain minimal modifications to the bcdDevice range (git-fixes).\n- usb: usb-storage: No additional quirks need to be added to the EL-R12 optical drive (stable-fixes).\n- usb: vhci-hcd: Prevent suspending virtually attached devices (git-fixes).\n- usb: xhci: limit run_graceperiod for only usb 3.0 devices (stable-fixes).\n- usbip: Fix locking bug in RT-enabled kernels (stable-fixes).\n- usbnet: limit max_mtu based on device's hard_mtu (git-fixes).\n- via_wdt: fix critical boot hang due to unnamed resource allocation (stable-fixes).\n- virtio_console: fix order of fields cols and rows (stable-fixes).\n- w1: fix redundant counter decrement in w1_attach_slave_device() (git-fixes).\n- w1: therm: Fix off-by-one buffer overflow in alarms_store (git-fixes).\n- watchdog: imx7ulp_wdt: handle the nowayout option (stable-fixes).\n- watchdog: wdat_wdt: Fix ACPI table leak in probe function (git-fixes).\n- wifi: ath10k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: ath10k: fix lock protection in ath10k_wmi_event_peer_sta_ps_state_chg() (stable-fixes).\n- wifi: ath10k: sdio: add missing lock protection in ath10k_sdio_fw_crashed_dump() (git-fixes).\n- wifi: ath11k: add pm quirk for Thinkpad Z13/Z16 Gen1 (stable-fixes).\n- wifi: ath11k: fix peer HE MCS assignment (git-fixes).\n- wifi: ath11k: restore register window after global reset (git-fixes).\n- wifi: ath12k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: ath12k: fix preferred hardware mode calculation (stable-fixes).\n- wifi: ath9k: debug.h: fix kernel-doc bad lines and struct ath_tx_stats (git-fixes).\n- wifi: ath9k: fix kernel-doc warnings in common-debug.h (git-fixes).\n- wifi: avoid kernel-infoleak from struct iw_point (git-fixes).\n- wifi: brcmfmac: Add DMI nvram filename quirk for Acer A1 840 tablet (stable-fixes).\n- wifi: cfg80211: Fix bitrate calculation overflow for HE rates (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n- wifi: cfg80211: cancel rfkill_block work in wiphy_unregister() (git-fixes).\n- wifi: cfg80211: sme: store capped length in __cfg80211_connect_result() (git-fixes).\n- wifi: cfg80211: stop NAN and P2P in cfg80211_leave (git-fixes).\n- wifi: cfg80211: wext: fix IGTK key ID off-by-one (git-fixes).\n- wifi: cw1200: Fix potential memory leak in cw1200_bh_rx_helper() (git-fixes).\n- wifi: ieee80211: correct FILS status codes (git-fixes).\n- wifi: iwlegacy: add missing mutex protection in il3945_store_measurement() (stable-fixes).\n- wifi: iwlegacy: add missing mutex protection in il4965_store_tx_power() (stable-fixes).\n- wifi: iwlwifi: mvm: check the validity of noa_len (stable-fixes).\n- wifi: libertas: fix WARNING in usb_tx_block (stable-fixes).\n- wifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration (git-fixes).\n- wifi: mac80211: collect station statistics earlier when disconnect (stable-fixes).\n- wifi: mac80211: correctly check if CSA is active (stable-fixes).\n- wifi: mac80211: correctly decode TTLM with default link map (git-fixes).\n- wifi: mac80211: do not increment crypto_tx_tailroom_needed_cnt twice (stable-fixes).\n- wifi: mac80211: do not use old MBSSID elements (git-fixes).\n- wifi: mac80211: fix CMAC functions not handling errors (git-fixes).\n- wifi: mac80211: fix NULL pointer dereference in mesh_rx_csa_frame() (git-fixes).\n- wifi: mac80211: ocb: skip rx_no_sta when interface is not joined (stable-fixes).\n- wifi: mac80211: restore non-chanctx injection behaviour (git-fixes).\n- wifi: mt76: Fix DTS power-limits on little endian systems (git-fixes).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- wifi: nl80211: vendor-cmd: intel: fix a blank kernel-doc line warning (git-fixes).\n- wifi: radiotap: reject radiotap with unknown bits (git-fixes).\n- wifi: rsi: Fix memory corruption due to not set vif driver data size (git-fixes).\n- wifi: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring() (git-fixes).\n- wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb() (git-fixes).\n- wifi: rtl8xxxu: fix slab-out-of-bounds in rtl8xxxu_sta_add (git-fixes).\n- wifi: rtlwifi: 8192cu: fix tid out of range in rtl92cu_tx_fill_desc() (git-fixes).\n- wifi: rtw88: 8822b: Avoid WARNING in rtw8822b_config_trx_mode() (stable-fixes).\n- wifi: rtw88: Add USB ID 2001:3329 for D-Link AC13U rev. A1 (stable-fixes).\n- wifi: rtw88: Fix alignment fault in rtw_core_enable_beacon() (git-fixes).\n- wifi: rtw88: fix DTIM period handling when conf-\u003edtim_period is zero (stable-fixes).\n- wifi: rtw88: limit indirect IO under powered off for RTL8822CS (git-fixes).\n- wifi: rtw88: rtw8821cu: Add ID for Mercusys MU6H (stable-fixes).\n- wifi: rtw89: pci: restore LDO setting after device resume (stable-fixes).\n- wifi: rtw89: wow: add reason codes for disassociation in WoWLAN mode (stable-fixes).\n- wifi: wlcore: ensure skb headroom before skb_push (stable-fixes).\n- workqueue: mark power efficient workqueue as unbounded if (bsc#1257891)\n- x86/hyperv: Fix APIC ID and VP index confusion in hv_snp_boot_ap() (git-fixes).\n- x86/microcode/AMD: Add TSA microcode SHAs (bsc#1256528).\n- x86/microcode/AMD: Add Zen5 model 0x44, stepping 0x1 minrev (bsc#1256528).\n- x86/microcode/AMD: Add more known models to entry sign checking (bsc#1256528).\n- x86/microcode/AMD: Add some forgotten models to the SHA check (bsc#1256528).\n- x86/microcode/AMD: Clean the cache if update did not load microcode (bsc#1256528).\n- x86/microcode/AMD: Extend the SHA check to Zen5, block loading of any unreleased standalone Zen5 microcode patches (bsc#1256528).\n- x86/microcode/AMD: Fix Entrysign revision check for Zen5/Strix Halo (bsc#1256528).\n- x86/microcode/AMD: Fix __apply_microcode_amd()'s return value (bsc#1256528).\n- x86/microcode/AMD: Limit Entrysign signature checking to known generations (bsc#1256528).\n- x86/microcode/AMD: Load only SHA256-checksummed patches (bsc#1256528).\n- x86/microcode/AMD: Select which microcode patch to load (bsc#1256528).\n- x86/microcode/AMD: Use sha256() instead of init/update/final (bsc#1256528).\n- x86/microcode: Fix Entrysign revision check for Zen1/Naples (bsc#1256528).\n- x86: make page fault handling disable interrupts properly (git-fixes).\n- xhci: dbgtty: fix device unregister (git-fixes).\n","status":"published","published":"2026-03-24T16:48:38Z","modified":"2026-03-28T17:24:51.593455Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20876-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and 6.1 RT kernel was updated to receive various security bugfixes.\n\n\nThe following security bugs were fixed:\n\n- CVE-2023-53817: crypto: lib/mpi - avoid null pointer deref in mpi_cmp_ui() (bsc#1254992).\n- CVE-2025-37861: scsi: mpi3mr: Synchronous access b/w reset and tm thread for reply queue (bsc#1243055).\n- CVE-2025-38321: smb: Log an error when close_all_cached_dirs fails (bsc#1246328).\n- CVE-2025-38728: smb3: fix for slab out of bounds on mount to ksmbd (bsc#1249256).\n- CVE-2025-39748: bpf: Forget ranges when refining tnum after JSET (bsc#1249587).\n- CVE-2025-39880: libceph: fix invalid accesses to ceph_connection_v1_info (bsc#1250388).\n- CVE-2025-39890: wifi: ath12k: fix memory leak in ath12k_service_ready_ext_event (bsc#1250334).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-39977: futex: Prevent use-after-free during requeue-PI (bsc#1252046).\n- CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted (bsc#1252342).\n- CVE-2025-40024: vhost: Take a reference on the task in struct vhost_task (bsc#1252686).\n- CVE-2025-40033: remoteproc: pru: Fix potential NULL pointer dereference in pru_rproc_set_ctable() (bsc#1252824).\n- CVE-2025-40042: tracing: Fix race condition in kprobe initialization causing NULL pointer dereference (bsc#1252861).\n- CVE-2025-40053: net: dlink: handle copy_thresh allocation failure (bsc#1252808).\n- CVE-2025-40081: perf: arm_spe: Prevent overflow in PERF_IDX2OFF() (bsc#1252776).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40123: bpf: Enforce expected_attach_type for tailcall compatibility (bsc#1253365).\n- CVE-2025-40134: dm: fix NULL pointer dereference in __dm_suspend() (bsc#1253386).\n- CVE-2025-40135: ipv6: use RCU in ip6_xmit() (bsc#1253342).\n- CVE-2025-40153: mm: hugetlb: avoid soft lockup when mprotect to large memory area (bsc#1253408).\n- CVE-2025-40158: ipv6: use RCU in ip6_output() (bsc#1253402).\n- CVE-2025-40160: xen/events: Cleanup find_virq() return codes (bsc#1253400).\n- CVE-2025-40167: ext4: detect invalid INLINE_DATA + EXTENTS flag combination (bsc#1253458).\n- CVE-2025-40170: net: use dst_dev_rcu() in sk_setup_caps() (bsc#1253413).\n- CVE-2025-40178: pid: Add a judgment for ns null in pid_nr_ns (bsc#1253463).\n- CVE-2025-40179: ext4: verify orphan file size is not too big (bsc#1253442).\n- CVE-2025-40187: net/sctp: fix a null dereference in sctp_disposition sctp_sf_do_5_1D_ce() (bsc#1253647).\n- CVE-2025-40190: ext4: guard against EA inode refcount underflow in xattr update (bsc#1253623).\n- CVE-2025-40192: Revert \"ipmi: fix msg stack when IPMI is disconnected\" (bsc#1253622).\n- CVE-2025-40220: fuse: fix livelock in synchronous file put from fuseblk workers (bsc#1254520).\n- CVE-2025-40231: vsock: fix lock inversion in vsock_assign_transport() (bsc#1254815).\n- CVE-2025-40233: ocfs2: clear extent cache after moving/defragmenting extents (bsc#1254813).\n- CVE-2025-40238: net/mlx5: Fix IPsec cleanup over MPV device (bsc#1254871).\n- CVE-2025-40240: sctp: avoid NULL dereference when chunk data buffer is missing (bsc#1254869).\n- CVE-2025-40242: gfs2: Fix unlikely race in gdlm_put_lock (bsc#1255075).\n- CVE-2025-40248: vsock: Ignore signal/timeout on connect() if already established (bsc#1254864).\n- CVE-2025-40250: net/mlx5: Clean up only new IRQ glue on request_irq() failure (bsc#1254854).\n- CVE-2025-40251: devlink: rate: Unset parent pointer in devl_rate_nodes_destroy (bsc#1254856).\n- CVE-2025-40252: net: qlogic/qede: fix potential out-of-bounds read in qede_tpa_cont() and qede_tpa_end() (bsc#1254849).\n- CVE-2025-40254: net: openvswitch: remove never-working support for setting nsh fields (bsc#1254852).\n- CVE-2025-40257: mptcp: fix a race in mptcp_pm_del_add_timer() (bsc#1254842).\n- CVE-2025-40258: mptcp: fix race condition in mptcp_schedule_work() (bsc#1254843).\n- CVE-2025-40259: scsi: sg: Do not sleep in atomic context (bsc#1254845).\n- CVE-2025-40261: nvme: nvme-fc: Ensure -\u003eioerr_work is cancelled in nvme_fc_delete_ctrl() (bsc#1254839).\n- CVE-2025-40264: be2net: pass wrb_params in case of OS2BMC (bsc#1254835).\n- CVE-2025-40268: cifs: client: fix memory leak in smb3_fs_context_parse_param (bsc#1255082).\n- CVE-2025-40271: fs/proc: fix uaf in proc_readdir_de() (bsc#1255297).\n- CVE-2025-40274: KVM: guest_memfd: Remove bindings on memslot deletion when gmem is dying (bsc#1254830).\n- CVE-2025-40278: net: sched: act_ife: initialize struct tc_ife to fix KMSAN kernel-infoleak (bsc#1254825).\n- CVE-2025-40279: net: sched: act_connmark: initialize struct tc_ife to fix kernel leak (bsc#1254846).\n- CVE-2025-40280: tipc: Fix use-after-free in tipc_mon_reinit_self() (bsc#1254847).\n- CVE-2025-40289: drm/amdgpu: hide VRAM sysfs attributes on GPUs without VRAM (bsc#1255042).\n- CVE-2025-40292: virtio-net: fix received length check in big packets (bsc#1255175).\n- CVE-2025-40293: iommufd: Don't overflow during division for dirty tracking (bsc#1255179).\n- CVE-2025-40297: net: bridge: fix use-after-free due to MST port state bypass (bsc#1255187).\n- CVE-2025-40307: exfat: validate cluster allocation bits of the allocation bitmap (bsc#1255039).\n- CVE-2025-40319: bpf: Sync pending IRQ work before freeing ring buffer (bsc#1254794).\n- CVE-2025-40328: smb: client: fix potential UAF in smb2_close_cached_fid() (bsc#1254624).\n- CVE-2025-40331: sctp: Prevent TOCTOU out-of-bounds write (bsc#1254615).\n- CVE-2025-40338: ASoC: Intel: avs: Do not share the name pointer between components (bsc#1255273).\n- CVE-2025-40339: drm/amdgpu: fix nullptr err of vm_handle_moved (bsc#1255428).\n- CVE-2025-40346: arch_topology: Fix incorrect error check in topology_parse_cpu_capacity() (bsc#1255318).\n- CVE-2025-40350: net/mlx5e: RX, Fix generating skb from non-linear xdp_buff for striding RQ (bsc#1255260).\n- CVE-2025-40355: sysfs: check visibility before changing group attribute ownership (bsc#1255261).\n- CVE-2025-40360: drm/sysfb: Do not dereference NULL pointer in plane reset (bsc#1255095).\n- CVE-2025-40363: net: ipv6: fix field-spanning memcpy warning in AH output (bsc#1255102).\n- CVE-2025-68171: x86/fpu: Ensure XFD state on signal delivery (bsc#1255255).\n- CVE-2025-68174: amd/amdkfd: enhance kfd process check in switch partition (bsc#1255327).\n- CVE-2025-68178: blk-cgroup: fix possible deadlock while configuring policy (bsc#1255266).\n- CVE-2025-68188: tcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check() (bsc#1255269).\n- CVE-2025-68190: drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked() (bsc#1255131).\n- CVE-2025-68200: bpf: Add bpf_prog_run_data_pointers() (bsc#1255241).\n- CVE-2025-68201: drm/amdgpu: remove two invalid BUG_ON()s (bsc#1255136).\n- CVE-2025-68204: pmdomain: arm: scmi: Fix genpd leak on provider registration failure (bsc#1255224).\n- CVE-2025-68206: netfilter: nft_ct: add seqadj extension for natted connections (bsc#1255142).\n- CVE-2025-68208: bpf: account for current allocated stack depth in widen_imprecise_scalars() (bsc#1255227).\n- CVE-2025-68209: mlx5: Fix default values in create CQ (bsc#1255230).\n- CVE-2025-68227: mptcp: Fix proto fallback detection with BPF (bsc#1255216).\n- CVE-2025-68230: drm/amdgpu: fix gpu page fault after hibernation on PF passthrough (bsc#1255134).\n- CVE-2025-68239: binfmt_misc: restore write access before closing files opened by open_exec() (bsc#1255272).\n- CVE-2025-68241: ipv4: route: Prevent rt_bind_exception() from rebinding stale fnhe (bsc#1255157).\n- CVE-2025-68245: net: netpoll: fix incorrect refcount handling causing incorrect cleanup (bsc#1255268).\n- CVE-2025-68255: staging: rtl8723bs: fix stack buffer overflow in OnAssocReq IE parsing (bsc#1255395).\n- CVE-2025-68259: KVM: SVM: Don't skip unrelated instruction if INT3/INTO is replaced (bsc#1255199).\n- CVE-2025-68261: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() (bsc#1255164).\n- CVE-2025-68264: ext4: refresh inline data size before write operations (bsc#1255380).\n- CVE-2025-68283: libceph: replace BUG_ON with bounds check for map-\u003emax_osd (bsc#1255379).\n- CVE-2025-68284: libceph: prevent potential out-of-bounds writes in handle_auth_session_key() (bsc#1255377).\n- CVE-2025-68285: libceph: fix potential use-after-free in have_mon_and_osd_map() (bsc#1255401).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68296: drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup (bsc#1255128).\n- CVE-2025-68297: ceph: fix crash in process_v2_sparse_read() for encrypted directories (bsc#1255403).\n- CVE-2025-68301: net: atlantic: fix fragment overflow handling in RX path (bsc#1255120).\n- CVE-2025-68320: lan966x: Fix sleeping in atomic context (bsc#1255172).\n- CVE-2025-68325: net/sched: sch_cake: Fix incorrect qlen reduction in cake_drop (bsc#1255417).\n- CVE-2025-68327: usb: renesas_usbhs: Fix synchronous external abort on unbind (bsc#1255488).\n- CVE-2025-68337: jbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted (bsc#1255482).\n- CVE-2025-68340: team: Move team device type change at the end of team_port_add (bsc#1255507).\n- CVE-2025-68349: NFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid (bsc#1255544).\n- CVE-2025-68363: bpf: Check skb-\u003etransport_header is set in bpf_skb_check_mtu (bsc#1255552).\n- CVE-2025-68365: fs/ntfs3: Initialize allocated memory before use (bsc#1255548).\n- CVE-2025-68366: nbd: defer config unlock in nbd_genl_connect (bsc#1255622).\n- CVE-2025-68367: macintosh/mac_hid: fix race condition in mac_hid_toggle_emumouse (bsc#1255547).\n- CVE-2025-68372: nbd: defer config put in recv_work (bsc#1255537).\n- CVE-2025-68374: md: fix rcu protection in md_wakeup_thread (bsc#1255530).\n- CVE-2025-68378: bpf: Refactor stack map trace depth calculation into helper function (bsc#1255614).\n- CVE-2025-68379: RDMA/rxe: Fix null deref on srq-\u003erq.queue after resize failure (bsc#1255695).\n- CVE-2025-68727: ntfs3: Fix uninit buffer allocated by __getname() (bsc#1255568).\n- CVE-2025-68728: ntfs3: fix uninit memory after failed mi_read in mi_format_new (bsc#1255539).\n- CVE-2025-68733: smack: fix bug: unprivileged task can create labels (bsc#1255615).\n- CVE-2025-68736: landlock: Fix handling of disconnected directories (bsc#1255698).\n- CVE-2025-68742: bpf: Improve program stats run-time calculation (bsc#1255707).\n- CVE-2025-68744: bpf: Free special fields when update [lru_,]percpu_hash maps (bsc#1255709).\n- CVE-2025-68764: NFS: Automounted filesystems should inherit ro,noexec,nodev,sync flags (bsc#1255930).\n- CVE-2025-68768: inet: frags: add inet_frag_queue_flush() (bsc#1256579).\n- CVE-2025-68770: bnxt_en: Fix XDP_TX path (bsc#1256584).\n- CVE-2025-68771: ocfs2: fix kernel BUG in ocfs2_find_victim_chain (bsc#1256582).\n- CVE-2025-68775: net/handshake: duplicate handshake cancellations leak socket (bsc#1256665).\n- CVE-2025-68776: net/hsr: fix NULL pointer dereference in prp_get_untagged_frame() (bsc#1256659).\n- CVE-2025-68778: btrfs: don't log conflicting inode if it's a dir moved in the current transaction (bsc#1256683).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68788: fsnotify: do not generate ACCESS/MODIFY events on child for special files (bsc#1256638).\n- CVE-2025-68795: ethtool: Avoid overflowing userspace buffer on stats query (bsc#1256688).\n- CVE-2025-68798: perf/x86/amd: Check event before enable to avoid GPF (bsc#1256689).\n- CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats (bsc#1256646).\n- CVE-2025-68801: mlxsw: spectrum_router: Fix neighbour use-after-free (bsc#1256653).\n- CVE-2025-68803: nfsd: set security label during create operations (bsc#1256770).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-68813: ipvs: fix ipv4 null-ptr-deref in route error path (bsc#1256641).\n- CVE-2025-68814: io_uring: fix filename leak in __io_openat_prep() (bsc#1256651).\n- CVE-2025-68815: net/sched: ets: Remove drr class from the active list if it changes to strict (bsc#1256680).\n- CVE-2025-68816: net/mlx5: fw_tracer, Validate format string parameters (bsc#1256674).\n- CVE-2025-68820: ext4: xattr: fix null pointer deref in ext4_raw_inode() (bsc#1256754).\n- CVE-2025-71064: net: hns3: using the num_tqps in the vf driver to apply for resources (bsc#1256654).\n- CVE-2025-71066: net/sched: ets: Always remove class from active list before deleting in ets_qdisc_change (bsc#1256645).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71077: tpm: Cap the number of PCR banks (bsc#1256613).\n- CVE-2025-71084: RDMA/cm: Fix leaking the multicast GID table reference (bsc#1256622).\n- CVE-2025-71085: ipv6: BUG() in pskb_expand_head() as part of calipso_skbuff_setattr() (bsc#1256623).\n- CVE-2025-71087: iavf: fix off-by-one issues in iavf_config_rss_reg() (bsc#1256628).\n- CVE-2025-71088: mptcp: fallback earlier on simult connection (bsc#1256630).\n- CVE-2025-71089: iommu: disable SVA when CONFIG_X86 is set (bsc#1256612).\n- CVE-2025-71091: team: fix check for port enabled in team_queue_override_port_prio_changed() (bsc#1256773).\n- CVE-2025-71093: e1000: fix OOB in e1000_tbi_should_accept() (bsc#1256777).\n- CVE-2025-71094: net: usb: asix: ax88772: Increase phy_name size (bsc#1256597).\n- CVE-2025-71095: net: stmmac: fix the crash issue for zero copy XDP_TX action (bsc#1256605).\n- CVE-2025-71096: RDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly (bsc#1256606).\n- CVE-2025-71097: ipv4: Fix reference count leak when using error routes with nexthop objects (bsc#1256607).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71112: net: hns3: add VLAN id validation before using (bsc#1256726).\n- CVE-2025-71113: crypto: af_alg - zero initialize memory allocated via sock_kmalloc (bsc#1256716).\n- CVE-2025-71116: libceph: make decode_pool() more resilient against corrupted osdmaps (bsc#1256744).\n- CVE-2025-71120: SUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf (bsc#1256779).\n- CVE-2025-71123: ext4: fix string copying in parse_apply_sb_mount_options() (bsc#1256757).\n- CVE-2025-71126: mptcp: reset fallback status gracefully at disconnect() time (bsc#1256755).\n- CVE-2025-71133: RDMA/irdma: avoid invalid read in irdma_net_event (bsc#1256733).\n- CVE-2025-71135: md/raid5: fix possible null-pointer dereferences in raid5_store_group_thread_cnt() (bsc#1256761).\n- CVE-2025-71137: octeontx2-pf: fix \"UBSAN: shift-out-of-bounds error\" (bsc#1256760).\n- CVE-2025-71148: net/handshake: restore destructor on submit failure (bsc#1257159).\n- CVE-2025-71149: io_uring/poll: correctly handle io_poll_add() return value on update (bsc#1257164).\n- CVE-2025-71184: btrfs: fix NULL dereference on root when tracing inode eviction (bsc#1257635).\n- CVE-2025-71194: btrfs: fix deadlock in wait_current_trans() due to ignored transaction type (bsc#1257687).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22976: net/sched: sch_qfq: Fix NULL deref when deactivating inactive aggregate in qfq_reset (bsc#1257035).\n- CVE-2026-22977: net: sock: fix hardened usercopy panic in sock_recv_errqueue (bsc#1257053).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22982: net: mscc: ocelot: Fix crash when adding interface under a lag (bsc#1257179).\n- CVE-2026-22984: libceph: prevent potential out-of-bounds reads in handle_auth_done() (bsc#1257217).\n- CVE-2026-22990: libceph: replace overzealous BUG_ON in osdmap_apply_incremental() (bsc#1257221).\n- CVE-2026-22991: libceph: make free_choose_arg_map() resilient to partial allocation (bsc#1257220).\n- CVE-2026-22992: libceph: return the handler error from mon_handle_auth_done() (bsc#1257218).\n- CVE-2026-22996: net/mlx5e: Don't store mlx5e_priv in mlx5e_dev devlink priv.\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-22999: net/sched: sch_qfq: do not free existing class in qfq_change_class() (bsc#1257236).\n- CVE-2026-23000: net/mlx5e: Fix crash on profile change rollback failure (bsc#1257234).\n- CVE-2026-23001: macvlan: Use 'hash' iterators to simplify code (bsc#1257232).\n- CVE-2026-23003: geneve: Fix incorrect inner network header offset when innerprotoinherit is set (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23005: x86/fpu: Clear XSTATE_BV in guest XSAVE state whenever XFD[i]=1 (bsc#1257245).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23011: ipv4: ip_gre: make ipgre_header() robust (bsc#1257207).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23053: NFS: Fix a deadlock involving nfs_release_folio() (bsc#1257718).\n- CVE-2026-23057: vsock/virtio: Coalesce only linear skb (bsc#1257740).\n- CVE-2026-23060: crypto: authencesn - reject too-short AAD (assoclen\u003c8) to match ESP/ESN spec (bsc#1257735).\n- CVE-2026-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: fou: Don't allow 0 for FOU_ATTR_IPPROTO (bsc#1257745).\n- CVE-2026-23084: be2net: Fix NULL pointer dereference in be_cmd_get_mac_from_list (bsc#1257830).\n- CVE-2026-23085: irqchip/gic-v3-its: Avoid truncating memory addresses (bsc#1257758).\n- CVE-2026-23086: vsock/virtio: cap TX credit to local buffer size (bsc#1257757).\n- CVE-2026-23089: ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (bsc#1257790).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23102: arm64/fpsimd: signal: Mandate SVE payload for streaming-mode state (bsc#1257772).\n- CVE-2026-23104: ice: fix devlink reload call trace (bsc#1257763).\n- CVE-2026-23105: net/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag (bsc#1257775).\n- CVE-2026-23107: arm64/fpsimd: signal: Allocate SSVE storage when restoring ZA (bsc#1257762).\n- CVE-2026-23110: scsi: core: Wake up the error handler when final completions race against each other (bsc#1257761).\n- CVE-2026-23111: netfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate() (bsc#1258181).\n- CVE-2026-23112: nvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec (bsc#1258184).\n- CVE-2026-23113: io_uring/io-wq: check IO_WQ_BIT_EXIT inside work run loop (bsc#1258278).\n- CVE-2026-23116: pmdomain: imx8m-blk-ctrl: Remove separate rst and clk mask for 8mq vpu (bsc#1258277).\n- CVE-2026-23119: bonding: provide a net pointer to __skb_flow_dissect() (bsc#1258273).\n- CVE-2026-23139: netfilter: nf_conncount: update last_gc only when GC has been performed (bsc#1258304).\n- CVE-2026-23141: btrfs: send: check for inline extents in range_is_hole_in_parent() (bsc#1258377).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23171: net: bonding: update the slave array for broadcast mode (bsc#1258349).\n- CVE-2026-23173: net/mlx5e: TC, delete flows only for existing peers (bsc#1258520).\n- CVE-2026-23179: nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready() (bsc#1258394).\n- CVE-2026-23191: ALSA: aloop: Fix racy access at PCM trigger (bsc#1258395).\n- CVE-2026-23198: KVM: Don't clobber irqfd routing type when deassigning irqfd (bsc#1258321).\n- CVE-2026-23208: ALSA: usb-audio: Prevent excessive number of frames (bsc#1258468).\n- CVE-2026-23209: macvlan: fix error recovery in macvlan_common_newlink() (bsc#1258518).\n- CVE-2026-23213: drm/amd/pm: Disable MMIO access during SMU Mode 1 reset (bsc#1258465).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n\nThe following non-security bugs were fixed:\n\n- ACPI: CPPC: Fix missing PCC check for guaranteed_perf (git-fixes).\n- ACPI: CPPC: Fix remaining for_each_possible_cpu() to use online CPUs (git-fixes).\n- ACPI: PCC: Fix race condition by removing static qualifier (git-fixes).\n- ACPI: PM: Add unused power resource quirk for THUNDEROBOT ZERO (git-fixes).\n- ACPI: processor: Fix NULL-pointer dereference in acpi_processor_errata_piix4() (stable-fixes).\n- ACPI: processor_core: fix map_x2apic_id for amd-pstate on am4 (git-fixes).\n- ACPI: property: Fix fwnode refcount leak in acpi_fwnode_graph_parse_endpoint() (git-fixes).\n- ACPI: property: Use ACPI functions in acpi_graph_get_next_endpoint() only (stable-fixes).\n- ACPICA: Abort AML bytecode execution when executing AML_FATAL_OP (stable-fixes).\n- ACPICA: Avoid walking the Namespace if start_node is NULL (stable-fixes).\n- ACPICA: Fix NULL pointer dereference in acpi_ev_address_space_dispatch() (git-fixes).\n- ALSA: ac97: fix a double free in snd_ac97_controller_register() (git-fixes).\n- ALSA: ctxfi: Fix potential OOB access in audio mixer handling (stable-fixes).\n- ALSA: dice: fix buffer overflow in detect_stream_formats() (git-fixes).\n- ALSA: firewire-motu: add bounds check in put_user loop for DSP events (git-fixes).\n- ALSA: firewire-motu: fix buffer overflow in hwdep read for DSP events (git-fixes).\n- ALSA: hda/conexant: Add headset mic fix for MECHREVO Wujie 15X Pro (stable-fixes).\n- ALSA: hda/realtek - fixed speaker no sound (stable-fixes).\n- ALSA: hda/realtek: Add quirk for Inspur S14-G1 (stable-fixes).\n- ALSA: hda/realtek: Fix headset mic for TongFang X6AR55xU (stable-fixes).\n- ALSA: hda/realtek: Really fix headset mic for TongFang X6AR55xU (git-fixes).\n- ALSA: hda/realtek: add HP Laptop 15s-eq1xxx mute LED quirk (stable-fixes).\n- ALSA: hda/realtek: fix right sounds and mute/micmute LEDs for HP machine (stable-fixes).\n- ALSA: hda: cs35l41: Fix NULL pointer dereference in cs35l41_hda_read_acpi() (git-fixes).\n- ALSA: pcmcia: Fix resource leak in snd_pdacf_probe error path (git-fixes).\n- ALSA: scarlett2: Fix buffer overflow in config retrieval (git-fixes).\n- ALSA: uapi: Fix typo in asound.h comment (git-fixes).\n- ALSA: usb-audio: Add DSD quirk for LEAK Stereo 230 (stable-fixes).\n- ALSA: usb-audio: Add iface reset and delay quirk for AB13X USB Audio (stable-fixes).\n- ALSA: usb-audio: Add native DSD quirks for PureAudio DAC series (stable-fixes).\n- ALSA: usb-audio: Add sanity check for OOB writes at silencing (stable-fixes).\n- ALSA: usb-audio: Avoid implicit feedback mode on DIYINHK USB Audio 2.0 (stable-fixes).\n- ALSA: usb-audio: Cap the packet size pre-calculations (git-fixes).\n- ALSA: usb-audio: Check max frame size for implicit feedback mode, too (stable-fixes).\n- ALSA: usb-audio: Fix use-after-free in snd_usb_mixer_free() (git-fixes).\n- ALSA: usb-audio: Remove VALIDATE_RATES quirk for Focusrite devices (git-fixes).\n- ALSA: usb-audio: Update for native DSD support quirks (stable-fixes).\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: Use correct version for UAC3 header validation (git-fixes).\n- ALSA: usb-audio: Use inclusive terms (git-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ALSA: usb-mixer: us16x08: validate meter packet indices (git-fixes).\n- ALSA: usb: Increase volume range that triggers a warning (git-fixes).\n- ALSA: vxpocket: Fix resource leak in vxpocket_probe error path (git-fixes).\n- APEI/GHES: ensure that won't go past CPER allocated record (stable-fixes).\n- ASoC: Intel: catpt: Fix error path in hw_params() (git-fixes).\n- ASoC: Intel: sof_es8336: Add DMI quirk for Huawei BOD-WXX9 (stable-fixes).\n- ASoC: Intel: sof_es8336: fix headphone GPIO logic inversion (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- ASoC: SOF: ipc4-control: Keep the payload size up to date (git-fixes).\n- ASoC: SOF: ipc4-control: Use the correct size for scontrol-\u003eipc_control_data (git-fixes).\n- ASoC: SOF: ipc4-topology: Correct the allocation size for bytes controls (git-fixes).\n- ASoC: ak4458: Disable regulator when error happens (git-fixes).\n- ASoC: ak5558: Disable regulator when error happens (git-fixes).\n- ASoC: amd: drop unused Kconfig symbols (git-fixes).\n- ASoC: amd: fix memory leak in acp3x pdm dma ops (git-fixes).\n- ASoC: amd: yc: Add ASUS ExpertBook PM1503CDA to quirks list (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for ASUS Vivobook Pro 15X M6501RR (stable-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer TravelMate P216-41-TCO (stable-fixes).\n- ASoC: amd: yc: Add quirk for HP 200 G2a 16 (stable-fixes).\n- ASoC: amd: yc: Add quirk for Honor MagicBook X16 2025 (stable-fixes).\n- ASoC: amd: yc: Fix microphone on ASUS M6500RE (stable-fixes).\n- ASoC: bcm: bcm63xx-pcm-whistler: Check return value of of_dma_configure() (git-fixes).\n- ASoC: codecs: max98390: Check return value of devm_gpiod_get_optional() in max98390_i2c_probe() (stable-fixes).\n- ASoC: codecs: wcd938x: fix OF node leaks on probe failure (git-fixes).\n- ASoC: codecs: wsa881x: Drop unused version readout (stable-fixes).\n- ASoC: codecs: wsa881x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa883x: fix unnecessary initialisation (git-fixes).\n- ASoC: codecs: wsa884x: fix codec initialisation (git-fixes).\n- ASoC: cs35l45: Corrects ASP_TX5 DAPM widget channel (stable-fixes).\n- ASoC: davinci-evm: Fix reference leak in davinci_evm_probe (stable-fixes).\n- ASoC: fsl: imx-card: Do not force slot width to sample width (git-fixes).\n- ASoC: fsl_sai: Add missing registers to cache default (stable-fixes).\n- ASoC: fsl_xcvr: clear the channel status control memory (git-fixes).\n- ASoC: nau8821: Avoid unnecessary blocking in IRQ handler (stable-fixes).\n- ASoC: nau8821: Cancel delayed work on component remove (git-fixes).\n- ASoC: nau8821: Cancel pending work before suspend (git-fixes).\n- ASoC: nau8821: Consistently clear interrupts before unmasking (git-fixes).\n- ASoC: nau8821: Fixup nau8821_enable_jack_detect() (git-fixes).\n- ASoC: pxa: drop unused Kconfig symbol (git-fixes).\n- ASoC: qcom: q6adm: the the copp device only during last instance (git-fixes).\n- ASoC: qcom: q6apm-dai: set flags to reflect correct operation of appl_ptr (git-fixes).\n- ASoC: qcom: q6asm-dai: perform correct state check before closing (git-fixes).\n- ASoC: qcom: qdsp6: q6asm-dai: set 10 ms period and buffer alignment (git-fixes).\n- ASoC: rockchip: i2s-tdm: Use param rate if not provided by set_sysclk (git-fixes).\n- ASoC: stm32: sai: fix OF node leak on probe (git-fixes).\n- ASoC: stm32: sai: fix clk prepare imbalance on probe failure (git-fixes).\n- ASoC: stm32: sai: fix device leak on probe (git-fixes).\n- ASoC: sun4i-spdif: Add missing kerneldoc fields for sun4i_spdif_quirks (git-fixes).\n- ASoC: sunxi: sun50i-dmic: Add missing check for devm_regmap_init_mmio (stable-fixes).\n- ASoC: tlv320adcx140: Propagate error codes during probe (stable-fixes).\n- ASoC: tlv320adcx140: fix null pointer (git-fixes).\n- ASoC: tlv320adcx140: fix word length (git-fixes).\n- ASoC: wm8962: Add WM8962_ADC_MONOMIX to \"3D Coefficients\" mask (stable-fixes).\n- ASoC: wm8962: Do not report a microphone if it's shorted to ground on plug (stable-fixes).\n- Add dtb-spacemit SpacemiT boards include MilkV-Jupiter, Banana Pi F3 and Orange Pi RV2.\n- Bluetooth: HCI: Fix tracking of advertisement set/instance 0x00 (git-fixes).\n- Bluetooth: L2CAP: Fix invalid response to L2CAP_ECRED_RECONF_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix missing key size check for L2CAP_LE_CONN_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix not checking output MTU is acceptable on L2CAP_ECRED_CONN_REQ (git-fixes).\n- Bluetooth: L2CAP: Fix response to L2CAP_ECRED_CONN_REQ (git-fixes).\n- Bluetooth: MGMT: Fix memory leak in set_ssp_complete (git-fixes).\n- Bluetooth: SMP: Fix not generating mackey and ltk when repairing (git-fixes).\n- Bluetooth: btrtl: Avoid loading the config file on security chips (stable-fixes).\n- Bluetooth: btusb: Add USB ID 7392:e611 for Edimax EW-7611UXB (stable-fixes).\n- Bluetooth: btusb: Add device ID for Realtek RTL8761BU (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 13d3/3533 for RTL8821CE (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID 2b89/6275 for RTL8761BUV (stable-fixes).\n- Bluetooth: btusb: Add new VID/PID for RTL8852CE (stable-fixes).\n- Bluetooth: btusb: revert use of devm_kzalloc in btusb (git-fixes).\n- Bluetooth: hci_conn: Set link_policy on incoming ACL connections (stable-fixes).\n- Bluetooth: hci_conn: use mod_delayed_work for active mode timeout (stable-fixes).\n- Bluetooth: hci_qca: Cleanup on all setup failures (git-fixes).\n- Bluetooth: hci_sock: Prevent race in socket write iter and sock bind (git-fixes).\n- Bluetooth: hci_uart: fix null-ptr-deref in hci_uart_write_work (git-fixes).\n- Documentation/kernel-parameters: fix typo in retbleed= kernel parameter description (git-fixes).\n- Documentation: PCI: endpoint: Fix ntb/vntb copy \u0026 paste errors (git-fixes).\n- Documentation: hid-alps: Fix packet format section headings (git-fixes).\n- Documentation: mailbox: mbox_chan_ops.flush() is optional (git-fixes).\n- Documentation: parport-lowlevel: Separate function listing code blocks (git-fixes).\n- HID: Apply quirk HID_QUIRK_ALWAYS_POLL to Edifier QR30 (2d99:a101) (stable-fixes).\n- HID: apple: Add \"SONiX KN85 Keyboard\" to the list of non-apple keyboards (stable-fixes).\n- HID: apple: Add SONiX AK870 PRO to non_apple_keyboards quirk list (stable-fixes).\n- HID: elecom: Add support for ELECOM HUGE Plus M-HT1MRBK (stable-fixes).\n- HID: elecom: Add support for ELECOM M-XT3URBK (018F) (stable-fixes).\n- HID: hid-input: Extend Elan ignore battery quirk to USB (stable-fixes).\n- HID: hid-pl: handle probe errors (git-fixes).\n- HID: i2c-hid: fix potential buffer overflow in i2c_hid_get_report() (stable-fixes).\n- HID: input: map HID_GD_Z to ABS_DISTANCE for stylus/pen (stable-fixes).\n- HID: intel-ish-hid: Reset enum_devices_done before enumeration (stable-fixes).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- HID: logitech-dj: Remove duplicate error logging (git-fixes).\n- HID: logitech-hidpp: Check maxfield in hidpp_get_report_length() (stable-fixes).\n- HID: logitech-hidpp: Do not assume FAP in hidpp_send_message_sync() (git-fixes).\n- HID: magicmouse: Do not crash on missing msc-\u003einput (stable-fixes).\n- HID: multitouch: add MT_QUIRK_STICKY_FINGERS to MT_CLS_VTL (stable-fixes).\n- HID: multitouch: add eGalaxTouch EXC3188 support (stable-fixes).\n- HID: playstation: Add missing check for input_ff_create_memless (git-fixes).\n- HID: playstation: Center initial joystick axes to prevent spurious events (stable-fixes).\n- HID: prodikeys: Check presence of pm-\u003einput_ep82 (stable-fixes).\n- HID: quirks: Add another Chicony HP 5MP Cameras to hid_ignore_list (stable-fixes).\n- HID: quirks: work around VID/PID conflict for appledisplay (git-fixes).\n- HID: usbhid: paper over wrong bNumDescriptor field (stable-fixes).\n- Input: atkbd - skip deactivate for HONOR FMB-P's internal keyboard (git-fixes).\n- Input: cros_ec_keyb - fix an invalid memory access (stable-fixes).\n- Input: goodix - add support for ACPI ID GDIX1003 (stable-fixes).\n- Input: goodix - add support for ACPI ID GDX9110 (stable-fixes).\n- Input: i8042 - add TUXEDO InfinityBook Max Gen10 AMD to i8042 quirk table (stable-fixes).\n- Input: i8042 - add quirk for ASUS Zenbook UX425QA_UM425QA (stable-fixes).\n- Input: i8042 - add quirks for MECHREVO Wujie 15X Pro (stable-fixes).\n- Input: stmfts - correct wording for the warning message (git-fixes).\n- Input: stmfts - make comments correct (git-fixes).\n- Input: ti_am335x_tsc - fix off-by-one error in wire_order validation (git-fixes).\n- KEYS: trusted: Fix a memory leak in tpm2_load_cmd (git-fixes).\n- KEYS: trusted_tpm1: Compare HMAC values in constant time (git-fixes).\n- Move upstreamed SCSI patches into sorted section\n- Move upstreamed ath12k patch into sorted section\n- Move upstreamed mm and SCSI patches into sorted section\n- NTB: ntb_transport: Fix too small buffer for debugfs_name (git-fixes).\n- PCI/ACPI: Restrict program_hpx_type2() to AER bits (git-fixes).\n- PCI/IOV: Fix race between SR-IOV enable/disable and hotplug (git-fixes).\n- PCI/MSI: Unmap MSI-X region on error (stable-fixes).\n- PCI/P2PDMA: Release per-CPU pgmap ref when vm_insert_page() fails (git-fixes).\n- PCI/PM: Avoid redundant delays on D3hot-\u003eD3cold (git-fixes).\n- PCI/PM: Reinstate clearing state_saved in legacy and !PM codepaths (git-fixes).\n- PCI/portdrv: Fix potential resource leak (git-fixes).\n- PCI: Add ACS quirk for Pericom PI7C9X2G404 switches [12d8:b404] (git-fixes).\n- PCI: Add ACS quirk for Qualcomm Hamoa \u0026 Glymur (stable-fixes).\n- PCI: Add PCIE_MSG_CODE_ASSERT_INTx message macros (stable-fixes).\n- PCI: Add defines for bridge window indexing (stable-fixes).\n- PCI: Correct PCI_CAP_EXP_ENDPOINT_SIZEOF_V2 value (git-fixes).\n- PCI: Do not attempt to set ExtTag for VFs (git-fixes).\n- PCI: Enable ACS after configuring IOMMU for OF platforms (stable-fixes).\n- PCI: Fix pci_slot_lock () device locking (stable-fixes).\n- PCI: Fix pci_slot_trylock() error handling (git-fixes).\n- PCI: Initialize RCB from pci_configure_device() (git-fixes).\n- PCI: Log bridge info when first enumerating bridge (stable-fixes).\n- PCI: Log bridge windows conditionally (stable-fixes).\n- PCI: Mark 3ware-9650SA Root Port Extended Tags as broken (git-fixes).\n- PCI: Mark ASM1164 SATA controller to avoid bus reset (stable-fixes).\n- PCI: Mark Nvidia GB10 to avoid bus reset (stable-fixes).\n- PCI: Move pci_read_bridge_windows() below individual window accessors (stable-fixes).\n- PCI: Supply bridge device, not secondary bus, to read window details (stable-fixes).\n- PCI: dw-rockchip: Disable BAR 0 and BAR 1 for Root Port (stable-fixes).\n- PCI: dwc: Fix wrong PORT_LOGIC_LTSSM_STATE_MASK definition (git-fixes).\n- PCI: endpoint: Fix swapped parameters in pci_{primary/secondary}_epc_epf_unlink() functions (git-fixes).\n- PCI: keystone: Exit ks_pcie_probe() for invalid mode (git-fixes).\n- PCI: mediatek: Fix IRQ domain leak when MSI allocation fails (git-fixes).\n- PCI: rcar-gen2: Drop ARM dependency from PCI_RCAR_GEN2 (git-fixes).\n- PM: runtime: Do not clear needs_force_resume with enabled runtime PM (git-fixes).\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- PM: sleep: wakeirq: harden dev_pm_clear_wake_irq() against races (git-fixes).\n- PM: wakeup: Handle empty list in wakeup_sources_walk_start() (git-fixes).\n- USB: Fix descriptor count when handling invalid MBIM extended descriptor (git-fixes).\n- USB: OHCI/UHCI: Add soft dependencies on ehci_platform (stable-fixes).\n- USB: lpc32xx_udc: Fix error handling in probe (git-fixes).\n- USB: serial: belkin_sa: fix TIOCMBIS and TIOCMBIC (git-fixes).\n- USB: serial: ftdi_sio: add support for PICAXE AXE027 cable (stable-fixes).\n- USB: serial: ftdi_sio: add support for u-blox EVK-M101 (stable-fixes).\n- USB: serial: ftdi_sio: match on interface number for jtag (stable-fixes).\n- USB: serial: kobil_sct: fix TIOCMBIS and TIOCMBIC (git-fixes).\n- USB: serial: option: add Foxconn T99W760 (stable-fixes).\n- USB: serial: option: add Quectel RG255C (stable-fixes).\n- USB: serial: option: add Telit Cinterion FE910C04 new compositions (stable-fixes).\n- USB: serial: option: add Telit FN920C04 ECM compositions (stable-fixes).\n- USB: serial: option: add Telit FN920C04 RNDIS compositions (stable-fixes).\n- USB: serial: option: add Telit LE910 MBIM composition (stable-fixes).\n- USB: serial: option: add UNISOC UIS7720 (stable-fixes).\n- USB: serial: option: add support for Rolling RW101R-GL (stable-fixes).\n- USB: serial: option: move Telit 0x10c7 composition in the right place (stable-fixes).\n- USB: storage: Remove subclass and protocol overrides from Novatek quirk (git-fixes).\n- Update config files: disable CONFIG_DEVPORT for arm64 (bsc#1256792)\n- Workaround for hybrid git workflow in SLFO 1.0/1.1\n- arm64: zynqmp: Fix usb node drive strength and slew rate (git-fixes)\n- arm64: zynqmp: Revert usb node drive strength and slew rate for (git-fixes)\n- ata: libata: Add cpr_log to ata_dev_print_features() early return (git-fixes).\n- ata: libata: avoid long timeouts on hot-unplugged SATA DAS (stable-fixes).\n- ata: pata_ftide010: Fix some DMA timings (git-fixes).\n- atm/fore200e: Fix possible data race in fore200e_open() (git-fixes).\n- atm: Fix dma_free_coherent() size (git-fixes).\n- atm: fore200e: fix use-after-free in tasklets during device removal (git-fixes).\n- atm: idt77252: Add missing `dma_map_error()` (stable-fixes).\n- auxdisplay: arm-charlcd: fix release_mem_region() size (git-fixes).\n- backlight: led-bl: Add devlink to supplier LEDs (git-fixes).\n- backlight: lp855x: Fix lp855x.h kernel-doc warnings (git-fixes).\n- backlight: qcom-wled: Change PM8950 WLED configurations (git-fixes).\n- backlight: qcom-wled: Support ovp values for PMI8994 (git-fixes).\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- bpf/selftests: test_select_reuseport_kern: Remove unused header (bsc#1257603).\n- bpf: Do not let BPF test infra emit invalid GSO types to stack (bsc#1255569).\n- bpf: Reject bpf_timer for PREEMPT_RT (git-fixes).\n- broadcom: b44: prevent uninitialized value usage (git-fixes).\n- bs-upload-kernel: Fix cve branch uploads\n- btrfs: do not strictly require dirty metadata threshold for metadata writepages (stable-fixes).\n- btrfs: make sure extent and csum paths are always released in scrub_raid56_parity_stripe() (git-fixes).\n- btrfs: scrub: always update btrfs_scrub_progress::last_physical (git-fixes).\n- bus: fsl-mc: Replace snprintf and sprintf with sysfs_emit in sysfs show functions (stable-fixes).\n- bus: fsl-mc: fix an error handling in fsl_mc_device_add() (git-fixes).\n- bus: fsl-mc: fix use-after-free in driver_override_show() (git-fixes).\n- can: ctucanfd: fix SSP_SRC in cases when bit-rate is higher than 1 MBit (git-fixes).\n- can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: etas_es58x: allow partial RX URB allocation to succeed (git-fixes).\n- can: gs_usb: gs_can_open(): fix error handling (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): fix error message (git-fixes).\n- can: gs_usb: gs_usb_receive_bulk_callback(): unanchor URL on usb_submit_urb() error (git-fixes).\n- can: gs_usb: gs_usb_xmit_callback(): fix handling of failed transmitted URBs (git-fixes).\n- can: j1939: make j1939_session_activate() fail if device is no longer registered (stable-fixes).\n- can: j1939: make j1939_sk_bind() fail if device is no longer registered (git-fixes).\n- can: kvaser_usb: kvaser_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: kvaser_usb: leaf: Fix potential infinite loop in command parsers (git-fixes).\n- can: mcba_usb: mcba_usb_read_bulk_callback(): fix URB memory leak (git-fixes).\n- can: sja1000: fix max irq loop handling (git-fixes).\n- can: sun4i_can: sun4i_can_interrupt(): fix max irq loop handling (git-fixes).\n- can: usb_8dev: usb_8dev_read_bulk_callback(): fix URB memory leak (git-fixes).\n- char: applicom: fix NULL pointer dereference in ac_ioctl (stable-fixes).\n- char: tpm: cr50: Remove IRQF_ONESHOT (stable-fixes).\n- cifs: Fix copy offload to flush destination region (bsc#1252511).\n- cifs: Fix flushing, invalidation and file size with copy_file_range() (bsc#1252511).\n- cifs: Fix uncached read into ITER_KVEC iterator (bsc#1245449).\n- cifs: add new field to track the last access time of cfid (git-fixes).\n- cifs: add xid to query server interface call (git-fixes).\n- cifs: after disabling multichannel, mark tcon for reconnect (git-fixes).\n- cifs: avoid redundant calls to disable multichannel (git-fixes).\n- cifs: cifs_pick_channel should try selecting active channels (git-fixes).\n- cifs: deal with the channel loading lag while picking channels (git-fixes).\n- cifs: dns resolution is needed only for primary channel (git-fixes).\n- cifs: do not disable interface polling on failure (git-fixes).\n- cifs: do not search for channel if server is terminating (git-fixes).\n- cifs: fix a pending undercount of srv_count (git-fixes).\n- cifs: fix lock ordering while disabling multichannel (git-fixes).\n- cifs: fix stray unlock in cifs_chan_skip_or_disable (git-fixes).\n- cifs: fix use after free for iface while disabling secondary channels (git-fixes).\n- cifs: handle servers that still advertise multichannel after disabling (git-fixes).\n- cifs: handle when server starts supporting multichannel (git-fixes).\n- cifs: handle when server stops supporting multichannel (git-fixes).\n- cifs: make cifs_chan_update_iface() a void function (git-fixes).\n- cifs: make sure server interfaces are requested only for SMB3+ (git-fixes).\n- cifs: make sure that channel scaling is done only once (git-fixes).\n- cifs: reconnect worker should take reference on server struct unconditionally (git-fixes).\n- cifs: reset connections for all channels when reconnect requested (git-fixes).\n- cifs: reset iface weights when we cannot find a candidate (git-fixes).\n- cifs: serialize other channels when query server interfaces is pending (git-fixes).\n- cifs: update dstaddr whenever channel iface is updated (git-fixes).\n- clk: clk-apple-nco: Add \"apple,t8103-nco\" compatible (git-fixes).\n- clk: mediatek: Fix error handling in runtime PM setup (git-fixes).\n- clk: meson: g12a: Limit the HDMI PLL OD to /4 (git-fixes).\n- clk: meson: gxbb: Limit the HDMI PLL OD to /4 on GXL/GXM SoCs (git-fixes).\n- clk: qcom: camcc-sm6350: Fix PLL config of PLL2 (git-fixes).\n- clk: qcom: camcc-sm6350: Specify Titan GDSC power domain as a parent to other (git-fixes).\n- clk: qcom: dispcc-sdm845: Enable parents for pixel clocks (git-fixes).\n- clk: qcom: gcc-msm8917: Remove ALWAYS_ON flag from cpp_gdsc (git-fixes).\n- clk: qcom: gcc-msm8953: Remove ALWAYS_ON flag from cpp_gdsc (git-fixes).\n- clk: qcom: gfx3d: add parent to parent request map (git-fixes).\n- clk: qcom: rcg2: compute 2d using duty fraction directly (git-fixes).\n- clk: renesas: cpg-mssr: Add missing 1ms delay into reset toggle callback (git-fixes).\n- clk: renesas: r9a06g032: Fix memory leak in error path (git-fixes).\n- clk: renesas: rzg2l: Fix intin variable size (git-fixes).\n- clk: renesas: rzg2l: Select correct div round macro (git-fixes).\n- clk: tegra: tegra124-emc: Fix potential memory leak in tegra124_clk_register_emc() (git-fixes).\n- clk: tegra: tegra124-emc: fix device leak on set_rate() (git-fixes).\n- clocksource: Print durations for sync check unconditionally (bsc#1241345).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1241345).\n- comedi: Fix getting range information for subdevices 16 to 255 (git-fixes).\n- comedi: c6xdigio: Fix invalid PNP driver unregistration (git-fixes).\n- comedi: check device's attached status in compat ioctls (git-fixes).\n- comedi: dmm32at: serialize use of paged registers (git-fixes).\n- comedi: fix divide-by-zero in comedi_buf_munge() (stable-fixes).\n- comedi: multiq3: sanitize config options in multiq3_attach() (git-fixes).\n- comedi: pcl818: fix null-ptr-deref in pcl818_ai_cancel() (git-fixes).\n- cpufreq: intel_pstate: Check IDA only before MSR_IA32_PERF_CTL writes (git-fixes).\n- cpuidle: menu: Use residency threshold in polling state override decisions (bsc#1255026).\n- crypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id (git-fixes).\n- crypto: authenc - Correctly pass EINPROGRESS back up to the caller (git-fixes).\n- crypto: authencesn - reject too-short AAD (assoclen\u0026lt;8) to match ESP/ESN spec (git-fixes).\n- crypto: cavium - fix dma_free_coherent() size (git-fixes).\n- crypto: ccp - Add an S4 restore flow (git-fixes).\n- crypto: ccree - Correctly handle return of sg_nents_for_len (git-fixes).\n- crypto: hisilicon/qm - restore original qos values (git-fixes).\n- crypto: hisilicon/sec2 - support skcipher/aead fallback for hardware queue unavailable (git-fixes).\n- crypto: iaa - Fix incorrect return value in save_iaa_wq() (git-fixes).\n- crypto: iaa - Fix out-of-bounds index in find_empty_iaa_compression_mode (git-fixes).\n- crypto: octeontx - Fix length check to avoid truncation in ucode_load_store (git-fixes).\n- crypto: octeontx - fix dma_free_coherent() size (git-fixes).\n- crypto: omap - Allocate OMAP_CRYPTO_FORCE_COPY scatterlists correctly (git-fixes).\n- crypto: qat - fix duplicate restarting msg during AER error (git-fixes).\n- crypto: qat - fix parameter order used in ICP_QAT_FW_COMN_FLAGS_BUILD (git-fixes).\n- crypto: qat - fix warning on adf_pfvf_pf_proto.c (git-fixes).\n- crypto: rockchip - drop redundant crypto_skcipher_ivsize() calls (git-fixes).\n- crypto: seqiv - Do not use req-\u003eiv after crypto_aead_encrypt (git-fixes).\n- crypto: virtio - Add spinlock protection with virtqueue notification (git-fixes).\n- crypto: virtio - Remove duplicated virtqueue_kick in virtio_crypto_skcipher_crypt_req (git-fixes).\n- device property: Allow secondary lookup in fwnode_get_next_child_node() (git-fixes).\n- dm-integrity: limit MAX_TAG_SIZE to 255 (git-fixes).\n- dm-verity: fix unreliable memory allocation (git-fixes).\n- dm: fix queue start/stop imbalance under suspend/load/resume races (bsc#1253386)\n- dma: dma-axi-dmac: fix SW cyclic transfers (git-fixes).\n- dmaengine: apple-admac: Add \"apple,t8103-admac\" compatible (git-fixes).\n- dmaengine: at_hdmac: fix device leak on of_dma_xlate() (git-fixes).\n- dmaengine: bcm-sba-raid: fix device leak on probe (git-fixes).\n- dmaengine: dw: dmamux: fix OF node leak on route allocation failure (git-fixes).\n- dmaengine: idxd: fix device leaks on compat bind and unbind (git-fixes).\n- dmaengine: lpc18xx-dmamux: fix device leak on route allocation (git-fixes).\n- dmaengine: mediatek: uart-apdma: Fix above 4G addressing TX/RX (git-fixes).\n- dmaengine: omap-dma: fix dma_pool resource leak in error paths (git-fixes).\n- dmaengine: qcom: gpi: Fix memory leak in gpi_peripheral_config() (git-fixes).\n- dmaengine: sh: rz-dmac: Fix rz_dmac_terminate_all() (git-fixes).\n- dmaengine: sun6i: Choose appropriate burst length under maxburst (stable-fixes).\n- dmaengine: tegra-adma: Fix use-after-free (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on am335x route allocation (git-fixes).\n- dmaengine: ti: dma-crossbar: fix device leak on dra7x route allocation (git-fixes).\n- dmaengine: ti: k3-udma: fix device leak on udma lookup (git-fixes).\n- dmaengine: xilinx: xdma: Fix regmap max_register (git-fixes).\n- dmaengine: xilinx_dma: Fix uninitialized addr_width when \"xlnx,addrwidth\" property is missing (git-fixes).\n- docs: ABI: sysfs-devices-soc: Fix swapped sample values (git-fixes).\n- docs: fix WARNING document not included in any toctree (stable-fixes).\n- docs: w1: fix w1-netlink invalid URL (git-fixes).\n- dpll: Prevent duplicate registrations (git-fixes).\n- dpll: fix device-id-get and pin-id-get to return errors properly (git-fixes).\n- dpll: fix return value check for kmemdup (git-fixes).\n- dpll: indent DPLL option type by a tab (git-fixes).\n- dpll: spec: add missing module-name and clock-id to pin-get reply (git-fixes).\n- drivers/usb/dwc3: fix PCI parent check (git-fixes).\n- drivers: iio: mpu3050: use dev_err_probe for regulator request (git-fixes).\n- drm/amd/display: Avoid updating surface with the same surface under MPO (stable-fixes).\n- drm/amd/display: Bump the HDMI clock to 340MHz (stable-fixes).\n- drm/amd/display: Check NULL before accessing (stable-fixes).\n- drm/amd/display: Fix DP no audio issue (stable-fixes).\n- drm/amd/display: Fix logical vs bitwise bug in get_embedded_panel_info_v2_1() (git-fixes).\n- drm/amd/display: Increase DPCD read retries (stable-fixes).\n- drm/amd/display: Move sleep into each retry for retrieve_link_cap() (stable-fixes).\n- drm/amd/display: Use GFP_ATOMIC in dc_create_plane_state() (stable-fixes).\n- drm/amd/display: Use same max plane scaling limits for all 64 bpp formats (git-fixes).\n- drm/amd/display: fix wrong color value mapping on MCM shaper LUT (git-fixes).\n- drm/amd/pm: Do not clear SI SMC table when setting power limit (git-fixes).\n- drm/amd/pm: Workaround SI powertune issue on Radeon 430 (v2) (git-fixes).\n- drm/amd/pm: fix race in power state check before mutex lock (git-fixes).\n- drm/amd: Clean up kfd node on surprise disconnect (stable-fixes).\n- drm/amd: Fix hang on amdgpu unload by using pci_dev_is_disconnected() (git-fixes).\n- drm/amdgpu/gfx10: fix wptr reset in KGQ init (stable-fixes).\n- drm/amdgpu/gfx11: fix wptr reset in KGQ init (stable-fixes).\n- drm/amdgpu/soc21: fix xclk for APUs (stable-fixes).\n- drm/amdgpu: Add HAINAN clock adjustment (stable-fixes).\n- drm/amdgpu: Adjust usleep_range in fence wait (stable-fixes).\n- drm/amdgpu: Fix memory leak in amdgpu_acpi_enumerate_xcc() (git-fixes).\n- drm/amdgpu: Fix memory leak in amdgpu_ras_init() (git-fixes).\n- drm/amdgpu: Forward VMID reservation errors (git-fixes).\n- drm/amdgpu: Skip emit de meta data on gfx11 with rs64 enabled (stable-fixes).\n- drm/amdgpu: add missing lock to amdgpu_ttm_access_memory_sdma (git-fixes).\n- drm/amdgpu: add support for HDP IP version 6.1.1 (stable-fixes).\n- drm/amdgpu: avoid a warning in timedout job handler (stable-fixes).\n- drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove (git-fixes).\n- drm/amdgpu: fix cyan_skillfish2 gpu info fw handling (git-fixes).\n- drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify (git-fixes).\n- drm/amdgpu: update mappings not managed by KFD (bsc#1255428)\n- drm/amdkfd: Fix GART PTE for non-4K pagesize in svm_migrate_gart_map() (stable-fixes).\n- drm/amdkfd: Fix out-of-bounds write in kfd_event_page_set() (stable-fixes).\n- drm/amdkfd: Fix watch_id bounds checking in debug address watch v2 (git-fixes).\n- drm/amdkfd: fix a memory leak in device_queue_manager_init() (git-fixes).\n- drm/amdkfd: fix debug watchpoints for logical devices (stable-fixes).\n- drm/atmel-hlcdc: do not reject the commit if the src rect has fractional parts (stable-fixes).\n- drm/atmel-hlcdc: fix memory leak from the atomic_destroy_state callback (stable-fixes).\n- drm/atmel-hlcdc: fix use-after-free of drm_crtc_commit after release (stable-fixes).\n- drm/bridge: samsung-dsim: Fix memory leak in error path (git-fixes).\n- drm/bridge: ti-sn65dsi86: Enable HPD polling if IRQ is not used (git-fixes).\n- drm/buddy: Prevent BUG_ON by validating rounded allocation (git-fixes).\n- drm/display/dp_mst: Add protection against 0 vcpi (stable-fixes).\n- drm/gma500: Remove unused helper psb_fbdev_fb_setcolreg() (git-fixes).\n- drm/i915/acpi: free _DSM package when no connectors (git-fixes).\n- drm/i915/gem: Zero-initialize the eb.vma array in i915_gem_do_execbuffer (git-fixes).\n- drm/i915/wakeref: clean up INTEL_WAKEREF_PUT_* flag macros (stable-fixes).\n- drm/imx/tve: fix probe device leak (git-fixes).\n- drm/logicvc: Fix device node reference leak in logicvc_drm_config_parse() (git-fixes).\n- drm/mediatek: Fix CCORR mtk_ctm_s31_32_to_s1_n function issue (git-fixes).\n- drm/mediatek: Fix device node reference leak in mtk_dp_dt_parse() (git-fixes).\n- drm/mgag200: Fix big-endian support (git-fixes).\n- drm/mgag200: fix mgag200_bmc_stop_scanout() (git-fixes).\n- drm/msm/a2xx: fix pixel shader start on A225 (git-fixes).\n- drm/msm/a2xx: stop over-complaining about the legacy firmware (git-fixes).\n- drm/msm/a6xx: Fix out of bound IO access in a6xx_get_gmu_registers (git-fixes).\n- drm/msm/a6xx: Flush LRZ cache before PT switch (git-fixes).\n- drm/msm/dpu: Add missing NULL pointer check for pingpong interface (git-fixes).\n- drm/msm/dpu: Remove dead-code in dpu_encoder_helper_reset_mixers() (git-fixes).\n- drm/msm/dpu: fix CMD panels on DPU 1.x - 3.x (git-fixes).\n- drm/nouveau/disp/nv50-: Set lock_core in curs507a_prepare (git-fixes).\n- drm/nouveau/dispnv50: Do not call drm_atomic_get_crtc_state() in prepare_fb (git-fixes).\n- drm/nouveau: add missing DCB connector types (git-fixes).\n- drm/nouveau: implement missing DCB connector types; gracefully handle unknown connectors (git-fixes).\n- drm/nouveau: restrict the flush page to a 32-bit address (git-fixes).\n- drm/panel-simple: fix connector type for DataImage SCF0700C48GGU18 panel (git-fixes).\n- drm/panel: sony-td4353-jdi: Enable prepare_prev_first (git-fixes).\n- drm/pl111: Fix error handling in pl111_amba_probe (git-fixes).\n- drm/radeon: Add HAINAN clock adjustment (stable-fixes).\n- drm/radeon: Remove __counted_by from ClockInfoArray.clockInfo[] (stable-fixes).\n- drm/radeon: delete radeon_fence_process in is_signaled, no deadlock (stable-fixes).\n- drm/tegra: dsi: fix device leak on probe (git-fixes).\n- drm/tegra: hdmi: sor: Fix error: variable ‘j’ set but not used (stable-fixes).\n- drm/tilcdc: request and mapp iomem with devres (stable-fixes).\n- drm/ttm: Avoid NULL pointer deref for evicted BOs (git-fixes).\n- drm/v3d: Set DMA segment size to avoid debug warnings (stable-fixes).\n- drm/vgem-fence: Fix potential deadlock on release (git-fixes).\n- drm/vmwgfx: Fix an error return check in vmw_compat_shader_add() (git-fixes).\n- drm/vmwgfx: Fix invalid kref_put callback in vmw_bo_dirty_release (git-fixes).\n- drm/vmwgfx: Return the correct value in vmw_translate_ptr functions (git-fixes).\n- drm/vmwgfx: Use kref in vmw_bo_dirty (stable-fixes).\n- drm: Account property blob allocations to memcg (stable-fixes).\n- drm: nouveau: Replace sprintf() with sysfs_emit() (git-fixes).\n- drm: sti: fix device leaks at component probe (git-fixes).\n- efi/libstub: Describe missing 'out' parameter in efi_load_initrd (git-fixes).\n- efi/libstub: Fix page table access in 5-level to 4-level paging transition (git-fixes).\n- efi: Fix reservation of unaccepted memory table (git-fixes).\n- efivarfs: fix error propagation in efivar_entry_get() (git-fixes).\n- exfat: add a check for invalid data size (git-fixes).\n- exfat: using hweight instead of internal logic (git-fixes).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- ext4: use optimized mballoc scanning regardless of inode format (bsc#1254378).\n- ext4: wait for ongoing I/O to complete before freeing blocks (bsc#1256366).\n- fbcon: check return value of con2fb_acquire_newinfo() (git-fixes).\n- fbdev: au1200fb: Fix a memory leak in au1200fb_drv_probe() (git-fixes).\n- fbdev: ffb: fix corrupted video output on Sun FFB1 (stable-fixes).\n- fbdev: gbefb: fix to use physical address instead of dma address (stable-fixes).\n- fbdev: of: display_timing: fix refcount leak in of_get_display_timings() (git-fixes).\n- fbdev: pxafb: Fix multiple clamped values in pxafb_adjust_timing (git-fixes).\n- fbdev: rivafb: fix divide error in nv3_arb() (git-fixes).\n- fbdev: smscufx: properly copy ioctl memory to kernelspace (stable-fixes).\n- fbdev: ssd1307fb: fix potential page leak in ssd1307fb_probe() (git-fixes).\n- fbdev: tcx.c fix mem_map to correct smem_start offset (git-fixes).\n- fbdev: vt8500lcdfb: fix missing dma_free_coherent() (git-fixes).\n- firewire: nosy: Fix dma_free_coherent() size (git-fixes).\n- firmware: imx: scu-irq: Init workqueue before request mbox channel (stable-fixes).\n- firmware: imx: scu-irq: fix OF node leak in (git-fixes).\n- firmware: stratix10-svc: Add mutex in stratix10 memory management (git-fixes).\n- firmware: stratix10-svc: fix bug in saving controller data (git-fixes).\n- firmware: stratix10-svc: fix make htmldocs warning for stratix10_svc (git-fixes).\n- fix it87_wdt early reboot by reporting running timer (stable-fixes).\n- fpga: dfl: use subsys_initcall to allow built-in drivers to be added (git-fixes).\n- fpga: of-fpga-region: Fail if any bridge is missing (stable-fixes).\n- fs: dlm: allow to F_SETLKW getting interrupted (bsc#1255025).\n- genalloc.h: fix htmldocs warning (git-fixes).\n- gpio: aspeed-sgpio: Change the macro to support deferred probe (stable-fixes).\n- gpio: omap: do not register driver in probe() (git-fixes).\n- gpio: pca953x: Add support for level-triggered interrupts (stable-fixes).\n- gpio: pca953x: Utilise dev_err_probe() where it makes sense (stable-fixes).\n- gpio: pca953x: Utilise temporary variable for struct device (stable-fixes).\n- gpio: pca953x: fix wrong error probe return value (git-fixes).\n- gpio: pca953x: handle short interrupt pulses on PCAL devices (git-fixes).\n- gpio: pca953x: mask interrupts in irq shutdown (stable-fixes).\n- gpio: rockchip: Stop calling pinctrl for set_direction (git-fixes).\n- gpio: rockchip: mark the GPIO controller as sleeping (git-fixes).\n- gpio: sprd: Change sprd_gpio lock to raw_spin_lock (stable-fixes).\n- gpu: host1x: Fix race in syncpt alloc/free (git-fixes).\n- hwmon: (f71882fg) Add F81968 support (stable-fixes).\n- hwmon: (ibmpex) fix use-after-free in high/low store (git-fixes).\n- hwmon: (max16065) Use READ/WRITE_ONCE to avoid compiler optimization induced race (git-fixes).\n- hwmon: (max16065) Use local variable to avoid TOCTOU (git-fixes).\n- hwmon: (nct6775) Add ASUS Pro WS WRX90E-SAGE SE (stable-fixes).\n- hwmon: (occ) Mark occ_init_attribute() as __printf (git-fixes).\n- hwmon: (tmp401) fix overflow caused by default conversion rate value (git-fixes).\n- hwmon: (w83791d) Convert macros to functions to avoid TOCTOU (git-fixes).\n- hwmon: (w83l786ng) Convert macros to functions to avoid TOCTOU (git-fixes).\n- hwmon: sy7636a: Fix regulator_enable resource leak on error path (git-fixes).\n- i2c: amd-mp2: fix reference leak in MP2 PCI device (git-fixes).\n- i2c: designware: Disable SMBus interrupts to prevent storms from mis-configured firmware (stable-fixes).\n- i2c: i2c.h: fix a bad kernel-doc line (git-fixes).\n- i3c: Move device name assignment after i3c_bus_init (git-fixes).\n- i3c: dw: Initialize spinlock to avoid upsetting lockdep (git-fixes).\n- i3c: fix refcount inconsistency in i3c_master_register (git-fixes).\n- i3c: master: Inherit DMA masks and parameters from parent device (stable-fixes).\n- i3c: master: svc: Initialize 'dev' to NULL in svc_i3c_master_ibi_isr() (stable-fixes).\n- i3c: master: svc: Prevent incomplete IBI transaction (git-fixes).\n- ice: use netif_get_num_default_rss_queues() (bsc#1247712).\n- idr: fix idr_alloc() returning an ID out of range (git-fixes).\n- iio: Use IRQF_NO_THREAD (stable-fixes).\n- iio: accel: bmc150: Fix irq assumption regression (stable-fixes).\n- iio: accel: fix ADXL355 startup race condition (git-fixes).\n- iio: accel: iis328dq: fix gain values (git-fixes).\n- iio: adc: ad7280a: fix ad7280_store_balance_timer() (git-fixes).\n- iio: adc: ad7280a: handle spi_setup() errors in probe() (git-fixes).\n- iio: adc: ad9467: fix ad9434 vref mask (git-fixes).\n- iio: adc: at91-sama5d2_adc: Fix potential use-after-free in sama5d2_adc driver (git-fixes).\n- iio: adc: ti_am335x_adc: Limit step_avg to valid range for gcc complains (stable-fixes).\n- iio: core: Clean up device correctly on iio_device_alloc() failure (git-fixes).\n- iio: core: add missing mutex_destroy in iio_dev_release() (git-fixes).\n- iio: dac: ad5686: add AD5695R to ad5686_chip_info_tbl (git-fixes).\n- iio: gyro: itg3200: Fix unchecked return value in read_raw (git-fixes).\n- iio: imu: st_lsm6dsx: Fix measurement unit for odr struct member (git-fixes).\n- iio: imu: st_lsm6dsx: fix array size for st_lsm6dsx_settings fields (git-fixes).\n- iio: imu: st_lsm6dsx: fix iio_chan_spec for sensors without event detection (git-fixes).\n- iio: magnetometer: Remove IRQF_ONESHOT (stable-fixes).\n- iio: sca3000: Fix a resource leak in sca3000_probe() (git-fixes).\n- iio: st_lsm6dsx: Fixed calibrated timestamp calculation (git-fixes).\n- iio:common:ssp_sensors: Fix an error handling path ssp_probe() (git-fixes).\n- ima: Handle error code returned by ima_filter_rule_match() (git-fixes).\n- intel_th: Fix error handling in intel_th_output_open (git-fixes).\n- intel_th: fix device leak on output open() (git-fixes).\n- iomap: account for unaligned end offsets when truncating read range (git-fixes).\n- ipmi: Fix __scan_channels() failing to rescan channels (stable-fixes).\n- ipmi: Fix handling of messages with provided receive message pointer (git-fixes).\n- ipmi: Fix the race between __scan_channels() and deliver_response() (stable-fixes).\n- ipmi: Rework user message limit handling (git-fixes).\n- ipmi: ipmb: initialise event handler read bytes (git-fixes).\n- irqchip/mchp-eic: Fix error code in mchp_eic_domain_alloc() (git-fixes).\n- kABI workaround for HCI_LE_ADV_0 addition (git-fixes).\n- kconfig/mconf: Initialize the default locale at startup (stable-fixes).\n- kconfig/nconf: Initialize the default locale at startup (stable-fixes).\n- kernel-binary: Require libdw in Factory Libdw is required for gendwarfksyms\n- kernel-binary: Support building gendwarfksyms on SLE/Leap 15\n- landlock: Optimize file path walks and prepare for audit support (bsc#1255698).\n- leds: led-class: Only Add LED to leds_list when it is fully ready (git-fixes).\n- leds: leds-lp50xx: Allow LED 0 to be added to module bank (git-fixes).\n- leds: leds-lp50xx: Enable chip before any communication (git-fixes).\n- leds: leds-lp50xx: LP5009 supports 3 modules for a total of 9 LEDs (git-fixes).\n- leds: netxbig: Fix GPIO descriptor leak in error paths (git-fixes).\n- leds: qcom-lpg: Check the return value of regmap_bulk_write() (git-fixes).\n- lib/crypto: aes: Fix missing MMU protection for AES S-box (git-fixes).\n- lib/vsprintf: Check pointer before dereferencing in time_and_date() (git-fixes).\n- mISDN: annotate data-race around dev-\u003ework (git-fixes).\n- mailbox: mailbox-test: Fix debugfs_create_dir error checking (git-fixes).\n- media: TDA1997x: Remove redundant cancel_delayed_work in probe (git-fixes).\n- media: adv7180: fix frame interval in progressive mode (stable-fixes).\n- media: adv7842: Avoid possible out-of-bounds array accesses in adv7842_cp_log_status() (git-fixes).\n- media: amphion: Add a frame flush mode for decoder (stable-fixes).\n- media: amphion: Cancel message work before releasing the VPU core (git-fixes).\n- media: amphion: Clear last_buffer_dequeued flag for DEC_CMD_START (stable-fixes).\n- media: amphion: Make some vpu_v4l2 functions static (stable-fixes).\n- media: amphion: Remove vpu_vb_is_codecconfig (git-fixes).\n- media: atomisp: Prefix firmware paths with \"intel/ipu/\" (bsc#1252973).\n- media: atomisp: Remove firmware_name module parameter (bsc#1252973).\n- media: ccs: Accommodate C-PHY into the calculation (git-fixes).\n- media: ccs: Avoid possible division by zero (git-fixes).\n- media: cec: Fix debugfs leak on bus_register() failure (git-fixes).\n- media: cx23885: Add missing unmap in snd_cx23885_hw_params() (git-fixes).\n- media: cx25821: Add missing unmap in snd_cx25821_hw_params() (git-fixes).\n- media: cx25821: Fix a resource leak in cx25821_dev_setup() (stable-fixes).\n- media: cx88: Add missing unmap in snd_cx88_hw_params() (git-fixes).\n- media: dvb-core: dmxdevfilter must always flush bufs (stable-fixes).\n- media: dvb-core: fix wrong reinitialization of ringbuffer on reopen (git-fixes).\n- media: dvb-net: fix OOB access in ULE extension header tables (git-fixes).\n- media: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg() (git-fixes).\n- media: i2c/tw9903: Fix potential memory leak in tw9903_probe() (git-fixes).\n- media: i2c/tw9906: Fix potential memory leak in tw9906_probe() (git-fixes).\n- media: i2c: ADV7604: Remove redundant cancel_delayed_work in probe (git-fixes).\n- media: i2c: adv7842: Remove redundant cancel_delayed_work in probe (git-fixes).\n- media: i2c: ov5647: Correct minimum VBLANK value (git-fixes).\n- media: i2c: ov5647: Correct pixel array offset (git-fixes).\n- media: i2c: ov5647: Fix PIXEL_RATE value for VGA mode (git-fixes).\n- media: i2c: ov5647: Initialize subdev before controls (git-fixes).\n- media: i2c: ov5647: Sensor should report RAW color space (git-fixes).\n- media: i2c: ov5647: use our own mutex for the ctrl lock (git-fixes).\n- media: msp3400: Avoid possible out-of-bounds array accesses in msp3400c_thread() (git-fixes).\n- media: mtk-mdp: Fix a reference leak bug in mtk_mdp_remove() (git-fixes).\n- media: mtk-mdp: Fix error handling in probe function (git-fixes).\n- media: omap3isp: isp_video_mbus_to_pix/pix_to_mbus fixes (stable-fixes).\n- media: omap3isp: isppreview: always clamp in preview_try_format() (stable-fixes).\n- media: omap3isp: set initial format (stable-fixes).\n- media: pvrusb2: Fix incorrect variable used in trace message (git-fixes).\n- media: pvrusb2: fix URB leak in pvr2_send_request_ex (stable-fixes).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- media: radio-keene: fix memory leak in error path (git-fixes).\n- media: rc: st_rc: Fix reset control resource leak (git-fixes).\n- media: renesas: rcar_drif: fix device node reference leak in rcar_drif_bond_enabled (git-fixes).\n- media: rkisp1: Fix filter mode register configuration (stable-fixes).\n- media: samsung: exynos4-is: fix potential ABBA deadlock on init (git-fixes).\n- media: solo6x10: Check for out of bounds chip_id (stable-fixes).\n- media: uvcvideo: Fix allocation for small frame sizes (git-fixes).\n- media: v4l2-mem2mem: Fix outdated documentation (git-fixes).\n- media: venus: vdec: fix error state assignment for zero bytesused (git-fixes).\n- media: verisilicon: Fix CPU stalls on G2 bus error (git-fixes).\n- media: verisilicon: Protect G2 HEVC decoder against invalid DPB index (git-fixes).\n- media: verisilicon: Store chroma and motion vectors offset (stable-fixes).\n- media: verisilicon: g2: Use common helpers to compute chroma and mv offsets (stable-fixes).\n- media: videobuf2: Fix device reference leak in vb2_dc_alloc error path (git-fixes).\n- media: vidtv: initialize local pointers upon transfer of memory ownership (git-fixes).\n- media: vpif_capture: fix section mismatch (git-fixes).\n- media: vpif_display: fix section mismatch (git-fixes).\n- mei: me: add nova lake point S DID (stable-fixes).\n- mei: me: add wildcat lake P DID (stable-fixes).\n- mfd: altera-sysmgr: Fix device leak on sysmgr regmap lookup (git-fixes).\n- mfd: arizona: Fix regulator resource leak on wm5102_clear_write_sequencer() failure (git-fixes).\n- mfd: core: Add locking around 'mfd_of_node_list' (git-fixes).\n- mfd: da9055: Fix missing regmap_del_irq_chip() in error path (git-fixes).\n- mfd: max77620: Fix potential IRQ chip conflict when probing two devices (git-fixes).\n- mfd: mt6358-irq: Fix missing irq_domain_remove() in error path (git-fixes).\n- mfd: mt6397-irq: Fix missing irq_domain_remove() in error path (git-fixes).\n- mfd: tps6105x: Fix kernel-doc warnings relating to the core struct and tps6105x_mode (git-fixes).\n- mfd: wm8350-core: Use IRQF_ONESHOT (git-fixes).\n- misc: bcm_vk: Fix possible null-pointer dereferences in bcm_vk_read() (stable-fixes).\n- misc: eeprom: Fix EWEN/EWDS/ERAL commands for 93xx56 and 93xx66 (stable-fixes).\n- mm, page_alloc, thp: prevent reclaim for __GFP_THISNODE THP allocations (bsc#1254447 bsc#1253087).\n- mmc: mmci: Fix device_node reference leak in of_get_dml_pipe_index() (git-fixes).\n- mmc: rtsx_pci_sdmmc: implement sdmmc_card_busy function (git-fixes).\n- mmc: rtsx_pci_sdmmc: increase power-on settling delay to 5ms (git-fixes).\n- mmc: sdhci-esdhc-imx: add alternate ARCH_S32 dependency to Kconfig (git-fixes).\n- mmc: sdhci-msm: Avoid early clock doubling during HS400 transition (stable-fixes).\n- mmc: sdhci-of-dwcmshc: Prevent illegal clock reduction in HS200/HS400 mode (git-fixes).\n- most: usb: fix double free on late probe failure (git-fixes).\n- mt76: mt7615: Fix memory leak in mt7615_mcu_wtbl_sta_add() (git-fixes).\n- mtd: lpddr_cmds: fix signed shifts in lpddr_cmds (git-fixes).\n- mtd: maps: pcmciamtd: fix potential memory leak in pcmciamtd_detach() (git-fixes).\n- mtd: nand: relax ECC parameter validation check (git-fixes).\n- mtd: parsers: Fix memory leak in mtd_parser_tplink_safeloader_parse() (git-fixes).\n- mtd: parsers: ofpart: fix OF node refcount leak in parse_fixed_partitions() (git-fixes).\n- mtd: rawnand: cadence: Fix return type of CDMA send-and-wait helper (git-fixes).\n- mtd: rawnand: lpc32xx_slc: fix GPIO descriptor leak on probe error and remove (git-fixes).\n- mtd: rawnand: pl353: Fix software ECC support (git-fixes).\n- mtd: rawnand: renesas: Handle devm_pm_runtime_enable() errors (git-fixes).\n- mtd: spinand: Fix kernel doc (git-fixes).\n- myri10ge: avoid uninitialized variable use (stable-fixes).\n- net: can: j1939: j1939_xtp_rx_rts_session_active(): deactivate session upon receiving the second rts (git-fixes).\n- net: hv_netvsc: reject RSS hash key programming without RX indirection table (bsc#1257473).\n- net: mdio: aspeed: add dummy read to avoid read-after-write issue (git-fixes).\n- net: nfc: fix deadlock between nfc_unregister_device and rfkill_fop_write (git-fixes).\n- net: nfc: nci: Fix parameter validation for packet data (git-fixes).\n- net: phy: adin1100: Fix software power-down ready condition (git-fixes).\n- net: phy: mxl-gpy: fix bogus error on USXGMII and integrated PHY (git-fixes).\n- net: phy: mxl-gpy: fix link properties on USXGMII and internal PHYs (git-fixes).\n- net: rose: fix invalid array index in rose_kill_by_device() (git-fixes).\n- net: tcp: allow zero-window ACK update the window (bsc#1254767).\n- net: usb: catc: enable basic endpoint checking (git-fixes).\n- net: usb: dm9601: remove broken SR9700 support (git-fixes).\n- net: usb: kalmia: validate USB endpoints (git-fixes).\n- net: usb: kaweth: remove TX queue manipulation in kaweth_set_rx_mode (git-fixes).\n- net: usb: kaweth: validate USB endpoints (git-fixes).\n- net: usb: lan78xx: scan all MDIO addresses on LAN7801 (git-fixes).\n- net: usb: pegasus: enable basic endpoint checking (git-fixes).\n- net: usb: pegasus: fix memory leak in update_eth_regs_async() (git-fixes).\n- net: usb: r8152: fix transmit queue timeout (stable-fixes).\n- net: usb: rtl8150: fix memory leak on usb_submit_urb() failure (git-fixes).\n- net: usb: sr9700: fix incorrect command used to write single register (git-fixes).\n- net: usb: sr9700: remove code to drive nonexistent multicast filter (stable-fixes).\n- net: usb: sr9700: support devices with virtual driver CD (stable-fixes).\n- net: wan/fsl_ucc_hdlc: Fix dma_free_coherent() in uhdlc_memclean() (git-fixes).\n- net: wan: farsync: Fix use-after-free bugs caused by unfinished tasklets (git-fixes).\n- net: wwan: iosm: Fix memory leak in ipc_mux_deinit() (git-fixes).\n- net: wwan: t7xx: fix potential skb-\u003efrags overflow in RX path (git-fixes).\n- nfc: hci: shdlc: Stop timers and work before freeing context (git-fixes).\n- nfc: llcp: Fix memleak in nfc_llcp_send_ui_frame() (git-fixes).\n- nfc: nci: Fix race between rfkill and nci_unregister_device() (git-fixes).\n- nfc: nxp-nci: remove interrupt trigger type (stable-fixes).\n- nfc: pn533: Fix error code in pn533_acr122_poweron_rdr() (git-fixes).\n- nfc: pn533: properly drop the usb interface reference on disconnect (git-fixes).\n- ntb: ntb_hw_switchtec: Fix array-index-out-of-bounds access (stable-fixes).\n- ntb: ntb_hw_switchtec: Fix shift-out-of-bounds for 0 mw lut (stable-fixes).\n- nvme: Use non zero KATO for persistent discovery connections (git-fixes).\n- of: fix reference count leak in of_alias_scan() (git-fixes).\n- of: platform: Use default match table for /firmware (git-fixes).\n- orangefs: fix xattr related buffer overflow.. (git-fixes).\n- phy: broadcom: bcm63xx-usbh: fix section mismatches (git-fixes).\n- phy: freescale: imx8m-pcie: assert phy reset during power on (stable-fixes).\n- phy: fsl-imx8mq-usb: disable bind/unbind platform driver feature (stable-fixes).\n- phy: mvebu-cp110-utmi: fix dr_mode property read from dts (stable-fixes).\n- phy: renesas: rcar-gen3-usb2: Fix an error handling path in rcar_gen3_phy_usb2_probe() (git-fixes).\n- phy: rockchip: inno-usb2: fix communication disruption in gadget mode (git-fixes).\n- phy: rockchip: inno-usb2: fix disconnection in gadget mode (git-fixes).\n- phy: stm32-usphyc: Fix off by one in probe() (git-fixes).\n- phy: tegra: xusb: Explicitly configure HS_DISCON_LEVEL to 0x7 (git-fixes).\n- pinctrl: equilibrium: Fix device node reference leak in pinbank_init() (git-fixes).\n- pinctrl: meson: mark the GPIO controller as sleeping (git-fixes).\n- pinctrl: qcom: lpass-lpi: mark the GPIO controller as sleeping (git-fixes).\n- pinctrl: qcom: msm: Fix deadlock in pinmux configuration (stable-fixes).\n- pinctrl: qcom: sm8250-lpass-lpi: Fix i2s2_data_groups definition (git-fixes).\n- pinctrl: single: Fix PIN_CONFIG_BIAS_DISABLE handling (stable-fixes).\n- pinctrl: single: Fix incorrect type for error return variable (git-fixes).\n- pinctrl: single: fix refcount leak in pcs_add_gpio_func() (git-fixes).\n- pinctrl: stm32: fix hwspinlock resource leak in probe function (git-fixes).\n- platform/chrome: cros_ec_ishtp: Fix UAF after unbinding driver (git-fixes).\n- platform/chrome: cros_ec_lightbar: Fix response size initialization (git-fixes).\n- platform/chrome: cros_typec_switch: Do not touch struct fwnode_handle::dev (git-fixes).\n- platform/mellanox: mlxbf-pmc: Remove trailing whitespaces from event names (git-fixes).\n- platform/x86/amd/pmc: Add quirk for MECHREVO Wujie 15X Pro (stable-fixes).\n- platform/x86/amd/pmc: Add spurious_8042 to Xbox Ally (stable-fixes).\n- platform/x86/amd: pmc: Add Lenovo Legion Go 2 to pmc quirk list (stable-fixes).\n- platform/x86/intel/hid: Add Dell Pro Rugged 10/12 tablet to VGBS DMI quirks (stable-fixes).\n- platform/x86: acer-wmi: Ignore backlight event (stable-fixes).\n- platform/x86: asus-wmi: use brightness_set_blocking() for kbd led (git-fixes).\n- platform/x86: classmate-laptop: Add missing NULL pointer checks (stable-fixes).\n- platform/x86: huawei-wmi: add keys for HONOR models (stable-fixes).\n- platform/x86: ibm_rtl: fix EBDA signature search pointer arithmetic (git-fixes).\n- platform/x86: intel: chtwc_int33fe: do not dereference swnode args (git-fixes).\n- platform/x86: intel: punit_ipc: fix memory corruption (git-fixes).\n- platform/x86: intel_telemetry: Fix PSS event register mask (git-fixes).\n- platform/x86: intel_telemetry: Fix swapped arrays in PSS output (git-fixes).\n- platform/x86: msi-laptop: add missing sysfs_remove_group() (git-fixes).\n- platform/x86: panasonic-laptop: Fix sysfs group leak in error path (stable-fixes).\n- platform/x86: toshiba_haps: Fix memory leaks in add/remove routines (git-fixes).\n- power: reset: nvmem-reboot-mode: respect cell size for nvmem_cell_write (git-fixes).\n- power: supply: ab8500: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: act8945a: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: apm_power: only unset own apm_get_power_status (git-fixes).\n- power: supply: bq256xx: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: bq25980: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: bq27xxx: fix wrong errno when bus ops are unsupported (git-fixes).\n- power: supply: cpcap-battery: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: cw2015: Check devm_delayed_work_autocancel() return code (git-fixes).\n- power: supply: goldfish: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: qcom_battmgr: Recognize \"LiP\" as lithium-polymer (git-fixes).\n- power: supply: rt9455: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: rt9467: Prevent using uninitialized local variable in rt9467_set_value_from_ranges() (git-fixes).\n- power: supply: rt9467: Return error on failure in rt9467_set_value_from_ranges() (git-fixes).\n- power: supply: sbs-battery: Fix use-after-free in power_supply_changed() (git-fixes).\n- power: supply: wm831x: Check wm831x_set_bits() return value (git-fixes).\n- power: supply: wm97xx: Fix NULL pointer dereference in power_supply_changed() (git-fixes).\n- powercap: fix race condition in register_control_type() (stable-fixes).\n- powercap: fix sscanf() error return value handling (stable-fixes).\n- powercap: intel_rapl_tpmi: Remove FW_BUG from invalid version check (git-fixes).\n- powerpc/64s/slb: Fix SLB multihit issue during SLB preload (bac#1236022 ltc#211187).\n- powerpc/addnote: Fix overflow on 32-bit builds (bsc#1215199).\n- powerpc/eeh: fix recursive pci_lock_rescan_remove locking in EEH event handling (bsc#1253262 ltc#216029).\n- powerpc/kexec: Enable SMT before waking offline CPUs (bsc#1214285 bsc#1205462 bsc#1253739 bsc#1254244).\n- pwm: bcm2835: Make sure the channel is enabled after pwm_request() (git-fixes).\n- rapidio: replace rio_free_net() with kfree() in rio_scan_alloc_net() (git-fixes).\n- regmap: Fix race condition in hwspinlock irqsave routine (git-fixes).\n- regmap: maple: free entry on mas_store_gfp() failure (stable-fixes).\n- regulator: core: Protect regulator_supply_alias_list with regulator_list_mutex (git-fixes).\n- regulator: core: disable supply if enabling main regulator fails (git-fixes).\n- regulator: core: fix locking in regulator_resolve_supply() error path (git-fixes).\n- regulator: core: move supply check earlier in set_machine_constraints() (git-fixes).\n- remove a bpf CVE change which is already part of the base kernel\n- remove an Intel CPU model change which is already part of the base kernel\n- reset: fix BIT macro reference (stable-fixes).\n- rpm/mkspec-dtb: add riscv64 dtb-thead subpackage\n- rpmsg: core: fix race in driver_override_show() and use core helper (git-fixes).\n- rpmsg: glink: fix rpmsg device leak (git-fixes).\n- rtc: gamecube: Check the return value of ioremap() (git-fixes).\n- rtc: interface: Alarm race handling should not discard preceding error (git-fixes).\n- rtc: zynqmp: correct frequency value (stable-fixes).\n- sched: Increase sched_tick_remote timeout (bsc#1254510).\n- scripts/python/git_sort/git_sort.yaml: add cifs for-next repository\n- scripts: obsapi: Support URL trailing / in oscrc\n- scripts: teaapi: Add paging\n- scripts: uploader: Fix no change condition for _maintainership.json\n- scripts: uploader: Handle missing upstream in is_pr_open\n- scrits: teaapi: Add list_repos\n- scsi: lpfc: Add capability to register Platform Name ID to fabric (bsc#1254119).\n- scsi: lpfc: Allow support for BB credit recovery in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Ensure unregistration of rpis for received PLOGIs (bsc#1254119).\n- scsi: lpfc: Fix leaked ndlp krefs when in point-to-point topology (bsc#1254119).\n- scsi: lpfc: Fix reusing an ndlp that is marked NLP_DROPPED during FLOGI (bsc#1254119).\n- scsi: lpfc: Modify kref handling for Fabric Controller ndlps (bsc#1254119).\n- scsi: lpfc: Remove redundant NULL ptr assignment in lpfc_els_free_iocb() (bsc#1254119).\n- scsi: lpfc: Revise discovery related function headers and comments (bsc#1254119).\n- scsi: lpfc: Rework lpfc_sli4_fcf_rr_next_index_get() (bsc#1256861).\n- scsi: lpfc: Update lpfc version to 14.4.0.12 (bsc#1254119).\n- scsi: lpfc: Update lpfc version to 14.4.0.13 (bsc#1256861).\n- scsi: lpfc: Update various NPIV diagnostic log messaging (bsc#1254119).\n- scsi: qla2xxx: Add Speed in SFP print information (bsc#1256863).\n- scsi: qla2xxx: Add bsg interface to support firmware img validation (bsc#1256863).\n- scsi: qla2xxx: Add load flash firmware mailbox support for 28xxx (bsc#1256863).\n- scsi: qla2xxx: Add support for 64G SFP speed (bsc#1256863).\n- scsi: qla2xxx: Allow recovery for tape devices (bsc#1256863).\n- scsi: qla2xxx: Delay module unload while fabric scan in progress (bsc#1256863).\n- scsi: qla2xxx: Fix bsg_done() causing double free (bsc#1256863).\n- scsi: qla2xxx: Free sp in error path to fix system crash (bsc#1256863).\n- scsi: qla2xxx: Query FW again before proceeding with login (bsc#1256863).\n- scsi: qla2xxx: Update version to 10.02.10.100-k (bsc#1256863).\n- scsi: qla2xxx: Validate MCU signature before executing MBC 03h (bsc#1256863).\n- scsi: qla2xxx: Validate sp before freeing associated memory (bsc#1256863).\n- scsi: storvsc: Process unsupported MODE_SENSE_10 (bsc#1257296).\n- selftests/bpf: Skip timer cases when bpf_timer is not supported (git-fixes).\n- serial: 8250: 8250_omap.c: Clear DMA RX running status only after DMA termination is done (stable-fixes).\n- serial: 8250_dw: handle clock enable errors in runtime_resume (stable-fixes).\n- serial: 8250_pci: Fix broken RS485 for F81504/508/512 (git-fixes).\n- serial: SH_SCI: improve \"DMA support\" prompt (git-fixes).\n- serial: add support of CPCI cards (stable-fixes).\n- serial: amba-pl011: prefer dma_mapping_error() over explicit address checking (git-fixes).\n- serial: imx: change SERIAL_IMX_CONSOLE to bool (git-fixes).\n- serial: sprd: Return -EPROBE_DEFER when uart clock is not ready (stable-fixes).\n- shrink_slab_memcg: clear_bits of skipped shrinkers (bsc#1256564).\n- slimbus: core: fix OF node leak on registration failure (git-fixes).\n- slimbus: core: fix device reference leak on report present (git-fixes).\n- slimbus: core: fix of_slim_get_device() kernel doc (git-fixes).\n- slimbus: core: fix runtime PM imbalance on report present (git-fixes).\n- slimbus: ngd: Fix reference count leak in qcom_slim_ngd_notify_slaves (git-fixes).\n- smb3: add missing null server pointer check (git-fixes).\n- smb: change return type of cached_dir_lease_break() to bool (git-fixes).\n- smb: client: ensure open_cached_dir_by_dentry() only returns valid cfid (git-fixes).\n- smb: client: fix cifs_pick_channel when channel needs reconnect (git-fixes).\n- smb: client: fix warning when reconnecting channel (git-fixes).\n- smb: client: introduce close_cached_dir_locked() (git-fixes).\n- smb: client: remove unused fid_lock (git-fixes).\n- smb: client: short-circuit in open_cached_dir_by_dentry() if !dentry (git-fixes).\n- smb: client: split cached_fid bitfields to avoid shared-byte RMW races (bsc#1250748,bsc#1257154).\n- smb: client: update cfid-\u003elast_access_time in open_cached_dir_by_dentry() (git-fixes).\n- smb: improve directory cache reuse for readdir operations (bsc#1252712).\n- smc91x: fix broken irq-context in PREEMPT_RT (git-fixes).\n- soc/tegra: fuse: speedo-tegra210: Update speedo IDs (git-fixes).\n- soc: amlogic: canvas: fix device leak on lookup (git-fixes).\n- soc: mediatek: svs: Fix memory leak in svs_enable_debug_write() (git-fixes).\n- soc: qcom: cmd-db: Use devm_memremap() to fix memory leak in cmd_db_dev_probe (git-fixes).\n- soc: qcom: ocmem: fix device leak on lookup (git-fixes).\n- soc: qcom: smem: fix hwspinlock resource leak in probe error paths (git-fixes).\n- soc: qcom: smem: handle ENOMEM error during probe (git-fixes).\n- soc: ti: k3-socinfo: Fix regmap leak on probe failure (git-fixes).\n- soc: ti: pruss: Fix double free in pruss_clk_mux_setup() (git-fixes).\n- soundwire: dmi-quirks: add mapping for Avell B.ON (OEM rebranded of NUC15) (stable-fixes).\n- spi-geni-qcom: initialize mode related registers to 0 (stable-fixes).\n- spi-geni-qcom: use xfer-\u003ebits_per_word for can_dma() (stable-fixes).\n- spi: amlogic-spifc-a1: Handle devm_pm_runtime_enable() errors (git-fixes).\n- spi: bcm63xx: drop wrong casts in probe() (git-fixes).\n- spi: bcm63xx: fix premature CS deassertion on RX-only transactions (git-fixes).\n- spi: fsl-cpm: Check length parity before switching to 16 bit mode (git-fixes).\n- spi: imx: keep dma request disabled before dma transfer setup (stable-fixes).\n- spi: spi-mem: Limit octal DTR constraints to octal DTR situations (stable-fixes).\n- spi: spi-mem: Protect dirmap_create() with spi_mem_access_start/end (stable-fixes).\n- spi: spi-sprd-adi: Fix double free in probe error path (git-fixes).\n- spi: sprd-adi: switch to use spi_alloc_host() (stable-fixes).\n- spi: sprd: adi: Use devm_register_restart_handler() (stable-fixes).\n- spi: stm32: fix Overrun issue at \u0026lt; 8bpw (stable-fixes).\n- spi: tegra114: Preserve SPI mode bits in def_command1_reg (git-fixes).\n- spi: tegra210-qspi: Remove cache operations (git-fixes)\n- spi: tegra210-quad: Add support for internal DMA (git-fixes)\n- spi: tegra210-quad: Check hardware status on timeout (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (bsc#1253155)\n- spi: tegra210-quad: Fix timeout handling (git-fixes).\n- spi: tegra210-quad: Move curr_xfer read inside spinlock (bsc#1257952)\n- spi: tegra210-quad: Move curr_xfer read inside spinlock (git-fixes).\n- spi: tegra210-quad: Protect curr_xfer assignment in (bsc#1257952)\n- spi: tegra210-quad: Protect curr_xfer assignment in tegra_qspi_setup_transfer_one (git-fixes).\n- spi: tegra210-quad: Protect curr_xfer check in IRQ handler (bsc#1257952)\n- spi: tegra210-quad: Protect curr_xfer check in IRQ handler (git-fixes).\n- spi: tegra210-quad: Protect curr_xfer clearing in (bsc#1257952)\n- spi: tegra210-quad: Protect curr_xfer clearing in tegra_qspi_non_combined_seq_xfer (git-fixes).\n- spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer (bsc#1257952)\n- spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer (git-fixes).\n- spi: tegra210-quad: Refactor error handling into helper functions (bsc#1253155)\n- spi: tegra210-quad: Return IRQ_HANDLED when timeout already processed (bsc#1257952)\n- spi: tegra210-quad: Return IRQ_HANDLED when timeout already processed transfer (git-fixes).\n- spi: tegra210-quad: Update dummy sequence configuration (git-fixes)\n- spi: tegra: Fix a memory leak in tegra_slink_probe() (git-fixes).\n- spi: wpcm-fiu: Fix potential NULL pointer dereference in wpcm_fiu_probe() (git-fixes).\n- spi: wpcm-fiu: Fix uninitialized res (git-fixes).\n- spi: wpcm-fiu: Simplify with dev_err_probe() (stable-fixes).\n- spi: wpcm-fiu: Use devm_platform_ioremap_resource_byname() (stable-fixes).\n- spi: xilinx: increase number of retries before declaring stall (stable-fixes).\n- staging: fbtft: core: fix potential memory leak in fbtft_probe_common() (git-fixes).\n- staging: rtl8723bs: fix memory leak on failure path (stable-fixes).\n- staging: rtl8723bs: fix null dereference in find_network (git-fixes).\n- staging: rtl8723bs: fix out-of-bounds read in OnBeacon ESR IE parsing (stable-fixes).\n- staging: rtl8723bs: fix out-of-bounds read in rtw_get_ie() parser (stable-fixes).\n- supported.conf: Mark lan 743x supported (jsc#PED-14571)\n- thermal: int340x: Fix sysfs group leak on DLVR registration failure (stable-fixes).\n- thunderbolt: Add support for Intel Wildcat Lake (stable-fixes).\n- tools/power cpupower: Reset errno before strtoull() (stable-fixes).\n- tools/power/x86/intel-speed-select: Fix file descriptor leak in isolate_cpus() (git-fixes).\n- tpm: st33zp24: Fix missing cleanup on get_burstcount() error (git-fixes).\n- tpm: tpm_i2c_infineon: Fix locality leak on get_burstcount() failure (git-fixes).\n- tracing: Fix access to trace_event_file (bsc#1254373).\n- uacce: ensure safe queue release with state management (git-fixes).\n- uacce: fix cdev handling in the cleanup path (git-fixes).\n- uacce: fix isolate sysfs check condition (git-fixes).\n- uacce: implement mremap in uacce_vm_ops to return -EPERM (git-fixes).\n- uio: uio_fsl_elbc_gpcm:: Add null pointer check to uio_fsl_elbc_gpcm_probe (git-fixes).\n- usb: bdc: fix sleep during atomic (git-fixes).\n- usb: cdns3: Fix double resource release in cdns3_pci_probe (git-fixes).\n- usb: chaoskey: fix locking for O_NONBLOCK (git-fixes).\n- usb: chipidea: udc: limit usb request length to max 16KB (stable-fixes).\n- usb: core: add USB_QUIRK_NO_BOS for devices that hang on BOS descriptor (stable-fixes).\n- usb: dwc2: disable platform lowlevel hw resources during shutdown (stable-fixes).\n- usb: dwc2: fix hang during shutdown if set as peripheral (git-fixes).\n- usb: dwc2: fix hang during suspend if set as peripheral (git-fixes).\n- usb: dwc2: fix resume failure if dr_mode is host (git-fixes).\n- usb: dwc3: Abort suspend on soft disconnect failure (git-fixes).\n- usb: dwc3: Check for USB4 IP_NAME (stable-fixes).\n- usb: dwc3: Fix race condition between concurrent dwc3_remove_requests() call paths (git-fixes).\n- usb: dwc3: keep susphy enabled during exit to avoid controller faults (git-fixes).\n- usb: dwc3: of-simple: fix clock resource leak in dwc3_of_simple_probe (git-fixes).\n- usb: dwc3: pci: Sort out the Intel device IDs (stable-fixes).\n- usb: dwc3: pci: add support for the Intel Nova Lake -S (stable-fixes).\n- usb: gadget: configfs: Correctly set use_os_string at bind (git-fixes).\n- usb: gadget: f_eem: Fix memory leak in eem_unwrap (git-fixes).\n- usb: gadget: lpc32xx_udc: fix clock imbalance in error path (git-fixes).\n- usb: gadget: renesas_usbf: Handle devm_pm_runtime_enable() errors (git-fixes).\n- usb: gadget: tegra-xudc: Add handling for BLCG_COREPLL_PWRDN (git-fixes).\n- usb: gadget: tegra-xudc: Always reinitialize data toggle when clear halt (git-fixes).\n- usb: ohci-nxp: Use helper function devm_clk_get_enabled() (stable-fixes).\n- usb: ohci-nxp: fix device leak on probe failure (git-fixes).\n- usb: phy: Initialize struct usb_phy list_head (git-fixes).\n- usb: phy: isp1301: fix non-OF device reference imbalance (git-fixes).\n- usb: raw-gadget: cap raw_io transfer length to KMALLOC_MAX_SIZE (git-fixes).\n- usb: raw-gadget: do not limit transfer length (git-fixes).\n- usb: renesas_usbhs: Fix a resource leak in usbhs_pipe_malloc() (git-fixes).\n- usb: storage: Fix memory leak in USB bulk transport (git-fixes).\n- usb: storage: sddr55: Reject out-of-bound new_pba (stable-fixes).\n- usb: typec: tipd: Clear interrupts first (git-fixes).\n- usb: typec: ucsi: Handle incorrect num_connectors capability (stable-fixes).\n- usb: typec: ucsi: psy: Set max current to zero when disconnected (git-fixes).\n- usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer (git-fixes).\n- usb: udc: Add trace event for usb_gadget_set_state (stable-fixes).\n- usb: usb-storage: Maintain minimal modifications to the bcdDevice range (git-fixes).\n- usb: usb-storage: No additional quirks need to be added to the EL-R12 optical drive (stable-fixes).\n- usb: vhci-hcd: Prevent suspending virtually attached devices (git-fixes).\n- usb: xhci: limit run_graceperiod for only usb 3.0 devices (stable-fixes).\n- usbip: Fix locking bug in RT-enabled kernels (stable-fixes).\n- usbnet: limit max_mtu based on device's hard_mtu (git-fixes).\n- via_wdt: fix critical boot hang due to unnamed resource allocation (stable-fixes).\n- virtio_console: fix order of fields cols and rows (stable-fixes).\n- w1: fix redundant counter decrement in w1_attach_slave_device() (git-fixes).\n- w1: therm: Fix off-by-one buffer overflow in alarms_store (git-fixes).\n- watchdog: imx7ulp_wdt: handle the nowayout option (stable-fixes).\n- watchdog: wdat_wdt: Fix ACPI table leak in probe function (git-fixes).\n- wifi: ath10k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: ath10k: fix lock protection in ath10k_wmi_event_peer_sta_ps_state_chg() (stable-fixes).\n- wifi: ath10k: sdio: add missing lock protection in ath10k_sdio_fw_crashed_dump() (git-fixes).\n- wifi: ath11k: add pm quirk for Thinkpad Z13/Z16 Gen1 (stable-fixes).\n- wifi: ath11k: fix peer HE MCS assignment (git-fixes).\n- wifi: ath11k: restore register window after global reset (git-fixes).\n- wifi: ath12k: fix dma_free_coherent() pointer (git-fixes).\n- wifi: ath12k: fix preferred hardware mode calculation (stable-fixes).\n- wifi: ath9k: debug.h: fix kernel-doc bad lines and struct ath_tx_stats (git-fixes).\n- wifi: ath9k: fix kernel-doc warnings in common-debug.h (git-fixes).\n- wifi: avoid kernel-infoleak from struct iw_point (git-fixes).\n- wifi: brcmfmac: Add DMI nvram filename quirk for Acer A1 840 tablet (stable-fixes).\n- wifi: cfg80211: Fix bitrate calculation overflow for HE rates (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n- wifi: cfg80211: cancel rfkill_block work in wiphy_unregister() (git-fixes).\n- wifi: cfg80211: sme: store capped length in __cfg80211_connect_result() (git-fixes).\n- wifi: cfg80211: stop NAN and P2P in cfg80211_leave (git-fixes).\n- wifi: cfg80211: wext: fix IGTK key ID off-by-one (git-fixes).\n- wifi: cw1200: Fix potential memory leak in cw1200_bh_rx_helper() (git-fixes).\n- wifi: ieee80211: correct FILS status codes (git-fixes).\n- wifi: iwlegacy: add missing mutex protection in il3945_store_measurement() (stable-fixes).\n- wifi: iwlegacy: add missing mutex protection in il4965_store_tx_power() (stable-fixes).\n- wifi: iwlwifi: mvm: check the validity of noa_len (stable-fixes).\n- wifi: libertas: fix WARNING in usb_tx_block (stable-fixes).\n- wifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration (git-fixes).\n- wifi: mac80211: collect station statistics earlier when disconnect (stable-fixes).\n- wifi: mac80211: correctly check if CSA is active (stable-fixes).\n- wifi: mac80211: correctly decode TTLM with default link map (git-fixes).\n- wifi: mac80211: do not increment crypto_tx_tailroom_needed_cnt twice (stable-fixes).\n- wifi: mac80211: do not use old MBSSID elements (git-fixes).\n- wifi: mac80211: fix CMAC functions not handling errors (git-fixes).\n- wifi: mac80211: fix NULL pointer dereference in mesh_rx_csa_frame() (git-fixes).\n- wifi: mac80211: ocb: skip rx_no_sta when interface is not joined (stable-fixes).\n- wifi: mac80211: restore non-chanctx injection behaviour (git-fixes).\n- wifi: mt76: Fix DTS power-limits on little endian systems (git-fixes).\n- wifi: mwifiex: Fix a loop in mwifiex_update_ampdu_rxwinsize() (git-fixes).\n- wifi: nl80211: vendor-cmd: intel: fix a blank kernel-doc line warning (git-fixes).\n- wifi: radiotap: reject radiotap with unknown bits (git-fixes).\n- wifi: rsi: Fix memory corruption due to not set vif driver data size (git-fixes).\n- wifi: rtl818x: Fix potential memory leaks in rtl8180_init_rx_ring() (git-fixes).\n- wifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb() (git-fixes).\n- wifi: rtl8xxxu: fix slab-out-of-bounds in rtl8xxxu_sta_add (git-fixes).\n- wifi: rtlwifi: 8192cu: fix tid out of range in rtl92cu_tx_fill_desc() (git-fixes).\n- wifi: rtw88: 8822b: Avoid WARNING in rtw8822b_config_trx_mode() (stable-fixes).\n- wifi: rtw88: Add USB ID 2001:3329 for D-Link AC13U rev. A1 (stable-fixes).\n- wifi: rtw88: Fix alignment fault in rtw_core_enable_beacon() (git-fixes).\n- wifi: rtw88: fix DTIM period handling when conf-\u003edtim_period is zero (stable-fixes).\n- wifi: rtw88: limit indirect IO under powered off for RTL8822CS (git-fixes).\n- wifi: rtw88: rtw8821cu: Add ID for Mercusys MU6H (stable-fixes).\n- wifi: rtw89: pci: restore LDO setting after device resume (stable-fixes).\n- wifi: rtw89: wow: add reason codes for disassociation in WoWLAN mode (stable-fixes).\n- wifi: wlcore: ensure skb headroom before skb_push (stable-fixes).\n- workqueue: mark power efficient workqueue as unbounded if (bsc#1257891)\n- x86/hyperv: Fix APIC ID and VP index confusion in hv_snp_boot_ap() (git-fixes).\n- x86/microcode/AMD: Add TSA microcode SHAs (bsc#1256528).\n- x86/microcode/AMD: Add Zen5 model 0x44, stepping 0x1 minrev (bsc#1256528).\n- x86/microcode/AMD: Add more known models to entry sign checking (bsc#1256528).\n- x86/microcode/AMD: Add some forgotten models to the SHA check (bsc#1256528).\n- x86/microcode/AMD: Clean the cache if update did not load microcode (bsc#1256528).\n- x86/microcode/AMD: Extend the SHA check to Zen5, block loading of any unreleased standalone Zen5 microcode patches (bsc#1256528).\n- x86/microcode/AMD: Fix Entrysign revision check for Zen5/Strix Halo (bsc#1256528).\n- x86/microcode/AMD: Fix __apply_microcode_amd()'s return value (bsc#1256528).\n- x86/microcode/AMD: Limit Entrysign signature checking to known generations (bsc#1256528).\n- x86/microcode/AMD: Load only SHA256-checksummed patches (bsc#1256528).\n- x86/microcode/AMD: Select which microcode patch to load (bsc#1256528).\n- x86/microcode/AMD: Use sha256() instead of init/update/final (bsc#1256528).\n- x86/microcode: Fix Entrysign revision check for Zen1/Naples (bsc#1256528).\n- x86: make page fault handling disable interrupts properly (git-fixes).\n- xhci: dbgtty: fix device unregister (git-fixes).\n","status":"published","published":"2026-03-24T16:48:29Z","modified":"2026-03-31T17:23:42.028094Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"USN-8162-1","title":"linux-nvidia-tegra-5.15 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - Netfilter;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-37849, CVE-2025-38057, CVE-2025-38125, CVE-2025-38232,\nCVE-2025-38408, CVE-2025-38591, CVE-2025-40149, CVE-2025-40164,\nCVE-2025-68211, CVE-2025-68340, CVE-2025-68365, CVE-2025-68725,\nCVE-2025-68817, CVE-2025-71080, CVE-2025-71163, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71194, CVE-2025-71196, CVE-2025-71197, CVE-2025-71199,\nCVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23011, CVE-2026-23026, CVE-2026-23033,\nCVE-2026-23037, CVE-2026-23038, 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-23145, CVE-2026-23146, CVE-2026-23150,\nCVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-04-09T20:46:33Z","modified":"2026-11-04T20:00:57.209282559Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8180-1","title":"linux, linux-aws, linux-aws-5.15, linux-gcp, linux-gke, linux-gkeop, linux-lowlatency, linux-lowlatency-hwe-5.15, linux-nvidia, linux-oracle vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-38057, CVE-2025-38125, CVE-2025-38232, CVE-2025-38408,\nCVE-2025-38591, CVE-2025-40149, CVE-2025-40164, CVE-2025-68211,\nCVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817,\nCVE-2025-71162, CVE-2025-71163, 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-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23011, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058,\nCVE-2026-23061, CVE-2026-23063, CVE-2026-23064, CVE-2026-23071,\nCVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23078,\nCVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23087, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103,\nCVE-2026-23105, CVE-2026-23108, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23124, CVE-2026-23125, CVE-2026-23128,\nCVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,\nCVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-04-16T14:56:50Z","modified":"2026-11-04T20:02:50.833991911Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8180-2","title":"linux-fips, linux-gcp-fips vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-38057, CVE-2025-38125, CVE-2025-38232, CVE-2025-38408,\nCVE-2025-38591, CVE-2025-40149, CVE-2025-40164, CVE-2025-68211,\nCVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817,\nCVE-2025-71162, CVE-2025-71163, 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-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23011, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058,\nCVE-2026-23061, CVE-2026-23063, CVE-2026-23064, CVE-2026-23071,\nCVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23078,\nCVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23087, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103,\nCVE-2026-23105, CVE-2026-23108, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23124, CVE-2026-23125, CVE-2026-23128,\nCVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,\nCVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-04-17T10:03:16Z","modified":"2026-11-04T20:00:54.404675837Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8180-3","title":"linux-azure, linux-intel-iotg, linux-intel-iotg-5.15, linux-kvm, linux-oracle-5.15 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-38057, CVE-2025-38125, CVE-2025-38232, CVE-2025-38408,\nCVE-2025-38591, CVE-2025-40149, CVE-2025-40164, CVE-2025-68211,\nCVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817,\nCVE-2025-71162, CVE-2025-71163, 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-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23011, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058,\nCVE-2026-23061, CVE-2026-23063, CVE-2026-23064, CVE-2026-23071,\nCVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23078,\nCVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23087, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103,\nCVE-2026-23105, CVE-2026-23108, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23124, CVE-2026-23125, CVE-2026-23128,\nCVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,\nCVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-04-23T10:08:08Z","modified":"2026-11-04T20:01:09.397438585Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8180-4","title":"linux-azure-fips vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-38057, CVE-2025-38125, CVE-2025-38232, CVE-2025-38408,\nCVE-2025-38591, CVE-2025-40149, CVE-2025-40164, CVE-2025-68211,\nCVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817,\nCVE-2025-71162, CVE-2025-71163, 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-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23011, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058,\nCVE-2026-23061, CVE-2026-23063, CVE-2026-23064, CVE-2026-23071,\nCVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23078,\nCVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23087, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103,\nCVE-2026-23105, CVE-2026-23108, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23124, CVE-2026-23125, CVE-2026-23128,\nCVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,\nCVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-04-23T10:16:04Z","modified":"2026-11-04T20:00:51.459848197Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8180-5","title":"linux-ibm, linux-ibm-5.15 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-38057, CVE-2025-38125, CVE-2025-38232, CVE-2025-38408,\nCVE-2025-38591, CVE-2025-40149, CVE-2025-40164, CVE-2025-68211,\nCVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817,\nCVE-2025-71162, CVE-2025-71163, 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-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23011, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058,\nCVE-2026-23061, CVE-2026-23063, CVE-2026-23064, CVE-2026-23071,\nCVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23078,\nCVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23087, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103,\nCVE-2026-23105, CVE-2026-23108, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23124, CVE-2026-23125, CVE-2026-23128,\nCVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,\nCVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-04-24T09:40:12Z","modified":"2026-11-04T20:01:47.808317844Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8180-6","title":"linux-raspi vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-38057, CVE-2025-38125, CVE-2025-38232, CVE-2025-38408,\nCVE-2025-38591, CVE-2025-40149, CVE-2025-40164, CVE-2025-68211,\nCVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817,\nCVE-2025-71162, CVE-2025-71163, 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-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23011, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058,\nCVE-2026-23061, CVE-2026-23063, CVE-2026-23064, CVE-2026-23071,\nCVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23078,\nCVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23087, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103,\nCVE-2026-23105, CVE-2026-23108, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23124, CVE-2026-23125, CVE-2026-23128,\nCVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,\nCVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-05-11T13:31:35Z","modified":"2026-11-04T20:02:26.337311915Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8186-1","title":"linux-intel-iot-realtime, linux-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 - ARM64 architecture;\n - Block layer subsystem;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-38057, CVE-2025-38125, CVE-2025-38232, CVE-2025-38408,\nCVE-2025-38591, CVE-2025-40149, CVE-2025-40164, CVE-2025-68211,\nCVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817,\nCVE-2025-71080, CVE-2025-71162, CVE-2025-71163, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71194, CVE-2025-71196, CVE-2025-71197, CVE-2025-71199,\nCVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23011, CVE-2026-23026, CVE-2026-23033,\nCVE-2026-23037, CVE-2026-23038, CVE-2026-23049, CVE-2026-23056,\nCVE-2026-23058, CVE-2026-23061, CVE-2026-23063, CVE-2026-23064,\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-23087, CVE-2026-23089, CVE-2026-23090,\nCVE-2026-23091, CVE-2026-23093, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23103, CVE-2026-23105, CVE-2026-23108, CVE-2026-23119,\nCVE-2026-23120, CVE-2026-23121, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23128, CVE-2026-23133, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23150, CVE-2026-23164, CVE-2026-23167, CVE-2026-23170,\nCVE-2026-23209)\n","status":"published","published":"2026-04-17T10:11:57Z","modified":"2026-11-04T20:02:26.781247416Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8187-1","title":"linux-nvidia-tegra, linux-nvidia-tegra-igx vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-38057, CVE-2025-38125, CVE-2025-38232, CVE-2025-38408,\nCVE-2025-38591, CVE-2025-40149, CVE-2025-40164, CVE-2025-68211,\nCVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817,\nCVE-2025-71080, CVE-2025-71163, 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-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23011, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058,\nCVE-2026-23061, CVE-2026-23063, CVE-2026-23064, CVE-2026-23071,\nCVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23078,\nCVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23087, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103,\nCVE-2026-23105, CVE-2026-23108, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23124, CVE-2026-23125, CVE-2026-23128,\nCVE-2026-23133, CVE-2026-23145, CVE-2026-23146, CVE-2026-23150,\nCVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-04-17T10:20:59Z","modified":"2026-11-04T20:02:30.835188911Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8188-1","title":"linux-hwe-5.15 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Cryptographic API;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - Netfilter;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-37849, CVE-2025-38057, CVE-2025-38125, CVE-2025-38232,\nCVE-2025-38408, CVE-2025-38591, CVE-2025-40149, CVE-2025-40164,\nCVE-2025-68211, CVE-2025-68340, CVE-2025-68365, CVE-2025-68725,\nCVE-2025-68817, CVE-2025-71162, CVE-2025-71163, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71194, CVE-2025-71196, CVE-2025-71197, CVE-2025-71199,\nCVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23011, CVE-2026-23026, CVE-2026-23033,\nCVE-2026-23037, CVE-2026-23038, 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-23145, CVE-2026-23146, CVE-2026-23150,\nCVE-2026-23164, CVE-2026-23167, CVE-2026-23170, CVE-2026-23209)\n","status":"published","published":"2026-04-17T10:28:32Z","modified":"2026-11-04T20:02:06.689665497Z","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-8275-1","title":"linux-xilinx-zynqmp vulnerabilities","description":"Stonejiajia, Shir Tamari and Sagi Tzadik discovered that the OverlayFS\nimplementation in the Ubuntu Linux kernel did not properly perform\npermission checks in certain situations. A local attacker could possibly\nuse this to gain elevated privileges. (CVE-2023-2640)\n\nShir Tamari and Sagi Tzadik discovered that the OverlayFS implementation in\nthe Ubuntu Linux kernel did not properly perform permission checks in\ncertain situations. A local attacker could possibly use this to gain\nelevated privileges. (CVE-2023-32629)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - Block layer subsystem;\n - Drivers core;\n - Bluetooth drivers;\n - DMA engine subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - UACCE accelerator framework;\n - Ethernet bonding driver;\n - Network drivers;\n - STMicroelectronics network drivers;\n - Ethernet team driver;\n - NVME drivers;\n - PHY drivers;\n - SLIMbus drivers;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - Ext4 file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - NFC subsystem;\n - BPF subsystem;\n - IRQ subsystem;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - NET/ROM layer;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - XFRM subsystem;\n - Creative Sound Blaster X-Fi driver;\n - USB sound devices;\n(CVE-2023-53421, CVE-2023-53520, CVE-2023-53662, CVE-2023-54207,\nCVE-2025-38057, CVE-2025-38125, CVE-2025-38232, CVE-2025-38408,\nCVE-2025-38591, CVE-2025-40149, CVE-2025-40164, CVE-2025-68211,\nCVE-2025-68340, CVE-2025-68365, CVE-2025-68725, CVE-2025-68817,\nCVE-2025-71162, CVE-2025-71163, 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-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23011, CVE-2026-23026, CVE-2026-23033, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23049, CVE-2026-23056, CVE-2026-23058,\nCVE-2026-23061, CVE-2026-23063, CVE-2026-23064, CVE-2026-23071,\nCVE-2026-23073, CVE-2026-23075, CVE-2026-23076, CVE-2026-23078,\nCVE-2026-23080, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23087, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23103,\nCVE-2026-23105, CVE-2026-23108, CVE-2026-23112, CVE-2026-23119,\nCVE-2026-23120, CVE-2026-23121, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23128, CVE-2026-23133, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23150, CVE-2026-23164, CVE-2026-23167, CVE-2026-23170,\nCVE-2026-23209, CVE-2026-23273)\n","status":"published","published":"2026-05-19T09:19:03Z","modified":"2026-11-04T20:02:29.162600091Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8278-1","title":"linux, linux-aws, linux-aws-fips, linux-gcp, linux-gcp-fips, linux-gke, linux-gkeop, linux-ibm, linux-ibm-6.8, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-raspi, linux-raspi-realtime, linux-realtime, linux-realtime-6.8 vulnerabilities","description":"It 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\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - x86 architecture;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - Drivers core;\n - Null block device driver;\n - Ublk userspace block driver;\n - Bluetooth drivers;\n - Counter interface drivers;\n - DMA engine subsystem;\n - DPLL subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IIO subsystem;\n - On-Chip Interconnect management framework;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - Multiple devices driver;\n - UACCE accelerator framework;\n - MMC subsystem;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - NVME drivers;\n - PHY drivers;\n - x86 platform drivers;\n - i.MX PM domains;\n - SCSI subsystem;\n - SLIMbus drivers;\n - SPI subsystem;\n - TCM subsystem;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - HFS+ file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - Scheduler infrastructure;\n - Netfilter;\n - NFC subsystem;\n - Tracing infrastructure;\n - io_uring subsystem;\n - BPF subsystem;\n - Perf events;\n - Floating proportions library;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Ceph Core library;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - MAC80211 subsystem;\n - NET/ROM layer;\n - Packet sockets;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - Unix domain sockets;\n - VMware vSockets driver;\n - Wireless networking;\n - ALSA AC97 driver;\n - Generic PCM loopback sound driver;\n - Creative Sound Blaster X-Fi driver;\n - AMD SoC Alsa drivers;\n - Texas InstrumentS Audio (ASoC/HDA) drivers;\n - USB sound devices;\n - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, 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-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, 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-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-19T22:33:02Z","modified":"2026-11-05T19:04:28.160890429Z","updated_at":"2026-11-05T19:27:14.534654Z"},{"id":"USN-8278-2","title":"linux-azure vulnerabilities","description":"It 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\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n - ARM64 architecture;\n - x86 architecture;\n - Cryptographic API;\n - Compute Acceleration Framework;\n - Drivers core;\n - Null block device driver;\n - Ublk userspace block driver;\n - Bluetooth drivers;\n - Counter interface drivers;\n - DMA engine subsystem;\n - DPLL subsystem;\n - GPU drivers;\n - HID subsystem;\n - Intel Trace Hub HW tracing drivers;\n - IIO ADC drivers;\n - IIO subsystem;\n - On-Chip Interconnect management framework;\n - IRQ chip drivers;\n - Modular ISDN driver;\n - LED subsystem;\n - Multiple devices driver;\n - UACCE accelerator framework;\n - MMC subsystem;\n - Ethernet bonding driver;\n - Network drivers;\n - Mellanox network drivers;\n - NVME drivers;\n - PHY drivers;\n - x86 platform drivers;\n - i.MX PM domains;\n - SCSI subsystem;\n - SLIMbus drivers;\n - SPI subsystem;\n - TCM subsystem;\n - W1 Dallas's 1-wire bus driver;\n - Xen hypervisor drivers;\n - BTRFS file system;\n - EFI Variable file system;\n - exFAT file system;\n - Ext4 file system;\n - HFS+ file system;\n - Network file system (NFS) client;\n - Network file system (NFS) server daemon;\n - NTFS3 file system;\n - SMB network file system;\n - Scheduler infrastructure;\n - Netfilter;\n - NFC subsystem;\n - Tracing infrastructure;\n - io_uring subsystem;\n - BPF subsystem;\n - Perf events;\n - Floating proportions library;\n - Memory management;\n - Bluetooth subsystem;\n - CAN network layer;\n - Ceph Core library;\n - Networking core;\n - IPv4 networking;\n - IPv6 networking;\n - L2TP protocol;\n - MAC80211 subsystem;\n - NET/ROM layer;\n - Packet sockets;\n - Network traffic control;\n - SCTP protocol;\n - TLS protocol;\n - Unix domain sockets;\n - VMware vSockets driver;\n - Wireless networking;\n - ALSA AC97 driver;\n - Generic PCM loopback sound driver;\n - Creative Sound Blaster X-Fi driver;\n - AMD SoC Alsa drivers;\n - Texas InstrumentS Audio (ASoC/HDA) drivers;\n - USB sound devices;\n - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, 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-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, 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-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-26T19:00:47Z","modified":"2026-11-05T19:01:25.946958298Z","updated_at":"2026-11-05T19:27:36.688147Z"}]},"sources_more":{"osv":14}}