{"id":"CVE-2025-68173","aliases":["BELL-CVE-2025-68173","CLSA-2026-1791132991","CLSA-2026-1791876326","CLSA-2026-1791878869","DEBIAN-CVE-2025-68173","DLA-4436-1","EUVD-2025-203723","GHSA-6j5g-jv8m-99rc","MGASA-2026-0017","MGASA-2026-0018","OESA-2026-1759","OESA-2026-1760","OESA-2026-1761","ROOT-OS-DEBIAN-11-CVE-2025-68173","ROOT-OS-DEBIAN-12-CVE-2025-68173","ROOT-OS-UBUNTU-2204-CVE-2025-68173","ROOT-OS-UBUNTU-2404-CVE-2025-68173","SUSE-SU-2026:20838-1","SUSE-SU-2026:20873-1","SUSE-SU-2026:20931-1","SUSE-SU-2026:21284-1","UBUNTU-CVE-2025-68173","USN-8029-1","USN-8029-2","USN-8029-3","USN-8030-1","USN-8048-1","USN-8095-1","USN-8095-2","USN-8095-3","USN-8095-4","USN-8095-5","USN-8100-1","USN-8125-1","USN-8126-1","USN-8165-1","USN-8261-1","openSUSE-SU-2026:20416-1"],"status":"published","title":"ftrace: Fix softlockup in ftrace_module_enable","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\"ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\") and commit 42ea22e754ba (\"ftrace: Add cond_resched() to\nftrace_graph_set_hash()\").\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.","severity":{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high","from":"osv"},"epss":{"day":"2026-11-10","score":0.00201,"percentile":0.10083,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2025-12-16T13:42:53Z","modified":"2026-11-11T09:39:18Z","fixes":[{"ecosystem":"Alpaquita:23","package":"linux-lts","fixed_in":["6.1.159-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.58-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.1.159","6.6.117","6.12.58","6.17.8"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"linux","fixed_in":["6.1.159-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.63-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.17.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:22.04:LTS","package":"linux-aws-6.8","fixed_in":["6.8.0-1050.53~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1051.57~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-6.8","fixed_in":["6.8.0-1058.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","fixed_in":["6.8.0-1052.55~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-106.106~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1049.49~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-106.106.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1049.52~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1047.48~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-106.106~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1045.46~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-106.106"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1050.53"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","fixed_in":["6.17.0-1007.7~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1051.57"],"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-1052.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","fixed_in":["6.17.0-1008.8~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1048.53"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1035.38"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1049.49"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-106.106.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1049.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","fixed_in":["6.17.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1049.52.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1020.20"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","fixed_in":["6.17.0-1011.11"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1047.48"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","fixed_in":["6.17.0-1007.7~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1050.54"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1028.29"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1017.21"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2040.41"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1045.46"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","fixed_in":["6.17.0-1006.7~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1050.53+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1052.58+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-106.106+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1052.55+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux","fixed_in":["6.17.0-14.14"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-aws","fixed_in":["6.17.0-1007.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-azure","fixed_in":["6.17.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-gcp","fixed_in":["6.17.0-1007.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-oracle","fixed_in":["6.17.0-1007.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-raspi","fixed_in":["6.17.0-1008.8"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-realtime","fixed_in":["6.17.0-1006.7"],"sources":["osv"]},{"ecosystem":"Ubuntu:25.10","package":"linux-riscv","fixed_in":["6.17.0-14.14.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpaquita:23","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.1.158-r0"},{"fixed":"6.1.159-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.57-r0"},{"fixed":"6.12.58-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:Ubuntu:20.04","package":"linux-buildinfo-5.4.0-239-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-buildinfo-5.4.0-239-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-239","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-239-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-5.4.0-239-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-239","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-239-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-headers-5.4.0-239-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-image-unsigned-5.4.0-239-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-image-unsigned-5.4.0-239-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-5.4.0-239-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-5.4.0-239-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-modules-extra-5.4.0-239-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-source-5.4.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-239","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-239-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-5.4.0-239-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:20.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.4.0-239.259+tuxcare.els1"}]}],"bundled":396},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-buildinfo-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-266","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-cloud-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-doc","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-266","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-headers-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-image-unsigned-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-libc-dev","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-modules-extra-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-source-4.15.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-266","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-common","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:18.04","package":"linux-tools-host","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-buildinfo-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-cloud-tools-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.15.0-266","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-headers-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-hwe-cloud-tools-4.15.0-266","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-hwe-tools-4.15.0-266","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-image-unsigned-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-modules-extra-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-source-4.15.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.15.0-266-generic","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"TuxCare:Ubuntu:16.04","package":"linux-tools-4.15.0-266-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.15.0-266.277~16.04.1+tuxcare.els1"}]}],"bundled":277},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"4.5.0"},{"fixed":"6.1.159"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.117"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.58"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.17.8"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.159-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.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.63-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~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.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.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.2-1~exp1","6.17.5-1~exp1","6.17.6-1","6.17.7-1","6.17.7-2","6.17.8-1~bpo13+1"]},{"source":"osv","ecosystem":"Debian:11","package":"linux-6.1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.159-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"],"bundled":114},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.120-1.mga9"}]}],"bundled":236},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.14-14.mga9"}]}],"bundled":236},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-88.mga9"}]}],"bundled":236},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.120-1.mga9"}]}],"bundled":236},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.127.oe2403"}]}],"bundled":85},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.139.oe2403sp1"}]}],"bundled":122},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-144.0.0.140.oe2403sp2"}]}],"bundled":85},{"source":"osv","ecosystem":"Root:Debian:11","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root:Debian:11","package":"rootio-linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.10.262-1.aikido.113"},{"fixed":"5.10.262-1.aikido.114"}]}]},{"source":"osv","ecosystem":"Root: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 Micro 6.2","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.2","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Micro Extras 6.2","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"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.27.1"}]}],"bundled":176},{"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.27.1"}]}],"bundled":176},{"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.27.1"}]}],"bundled":176},{"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.27.1.160000.2.8"}]}],"bundled":176},{"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.27.1"}]}],"bundled":176},{"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.27.1"}]}],"bundled":176},{"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.27.1"}]}],"bundled":176},{"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.27.1"}]}],"bundled":176},{"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.27.1"}]}],"bundled":176},{"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.27.1"}]}],"bundled":176},{"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:16.04:LTS","package":"linux-aws-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1030.31~16.04.1","4.15.0-1031.33~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1035.37~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1039.41~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43~16.04.1","4.15.0-1043.45~16.04.1","4.15.0-1044.46~16.04.1","4.15.0-1045.47~16.04.1","4.15.0-1047.49~16.04.1","4.15.0-1048.50~16.04.1","4.15.0-1050.52~16.04.1","4.15.0-1051.53~16.04.1","4.15.0-1052.54~16.04.1","4.15.0-1054.56~16.04.1","4.15.0-1056.58~16.04.1","4.15.0-1057.59~16.04.1","4.15.0-1058.60~16.04.1","4.15.0-1060.62~16.04.1","4.15.0-1063.67~16.04.1","4.15.0-1065.69~16.04.1","4.15.0-1066.70~16.04.1","4.15.0-1067.71~16.04.1","4.15.0-1073.77~16.04.1","4.15.0-1074.78~16.04.1","4.15.0-1079.83~16.04.1","4.15.0-1080.84~16.04.1","4.15.0-1082.86~16.04.1","4.15.0-1083.87~16.04.1","4.15.0-1085.90~16.04.1","4.15.0-1088.93~16.04.1","4.15.0-1090.95~16.04.1","4.15.0-1091.96~16.04.1","4.15.0-1093.99~16.04.1","4.15.0-1094.101~16.04.1","4.15.0-1095.102~16.04.1","4.15.0-1096.103~16.04.1","4.15.0-1097.104~16.04.1","4.15.0-1098.105~16.04.1","4.15.0-1099.106~16.04.1","4.15.0-1102.109~16.04.1","4.15.0-1103.110~16.04.1","4.15.0-1106.113~16.04.1","4.15.0-1109.116~16.04.1","4.15.0-1110.117~16.04.1","4.15.0-1111.118~16.04.1","4.15.0-1112.119~16.04.1","4.15.0-1113.120~16.04.1","4.15.0-1115.122~16.04.1","4.15.0-1116.123~16.04.1","4.15.0-1118.125~16.04.1","4.15.0-1119.126~16.04.2","4.15.0-1120.128~16.04.1","4.15.0-1123.132~16.04.1","4.15.0-1124.133~16.04.1","4.15.0-1126.135~16.04.2","4.15.0-1127.136~16.04.1","4.15.0-1128.137~16.04.1","4.15.0-1130.139~16.04.1","4.15.0-1133.143~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.154~16.04.1","4.15.0-1143.155~16.04.1","4.15.0-1146.158~16.04.2","4.15.0-1147.159~16.04.1","4.15.0-1148.160~16.04.1","4.15.0-1151.164~16.04.1","4.15.0-1153.166~16.04.1","4.15.0-1154.167~16.04.1","4.15.0-1155.168~16.04.1","4.15.0-1156.169~16.04.1","4.15.0-1157.170~16.04.1","4.15.0-1158.171~16.04.1","4.15.0-1159.172~16.04.1","4.15.0-1160.173~16.04.1","4.15.0-1161.174~16.04.1","4.15.0-1162.175~16.04.1","4.15.0-1163.176~16.04.1","4.15.0-1164.177~16.04.1","4.15.0-1165.178~16.04.1","4.15.0-1166.179~16.04.1","4.15.0-1167.180~16.04.1","4.15.0-1168.181~16.04.1","4.15.0-1169.182~16.04.1","4.15.0-1170.183~16.04.1","4.15.0-1172.185~16.04.1","4.15.0-1173.186~16.04.1","4.15.0-1174.187~16.04.1","4.15.0-1175.188~16.04.1","4.15.0-1176.189~16.04.1","4.15.0-1177.190~16.04.1","4.15.0-1178.191~16.04.1","4.15.0-1179.192~16.04.1","4.15.0-1180.193~16.04.1","4.15.0-1181.194~16.04.1","4.15.0-1182.195~16.04.1","4.15.0-1183.196~16.04.1","4.15.0-1184.197~16.04.1","4.15.0-1185.198~16.04.1","4.15.0-1186.199~16.04.1","4.15.0-1187.200~16.04.1","4.15.0-1188.201~16.04.1","4.15.0-1189.202~16.04.1","4.15.0-1190.203~16.04.1","4.15.0-1191.204~16.04.1","4.15.0-1192.205~16.04.1","4.15.0-1194.207~16.04.1","4.15.0-1195.208~16.04.1","4.15.0-1196.209~16.04.1","4.15.0-1197.210~16.04.1","4.15.0-1198.211~16.04.1","4.15.0-1199.212~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.11.0-1009.9","4.11.0-1011.11","4.11.0-1013.13","4.11.0-1014.14","4.11.0-1015.15","4.11.0-1016.16","4.13.0-1005.7","4.13.0-1006.8","4.13.0-1007.9","4.13.0-1009.12","4.13.0-1011.14","4.13.0-1012.15","4.13.0-1014.17","4.13.0-1016.19","4.13.0-1018.21","4.15.0-1013.13~16.04.2","4.15.0-1014.14~16.04.1","4.15.0-1018.18~16.04.1","4.15.0-1019.19~16.04.1","4.15.0-1021.21~16.04.1","4.15.0-1022.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1025.26~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1030.31~16.04.1","4.15.0-1031.32~16.04.1","4.15.0-1032.33~16.04.1","4.15.0-1035.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1039.43","4.15.0-1040.44","4.15.0-1041.45","4.15.0-1042.46","4.15.0-1045.49","4.15.0-1046.50","4.15.0-1047.51","4.15.0-1049.54","4.15.0-1050.55","4.15.0-1051.56","4.15.0-1052.57","4.15.0-1055.60","4.15.0-1056.61","4.15.0-1057.62","4.15.0-1059.64","4.15.0-1060.65","4.15.0-1061.66","4.15.0-1063.68","4.15.0-1064.69","4.15.0-1066.71","4.15.0-1067.72","4.15.0-1069.74","4.15.0-1071.76","4.15.0-1075.80","4.15.0-1077.82","4.15.0-1082.92~16.04.1","4.15.0-1083.93~16.04.1","4.15.0-1089.99~16.04.1","4.15.0-1091.101~16.04.1","4.15.0-1092.102~16.04.1","4.15.0-1093.103~16.04.1","4.15.0-1095.105~16.04.1","4.15.0-1096.106~16.04.1","4.15.0-1098.109~16.04.1","4.15.0-1100.111~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1103.114~16.04.1","4.15.0-1106.118~16.04.1","4.15.0-1108.120~16.04.1","4.15.0-1109.121~16.04.1","4.15.0-1110.122~16.04.1","4.15.0-1111.123~16.04.1","4.15.0-1112.124~16.04.1","4.15.0-1113.126~16.04.1","4.15.0-1114.127~16.04.1","4.15.0-1115.128~16.04.1","4.15.0-1118.131~16.04.1","4.15.0-1121.134~16.04.1","4.15.0-1122.135~16.04.1","4.15.0-1123.136~16.04.1","4.15.0-1124.137~16.04.1","4.15.0-1125.138~16.04.1","4.15.0-1126.139~16.04.1","4.15.0-1127.140~16.04.1","4.15.0-1129.142~16.04.1","4.15.0-1130.143~16.04.1","4.15.0-1131.144~16.04.1","4.15.0-1133.146~16.04.1","4.15.0-1134.147~16.04.1","4.15.0-1136.149~16.04.1","4.15.0-1137.150~16.04.1","4.15.0-1138.151~16.04.1","4.15.0-1139.152~16.04.1","4.15.0-1142.156~16.04.1","4.15.0-1145.160~16.04.1","4.15.0-1146.161~16.04.1","4.15.0-1149.164~16.04.1","4.15.0-1150.165~16.04.1","4.15.0-1151.166~16.04.1","4.15.0-1153.168~16.04.1","4.15.0-1159.174~16.04.1","4.15.0-1162.177~16.04.1","4.15.0-1163.178~16.04.1","4.15.0-1164.179~16.04.1","4.15.0-1165.180~16.04.1","4.15.0-1166.181~16.04.1","4.15.0-1167.182~16.04.1","4.15.0-1168.183~16.04.1","4.15.0-1169.184~16.04.1","4.15.0-1170.185~16.04.1","4.15.0-1171.186~16.04.1","4.15.0-1172.187~16.04.1","4.15.0-1173.188~16.04.1","4.15.0-1174.189~16.04.1","4.15.0-1175.190~16.04.1","4.15.0-1176.191~16.04.1","4.15.0-1177.192~16.04.1","4.15.0-1178.193~16.04.1","4.15.0-1179.194~16.04.1","4.15.0-1180.195~16.04.1","4.15.0-1181.196~16.04.1","4.15.0-1182.197~16.04.1","4.15.0-1183.198~16.04.1","4.15.0-1184.199~16.04.1","4.15.0-1185.200~16.04.1","4.15.0-1186.201~16.04.1","4.15.0-1187.202~16.04.1","4.15.0-1188.203~16.04.1","4.15.0-1189.204~16.04.1","4.15.0-1190.205~16.04.1","4.15.0-1191.206~16.04.1","4.15.0-1192.207~16.04.1","4.15.0-1193.208~16.04.1","4.15.0-1194.209~16.04.1","4.15.0-1195.210~16.04.1","4.15.0-1196.211~16.04.1","4.15.0-1197.212~16.04.1","4.15.0-1200.215~16.04.1","4.15.0-1204.219~16.04.1","4.15.0-1205.220~16.04.1","4.15.0-1206.221~16.04.1","4.15.0-1208.223~16.04.1","4.15.0-1209.224~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.10.0-1004.4","4.10.0-1006.6","4.10.0-1007.7","4.10.0-1008.8","4.10.0-1009.9","4.13.0-1002.5","4.13.0-1006.9","4.13.0-1007.10","4.13.0-1008.11","4.13.0-1011.15","4.13.0-1012.16","4.13.0-1013.17","4.13.0-1015.19","4.13.0-1017.21","4.13.0-1019.23","4.15.0-1014.14~16.04.1","4.15.0-1015.15~16.04.1","4.15.0-1017.18~16.04.1","4.15.0-1018.19~16.04.2","4.15.0-1019.20~16.04.1","4.15.0-1021.22~16.04.1","4.15.0-1023.24~16.04.1","4.15.0-1024.25~16.04.2","4.15.0-1025.26~16.04.1","4.15.0-1026.27~16.04.1","4.15.0-1027.28~16.04.1","4.15.0-1028.29~16.04.1","4.15.0-1029.31~16.04.1","4.15.0-1030.32~16.04.1","4.15.0-1032.34~16.04.1","4.15.0-1033.35~16.04.1","4.15.0-1034.36~16.04.1","4.15.0-1036.38~16.04.1","4.15.0-1037.39~16.04.1","4.15.0-1040.42~16.04.1","4.15.0-1041.43","4.15.0-1042.44","4.15.0-1044.46","4.15.0-1046.49","4.15.0-1047.50","4.15.0-1049.52","4.15.0-1050.53","4.15.0-1052.56","4.15.0-1055.59","4.15.0-1058.62","4.15.0-1060.64","4.15.0-1061.65","4.15.0-1071.81~16.04.1","4.15.0-1077.87~16.04.1","4.15.0-1078.88~16.04.1","4.15.0-1080.90~16.04.1","4.15.0-1081.92~16.04.1","4.15.0-1083.94~16.04.1","4.15.0-1084.95~16.04.1","4.15.0-1086.98~16.04.1","4.15.0-1087.100~16.04.1","4.15.0-1088.101~16.04.1","4.15.0-1090.103~16.04.1","4.15.0-1091.104~16.04.1","4.15.0-1092.105~16.04.1","4.15.0-1093.106~16.04.1","4.15.0-1094.107~16.04.1","4.15.0-1095.108~16.04.1","4.15.0-1096.109~16.04.1","4.15.0-1097.110~16.04.1","4.15.0-1098.111~16.04.1","4.15.0-1099.112~16.04.1","4.15.0-1100.113~16.04.1","4.15.0-1103.116~16.04.1","4.15.0-1106.120~16.04.1","4.15.0-1107.121~16.04.1","4.15.0-1108.122~16.04.1","4.15.0-1109.123~16.04.1","4.15.0-1110.124~16.04.1","4.15.0-1111.125~16.04.1","4.15.0-1112.126~16.04.1","4.15.0-1114.128~16.04.1","4.15.0-1115.129~16.04.1","4.15.0-1116.130~16.04.1","4.15.0-1118.132~16.04.1","4.15.0-1119.133~16.04.1","4.15.0-1120.134~16.04.1","4.15.0-1121.135~16.04.1","4.15.0-1122.136~16.04.1","4.15.0-1124.138~16.04.1","4.15.0-1127.142~16.04.1","4.15.0-1130.146~16.04.1","4.15.0-1131.147~16.04.1","4.15.0-1134.150~16.04.2","4.15.0-1135.151~16.04.2","4.15.0-1136.152~16.04.1","4.15.0-1137.153~16.04.1","4.15.0-1138.154~16.04.1","4.15.0-1141.157~16.04.2","4.15.0-1142.158~16.04.1","4.15.0-1143.159~16.04.1","4.15.0-1146.162~16.04.1","4.15.0-1147.163~16.04.1","4.15.0-1148.164~16.04.1","4.15.0-1149.165~16.04.1","4.15.0-1150.166~16.04.1","4.15.0-1151.167~16.04.1","4.15.0-1152.168~16.04.1","4.15.0-1153.170~16.04.1","4.15.0-1154.171~16.04.1","4.15.0-1155.172~16.04.1","4.15.0-1156.173~16.04.1","4.15.0-1157.174~16.04.1","4.15.0-1158.175~16.04.1","4.15.0-1159.176~16.04.1","4.15.0-1160.177~16.04.1","4.15.0-1161.178~16.04.1","4.15.0-1162.179~16.04.1","4.15.0-1163.180~16.04.1","4.15.0-1164.181~16.04.1","4.15.0-1165.182~16.04.1","4.15.0-1166.183~16.04.1","4.15.0-1167.184~16.04.2","4.15.0-1168.185~16.04.1","4.15.0-1169.186~16.04.1","4.15.0-1170.187~16.04.1","4.15.0-1171.188~16.04.1","4.15.0-1172.189~16.04.1","4.15.0-1173.190~16.04.1","4.15.0-1174.191~16.04.1","4.15.0-1175.192~16.04.1","4.15.0-1176.193~16.04.1","4.15.0-1177.194~16.04.1","4.15.0-1178.195~16.04.1","4.15.0-1179.196~16.04.1","4.15.0-1180.197~16.04.1","4.15.0-1181.198~16.04.1","4.15.0-1182.199~16.04.1","4.15.0-1183.200~16.04.2","4.15.0-1184.201~16.04.1","4.15.0-1185.202~16.04.1","4.15.0-1187.204~16.04.1","4.15.0-1188.205~16.04.1","4.15.0-1189.206~16.04.1","4.15.0-1190.207~16.04.1","4.15.0-1191.208~16.04.1","4.15.0-1192.209~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-hwe","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-36.36~16.04.1","4.8.0-39.42~16.04.1","4.8.0-41.44~16.04.1","4.8.0-42.45~16.04.1","4.8.0-44.47~16.04.1","4.8.0-45.48~16.04.1","4.8.0-46.49~16.04.1","4.8.0-49.52~16.04.1","4.8.0-51.54~16.04.1","4.8.0-52.55~16.04.1","4.8.0-53.56~16.04.1","4.8.0-54.57~16.04.1","4.8.0-56.61~16.04.1","4.8.0-58.63~16.04.1","4.10.0-27.30~16.04.2","4.10.0-28.32~16.04.2","4.10.0-30.34~16.04.1","4.10.0-32.36~16.04.1","4.10.0-33.37~16.04.1","4.10.0-35.39~16.04.1","4.10.0-37.41~16.04.1","4.10.0-38.42~16.04.1","4.10.0-40.44~16.04.1","4.10.0-42.46~16.04.1","4.13.0-26.29~16.04.2","4.13.0-31.34~16.04.1","4.13.0-32.35~16.04.1","4.13.0-36.40~16.04.1","4.13.0-37.42~16.04.1","4.13.0-38.43~16.04.1","4.13.0-39.44~16.04.1","4.13.0-41.46~16.04.1","4.13.0-43.48~16.04.1","4.13.0-45.50~16.04.1","4.15.0-24.26~16.04.1","4.15.0-29.31~16.04.1","4.15.0-30.32~16.04.1","4.15.0-32.35~16.04.1","4.15.0-33.36~16.04.1","4.15.0-34.37~16.04.1","4.15.0-36.39~16.04.1","4.15.0-38.41~16.04.1","4.15.0-39.42~16.04.1","4.15.0-42.45~16.04.1","4.15.0-43.46~16.04.1","4.15.0-45.48~16.04.1","4.15.0-46.49~16.04.1","4.15.0-47.50~16.04.1","4.15.0-48.51~16.04.1","4.15.0-50.54~16.04.1","4.15.0-51.55~16.04.1","4.15.0-52.56~16.04.1","4.15.0-54.58~16.04.1","4.15.0-55.60~16.04.2","4.15.0-58.64~16.04.1","4.15.0-60.67~16.04.1","4.15.0-62.69~16.04.1","4.15.0-64.73~16.04.1","4.15.0-65.74~16.04.1","4.15.0-66.75~16.04.1","4.15.0-69.78~16.04.1","4.15.0-70.79~16.04.1","4.15.0-72.81~16.04.1","4.15.0-74.83~16.04.1","4.15.0-76.86~16.04.1","4.15.0-88.88~16.04.1","4.15.0-91.92~16.04.1","4.15.0-96.97~16.04.1","4.15.0-99.100~16.04.1","4.15.0-101.102~16.04.1","4.15.0-106.107~16.04.1","4.15.0-107.108~16.04.1","4.15.0-112.113~16.04.1","4.15.0-115.116~16.04.1","4.15.0-117.118~16.04.1","4.15.0-118.119~16.04.1","4.15.0-120.122~16.04.1","4.15.0-122.124~16.04.1","4.15.0-123.126~16.04.1","4.15.0-126.129~16.04.1","4.15.0-128.131~16.04.1","4.15.0-129.132~16.04.1","4.15.0-132.136~16.04.1","4.15.0-133.137~16.04.1","4.15.0-136.140~16.04.1","4.15.0-137.141~16.04.1","4.15.0-139.143~16.04.1","4.15.0-140.144~16.04.1","4.15.0-142.146~16.04.1","4.15.0-143.147~16.04.3","4.15.0-144.148~16.04.1","4.15.0-147.151~16.04.1","4.15.0-151.157~16.04.1","4.15.0-153.160~16.04.1","4.15.0-154.161~16.04.1","4.15.0-156.163~16.04.1","4.15.0-158.166~16.04.1","4.15.0-159.167~16.04.1","4.15.0-161.169~16.04.1","4.15.0-162.170~16.04.1","4.15.0-163.171~16.04.1","4.15.0-166.174~16.04.1","4.15.0-167.175~16.04.1","4.15.0-169.177~16.04.1","4.15.0-171.180~16.04.1","4.15.0-173.182~16.04.1","4.15.0-175.184~16.04.1","4.15.0-176.185~16.04.1","4.15.0-177.186~16.04.1","4.15.0-180.189~16.04.1","4.15.0-184.194~16.04.1","4.15.0-187.198~16.04.1","4.15.0-188.199~16.04.1","4.15.0-189.200~16.04.1","4.15.0-191.202~16.04.1","4.15.0-192.203~16.04.1","4.15.0-193.204~16.04.1","4.15.0-194.205~16.04.1","4.15.0-196.207~16.04.1","4.15.0-197.208~16.04.1","4.15.0-200.211~16.04.2","4.15.0-201.212~16.04.1","4.15.0-202.213~16.04.1","4.15.0-206.217~16.04.1","4.15.0-208.219~16.04.1","4.15.0-209.220~16.04.1","4.15.0-210.221~16.04.1","4.15.0-211.222~16.04.1","4.15.0-212.223~16.04.1","4.15.0-213.224~16.04.1","4.15.0-214.225~16.04.1","4.15.0-216.227~16.04.1","4.15.0-218.229~16.04.1","4.15.0-219.230~16.04.1","4.15.0-220.231~16.04.1","4.15.0-221.232~16.04.1","4.15.0-222.233~16.04.1","4.15.0-223.235~16.04.1","4.15.0-224.236~16.04.1","4.15.0-225.237~16.04.1","4.15.0-226.238~16.04.1","4.15.0-227.239~16.04.1","4.15.0-228.240~16.04.1","4.15.0-229.241~16.04.1","4.15.0-230.242~16.04.1","4.15.0-231.243~16.04.1","4.15.0-232.244~16.04.1","4.15.0-233.245~16.04.1","4.15.0-234.246~16.04.1","4.15.0-235.247~16.04.1","4.15.0-236.248~16.04.1","4.15.0-237.249~16.04.1","4.15.0-238.250~16.04.1","4.15.0-239.251~16.04.1","4.15.0-240.252~16.04.1","4.15.0-241.253~16.04.1","4.15.0-242.254~16.04.1","4.15.0-243.255~16.04.1","4.15.0-245.257~16.04.1","4.15.0-246.258~16.04.1","4.15.0-247.259~16.04.1","4.15.0-248.260~16.04.1","4.15.0-249.261~16.04.1","4.15.0-250.262~16.04.1","4.15.0-253.265~16.04.1","4.15.0-254.266~16.04.1","4.15.0-257.269~16.04.1","4.15.0-260.272~16.04.2","4.15.0-261.273~16.04.1","4.15.0-262.274~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:16.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1007.9~16.04.1","4.15.0-1008.10~16.04.1","4.15.0-1009.11~16.04.1","4.15.0-1010.12~16.04.1","4.15.0-1011.13~16.04.1","4.15.0-1013.15~16.04.1","4.15.0-1014.16~16.04.1","4.15.0-1015.17~16.04.1","4.15.0-1017.19~16.04.2","4.15.0-1018.20~16.04.1","4.15.0-1021.23~16.04.1","4.15.0-1022.25~16.04.1","4.15.0-1023.26~16.04.1","4.15.0-1025.28~16.04.1","4.15.0-1026.29~16.04.1","4.15.0-1027.30~16.04.1","4.15.0-1029.32~16.04.1","4.15.0-1030.33~16.04.1","4.15.0-1031.34~16.04.1","4.15.0-1033.36~16.04.1","4.15.0-1035.38~16.04.1","4.15.0-1037.41~16.04.1","4.15.0-1038.42~16.04.1","4.15.0-1039.43~16.04.1","4.15.0-1045.49~16.04.1","4.15.0-1046.50~16.04.1","4.15.0-1050.54~16.04.1","4.15.0-1051.55~16.04.1","4.15.0-1053.57~16.04.1","4.15.0-1054.58~16.04.1","4.15.0-1056.61~16.04.1","4.15.0-1058.64~16.04.1","4.15.0-1059.65~16.04.1","4.15.0-1061.67~16.04.1","4.15.0-1062.68~16.04.1","4.15.0-1064.71~16.04.1","4.15.0-1065.73~16.04.1","4.15.0-1066.74~16.04.1","4.15.0-1067.75~16.04.1","4.15.0-1068.76~16.04.1","4.15.0-1069.77~16.04.1","4.15.0-1070.78~16.04.1","4.15.0-1071.79~16.04.1","4.15.0-1072.80~16.04.1","4.15.0-1075.83~16.04.1","4.15.0-1078.86~16.04.1","4.15.0-1079.87~16.04.1","4.15.0-1080.88~16.04.1","4.15.0-1081.89~16.04.1","4.15.0-1082.90~16.04.1","4.15.0-1083.91~16.04.1","4.15.0-1084.92~16.04.1","4.15.0-1085.93~16.04.1","4.15.0-1086.94~16.04.1","4.15.0-1087.95~16.04.1","4.15.0-1089.98~16.04.1","4.15.0-1090.99~16.04.1","4.15.0-1091.100~16.04.1","4.15.0-1092.101~16.04.1","4.15.0-1093.102~16.04.1","4.15.0-1095.104~16.04.1","4.15.0-1098.108~16.04.1","4.15.0-1101.112~16.04.1","4.15.0-1102.113~16.04.1","4.15.0-1104.115~16.04.1","4.15.0-1105.116~16.04.1","4.15.0-1106.117~16.04.1","4.15.0-1107.118~16.04.1","4.15.0-1108.119~16.04.1","4.15.0-1111.122~16.04.2","4.15.0-1112.123~16.04.1","4.15.0-1113.124~16.04.1","4.15.0-1115.126~16.04.1","4.15.0-1116.127~16.04.1","4.15.0-1117.128~16.04.1","4.15.0-1118.129~16.04.1","4.15.0-1119.130~16.04.1","4.15.0-1120.131~16.04.1","4.15.0-1121.132~16.04.1","4.15.0-1122.133~16.04.1","4.15.0-1123.134~16.04.1","4.15.0-1124.135~16.04.1","4.15.0-1125.136~16.04.1","4.15.0-1126.137~16.04.1","4.15.0-1127.138~16.04.1","4.15.0-1128.139~16.04.1","4.15.0-1129.140~16.04.1","4.15.0-1130.141~16.04.1","4.15.0-1131.142~16.04.1","4.15.0-1132.143~16.04.1","4.15.0-1133.144~16.04.1","4.15.0-1134.145~16.04.1","4.15.0-1135.146~16.04.1","4.15.0-1136.147~16.04.1","4.15.0-1137.148~16.04.1","4.15.0-1138.149~16.04.1","4.15.0-1139.150~16.04.1","4.15.0-1140.151~16.04.1","4.15.0-1141.152~16.04.1","4.15.0-1142.153~16.04.1","4.15.0-1143.154~16.04.1","4.15.0-1144.155~16.04.1","4.15.0-1145.156~16.04.1","4.15.0-1148.159~16.04.1","4.15.0-1149.160~16.04.1","4.15.0-1150.161~16.04.1","4.15.0-1151.162~16.04.1","4.15.0-1153.164~16.04.1","4.15.0-1154.165~16.04.1","4.15.0-1156.167~16.04.1","4.15.0-1158.169~16.04.1","4.15.0-1160.171~16.04.1","4.15.0-1161.172~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.13.0-16.19","4.13.0-17.20","4.13.0-25.29","4.13.0-32.35","4.15.0-10.11","4.15.0-12.13","4.15.0-13.14","4.15.0-15.16","4.15.0-19.20","4.15.0-20.21","4.15.0-22.24","4.15.0-23.25","4.15.0-24.26","4.15.0-29.31","4.15.0-30.32","4.15.0-32.35","4.15.0-33.36","4.15.0-34.37","4.15.0-36.39","4.15.0-38.41","4.15.0-39.42","4.15.0-42.45","4.15.0-43.46","4.15.0-44.47","4.15.0-45.48","4.15.0-46.49","4.15.0-47.50","4.15.0-48.51","4.15.0-50.54","4.15.0-51.55","4.15.0-52.56","4.15.0-54.58","4.15.0-55.60","4.15.0-58.64","4.15.0-60.67","4.15.0-62.69","4.15.0-64.73","4.15.0-65.74","4.15.0-66.75","4.15.0-69.78","4.15.0-70.79","4.15.0-72.81","4.15.0-74.84","4.15.0-76.86","4.15.0-88.88","4.15.0-91.92","4.15.0-96.97","4.15.0-99.100","4.15.0-101.102","4.15.0-106.107","4.15.0-108.109","4.15.0-109.110","4.15.0-111.112","4.15.0-112.113","4.15.0-115.116","4.15.0-117.118","4.15.0-118.119","4.15.0-121.123","4.15.0-122.124","4.15.0-123.126","4.15.0-124.127","4.15.0-126.129","4.15.0-128.131","4.15.0-129.132","4.15.0-130.134","4.15.0-132.136","4.15.0-134.138","4.15.0-135.139","4.15.0-136.140","4.15.0-137.141","4.15.0-139.143","4.15.0-140.144","4.15.0-141.145","4.15.0-142.146","4.15.0-143.147","4.15.0-144.148","4.15.0-147.151","4.15.0-151.157","4.15.0-153.160","4.15.0-154.161","4.15.0-156.163","4.15.0-158.166","4.15.0-159.167","4.15.0-161.169","4.15.0-162.170","4.15.0-163.171","4.15.0-166.174","4.15.0-167.175","4.15.0-169.177","4.15.0-171.180","4.15.0-173.182","4.15.0-175.184","4.15.0-176.185","4.15.0-177.186","4.15.0-180.189","4.15.0-184.194","4.15.0-187.198","4.15.0-188.199","4.15.0-189.200","4.15.0-191.202","4.15.0-192.203","4.15.0-193.204","4.15.0-194.205","4.15.0-196.207","4.15.0-197.208","4.15.0-200.211","4.15.0-201.212","4.15.0-202.213","4.15.0-204.215","4.15.0-206.217","4.15.0-208.220","4.15.0-209.220","4.15.0-210.221","4.15.0-211.222","4.15.0-212.223","4.15.0-213.224","4.15.0-214.225","4.15.0-216.227","4.15.0-218.229","4.15.0-219.230","4.15.0-220.231","4.15.0-221.232","4.15.0-222.233","4.15.0-223.235","4.15.0-224.236","4.15.0-225.237","4.15.0-226.238","4.15.0-227.239","4.15.0-228.240","4.15.0-229.241","4.15.0-230.242","4.15.0-231.243","4.15.0-232.244","4.15.0-233.245","4.15.0-234.246","4.15.0-235.247","4.15.0-236.248","4.15.0-237.249","4.15.0-238.250","4.15.0-239.251","4.15.0-240.252","4.15.0-241.253","4.15.0-242.254","4.15.0-243.255","4.15.0-245.257","4.15.0-246.258","4.15.0-247.259","4.15.0-248.260","4.15.0-249.261","4.15.0-250.262","4.15.0-251.263","4.15.0-253.265","4.15.0-254.266","4.15.0-257.269","4.15.0-260.272","4.15.0-261.273","4.15.0-262.274"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1007.7","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1011.11","4.15.0-1016.16","4.15.0-1017.17","4.15.0-1019.19","4.15.0-1020.20","4.15.0-1021.21","4.15.0-1023.23","4.15.0-1025.25","4.15.0-1027.27","4.15.0-1029.30","4.15.0-1031.33","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1035.37","4.15.0-1037.39","4.15.0-1039.41","4.15.0-1040.42","4.15.0-1041.43","4.15.0-1043.45","4.15.0-1044.46","4.15.0-1045.47","4.15.0-1047.49","4.15.0-1048.50","4.15.0-1050.52","4.15.0-1051.53","4.15.0-1052.54","4.15.0-1054.56","4.15.0-1056.58","4.15.0-1057.59","4.15.0-1058.60","4.15.0-1060.62","4.15.0-1063.67","4.15.0-1065.69","4.15.0-1066.70","4.15.0-1067.71","4.15.0-1073.77","4.15.0-1076.80","4.15.0-1077.81","4.15.0-1079.83","4.15.0-1080.84","4.15.0-1082.86","4.15.0-1083.87","4.15.0-1086.91","4.15.0-1087.92","4.15.0-1088.93","4.15.0-1090.95","4.15.0-1091.96","4.15.0-1092.98","4.15.0-1093.99","4.15.0-1094.101","4.15.0-1095.102","4.15.0-1096.103","4.15.0-1097.104","4.15.0-1098.105","4.15.0-1099.106","4.15.0-1101.108","4.15.0-1102.109","4.15.0-1103.110","4.15.0-1106.113","4.15.0-1109.116","4.15.0-1110.117","4.15.0-1111.118","4.15.0-1112.119","4.15.0-1114.121","4.15.0-1115.122","4.15.0-1116.123","4.15.0-1118.125","4.15.0-1119.127","4.15.0-1121.129","4.15.0-1123.132","4.15.0-1124.133","4.15.0-1126.135","4.15.0-1127.136","4.15.0-1128.137","4.15.0-1130.139","4.15.0-1133.143","4.15.0-1136.147","4.15.0-1137.148","4.15.0-1139.150","4.15.0-1140.151","4.15.0-1141.152","4.15.0-1142.154","4.15.0-1143.155","4.15.0-1144.156","4.15.0-1146.158","4.15.0-1147.159","4.15.0-1148.160","4.15.0-1150.163","4.15.0-1151.164","4.15.0-1153.166","4.15.0-1154.167","4.15.0-1155.168","4.15.0-1156.169","4.15.0-1157.170","4.15.0-1158.171","4.15.0-1159.172","4.15.0-1160.173","4.15.0-1161.174","4.15.0-1162.175","4.15.0-1163.176","4.15.0-1164.177","4.15.0-1165.178","4.15.0-1166.179","4.15.0-1167.180","4.15.0-1168.181","4.15.0-1169.182","4.15.0-1170.183","4.15.0-1172.185","4.15.0-1173.186","4.15.0-1174.187","4.15.0-1175.188","4.15.0-1176.189","4.15.0-1177.190","4.15.0-1178.191","4.15.0-1179.192","4.15.0-1180.193","4.15.0-1181.194","4.15.0-1182.195","4.15.0-1183.196","4.15.0-1184.197","4.15.0-1185.198","4.15.0-1186.199","4.15.0-1187.200","4.15.0-1188.201","4.15.0-1189.202","4.15.0-1190.203","4.15.0-1191.204","4.15.0-1192.205","4.15.0-1194.207","4.15.0-1195.208","4.15.0-1196.209","4.15.0-1197.210","4.15.0-1198.211","4.15.0-1199.212"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:Pro:18.04:LTS","package":"linux-aws-5.4","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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"}]}],"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","5.15.0-1105.112~20.04.1","5.15.0-1106.113~20.04.1","5.15.0-1108.115~20.04.1","5.15.0-1109.116~20.04.1","5.15.0-1111.118~20.04.1","5.15.0-1112.119~20.04.1","5.15.0-1114.121~20.04.1","5.15.0-1115.122~20.04.1","5.15.0-1116.123~20.04.1","5.15.0-1117.124~20.04.1","5.15.0-1119.126~20.04.1","5.15.0-1120.127~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"}]}],"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","5.15.0-1110.119~20.04.1","5.15.0-1111.120~20.04.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1123.132~20.04.1","5.15.0-1125.134~20.04.1","5.15.0-1126.135~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-azure-fde-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1019.24~20.04.1.1","5.15.0-1020.25~20.04.1.1","5.15.0-1021.26~20.04.1.1","5.15.0-1029.36~20.04.1.1","5.15.0-1030.37~20.04.1.1","5.15.0-1031.38~20.04.1.1","5.15.0-1033.40~20.04.1.1","5.15.0-1034.41~20.04.1.2","5.15.0-1035.42~20.04.1.1","5.15.0-1036.43~20.04.1.1","5.15.0-1037.44~20.04.1.1","5.15.0-1038.45~20.04.1.1","5.15.0-1039.46~20.04.1.1","5.15.0-1040.47~20.04.1.1","5.15.0-1041.48~20.04.1.1","5.15.0-1042.49~20.04.1.1","5.15.0-1043.50~20.04.1.1","5.15.0-1046.53~20.04.1.1","5.15.0-1047.54~20.04.1.1","5.15.0-1049.56~20.04.1.1","5.15.0-1050.57~20.04.1.1","5.15.0-1051.59~20.04.1.1","5.15.0-1052.60~20.04.1.1","5.15.0-1053.61~20.04.1.1","5.15.0-1054.62~20.04.1.1","5.15.0-1056.64~20.04.1.1","5.15.0-1057.65~20.04.1.1","5.15.0-1058.66~20.04.2.1","5.15.0-1059.67~20.04.1.1","5.15.0-1060.69~20.04.1.1","5.15.0-1061.70~20.04.1.1","5.15.0-1063.72~20.04.1.1","5.15.0-1064.73~20.04.1.1","5.15.0-1065.74~20.04.1.1","5.15.0-1067.76~20.04.1.1","5.15.0-1068.77~20.04.1.1","5.15.0-1070.79~20.04.1.1","5.15.0-1071.80~20.04.1.1","5.15.0-1072.81~20.04.1.1","5.15.0-1073.82~20.04.1.1","5.15.0-1074.83~20.04.1.1","5.15.0-1076.85~20.04.1.1","5.15.0-1078.87~20.04.1.1","5.15.0-1081.90~20.04.1.1","5.15.0-1082.91~20.04.1.1","5.15.0-1086.95~20.04.1.1","5.15.0-1087.96~20.04.1.1","5.15.0-1088.97~20.04.1.1","5.15.0-1089.98~20.04.1.1","5.15.0-1091.100~20.04.1.1","5.15.0-1094.103~20.04.1.1","5.15.0-1096.105~20.04.1.1","5.15.0-1097.106~20.04.1.1","5.15.0-1098.107~20.04.1.1","5.15.0-1102.111~20.04.1.1","5.15.0-1103.112~20.04.1.1","5.15.0-1111.120~20.04.1.1","5.15.0-1114.123~20.04.1","5.15.0-1116.125~20.04.1","5.15.0-1117.126~20.04.2","5.15.0-1118.127~20.04.1","5.15.0-1119.128~20.04.1","5.15.0-1120.129~20.04.1","5.15.0-1121.130~20.04.1","5.15.0-1122.131~20.04.1","5.15.0-1124.133~20.04.1","5.15.0-1125.134~20.04.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"}]}],"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","5.15.0-1106.115~20.04.1","5.15.0-1108.117~20.04.1","5.15.0-1109.118~20.04.1","5.15.0-1111.121~20.04.1","5.15.0-1112.122~20.04.1","5.15.0-1114.124~20.04.1","5.15.0-1118.128~20.04.1","5.15.0-1120.130~20.04.1","5.15.0-1121.131~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"}]}],"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","5.15.0-176.186~20.04.1","5.15.0-177.187~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-185.195~20.04.1","5.15.0-186.196~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-198.208~20.04.1","5.15.0-202.212~20.04.1","5.15.0-203.213~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"}]}],"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","5.15.0-1099.102~20.04.1","5.15.0-1100.103~20.04.1","5.15.0-1102.105~20.04.1","5.15.0-1103.106~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.1","5.15.0-1114.118~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"}]}],"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","5.15.0-1100.106~20.04.1","5.15.0-1101.107~20.04.1","5.15.0-1103.109~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1107.113~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1112.118~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1115.121~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"}]}],"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","5.15.0-175.185~20.04.1","5.15.0-177.187~20.04.1","5.15.0-178.188~20.04.1","5.15.0-179.189~20.04.1","5.15.0-181.191~20.04.1","5.15.0-183.193~20.04.1","5.15.0-184.194~20.04.1","5.15.0-190.200~20.04.1","5.15.0-191.201~20.04.1","5.15.0-194.204~20.04.1","5.15.0-195.205~20.04.1","5.15.0-197.207~20.04.1","5.15.0-198.208~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:20.04:LTS","package":"linux-nvidia-tegra-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1057.57~20.04.1","5.15.0-1058.58~20.04.1","5.15.0-1060.60~20.04.1","5.15.0-1061.61~20.04.1","5.15.0-1063.63~20.04.1","5.15.0-1064.66~20.04.1","5.15.0-1065.67~20.04.1","5.15.0-1066.68~20.04.1","5.15.0-1067.69~20.04.1","5.15.0-1068.70~20.04.1","5.15.0-1070.72~20.04.1","5.15.0-1071.73~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"}]}],"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","5.15.0-1102.108~20.04.1","5.15.0-1104.110~20.04.1","5.15.0-1106.112~20.04.1","5.15.0-1108.114~20.04.1","5.15.0-1109.115~20.04.1","5.15.0-1110.116~20.04.1","5.15.0-1111.117~20.04.1","5.15.0-1114.120~20.04.1","5.15.0-1116.122~20.04.1","5.15.0-1117.123~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"}]}],"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","5.15.0-1099.103~20.04.1","5.15.0-1100.104~20.04.1","5.15.0-1102.106~20.04.1","5.15.0-1103.107~20.04.1","5.15.0-1105.109~20.04.1","5.15.0-1106.110~20.04.1","5.15.0-1107.111~20.04.1","5.15.0-1108.112~20.04.1","5.15.0-1109.113~20.04.1","5.15.0-1110.114~20.04.1","5.15.0-1111.115~20.04.1","5.15.0-1113.117~20.04.2","5.15.0-1114.118~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"}]}],"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","5.15.0-176.186","5.15.0-177.187","5.15.0-179.189","5.15.0-181.191","5.15.0-185.195","5.15.0-186.196","5.15.0-187.197","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-198.208","5.15.0-202.212","5.15.0-203.213"]},{"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"}]}],"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","5.15.0-1105.112","5.15.0-1106.113","5.15.0-1108.115","5.15.0-1109.116","5.15.0-1111.118","5.15.0-1112.119","5.15.0-1113.120","5.15.0-1114.121","5.15.0-1115.122","5.15.0-1116.123","5.15.0-1117.124","5.15.0-1119.126","5.15.0-1120.127"]},{"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-1050.53~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1123.132","5.15.0-1125.134","5.15.0-1126.135"]},{"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-1051.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-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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1114.123","5.15.0-1116.125","5.15.0-1117.126","5.15.0-1118.127","5.15.0-1119.128","5.15.0-1120.129","5.15.0-1121.130","5.15.0-1122.131","5.15.0-1124.133","5.15.0-1125.134"]},{"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"}]}],"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","5.15.0-1105.114","5.15.0-1106.115","5.15.0-1108.117","5.15.0-1109.118","5.15.0-1111.121","5.15.0-1112.122","5.15.0-1114.124","5.15.0-1115.125","5.15.0-1117.127","5.15.0-1118.128","5.15.0-1120.130","5.15.0-1121.131"]},{"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-1052.55~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1101.107","5.15.0-1102.108","5.15.0-1104.110","5.15.0-1105.111","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1115.121","5.15.0-1116.122"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1088.96","5.15.0-1089.97","5.15.0-1091.99","5.15.0-1092.100","5.15.0-1094.102","5.15.0-1095.103","5.15.0-1096.104","5.15.0-1097.105","5.15.0-1098.106","5.15.0-1099.107","5.15.0-1100.108","5.15.0-1102.110","5.15.0-1103.111"]},{"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-106.106~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.109","5.15.0-1106.110","5.15.0-1107.111","5.15.0-1108.112","5.15.0-1109.113","5.15.0-1110.114","5.15.0-1111.115","5.15.0-1113.117","5.15.0-1114.118"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.49~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"]},{"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"}]}],"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","5.15.0-1100.106","5.15.0-1101.107","5.15.0-1103.109","5.15.0-1104.110","5.15.0-1106.112","5.15.0-1107.113","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1114.120","5.15.0-1115.121"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-kvm","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-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","5.15.0-1097.102","5.15.0-1098.103","5.15.0-1100.105","5.15.0-1101.106","5.15.0-1103.108","5.15.0-1104.109","5.15.0-1105.110","5.15.0-1106.111","5.15.0-1107.112","5.15.0-1108.113","5.15.0-1109.114","5.15.0-1111.116","5.15.0-1112.117"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-175.185","5.15.0-177.187","5.15.0-178.188","5.15.0-179.189","5.15.0-181.191","5.15.0-183.193","5.15.0-184.194","5.15.0-190.200","5.15.0-191.201","5.15.0-194.204","5.15.0-195.205","5.15.0-197.207","5.15.0-198.208"]},{"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-106.106.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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1100.101","5.15.0-1101.102","5.15.0-1103.104","5.15.0-1104.105","5.15.0-1106.107","5.15.0-1107.108","5.15.0-1108.109","5.15.0-1109.110","5.15.0-1110.111","5.15.0-1111.112","5.15.0-1112.113","5.15.0-1114.115","5.15.0-1115.116"]},{"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-1049.52~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1057.57","5.15.0-1058.58","5.15.0-1060.60","5.15.0-1061.61","5.15.0-1063.63","5.15.0-1064.66","5.15.0-1065.67","5.15.0-1066.68","5.15.0-1067.69","5.15.0-1068.70","5.15.0-1070.72","5.15.0-1071.73"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-tegra-igx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1046.46","5.15.0-1047.47","5.15.0-1049.49","5.15.0-1050.50","5.15.0-1052.52","5.15.0-1053.53","5.15.0-1054.54","5.15.0-1055.55","5.15.0-1056.56","5.15.0-1057.57","5.15.0-1059.59"]},{"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"}]}],"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","5.15.0-1102.108","5.15.0-1103.109","5.15.0-1105.111","5.15.0-1106.112","5.15.0-1108.114","5.15.0-1109.115","5.15.0-1110.116","5.15.0-1111.117","5.15.0-1112.118","5.15.0-1113.119","5.15.0-1114.120","5.15.0-1116.122","5.15.0-1117.123"]},{"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-1047.48~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"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1099.102","5.15.0-1100.103","5.15.0-1102.105","5.15.0-1103.106","5.15.0-1105.108","5.15.0-1106.109","5.15.0-1108.111","5.15.0-1110.113","5.15.0-1113.116"]},{"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-106.106~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"]},{"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"}]}],"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","5.15.0-1070.74","5.15.0-1074.78","5.15.0-1075.79","5.15.0-1076.80","5.15.0-1077.81","5.15.0-1078.82","5.15.0-1079.83","5.15.0-1080.84"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:22.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1089.91","5.15.0-1090.92","5.15.0-1092.94","5.15.0-1093.95","5.15.0-1095.97","5.15.0-1096.98","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1097.99","5.15.0-1098.100","5.15.0-1099.101","5.15.0-1100.102","5.15.0-1101.103","5.15.0-1103.105","5.15.0-1104.106","5.15.0-1105.107","5.15.0-1106.108","5.15.0-1107.109","5.15.0-1108.110","5.15.0-1109.111","5.15.0-1111.115","5.15.0-1112.116"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1104.113","5.15.0-1105.114","5.15.0-1107.116","5.15.0-1108.117","5.15.0-1110.119","5.15.0-1111.120","5.15.0-1112.121","5.15.0-1113.122","5.15.0-1114.123","5.15.0-1115.124","5.15.0-1116.125","5.15.0-1118.127","5.15.0-1119.128"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1045.46~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"]},{"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"}]}],"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","5.15.0-1105.112+fips1","5.15.0-1106.113+fips1","5.15.0-1108.115+fips1","5.15.0-1109.116+fips1","5.15.0-1111.118+fips1","5.15.0-1112.119+fips1","5.15.0-1113.120+fips1","5.15.0-1114.121+fips1","5.15.0-1115.122+fips1","5.15.0-1116.123+fips1","5.15.0-1117.124+fips1","5.15.0-1119.126+fips1","5.15.0-1120.127+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1110.119+fips1","5.15.0-1111.120+fips1","5.15.0-1114.123+fips1","5.15.0-1116.125+fips1","5.15.0-1117.126+fips1","5.15.0-1118.127+fips1","5.15.0-1119.128+fips1","5.15.0-1121.130+fips1","5.15.0-1122.131+fips1","5.15.0-1123.132+fips1","5.15.0-1125.134+fips1","5.15.0-1126.135+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-176.186+fips1","5.15.0-177.187+fips1","5.15.0-179.189+fips1","5.15.0-181.191+fips1","5.15.0-185.195+fips1","5.15.0-186.196+fips1","5.15.0-190.200+fips1","5.15.0-191.201+fips1","5.15.0-194.204+fips1","5.15.0-198.208+fips1","5.15.0-202.212+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:22.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"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","5.15.0-1105.114+fips1","5.15.0-1106.115+fips1","5.15.0-1108.117+fips1","5.15.0-1109.118+fips1","5.15.0-1111.121+fips1","5.15.0-1112.122+fips1","5.15.0-1114.124+fips1","5.15.0-1115.125+fips1","5.15.0-1116.126+fips1","5.15.0-1118.128+fips1","5.15.0-1120.130+fips1","5.15.0-1121.131+fips1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7~24.04.1"}]}],"versions":["6.17.0-1005.5~24.04.2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.57"}]}],"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"]},{"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-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-1052.55"}]}],"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"]},{"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-1008.8~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.3"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1048.53"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1035.38"}]}],"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"]},{"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-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.49"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106.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"]},{"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-1049.52"}]}],"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"]},{"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-1008.8"}]}],"versions":["6.17.0-1004.4"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52.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"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1020.20"}]}],"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"]},{"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-1011.11"}]}],"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"]},{"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-1047.48"}]}],"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"]},{"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-1007.7~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.54"}]}],"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"]},{"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-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1028.29"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1017.21"}]}],"versions":["6.8.0-1011.15","6.8.0-1012.16","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1016.20"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2040.41"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1045.46"}]}],"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"]},{"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-1006.7~24.04.1"}]}],"versions":["6.17.0-1004.5~24.04.2"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.58+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106+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"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55+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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-14.14"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1015.15","6.17.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1006.7"}]}],"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"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-14.14.1"}]}],"versions":["6.14.0-13.13.2","6.17.0-4.4.1","6.17.0-5.5.1","6.17.0-6.6.1","6.17.0-7.7.1","6.17.0-8.8.1","6.17.0-12.12.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-14.14"}]}],"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"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8"}]}],"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"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1006.7"}]}],"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"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"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"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"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"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1008.8"}]}],"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"],"bundled":367},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1007.7"}]}],"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"],"bundled":366},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1011.11"}]}],"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"],"bundled":366},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55~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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106~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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.49~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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106.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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.48~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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1048.53"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1035.38"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.49"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106.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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1047.48"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53+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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-106.106+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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.55+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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1045.46~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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1045.46"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.53~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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1050.54"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2040.41"}]}],"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"],"bundled":423},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52~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"],"bundled":425},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52"}]}],"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"],"bundled":425},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1049.52.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"],"bundled":425},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.57"}]}],"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"],"bundled":426},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1051.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-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"],"bundled":1179},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1052.58+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"],"bundled":438},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1029.30"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29"],"bundled":609},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1.160000.2.8"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-obs-qa","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-rt","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.27.1"}]}],"bundled":176}],"products":[{"vendor":"linux","product":"linux"}],"references":[{"url":"https://git.kernel.org/stable/c/a1dd0abd741a8111260676da729825d6c1461a71","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/e81e6d6d99b16dae11adbeda5c996317942a940c","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/40c8ee40e48a2c82c762539952ed8fc0571db5bf","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/7e3c96010ade29bb340a5bdce8675f50c7f59001","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/4099b98203d6b33d990586542fa5beee408032a3","tags":["web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68173","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-6j5g-jv8m-99rc"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2025-68173","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu20.04els/CLSA-2026-1791132991.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50766","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50774","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53799","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53815","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53834","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-53840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50067","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50135","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50166","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38584","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39827","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40180","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68328","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68339","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68344","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68364","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68777","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-53266","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63826","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63829","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63887","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63888","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63892","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63893","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63915","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63922","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63930","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63934","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63957","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63962","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63983","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64009","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64014","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64470","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64541","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64543","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64546","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64548","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64550","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64557","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64583","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68093","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68108","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68142","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68155","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68202","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68236","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68365","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68367","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68399","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68414","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68426","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72157","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72165","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72255","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72288","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72336","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72389","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72390","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72404","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72413","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72472","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74256","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74289","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74345","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74377","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74387","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74395","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74436","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74450","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74454","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74469","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74479","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74496","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74510","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74550","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74565","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74575","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74582","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74587","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74589","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74597","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74628","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74631","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74649","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74651","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74669","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74682","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74688","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74689","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74700","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74704","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74720","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74746","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80536","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80676","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80681","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80731","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80733","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80737","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80738","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80752","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80757","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80789","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80797","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80798","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80801","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80809","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80824","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80828","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80830","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80841","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80851","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80852","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80854","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80875","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80884","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80886","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80925","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80928","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80971","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80976","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-81000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-81001","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89441","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89462","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89468","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89469","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89475","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89476","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89477","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89478","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89481","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89484","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89487","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89488","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89492","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89494","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89495","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89504","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89527","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89528","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89531","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89537","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89542","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89548","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89549","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89550","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89553","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89555","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89559","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89569","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89574","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89575","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89633","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89637","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89655","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89656","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89666","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89699","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89708","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89718","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89719","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89740","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89762","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89813","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89821","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89823","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89838","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89840","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89843","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89846","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89847","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89848","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89850","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89854","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89856","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89858","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89865","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89871","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89876","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89877","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89879","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89881","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89883","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89887","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89897","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89901","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89912","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89913","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89927","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89929","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89932","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89936","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89938","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89945","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89946","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89949","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89951","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89952","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89965","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89968","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89973","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90015","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90034","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90036","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90041","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90055","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90057","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90058","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90062","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90073","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90075","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90088","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90102","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90106","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90109","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90125","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90138","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90180","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90182","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90187","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90207","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90222","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90227","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90245","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90248","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90263","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90267","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90293","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90298","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90302","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90307","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90311","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90314","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90315","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90320","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90328","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90334","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90345","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90347","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90360","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90379","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90383","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90386","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90403","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90411","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90413","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90414","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90416","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90418","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90419","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90421","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90431","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92480","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92481","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92482","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92498","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92499","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92500","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92509","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92522","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92524","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92525","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93039","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93040","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93042","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93051","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93053","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93056","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93095","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93104","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93117","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93140","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93151","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93159","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93170","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93172","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93175","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93177","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93178","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93179","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93189","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93196","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93202","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93203","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93204","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu18.04els/CLSA-2026-1791876326.html","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-47659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4994","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50770","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-50864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54226","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2023-54287","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-50076","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40146","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40333","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68750","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63891","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63904","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63905","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63916","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63921","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-63933","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64322","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64351","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64372","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64423","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64452","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64483","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64505","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68160","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68357","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-68373","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72070","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72233","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72234","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72374","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-72398","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74350","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74444","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74540","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74580","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74588","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74609","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74641","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80570","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80576","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80599","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80755","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80796","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80800","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80812","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80863","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80864","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80890","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80907","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80908","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-80918","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89539","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89545","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89607","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89729","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89733","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89742","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89778","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89784","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89786","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89789","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89799","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89822","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89833","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89845","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89852","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89855","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89859","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89861","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89878","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89893","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89895","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89953","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89972","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89982","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89987","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89997","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90013","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90016","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90017","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90019","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90020","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90023","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90029","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90031","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90033","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90037","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90044","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90045","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90049","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93213","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93268","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93280","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93286","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93783","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93802","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93807","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93808","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97408","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97448","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97455","tags":["advisory"]},{"url":"https://errata.tuxcare.com/els_os/ubuntu16.04els/CLSA-2026-1791878869.html","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/68xxx/CVE-2025-68173.json","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2025-68173","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0017.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35021","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.117","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.118","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.119","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.120","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2026-0018.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35022","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1759","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-53232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37900","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37954","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38373","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38556","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38591","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38659","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38730","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39713","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39961","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40030","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40215","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40242","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40251","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40271","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40272","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40277","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40294","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40308","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40318","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40341","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40342","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40343","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40346","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40358","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40359","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40361","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68171","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68174","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68176","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68188","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68200","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68206","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68214","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68259","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68261","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68264","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68265","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68297","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68309","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68331","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68337","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68349","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68354","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68356","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68362","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68363","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68376","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68378","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68724","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68725","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68734","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68741","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68744","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68745","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68756","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68780","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68782","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68794","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68803","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68814","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68816","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68818","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71072","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71104","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71116","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71131","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71147","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71149","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71150","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22996","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22998","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23000","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23005","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23035","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23138","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1760","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71077","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71134","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71152","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71238","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22978","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22980","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22990","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22992","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23060","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23069","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23071","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23086","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23099","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23103","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23105","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23111","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23124","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23126","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23133","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23136","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23137","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23139","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23145","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23154","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23156","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23169","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23173","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23191","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23198","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23208","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23212","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23230","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1761","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68301","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620838-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1234634","tags":["report"]},{"url":"https://bugzilla.suse.com/1249590","tags":["report"]},{"url":"https://bugzilla.suse.com/1250748","tags":["report"]},{"url":"https://bugzilla.suse.com/1251135","tags":["report"]},{"url":"https://bugzilla.suse.com/1251966","tags":["report"]},{"url":"https://bugzilla.suse.com/1251971","tags":["report"]},{"url":"https://bugzilla.suse.com/1252008","tags":["report"]},{"url":"https://bugzilla.suse.com/1252266","tags":["report"]},{"url":"https://bugzilla.suse.com/1252911","tags":["report"]},{"url":"https://bugzilla.suse.com/1252924","tags":["report"]},{"url":"https://bugzilla.suse.com/1253129","tags":["report"]},{"url":"https://bugzilla.suse.com/1253691","tags":["report"]},{"url":"https://bugzilla.suse.com/1254817","tags":["report"]},{"url":"https://bugzilla.suse.com/1254928","tags":["report"]},{"url":"https://bugzilla.suse.com/1255129","tags":["report"]},{"url":"https://bugzilla.suse.com/1255144","tags":["report"]},{"url":"https://bugzilla.suse.com/1255148","tags":["report"]},{"url":"https://bugzilla.suse.com/1255311","tags":["report"]},{"url":"https://bugzilla.suse.com/1255490","tags":["report"]},{"url":"https://bugzilla.suse.com/1255572","tags":["report"]},{"url":"https://bugzilla.suse.com/1255721","tags":["report"]},{"url":"https://bugzilla.suse.com/1255868","tags":["report"]},{"url":"https://bugzilla.suse.com/1256640","tags":["report"]},{"url":"https://bugzilla.suse.com/1256675","tags":["report"]},{"url":"https://bugzilla.suse.com/1256679","tags":["report"]},{"url":"https://bugzilla.suse.com/1256708","tags":["report"]},{"url":"https://bugzilla.suse.com/1256732","tags":["report"]},{"url":"https://bugzilla.suse.com/1256784","tags":["report"]},{"url":"https://bugzilla.suse.com/1256802","tags":["report"]},{"url":"https://bugzilla.suse.com/1256865","tags":["report"]},{"url":"https://bugzilla.suse.com/1256867","tags":["report"]},{"url":"https://bugzilla.suse.com/1257154","tags":["report"]},{"url":"https://bugzilla.suse.com/1257174","tags":["report"]},{"url":"https://bugzilla.suse.com/1257209","tags":["report"]},{"url":"https://bugzilla.suse.com/1257222","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/1257332","tags":["report"]},{"url":"https://bugzilla.suse.com/1257466","tags":["report"]},{"url":"https://bugzilla.suse.com/1257472","tags":["report"]},{"url":"https://bugzilla.suse.com/1257473","tags":["report"]},{"url":"https://bugzilla.suse.com/1257551","tags":["report"]},{"url":"https://bugzilla.suse.com/1257552","tags":["report"]},{"url":"https://bugzilla.suse.com/1257553","tags":["report"]},{"url":"https://bugzilla.suse.com/1257554","tags":["report"]},{"url":"https://bugzilla.suse.com/1257556","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/1257561","tags":["report"]},{"url":"https://bugzilla.suse.com/1257562","tags":["report"]},{"url":"https://bugzilla.suse.com/1257565","tags":["report"]},{"url":"https://bugzilla.suse.com/1257570","tags":["report"]},{"url":"https://bugzilla.suse.com/1257572","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/1257581","tags":["report"]},{"url":"https://bugzilla.suse.com/1257586","tags":["report"]},{"url":"https://bugzilla.suse.com/1257600","tags":["report"]},{"url":"https://bugzilla.suse.com/1257631","tags":["report"]},{"url":"https://bugzilla.suse.com/1257635","tags":["report"]},{"url":"https://bugzilla.suse.com/1257679","tags":["report"]},{"url":"https://bugzilla.suse.com/1257682","tags":["report"]},{"url":"https://bugzilla.suse.com/1257686","tags":["report"]},{"url":"https://bugzilla.suse.com/1257687","tags":["report"]},{"url":"https://bugzilla.suse.com/1257688","tags":["report"]},{"url":"https://bugzilla.suse.com/1257704","tags":["report"]},{"url":"https://bugzilla.suse.com/1257705","tags":["report"]},{"url":"https://bugzilla.suse.com/1257706","tags":["report"]},{"url":"https://bugzilla.suse.com/1257707","tags":["report"]},{"url":"https://bugzilla.suse.com/1257709","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/1257726","tags":["report"]},{"url":"https://bugzilla.suse.com/1257729","tags":["report"]},{"url":"https://bugzilla.suse.com/1257730","tags":["report"]},{"url":"https://bugzilla.suse.com/1257732","tags":["report"]},{"url":"https://bugzilla.suse.com/1257734","tags":["report"]},{"url":"https://bugzilla.suse.com/1257735","tags":["report"]},{"url":"https://bugzilla.suse.com/1257737","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/1257742","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/1257755","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/1257814","tags":["report"]},{"url":"https://bugzilla.suse.com/1257815","tags":["report"]},{"url":"https://bugzilla.suse.com/1257816","tags":["report"]},{"url":"https://bugzilla.suse.com/1257817","tags":["report"]},{"url":"https://bugzilla.suse.com/1257818","tags":["report"]},{"url":"https://bugzilla.suse.com/1257830","tags":["report"]},{"url":"https://bugzilla.suse.com/1257942","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/1258232","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/1258258","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/1258276","tags":["report"]},{"url":"https://bugzilla.suse.com/1258277","tags":["report"]},{"url":"https://bugzilla.suse.com/1258279","tags":["report"]},{"url":"https://bugzilla.suse.com/1258286","tags":["report"]},{"url":"https://bugzilla.suse.com/1258289","tags":["report"]},{"url":"https://bugzilla.suse.com/1258290","tags":["report"]},{"url":"https://bugzilla.suse.com/1258297","tags":["report"]},{"url":"https://bugzilla.suse.com/1258298","tags":["report"]},{"url":"https://bugzilla.suse.com/1258299","tags":["report"]},{"url":"https://bugzilla.suse.com/1258303","tags":["report"]},{"url":"https://bugzilla.suse.com/1258304","tags":["report"]},{"url":"https://bugzilla.suse.com/1258308","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/1258323","tags":["report"]},{"url":"https://bugzilla.suse.com/1258324","tags":["report"]},{"url":"https://bugzilla.suse.com/1258326","tags":["report"]},{"url":"https://bugzilla.suse.com/1258331","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/1258355","tags":["report"]},{"url":"https://bugzilla.suse.com/1258358","tags":["report"]},{"url":"https://bugzilla.suse.com/1258374","tags":["report"]},{"url":"https://bugzilla.suse.com/1258376","tags":["report"]},{"url":"https://bugzilla.suse.com/1258377","tags":["report"]},{"url":"https://bugzilla.suse.com/1258379","tags":["report"]},{"url":"https://bugzilla.suse.com/1258389","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/1258421","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/1258430","tags":["report"]},{"url":"https://bugzilla.suse.com/1258442","tags":["report"]},{"url":"https://bugzilla.suse.com/1258455","tags":["report"]},{"url":"https://bugzilla.suse.com/1258461","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/1258483","tags":["report"]},{"url":"https://bugzilla.suse.com/1258484","tags":["report"]},{"url":"https://bugzilla.suse.com/1258489","tags":["report"]},{"url":"https://bugzilla.suse.com/1258517","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/1258672","tags":["report"]},{"url":"https://bugzilla.suse.com/1258824","tags":["report"]},{"url":"https://bugzilla.suse.com/1259329","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-39753","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-40230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68173","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68371","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68745","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-68818","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-71125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71134","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71183","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-71186","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-71193","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-71233","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-22980","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-23010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23024","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23026","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23031","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-23038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23050","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23055","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-23059","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-23062","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-23065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23070","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-23088","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-23097","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23100","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-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-23123","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23129","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23131","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-23136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23137","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-23142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23144","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-23148","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-23154","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-23157","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23161","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-23169","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-23177","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-23188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23189","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-23210","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-23223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23229","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-23230","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620873-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202620931-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202621284-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-68173","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2025-68173","tags":["report"]},{"url":"https://git.kernel.org/linus/4099b98203d6b33d990586542fa5beee408032a3","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8029-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8030-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8029-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8048-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8029-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8100-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-3","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-4","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8125-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8126-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8095-5","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8165-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8261-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2025-40001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40004","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-40031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40039","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-40045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40047","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-40050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40086","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-40089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40106","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-40113","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-40117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40119","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-40122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40123","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-40129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40152","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-40155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40177","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-40180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40186","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-40189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40203","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-40206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40218","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-40221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40230","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-40234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40242","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-40256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40270","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-40274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40276","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-40284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40301","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40306","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40307","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-40310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40311","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-40316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40320","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-40323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40341","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-40344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40352","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40353","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40355","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40356","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40359","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40360","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68175","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-68178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68190","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-68193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68240","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68243","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-68246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68309","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68311","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40041","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21833","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38502","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38556","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38627","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38643","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39678","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39807","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39825","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39832","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39835","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39838","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39843","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39845","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39876","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39881","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-39886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39894","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39907","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39909","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-39914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39929","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39932","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39934","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39937","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39942","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39950","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39952","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-39957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-39977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-39991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39992","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-40000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40016","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40024","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-40083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-40266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68283","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-68297","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-68305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68308","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-68339","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68340","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68343","tags":["report"]},{"url":"https://launchpad.net/bugs/2143853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37899","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36350","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36357","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-21931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-23163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37740","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37741","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37745","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37754","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37755","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37764","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37765","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37767","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37768","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37769","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37771","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37775","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37777","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37778","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37780","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37784","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37786","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37789","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37792","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37793","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37796","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37799","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37805","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37808","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37809","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37810","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37811","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37812","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37813","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37815","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37816","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37817","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37819","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37820","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37822","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37824","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37826","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37827","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37828","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37829","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37830","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37831","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37836","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37839","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37840","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37841","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37842","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37844","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37846","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37850","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37853","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37854","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37858","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37863","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37874","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37887","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37892","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37897","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37900","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37901","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37903","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37909","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37911","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37918","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37920","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37922","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37925","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37927","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37930","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37931","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37933","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37940","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37943","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37944","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37945","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37949","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37951","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37952","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37956","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37959","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37961","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37963","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37967","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37972","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37975","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37995","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38027","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38040","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38048","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38059","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38155","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38174","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38181","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38208","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38210","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38217","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38219","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38245","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38280","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38282","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38285","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38293","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38298","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38299","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38303","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38307","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38310","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38321","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38322","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38324","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38338","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38342","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38343","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38348","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38349","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38354","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38361","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38363","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38364","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38368","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38369","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38373","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38374","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38375","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38377","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38382","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38385","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38386","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38387","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38388","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38389","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38390","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38391","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38393","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38395","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38396","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38399","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38400","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38401","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38403","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38408","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38409","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38410","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38412","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38415","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38416","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38420","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38422","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38424","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38425","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38429","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38430","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38437","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38439","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38441","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38443","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38445","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38449","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38456","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38457","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38458","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38459","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38460","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38461","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38462","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38463","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38464","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38466","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38467","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38468","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38469","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38470","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38471","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38472","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38473","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38474","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38476","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38480","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38481","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38482","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38483","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38485","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38487","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38488","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38489","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38490","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38491","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38495","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38496","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38497","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38506","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38507","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38510","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38511","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38512","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38513","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38514","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38515","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38516","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38520","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38521","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38524","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38526","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38527","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38528","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38529","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38530","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38531","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38532","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38535","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38537","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38538","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38539","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38540","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38542","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38543","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38544","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38546","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38548","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38549","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38550","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38551","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38552","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38553","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38555","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38560","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38561","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38562","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38566","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38568","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38569","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38571","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38572","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38574","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38576","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38577","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38578","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38579","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38581","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38582","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38583","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38584","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38585","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38587","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38588","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38590","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38593","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38595","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38601","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38602","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38604","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38608","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38609","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38610","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38612","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38614","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38615","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38619","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38622","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38623","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38624","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38625","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38626","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38630","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38632","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38634","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38639","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38640","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38644","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38645","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38646","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38648","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38650","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38652","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38653","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38660","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38663","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38664","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38665","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38670","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38671","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38677","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38680","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38688","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38695","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38696","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38697","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38699","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38700","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38704","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38708","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38722","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38728","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38729","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38735","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39673","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39675","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39679","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39681","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39683","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39684","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39686","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39689","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39691","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39692","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39694","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39698","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39701","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39702","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39703","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39706","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39707","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39709","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39710","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39711","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39712","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39713","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39714","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39715","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39716","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39719","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39720","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39721","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39724","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39726","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39730","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39731","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39732","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39734","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39736","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39737","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39738","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39739","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39742","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39743","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39744","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39746","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39747","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39748","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39752","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39753","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39756","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39757","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39758","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39759","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39760","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39761","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39763","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39766","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39772","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39773","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39776","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39779","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39781","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39782","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39783","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39787","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39788","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39790","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39794","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39797","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39798","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39800","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39801","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39889","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-39989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68750","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23060","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23074","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-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://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-22022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-22111","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38022","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-68254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68256","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-68259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68263","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68325","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-68344","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68345","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68346","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68347","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-68363","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-68371","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68372","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-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-68740","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-68746","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-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-68763","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-68766","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-68770","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68771","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-68774","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68775","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-68778","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-68786","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-68794","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-68798","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-68804","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68806","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68808","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-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-68817","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-71065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71067","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-71071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71072","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-71088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71089","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-71095","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-71101","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-71107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71109","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-71119","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-71122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71127","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71130","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-71135","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-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-71147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23112","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23273","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2025-68173","title":"ftrace: Fix softlockup in ftrace_module_enable","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\"ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\") and commit 42ea22e754ba (\"ftrace: Add cond_resched() to\nftrace_graph_set_hash()\").\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.","status":"published","published":"2025-12-16T13:42:53.106Z","modified":"2026-05-11T21:48:04.42Z","updated_at":"2026-11-02T14:32:36.079745Z"}],"euvd":[{"id":"EUVD-2025-203723","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\"ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\") and commit 42ea22e754ba (\"ftrace: Add cond_resched() to\nftrace_graph_set_hash()\").\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.","status":"published","published":"2025-12-16T13:42:53Z","modified":"2026-05-11T21:48:04Z","updated_at":"2026-11-02T19:04:47.002236Z"}],"ghsa":[{"id":"GHSA-6j5g-jv8m-99rc","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\"ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\") and commit 42ea22e754ba (\"ftrace: Add cond_resched() to\nftrace_graph_set_hash()\").\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.","status":"published","published":"2025-12-16T15:30:44Z","modified":"2025-12-16T15:30:48Z","updated_at":"2026-11-02T15:05:12.969095Z"}],"nvd":[{"id":"CVE-2025-68173","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\"ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\") and commit 42ea22e754ba (\"ftrace: Add cond_resched() to\nftrace_graph_set_hash()\").\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.","status":"published","published":"2025-12-16T14:15:49.213Z","modified":"2026-10-14T13:10:00.187Z","updated_at":"2026-11-02T14:11:50.400521Z"}],"osv":[{"id":"OESA-2026-1759","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\n     vfs_ioctl fs/ioctl.c:51 [inline]\n     __do_sys_ioctl fs/ioctl.c:907 [inline]\n     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntimers: Fix NULL function pointer race in timer_shutdown_sync()\n\nThere is a race condition between timer_shutdown_sync() and timer\nexpiration that can lead to hitting a WARN_ON in expire_timers().\n\nThe issue occurs when timer_shutdown_sync() clears the timer function\nto NULL while the timer is still running on another CPU. The race\nscenario looks like this:\n\nCPU0\t\t\t\t\tCPU1\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tbase-\u0026gt;running_timer = timer;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t[call_timer_fn enter]\n\t\t\t\t\tmod_timer()\n\t\t\t\t\t...\ntimer_shutdown_sync()\nlock_timer_base()\n// For now, will not detach the timer but only clear its function to NULL\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\t\t\t\t\t[call_timer_fn exit]\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\tbase-\u0026gt;running_timer = NULL;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t...\n\t\t\t\t\t// Now timer is pending while its function set to NULL.\n\t\t\t\t\t// next timer trigger\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tWARN_ON_ONCE(!fn) // hit\n\t\t\t\t\t...\nlock_timer_base()\n// Now timer will detach\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\nThe problem is that timer_shutdown_sync() clears the timer function\nregardless of whether the timer is currently running. This can leave a\npending timer with a NULL function pointer, which triggers the\nWARN_ON_ONCE(!fn) check in expire_timers().\n\nFix this by only clearing the timer function when actually detaching the\ntimer. If the timer is running, leave the function pointer intact, which is\nsafe because the timer will be properly detached when it finishes running.(CVE-2025-68214)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:44.306450654Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1760","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\n     vfs_ioctl fs/ioctl.c:51 [inline]\n     __do_sys_ioctl fs/ioctl.c:907 [inline]\n     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntimers: Fix NULL function pointer race in timer_shutdown_sync()\n\nThere is a race condition between timer_shutdown_sync() and timer\nexpiration that can lead to hitting a WARN_ON in expire_timers().\n\nThe issue occurs when timer_shutdown_sync() clears the timer function\nto NULL while the timer is still running on another CPU. The race\nscenario looks like this:\n\nCPU0\t\t\t\t\tCPU1\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tbase-\u0026gt;running_timer = timer;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t[call_timer_fn enter]\n\t\t\t\t\tmod_timer()\n\t\t\t\t\t...\ntimer_shutdown_sync()\nlock_timer_base()\n// For now, will not detach the timer but only clear its function to NULL\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\t\t\t\t\t[call_timer_fn exit]\n\t\t\t\t\tlock_timer_base()\n\t\t\t\t\tbase-\u0026gt;running_timer = NULL;\n\t\t\t\t\tunlock_timer_base()\n\t\t\t\t\t...\n\t\t\t\t\t// Now timer is pending while its function set to NULL.\n\t\t\t\t\t// next timer trigger\n\t\t\t\t\t\u0026lt;SOFTIRQ\u0026gt;\n\t\t\t\t\texpire_timers()\n\t\t\t\t\tWARN_ON_ONCE(!fn) // hit\n\t\t\t\t\t...\nlock_timer_base()\n// Now timer will detach\nif (base-\u0026gt;running_timer != timer)\n\tret = detach_if_pending(timer, base, true);\nif (shutdown)\n\ttimer-\u0026gt;function = NULL;\nunlock_timer_base()\n\nThe problem is that timer_shutdown_sync() clears the timer function\nregardless of whether the timer is currently running. This can leave a\npending timer with a NULL function pointer, which triggers the\nWARN_ON_ONCE(!fn) check in expire_timers().\n\nFix this by only clearing the timer function when actually detaching the\ntimer. If the timer is running, leave the function pointer intact, which is\nsafe because the timer will be properly detached when it finishes running.(CVE-2025-68214)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: fix use-after-free in ksmbd_tree_connect_put under concurrency\n\nUnder high concurrency, A tree-connection object (tcon) is freed on\na disconnect path while another path still holds a reference and later\nexecutes *_put()/write on it.(CVE-2025-68817)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntpm: Cap the number of PCR banks\n\ntpm2_get_pcr_allocation() does not cap any upper limit for the number of\nbanks. Cap the limit to eight banks so that out of bounds values coming\nfrom external I/O cause on only limited harm.(CVE-2025-71077)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: change all pageblocks migrate type on coalescing\n\nWhen a page is freed it coalesces with a buddy into a higher order page\nwhile possible.  When the buddy page migrate type differs, it is expected\nto be updated to match the one of the page being freed.\n\nHowever, only the first pageblock of the buddy page is updated, while the\nrest of the pageblocks are left unchanged.\n\nThat causes warnings in later expand() and other code paths (like below),\nsince an inconsistency between migration type of the list containing the\npage and the page-owned pageblocks migration types is introduced.\n\n[  308.986589] ------------[ cut here ]------------\n[  308.987227] page type is 0, passed migratetype is 1 (nr=256)\n[  308.987275] WARNING: CPU: 1 PID: 5224 at mm/page_alloc.c:812 expand+0x23c/0x270\n[  308.987293] Modules linked in: algif_hash(E) af_alg(E) nft_fib_inet(E) nft_fib_ipv4(E) nft_fib_ipv6(E) nft_fib(E) nft_reject_inet(E) nf_reject_ipv4(E) nf_reject_ipv6(E) nft_reject(E) nft_ct(E) nft_chain_nat(E) nf_nat(E) nf_conntrack(E) nf_defrag_ipv6(E) nf_defrag_ipv4(E) nf_tables(E) s390_trng(E) vfio_ccw(E) mdev(E) vfio_iommu_type1(E) vfio(E) sch_fq_codel(E) drm(E) i2c_core(E) drm_panel_orientation_quirks(E) loop(E) nfnetlink(E) vsock_loopback(E) vmw_vsock_virtio_transport_common(E) vsock(E) ctcm(E) fsm(E) diag288_wdt(E) watchdog(E) zfcp(E) scsi_transport_fc(E) ghash_s390(E) prng(E) aes_s390(E) des_generic(E) des_s390(E) libdes(E) sha3_512_s390(E) sha3_256_s390(E) sha_common(E) paes_s390(E) crypto_engine(E) pkey_cca(E) pkey_ep11(E) zcrypt(E) rng_core(E) pkey_pckmo(E) pkey(E) autofs4(E)\n[  308.987439] Unloaded tainted modules: hmac_s390(E):2\n[  308.987650] CPU: 1 UID: 0 PID: 5224 Comm: mempig_verify Kdump: loaded Tainted: G            E       6.18.0-gcc-bpf-debug #431 PREEMPT\n[  308.987657] Tainted: [E]=UNSIGNED_MODULE\n[  308.987661] Hardware name: IBM 3906 M04 704 (z/VM 7.3.0)\n[  308.987666] Krnl PSW : 0404f00180000000 00000349976fa600 (expand+0x240/0x270)\n[  308.987676]            R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:3 PM:0 RI:0 EA:3\n[  308.987682] Krnl GPRS: 0000034980000004 0000000000000005 0000000000000030 000003499a0e6d88\n[  308.987688]            0000000000000005 0000034980000005 000002be803ac000 0000023efe6c8300\n[  308.987692]            0000000000000008 0000034998d57290 000002be00000100 0000023e00000008\n[  308.987696]            0000000000000000 0000000000000000 00000349976fa5fc 000002c99b1eb6f0\n[  308.987708] Krnl Code: 00000349976fa5f0: c020008a02f2\tlarl\t%r2,000003499883abd4\n                          00000349976fa5f6: c0e5ffe3f4b5\tbrasl\t%r14,0000034997378f60\n                         #00000349976fa5fc: af000000\t\tmc\t0,0\n                         \u0026gt;00000349976fa600: a7f4ff4c\t\tbrc\t15,00000349976fa498\n                          00000349976fa604: b9040026\t\tlgr\t%r2,%r6\n                          00000349976fa608: c0300088317f\tlarl\t%r3,0000034998800906\n                          00000349976fa60e: c0e5fffdb6e1\tbrasl\t%r14,00000349976b13d0\n                          00000349976fa614: af000000\t\tmc\t0,0\n[  308.987734] Call Trace:\n[  308.987738]  [\u0026lt;00000349976fa600\u0026gt;] expand+0x240/0x270\n[  308.987744] ([\u0026lt;00000349976fa5fc\u0026gt;] expand+0x23c/0x270)\n[  308.987749]  [\u0026lt;00000349976ff95e\u0026gt;] rmqueue_bulk+0x71e/0x940\n[  308.987754]  [\u0026lt;00000349976ffd7e\u0026gt;] __rmqueue_pcplist+0x1fe/0x2a0\n[  308.987759]  [\u0026lt;0000034997700966\u0026gt;] rmqueue.isra.0+0xb46/0xf40\n[  308.987763]  [\u0026lt;0000034997703ec8\u0026gt;] get_page_from_freelist+0x198/0x8d0\n[  308.987768]  [\u0026lt;0000034997706fa8\u0026gt;] __alloc_frozen_pages_noprof+0x198/0x400\n[  308.987774]  [\u0026lt;00000349977536f8\u0026gt;] alloc_pages_mpol+0xb8/0x220\n[  308.987781]  [\u0026lt;0000034997753bf6\u0026gt;] folio_alloc_mpol_noprof+0x26/0xc0\n[  308.987786]  [\u0026lt;0000034997753e4c\u0026gt;] vma_alloc_folio_noprof+0x6c/0xa0\n[  308.987791]  [\u0026lt;0000034997775b22\u0026gt;] vma_alloc_anon_folio_pmd+0x42/0x240\n[  308.987799]  [\u0026lt;000003499777bfea\u0026gt;] __do_huge_pmd_anonymous_page+0x3a/0x210\n[  308.987804]  [\u0026lt;00000349976cb0\n---truncated---(CVE-2025-71134)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: dsa: properly keep track of conduit reference\n\nProblem description\n-------------------\n\nDSA has a mumbo-jumbo of reference handling of the conduit net device\nand its kobject which, sadly, is just wrong and doesn\u0026apos;t make sense.\n\nThere are two distinct problems.\n\n1. The OF path, which uses of_find_net_device_by_node(), never releases\n   the elevated refcount on the conduit\u0026apos;s kobject. Nominally, the OF and\n   non-OF paths should result in objects having identical reference\n   counts taken, and it is already suspicious that\n   dsa_dev_to_net_device() has a put_device() call which is missing in\n   dsa_port_parse_of(), but we can actually even verify that an issue\n   exists. With CONFIG_DEBUG_KOBJECT_RELEASE=y, if we run this command\n   \u0026quot;before\u0026quot; and \u0026quot;after\u0026quot; applying this patch:\n\n(unbind the conduit driver for net device eno2)\necho 0000:00:00.2 \u0026gt; /sys/bus/pci/drivers/fsl_enetc/unbind\n\nwe see these lines in the output diff which appear only with the patch\napplied:\n\nkobject: \u0026apos;eno2\u0026apos; (ffff002009a3a6b8): kobject_release, parent 0000000000000000 (delayed 1000)\nkobject: \u0026apos;109\u0026apos; (ffff0020099d59a0): kobject_release, parent 0000000000000000 (delayed 1000)\n\n2. After we find the conduit interface one way (OF) or another (non-OF),\n   it can get unregistered at any time, and DSA remains with a long-lived,\n   but in this case stale, cpu_dp-\u0026gt;conduit pointer. Holding the net\n   device\u0026apos;s underlying kobject isn\u0026apos;t actually of much help, it just\n   prevents it from being freed (but we never need that kobject\n   directly). What helps us to prevent the net device from being\n   unregistered is the parallel netdev reference mechanism (dev_hold()\n   and dev_put()).\n\nActually we actually use that netdev tracker mechanism implicitly on\nuser ports since commit 2f1e8ea726e9 (\u0026quot;net: dsa: link interfaces with\nthe DSA master to get rid of lockdep warnings\u0026quot;), via netdev_upper_dev_link().\nBut time still passes at DSA switch probe time between the initial\nof_find_net_device_by_node() code and the user port creation time, time\nduring which the conduit could unregister itself and DSA wouldn\u0026apos;t know\nabout it.\n\nSo we have to run of_find_net_device_by_node() under rtnl_lock() to\nprevent that from happening, and release the lock only with the netdev\ntracker having acquired the reference.\n\nDo we need to keep the reference until dsa_unregister_switch() /\ndsa_switch_shutdown()?\n1: Maybe yes. A switch device will still be registered even if all user\n   ports failed to probe, see commit 86f8b1c01a0a (\u0026quot;net: dsa: Do not\n   make user port errors fatal\u0026quot;), and the cpu_dp-\u0026gt;conduit pointers\n   remain valid.  I haven\u0026apos;t audited all call paths to see whether they\n   will actually use the conduit in lack of any user port, but if they\n   do, it seems safer to not rely on user ports for that reference.\n2. Definitely yes. We support changing the conduit which a user port is\n   associated to, and we can get into a situation where we\u0026apos;ve moved all\n   user ports away from a conduit, thus no longer hold any reference to\n   it via the net device tracker. But we shouldn\u0026apos;t let it go nonetheless\n   - see the next change in relation to dsa_tree_find_first_conduit()\n   and LAG conduits which disappear.\n   We have to be prepared to return to the physical conduit, so the CPU\n   port must explicitly keep another reference to it. This is also to\n   say: the user ports and their CPU ports may not always keep a\n   reference to the same conduit net device, and both are needed.\n\nAs for the conduit\u0026apos;s kobject for the /sys/class/net/ entry, we don\u0026apos;t\ncare about it, we can release it as soon as we hold the net device\nobject itself.\n\nHistory and blame attribution\n-----------------------------\n\nThe code has been refactored so many times, it is very difficult to\nfollow and properly attribute a blame, but I\u0026apos;ll try to make a short\nhistory which I hope to be correct.\n\nWe have two distinct probing paths:\n- one for OF, introduced in 2016 i\n---truncated---(CVE-2025-71152)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: rtl8150: fix memory leak on usb_submit_urb() failure\n\nIn async_set_registers(), when usb_submit_urb() fails, the allocated\n  async_req structure and URB are not freed, causing a memory leak.\n\n  The completion callback async_set_reg_cb() is responsible for freeing\n  these allocations, but it is only called after the URB is successfully\n  submitted and completes (successfully or with error). If submission\n  fails, the callback never runs and the memory is leaked.\n\n  Fix this by freeing both the URB and the request structure in the error\n  path when usb_submit_urb() fails.(CVE-2025-71154)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix bsg_done() causing double free\n\nKernel panic observed on system,\n\n[5353358.825191] BUG: unable to handle page fault for address: ff5f5e897b024000\n[5353358.825194] #PF: supervisor write access in kernel mode\n[5353358.825195] #PF: error_code(0x0002) - not-present page\n[5353358.825196] PGD 100006067 P4D 0\n[5353358.825198] Oops: 0002 [#1] PREEMPT SMP NOPTI\n[5353358.825200] CPU: 5 PID: 2132085 Comm: qlafwupdate.sub Kdump: loaded Tainted: G        W    L    -------  ---  5.14.0-503.34.1.el9_5.x86_64 #1\n[5353358.825203] Hardware name: HPE ProLiant DL360 Gen11/ProLiant DL360 Gen11, BIOS 2.44 01/17/2025\n[5353358.825204] RIP: 0010:memcpy_erms+0x6/0x10\n[5353358.825211] RSP: 0018:ff591da8f4f6b710 EFLAGS: 00010246\n[5353358.825212] RAX: ff5f5e897b024000 RBX: 0000000000007090 RCX: 0000000000001000\n[5353358.825213] RDX: 0000000000001000 RSI: ff591da8f4fed090 RDI: ff5f5e897b024000\n[5353358.825214] RBP: 0000000000010000 R08: ff5f5e897b024000 R09: 0000000000000000\n[5353358.825215] R10: ff46cf8c40517000 R11: 0000000000000001 R12: 0000000000008090\n[5353358.825216] R13: ff591da8f4f6b720 R14: 0000000000001000 R15: 0000000000000000\n[5353358.825218] FS:  00007f1e88d47740(0000) GS:ff46cf935f940000(0000) knlGS:0000000000000000\n[5353358.825219] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[5353358.825220] CR2: ff5f5e897b024000 CR3: 0000000231532004 CR4: 0000000000771ef0\n[5353358.825221] PKRU: 55555554\n[5353358.825222] Call Trace:\n[5353358.825223]  \u0026lt;TASK\u0026gt;\n[5353358.825224]  ? show_trace_log_lvl+0x1c4/0x2df\n[5353358.825229]  ? show_trace_log_lvl+0x1c4/0x2df\n[5353358.825232]  ? sg_copy_buffer+0xc8/0x110\n[5353358.825236]  ? __die_body.cold+0x8/0xd\n[5353358.825238]  ? page_fault_oops+0x134/0x170\n[5353358.825242]  ? kernelmode_fixup_or_oops+0x84/0x110\n[5353358.825244]  ? exc_page_fault+0xa8/0x150\n[5353358.825247]  ? asm_exc_page_fault+0x22/0x30\n[5353358.825252]  ? memcpy_erms+0x6/0x10\n[5353358.825253]  sg_copy_buffer+0xc8/0x110\n[5353358.825259]  qla2x00_process_vendor_specific+0x652/0x1320 [qla2xxx]\n[5353358.825317]  qla24xx_bsg_request+0x1b2/0x2d0 [qla2xxx]\n\nMost routines in qla_bsg.c call bsg_done() only for success cases.\nHowever a few invoke it for failure case as well leading to a double\nfree. Validate before calling bsg_done().(CVE-2025-71238)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: avoid kernel-infoleak from struct iw_point\n\nstruct iw_point has a 32bit hole on 64bit arches.\n\nstruct iw_point {\n  void __user   *pointer;       /* Pointer to the data  (in user space) */\n  __u16         length;         /* number of fields or size in bytes */\n  __u16         flags;          /* Optional params */\n};\n\nMake sure to zero the structure to avoid disclosing 32bits of kernel data\nto user space.(CVE-2026-22978)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnfsd: provide locking for v4_end_grace\n\nWriting to v4_end_grace can race with server shutdown and result in\nmemory being accessed after it was freed - reclaim_str_hashtbl in\nparticularly.\n\nWe cannot hold nfsd_mutex across the nfsd4_end_grace() call as that is\nheld while client_tracking_op-\u0026gt;init() is called and that can wait for\nan upcall to nfsdcltrack which can write to v4_end_grace, resulting in a\ndeadlock.\n\nnfsd4_end_grace() is also called by the landromat work queue and this\ndoesn\u0026apos;t require locking as server shutdown will stop the work and wait\nfor it before freeing anything that nfsd4_end_grace() might access.\n\nHowever, we must be sure that writing to v4_end_grace doesn\u0026apos;t restart\nthe work item after shutdown has already waited for it.  For this we\nadd a new flag protected with nn-\u0026gt;client_lock.  It is set only while it\nis safe to make client tracking calls, and v4_end_grace only schedules\nwork while the flag is set with the spinlock held.\n\nSo this patch adds a nfsd_net field \u0026quot;client_tracking_active\u0026quot; which is\nset as described.  Another field \u0026quot;grace_end_forced\u0026quot;, is set when\nv4_end_grace is written.  After this is set, and providing\nclient_tracking_active is set, the laundromat is scheduled.\nThis \u0026quot;grace_end_forced\u0026quot; field bypasses other checks for whether the\ngrace period has finished.\n\nThis resolves a race which can result in use-after-free.(CVE-2026-22980)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: replace overzealous BUG_ON in osdmap_apply_incremental()\n\nIf the osdmap is (maliciously) corrupted such that the incremental\nosdmap epoch is different from what is expected, there is no need to\nBUG.  Instead, just declare the incremental osdmap to be invalid.(CVE-2026-22990)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: return the handler error from mon_handle_auth_done()\n\nCurrently any error from ceph_auth_handle_reply_done() is propagated\nvia finish_auth() but isn\u0026apos;t returned from mon_handle_auth_done().  This\nresults in higher layers learning that (despite the monitor considering\nus to be successfully authenticated) something went wrong in the\nauthentication phase and reacting accordingly, but msgr2 still trying\nto proceed with establishing the session in the background.  In the\ncase of secure mode this can trigger a WARN in setup_crypto() and later\nlead to a NULL pointer dereference inside of prepare_auth_signature().(CVE-2026-22992)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: authencesn - reject too-short AAD (assoclen\u0026lt;8) to match ESP/ESN spec\n\nauthencesn assumes an ESP/ESN-formatted AAD. When assoclen is shorter than\nthe minimum expected length, crypto_authenc_esn_decrypt() can advance past\nthe end of the destination scatterlist and trigger a NULL pointer dereference\nin scatterwalk_map_and_copy(), leading to a kernel panic (DoS).\n\nAdd a minimum AAD length check to fail fast on invalid inputs.(CVE-2026-23060)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: fix potential underflow in virtio_transport_get_credit()\n\nThe credit calculation in virtio_transport_get_credit() uses unsigned\narithmetic:\n\n  ret = vvs-\u0026gt;peer_buf_alloc - (vvs-\u0026gt;tx_cnt - vvs-\u0026gt;peer_fwd_cnt);\n\nIf the peer shrinks its advertised buffer (peer_buf_alloc) while bytes\nare in flight, the subtraction can underflow and produce a large\npositive value, potentially allowing more data to be queued than the\npeer can handle.\n\nReuse virtio_transport_has_space() which already handles this case and\nadd a comment to make it clear why we are doing that.\n\n[Stefano: use virtio_transport_has_space() instead of duplicating the code]\n[Stefano: tweak the commit message](CVE-2026-23069)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregmap: Fix race condition in hwspinlock irqsave routine\n\nPreviously, the address of the shared member \u0026apos;\u0026amp;map-\u0026gt;spinlock_flags\u0026apos; was\npassed directly to \u0026apos;hwspin_lock_timeout_irqsave\u0026apos;. This creates a race\ncondition where multiple contexts contending for the lock could overwrite\nthe shared flags variable, potentially corrupting the state for the\ncurrent lock owner.\n\nFix this by using a local stack variable \u0026apos;flags\u0026apos; to store the IRQ state\ntemporarily.(CVE-2026-23071)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: cap TX credit to local buffer size\n\nThe virtio transports derives its TX credit directly from peer_buf_alloc,\nwhich is set from the remote endpoint\u0026apos;s SO_VM_SOCKETS_BUFFER_SIZE value.\n\nOn the host side this means that the amount of data we are willing to\nqueue for a connection is scaled by a guest-chosen buffer size, rather\nthan the host\u0026apos;s own vsock configuration. A malicious guest can advertise\na large buffer and read slowly, causing the host to allocate a\ncorrespondingly large amount of sk_buff memory.\nThe same thing would happen in the guest with a malicious host, since\nvirtio transports share the same code base.\n\nIntroduce a small helper, virtio_transport_tx_buf_size(), that\nreturns min(peer_buf_alloc, buf_alloc), and use it wherever we consume\npeer_buf_alloc.\n\nThis ensures the effective TX window is bounded by both the peer\u0026apos;s\nadvertised buffer and our own buf_alloc (already clamped to\nbuffer_max_size via SO_VM_SOCKETS_BUFFER_MAX_SIZE), so a remote peer\ncannot force the other to queue more data than allowed by its own\nvsock settings.\n\nOn an unpatched Ubuntu 22.04 host (~64 GiB RAM), running a PoC with\n32 guest vsock connections advertising 2 GiB each and reading slowly\ndrove Slab/SUnreclaim from ~0.5 GiB to ~57 GiB; the system only\nrecovered after killing the QEMU process. That said, if QEMU memory is\nlimited with cgroups, the maximum memory used will be limited.\n\nWith this patch applied:\n\n  Before:\n    MemFree:        ~61.6 GiB\n    Slab:           ~142 MiB\n    SUnreclaim:     ~117 MiB\n\n  After 32 high-credit connections:\n    MemFree:        ~61.5 GiB\n    Slab:           ~178 MiB\n    SUnreclaim:     ~152 MiB\n\nOnly ~35 MiB increase in Slab/SUnreclaim, no host OOM, and the guest\nremains responsive.\n\nCompatibility with non-virtio transports:\n\n  - VMCI uses the AF_VSOCK buffer knobs to size its queue pairs per\n    socket based on the local vsk-\u0026gt;buffer_* values; the remote side\n    cannot enlarge those queues beyond what the local endpoint\n    configured.\n\n  - Hyper-V\u0026apos;s vsock transport uses fixed-size VMBus ring buffers and\n    an MTU bound; there is no peer-controlled credit field comparable\n    to peer_buf_alloc, and the remote endpoint cannot drive in-flight\n    kernel memory above those ring sizes.\n\n  - The loopback path reuses virtio_transport_common.c, so it\n    naturally follows the same semantics as the virtio transport.\n\nThis change is limited to virtio_transport_common.c and thus affects\nvirtio-vsock, vhost-vsock, and loopback, bringing them in line with the\n\u0026quot;remote window intersected with local policy\u0026quot; behaviour that VMCI and\nHyper-V already effectively have.\n\n[Stefano: small adjustments after changing the previous patch]\n[Stefano: tweak the commit message](CVE-2026-23086)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: limit BOND_MODE_8023AD to Ethernet devices\n\nBOND_MODE_8023AD makes sense for ARPHRD_ETHER only.\n\nsyzbot reported:\n\n BUG: KASAN: global-out-of-bounds in __hw_addr_create net/core/dev_addr_lists.c:63 [inline]\n BUG: KASAN: global-out-of-bounds in __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118\nRead of size 16 at addr ffffffff8bf94040 by task syz.1.3580/19497\n\nCPU: 1 UID: 0 PID: 19497 Comm: syz.1.3580 Tainted: G             L      syzkaller #0 PREEMPT(full)\nTainted: [L]=SOFTLOCKUP\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0xe8/0x150 lib/dump_stack.c:120\n  print_address_description mm/kasan/report.c:378 [inline]\n  print_report+0xca/0x240 mm/kasan/report.c:482\n  kasan_report+0x118/0x150 mm/kasan/report.c:595\n check_region_inline mm/kasan/generic.c:-1 [inline]\n  kasan_check_range+0x2b0/0x2c0 mm/kasan/generic.c:200\n  __asan_memcpy+0x29/0x70 mm/kasan/shadow.c:105\n  __hw_addr_create net/core/dev_addr_lists.c:63 [inline]\n  __hw_addr_add_ex+0x25d/0x760 net/core/dev_addr_lists.c:118\n  __dev_mc_add net/core/dev_addr_lists.c:868 [inline]\n  dev_mc_add+0xa1/0x120 net/core/dev_addr_lists.c:886\n  bond_enslave+0x2b8b/0x3ac0 drivers/net/bonding/bond_main.c:2180\n  do_set_master+0x533/0x6d0 net/core/rtnetlink.c:2963\n  do_setlink+0xcf0/0x41c0 net/core/rtnetlink.c:3165\n  rtnl_changelink net/core/rtnetlink.c:3776 [inline]\n  __rtnl_newlink net/core/rtnetlink.c:3935 [inline]\n  rtnl_newlink+0x161c/0x1c90 net/core/rtnetlink.c:4072\n  rtnetlink_rcv_msg+0x7cf/0xb70 net/core/rtnetlink.c:6958\n  netlink_rcv_skb+0x208/0x470 net/netlink/af_netlink.c:2550\n  netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline]\n  netlink_unicast+0x82f/0x9e0 net/netlink/af_netlink.c:1344\n  netlink_sendmsg+0x805/0xb30 net/netlink/af_netlink.c:1894\n  sock_sendmsg_nosec net/socket.c:727 [inline]\n  __sock_sendmsg+0x21c/0x270 net/socket.c:742\n  ____sys_sendmsg+0x505/0x820 net/socket.c:2592\n  ___sys_sendmsg+0x21f/0x2a0 net/socket.c:2646\n  __sys_sendmsg+0x164/0x220 net/socket.c:2678\n  do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n  __do_fast_syscall_32+0x1dc/0x560 arch/x86/entry/syscall_32.c:307\n  do_fast_syscall_32+0x34/0x80 arch/x86/entry/syscall_32.c:332\n entry_SYSENTER_compat_after_hwframe+0x84/0x8e\n \u0026lt;/TASK\u0026gt;\n\nThe buggy address belongs to the variable:\n lacpdu_mcast_addr+0x0/0x40(CVE-2026-23099)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipvlan: Make the addrs_lock be per port\n\nMake the addrs_lock be per port, not per ipvlan dev.\n\nInitial code seems to be written in the assumption,\nthat any address change must occur under RTNL.\nBut it is not so for the case of IPv6. So\n\n1) Introduce per-port addrs_lock.\n\n2) It was needed to fix places where it was forgotten\nto take lock (ipvlan_open/ipvlan_close)\n\nThis appears to be a very minor problem though.\nSince it\u0026apos;s highly unlikely that ipvlan_add_addr() will\nbe called on 2 CPU simultaneously. But nevertheless,\nthis could cause:\n\n1) False-negative of ipvlan_addr_busy(): one interface\niterated through all port-\u0026gt;ipvlans + ipvlan-\u0026gt;addrs\nunder some ipvlan spinlock, and another added IP\nunder its own lock. Though this is only possible\nfor IPv6, since looks like only ipvlan_addr6_event() can be\ncalled without rtnl_lock.\n\n2) Race since ipvlan_ht_addr_add(port) is called under\ndifferent ipvlan-\u0026gt;addrs_lock locks\n\nThis should not affect performance, since add/remove IP\nis a rare situation and spinlock is not taken on fast\npaths.(CVE-2026-23103)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: qfq: Use cl_is_active to determine whether class is active in qfq_rm_from_ag\n\nThis is more of a preventive patch to make the code more consistent and\nto prevent possible exploits that employ child qlen manipulations on qfq.\nuse cl_is_active instead of relying on the child qdisc\u0026apos;s qlen to determine\nclass activation.(CVE-2026-23105)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: fix inverted genmask check in nft_map_catchall_activate()\n\nnft_map_catchall_activate() has an inverted element activity check\ncompared to its non-catchall counterpart nft_mapelem_activate() and\ncompared to what is logically required.\n\nnft_map_catchall_activate() is called from the abort path to re-activate\ncatchall map elements that were deactivated during a failed transaction.\nIt should skip elements that are already active (they don\u0026apos;t need\nre-activation) and process elements that are inactive (they need to be\nrestored). Instead, the current code does the opposite: it skips inactive\nelements and processes active ones.\n\nCompare the non-catchall activate callback, which is correct:\n\n  nft_mapelem_activate():\n    if (nft_set_elem_active(ext, iter-\u0026gt;genmask))\n        return 0;   /* skip active, process inactive */\n\nWith the buggy catchall version:\n\n  nft_map_catchall_activate():\n    if (!nft_set_elem_active(ext, genmask))\n        continue;   /* skip inactive, process active */\n\nThe consequence is that when a DELSET operation is aborted,\nnft_setelem_data_activate() is never called for the catchall element.\nFor NFT_GOTO verdict elements, this means nft_data_hold() is never\ncalled to restore the chain-\u0026gt;use reference count. Each abort cycle\npermanently decrements chain-\u0026gt;use. Once chain-\u0026gt;use reaches zero,\nDELCHAIN succeeds and frees the chain while catchall verdict elements\nstill reference it, resulting in a use-after-free.\n\nThis is exploitable for local privilege escalation from an unprivileged\nuser via user namespaces + nftables on distributions that enable\nCONFIG_USER_NS and CONFIG_NF_TABLES.\n\nFix by removing the negation so the check matches nft_mapelem_activate():\nskip active elements, process inactive ones.(CVE-2026-23111)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nl2tp: avoid one data-race in l2tp_tunnel_del_work()\n\nWe should read sk-\u0026gt;sk_socket only when dealing with kernel sockets.\n\nsyzbot reported the following data-race:\n\nBUG: KCSAN: data-race in l2tp_tunnel_del_work / sk_common_release\n\nwrite to 0xffff88811c182b20 of 8 bytes by task 5365 on cpu 0:\n  sk_set_socket include/net/sock.h:2092 [inline]\n  sock_orphan include/net/sock.h:2118 [inline]\n  sk_common_release+0xae/0x230 net/core/sock.c:4003\n  udp_lib_close+0x15/0x20 include/net/udp.h:325\n  inet_release+0xce/0xf0 net/ipv4/af_inet.c:437\n  __sock_release net/socket.c:662 [inline]\n  sock_close+0x6b/0x150 net/socket.c:1455\n  __fput+0x29b/0x650 fs/file_table.c:468\n  ____fput+0x1c/0x30 fs/file_table.c:496\n  task_work_run+0x131/0x1a0 kernel/task_work.c:233\n  resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n  __exit_to_user_mode_loop kernel/entry/common.c:44 [inline]\n  exit_to_user_mode_loop+0x1fe/0x740 kernel/entry/common.c:75\n  __exit_to_user_mode_prepare include/linux/irq-entry-common.h:226 [inline]\n  syscall_exit_to_user_mode_prepare include/linux/irq-entry-common.h:256 [inline]\n  syscall_exit_to_user_mode_work include/linux/entry-common.h:159 [inline]\n  syscall_exit_to_user_mode include/linux/entry-common.h:194 [inline]\n  do_syscall_64+0x1e1/0x2b0 arch/x86/entry/syscall_64.c:100\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nread to 0xffff88811c182b20 of 8 bytes by task 827 on cpu 1:\n  l2tp_tunnel_del_work+0x2f/0x1a0 net/l2tp/l2tp_core.c:1418\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0x4ce/0x9d0 kernel/workqueue.c:3340\n  worker_thread+0x582/0x770 kernel/workqueue.c:3421\n  kthread+0x489/0x510 kernel/kthread.c:463\n  ret_from_fork+0x149/0x290 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246\n\nvalue changed: 0xffff88811b818000 -\u0026gt; 0x0000000000000000(CVE-2026-23120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: annotate data-race in ndisc_router_discovery()\n\nsyzbot found that ndisc_router_discovery() could read and write\nin6_dev-\u0026gt;ra_mtu without holding a lock [1]\n\nThis looks fine, IFLA_INET6_RA_MTU is best effort.\n\nAdd READ_ONCE()/WRITE_ONCE() to document the race.\n\nNote that we might also reject illegal MTU values\n(mtu \u0026lt; IPV6_MIN_MTU || mtu \u0026gt; skb-\u0026gt;dev-\u0026gt;mtu) in a future patch.\n\n[1]\nBUG: KCSAN: data-race in ndisc_router_discovery / ndisc_router_discovery\n\nread to 0xffff888119809c20 of 4 bytes by task 25817 on cpu 1:\n  ndisc_router_discovery+0x151d/0x1c90 net/ipv6/ndisc.c:1558\n  ndisc_rcv+0x2ad/0x3d0 net/ipv6/ndisc.c:1841\n  icmpv6_rcv+0xe5a/0x12f0 net/ipv6/icmp.c:989\n  ip6_protocol_deliver_rcu+0xb2a/0x10d0 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0xf0/0x1d0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x5e/0x140 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x27c/0x470 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x336/0x340 net/ipv6/ip6_input.c:79\n...\n\nwrite to 0xffff888119809c20 of 4 bytes by task 25816 on cpu 0:\n  ndisc_router_discovery+0x155a/0x1c90 net/ipv6/ndisc.c:1559\n  ndisc_rcv+0x2ad/0x3d0 net/ipv6/ndisc.c:1841\n  icmpv6_rcv+0xe5a/0x12f0 net/ipv6/icmp.c:989\n  ip6_protocol_deliver_rcu+0xb2a/0x10d0 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0xf0/0x1d0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x5e/0x140 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x27c/0x470 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x336/0x340 net/ipv6/ip6_input.c:79\n...\n\nvalue changed: 0x00000000 -\u0026gt; 0xe5400659(CVE-2026-23124)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetdevsim: fix a race issue related to the operation on bpf_bound_progs list\n\nThe netdevsim driver lacks a protection mechanism for operations on the\nbpf_bound_progs list. When the nsim_bpf_create_prog() performs\nlist_add_tail, it is possible that nsim_bpf_destroy_prog() is\nsimultaneously performs list_del. Concurrent operations on the list may\nlead to list corruption and trigger a kernel crash as follows:\n\n[  417.290971] kernel BUG at lib/list_debug.c:62!\n[  417.290983] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI\n[  417.290992] CPU: 10 PID: 168 Comm: kworker/10:1 Kdump: loaded Not tainted 6.19.0-rc5 #1\n[  417.291003] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[  417.291007] Workqueue: events bpf_prog_free_deferred\n[  417.291021] RIP: 0010:__list_del_entry_valid_or_report+0xa7/0xc0\n[  417.291034] Code: a8 ff 0f 0b 48 89 fe 48 89 ca 48 c7 c7 48 a1 eb ae e8 ed fb a8 ff 0f 0b 48 89 fe 48 89 c2 48 c7 c7 80 a1 eb ae e8 d9 fb a8 ff \u0026lt;0f\u0026gt; 0b 48 89 d1 48 c7 c7 d0 a1 eb ae 48 89 f2 48 89 c6 e8 c2 fb a8\n[  417.291040] RSP: 0018:ffffb16a40807df8 EFLAGS: 00010246\n[  417.291046] RAX: 000000000000006d RBX: ffff8e589866f500 RCX: 0000000000000000\n[  417.291051] RDX: 0000000000000000 RSI: ffff8e59f7b23180 RDI: ffff8e59f7b23180\n[  417.291055] RBP: ffffb16a412c9000 R08: 0000000000000000 R09: 0000000000000003\n[  417.291059] R10: ffffb16a40807c80 R11: ffffffffaf9edce8 R12: ffff8e594427ac20\n[  417.291063] R13: ffff8e59f7b44780 R14: ffff8e58800b7a05 R15: 0000000000000000\n[  417.291074] FS:  0000000000000000(0000) GS:ffff8e59f7b00000(0000) knlGS:0000000000000000\n[  417.291079] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  417.291083] CR2: 00007fc4083efe08 CR3: 00000001c3626006 CR4: 0000000000770ee0\n[  417.291088] PKRU: 55555554\n[  417.291091] Call Trace:\n[  417.291096]  \u0026lt;TASK\u0026gt;\n[  417.291103]  nsim_bpf_destroy_prog+0x31/0x80 [netdevsim]\n[  417.291154]  __bpf_prog_offload_destroy+0x2a/0x80\n[  417.291163]  bpf_prog_dev_bound_destroy+0x6f/0xb0\n[  417.291171]  bpf_prog_free_deferred+0x18e/0x1a0\n[  417.291178]  process_one_work+0x18a/0x3a0\n[  417.291188]  worker_thread+0x27b/0x3a0\n[  417.291197]  ? __pfx_worker_thread+0x10/0x10\n[  417.291207]  kthread+0xe5/0x120\n[  417.291214]  ? __pfx_kthread+0x10/0x10\n[  417.291221]  ret_from_fork+0x31/0x50\n[  417.291230]  ? __pfx_kthread+0x10/0x10\n[  417.291236]  ret_from_fork_asm+0x1a/0x30\n[  417.291246]  \u0026lt;/TASK\u0026gt;\n\nAdd a mutex lock, to prevent simultaneous addition and deletion operations\non the list.(CVE-2026-23126)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath10k: fix dma_free_coherent() pointer\n\ndma_alloc_coherent() allocates a DMA mapped buffer and stores the\naddresses in XXX_unaligned fields.  Those should be reused when freeing\nthe buffer rather than the aligned addresses.(CVE-2026-23133)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: reset sparse-read state in osd_fault()\n\nWhen a fault occurs, the connection is abandoned, reestablished, and any\npending operations are retried. The OSD client tracks the progress of a\nsparse-read reply using a separate state machine, largely independent of\nthe messenger\u0026apos;s state.\n\nIf a connection is lost mid-payload or the sparse-read state machine\nreturns an error, the sparse-read state is not reset. The OSD client\nwill then interpret the beginning of a new reply as the continuation of\nthe old one. If this makes the sparse-read machinery enter a failure\nstate, it may never recover, producing loops like:\n\n  libceph:  [0] got 0 extents\n  libceph: data len 142248331 != extent len 0\n  libceph: osd0 (1)...:6801 socket error on read\n  libceph: data len 142248331 != extent len 0\n  libceph: osd0 (1)...:6801 socket error on read\n\nTherefore, reset the sparse-read state in osd_fault(), ensuring retries\nstart from a clean state.(CVE-2026-23136)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nof: unittest: Fix memory leak in unittest_data_add()\n\nIn unittest_data_add(), if of_resolve_phandles() fails, the allocated\nunittest_data is not freed, leading to a memory leak.\n\nFix this by using scope-based cleanup helper __free(kfree) for automatic\nresource cleanup. This ensures unittest_data is automatically freed when\nit goes out of scope in error paths.\n\nFor the success path, use retain_and_null_ptr() to transfer ownership\nof the memory to the device tree and prevent double freeing.(CVE-2026-23137)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_conncount: update last_gc only when GC has been performed\n\nCurrently last_gc is being updated everytime a new connection is\ntracked, that means that it is updated even if a GC wasn\u0026apos;t performed.\nWith a sufficiently high packet rate, it is possible to always bypass\nthe GC, causing the list to grow infinitely.\n\nUpdate the last_gc value only when a GC has been actually performed.(CVE-2026-23139)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: fix iloc.bh leak in ext4_xattr_inode_update_ref\n\nThe error branch for ext4_xattr_inode_update_ref forget to release the\nrefcount for iloc.bh. Find this when review code.(CVE-2026-23145)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix segmentation of forwarding fraglist GRO\n\nThis patch enhances GSO segment handling by properly checking\nthe SKB_GSO_DODGY flag for frag_list GSO packets, addressing\nlow throughput issues observed when a station accesses IPv4\nservers via hotspots with an IPv6-only upstream interface.\n\nSpecifically, it fixes a bug in GSO segmentation when forwarding\nGRO packets containing a frag_list. The function skb_segment_list\ncannot correctly process GRO skbs that have been converted by XLAT,\nsince XLAT only translates the header of the head skb. Consequently,\nskbs in the frag_list may remain untranslated, resulting in protocol\ninconsistencies and reduced throughput.\n\nTo address this, the patch explicitly sets the SKB_GSO_DODGY flag\nfor GSO packets in XLAT\u0026apos;s IPv4/IPv6 protocol translation helpers\n(bpf_skb_proto_4_to_6 and bpf_skb_proto_6_to_4). This marks GSO\npackets as potentially modified after protocol translation. As a\nresult, GSO segmentation will avoid using skb_segment_list and\ninstead falls back to skb_segment for packets with the SKB_GSO_DODGY\nflag. This ensures that only safe and fully translated frag_list\npackets are processed by skb_segment_list, resolving protocol\ninconsistencies and improving throughput when forwarding GRO packets\nconverted by XLAT.(CVE-2026-23154)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nefivarfs: fix error propagation in efivar_entry_get()\n\nefivar_entry_get() always returns success even if the underlying\n__efivar_entry_get() fails, masking errors.\n\nThis may result in uninitialized heap memory being copied to userspace\nin the efivarfs_file_read() path.\n\nFix it by returning the error from __efivar_entry_get().(CVE-2026-23156)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: fix race in mptcp_pm_nl_flush_addrs_doit()\n\nsyzbot and Eulgyu Kim reported crashes in mptcp_pm_nl_get_local_id()\nand/or mptcp_pm_nl_is_backup()\n\nRoot cause is list_splice_init() in mptcp_pm_nl_flush_addrs_doit()\nwhich is not RCU ready.\n\nlist_splice_init_rcu() can not be called here while holding pernet-\u0026gt;lock\nspinlock.\n\nMany thanks to Eulgyu Kim for providing a repro and testing our patches.(CVE-2026-23169)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: TC, delete flows only for existing peers\n\nWhen deleting TC steering flows, iterate only over actual devcom\npeers instead of assuming all possible ports exist. This avoids\ntouching non-existent peers and ensures cleanup is limited to\ndevices the driver is currently connected to.\n\n BUG: kernel NULL pointer dereference, address: 0000000000000008\n #PF: supervisor write access in kernel mode\n #PF: error_code(0x0002) - not-present page\n PGD 133c8a067 P4D 0\n Oops: Oops: 0002 [#1] SMP\n CPU: 19 UID: 0 PID: 2169 Comm: tc Not tainted 6.18.0+ #156 NONE\n Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\n RIP: 0010:mlx5e_tc_del_fdb_peers_flow+0xbe/0x200 [mlx5_core]\n Code: 00 00 a8 08 74 a8 49 8b 46 18 f6 c4 02 74 9f 4c 8d bf a0 12 00 00 4c 89 ff e8 0e e7 96 e1 49 8b 44 24 08 49 8b 0c 24 4c 89 ff \u0026lt;48\u0026gt; 89 41 08 48 89 08 49 89 2c 24 49 89 5c 24 08 e8 7d ce 96 e1 49\n RSP: 0018:ff11000143867528 EFLAGS: 00010246\n RAX: 0000000000000000 RBX: dead000000000122 RCX: 0000000000000000\n RDX: ff11000143691580 RSI: ff110001026e5000 RDI: ff11000106f3d2a0\n RBP: dead000000000100 R08: 00000000000003fd R09: 0000000000000002\n R10: ff11000101c75690 R11: ff1100085faea178 R12: ff11000115f0ae78\n R13: 0000000000000000 R14: ff11000115f0a800 R15: ff11000106f3d2a0\n FS:  00007f35236bf740(0000) GS:ff110008dc809000(0000) knlGS:0000000000000000\n CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n CR2: 0000000000000008 CR3: 0000000157a01001 CR4: 0000000000373eb0\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  mlx5e_tc_del_flow+0x46/0x270 [mlx5_core]\n  mlx5e_flow_put+0x25/0x50 [mlx5_core]\n  mlx5e_delete_flower+0x2a6/0x3e0 [mlx5_core]\n  tc_setup_cb_reoffload+0x20/0x80\n  fl_reoffload+0x26f/0x2f0 [cls_flower]\n  ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]\n  ? mlx5e_tc_reoffload_flows_work+0xc0/0xc0 [mlx5_core]\n  tcf_block_playback_offloads+0x9e/0x1c0\n  tcf_block_unbind+0x7b/0xd0\n  tcf_block_setup+0x186/0x1d0\n  tcf_block_offload_cmd.isra.0+0xef/0x130\n  tcf_block_offload_unbind+0x43/0x70\n  __tcf_block_put+0x85/0x160\n  ingress_destroy+0x32/0x110 [sch_ingress]\n  __qdisc_destroy+0x44/0x100\n  qdisc_graft+0x22b/0x610\n  tc_get_qdisc+0x183/0x4d0\n  rtnetlink_rcv_msg+0x2d7/0x3d0\n  ? rtnl_calcit.isra.0+0x100/0x100\n  netlink_rcv_skb+0x53/0x100\n  netlink_unicast+0x249/0x320\n  ? __alloc_skb+0x102/0x1f0\n  netlink_sendmsg+0x1e3/0x420\n  __sock_sendmsg+0x38/0x60\n  ____sys_sendmsg+0x1ef/0x230\n  ? copy_msghdr_from_user+0x6c/0xa0\n  ___sys_sendmsg+0x7f/0xc0\n  ? ___sys_recvmsg+0x8a/0xc0\n  ? __sys_sendto+0x119/0x180\n  __sys_sendmsg+0x61/0xb0\n  do_syscall_64+0x55/0x640\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n RIP: 0033:0x7f35238bb764\n Code: 15 b9 86 0c 00 f7 d8 64 89 02 b8 ff ff ff ff eb bf 0f 1f 44 00 00 f3 0f 1e fa 80 3d e5 08 0d 00 00 74 13 b8 2e 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 00 f0 ff ff 77 4c c3 0f 1f 00 55 48 89 e5 48 83 ec 20 89 55\n RSP: 002b:00007ffed4c35638 EFLAGS: 00000202 ORIG_RAX: 000000000000002e\n RAX: ffffffffffffffda RBX: 000055a2efcc75e0 RCX: 00007f35238bb764\n RDX: 0000000000000000 RSI: 00007ffed4c356a0 RDI: 0000000000000003\n RBP: 00007ffed4c35710 R08: 0000000000000010 R09: 00007f3523984b20\n R10: 0000000000000004 R11: 0000000000000202 R12: 00007ffed4c35790\n R13: 000000006947df8f R14: 000055a2efcc75e0 R15: 00007ffed4c35780(CVE-2026-23173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: aloop: Fix racy access at PCM trigger\n\nThe PCM trigger callback of aloop driver tries to check the PCM state\nand stop the stream of the tied substream in the corresponding cable.\nSince both check and stop operations are performed outside the cable\nlock, this may result in UAF when a program attempts to trigger\nfrequently while opening/closing the tied stream, as spotted by\nfuzzers.\n\nFor addressing the UAF, this patch changes two things:\n- It covers the most of code in loopback_check_format() with\n  cable-\u0026gt;lock spinlock, and add the proper NULL checks.  This avoids\n  already some racy accesses.\n- In addition, now we try to check the state of the capture PCM stream\n  that may be stopped in this function, which was the major pain point\n  leading to UAF.(CVE-2026-23191)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: Don\u0026apos;t clobber irqfd routing type when deassigning irqfd\n\nWhen deassigning a KVM_IRQFD, don\u0026apos;t clobber the irqfd\u0026apos;s copy of the IRQ\u0026apos;s\nrouting entry as doing so breaks kvm_arch_irq_bypass_del_producer() on x86\nand arm64, which explicitly look for KVM_IRQ_ROUTING_MSI.  Instead, to\nhandle a concurrent routing update, verify that the irqfd is still active\nbefore consuming the routing information.  As evidenced by the x86 and\narm64 bugs, and another bug in kvm_arch_update_irqfd_routing() (see below),\nclobbering the entry type without notifying arch code is surprising and\nerror prone.\n\nAs a bonus, checking that the irqfd is active provides a convenient\nlocation for documenting _why_ KVM must not consume the routing entry for\nan irqfd that is in the process of being deassigned: once the irqfd is\ndeleted from the list (which happens *before* the eventfd is detached), it\nwill no longer receive updates via kvm_irq_routing_update(), and so KVM\ncould deliver an event using stale routing information (relative to\nKVM_SET_GSI_ROUTING returning to userspace).\n\nAs an even better bonus, explicitly checking for the irqfd being active\nfixes a similar bug to the one the clobbering is trying to prevent: if an\nirqfd is deactivated, and then its routing is changed,\nkvm_irq_routing_update() won\u0026apos;t invoke kvm_arch_update_irqfd_routing()\n(because the irqfd isn\u0026apos;t in the list).  And so if the irqfd is in bypass\nmode, IRQs will continue to be posted using the old routing information.\n\nAs for kvm_arch_irq_bypass_del_producer(), clobbering the routing type\nresults in KVM incorrectly keeping the IRQ in bypass mode, which is\nespecially problematic on AMD as KVM tracks IRQs that are being posted to\na vCPU in a list whose lifetime is tied to the irqfd.\n\nWithout the help of KASAN to detect use-after-free, the most common\nsympton on AMD is a NULL pointer deref in amd_iommu_update_ga() due to\nthe memory for irqfd structure being re-allocated and zeroed, resulting\nin irqfd-\u0026gt;irq_bypass_data being NULL when read by\navic_update_iommu_vcpu_affinity():\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000018\n  #PF: supervisor read access in kernel mode\n  #PF: error_code(0x0000) - not-present page\n  PGD 40cf2b9067 P4D 40cf2b9067 PUD 408362a067 PMD 0\n  Oops: Oops: 0000 [#1] SMP\n  CPU: 6 UID: 0 PID: 40383 Comm: vfio_irq_test\n  Tainted: G     U  W  O        6.19.0-smp--5dddc257e6b2-irqfd #31 NONE\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025\n  RIP: 0010:amd_iommu_update_ga+0x19/0xe0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   avic_update_iommu_vcpu_affinity+0x3d/0x90 [kvm_amd]\n   __avic_vcpu_load+0xf4/0x130 [kvm_amd]\n   kvm_arch_vcpu_load+0x89/0x210 [kvm]\n   vcpu_load+0x30/0x40 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x45/0x620 [kvm]\n   kvm_vcpu_ioctl+0x571/0x6a0 [kvm]\n   __se_sys_ioctl+0x6d/0xb0\n   do_syscall_64+0x6f/0x9d0\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x46893b\n    \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nIf AVIC is inhibited when the irfd is deassigned, the bug will manifest as\nlist corruption, e.g. on the next irqfd assignment.\n\n  list_add corruption. next-\u0026gt;prev should be prev (ffff8d474d5cd588),\n                       but was 0000000000000000. (next=ffff8d8658f86530).\n  ------------[ cut here ]------------\n  kernel BUG at lib/list_debug.c:31!\n  Oops: invalid opcode: 0000 [#1] SMP\n  CPU: 128 UID: 0 PID: 80818 Comm: vfio_irq_test\n  Tainted: G     U  W  O        6.19.0-smp--f19dc4d680ba-irqfd #28 NONE\n  Tainted: [U]=USER, [W]=WARN, [O]=OOT_MODULE\n  Hardware name: Google, Inc. Arcadia_IT_80/Arcadia_IT_80, BIOS 34.78.2-0 09/05/2025\n  RIP: 0010:__list_add_valid_or_report+0x97/0xc0\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   avic_pi_update_irte+0x28e/0x2b0 [kvm_amd]\n   kvm_pi_update_irte+0xbf/0x190 [kvm]\n   kvm_arch_irq_bypass_add_producer+0x72/0x90 [kvm]\n   irq_bypass_register_consumer+0xcd/0x170 [irqbypa\n---truncated---(CVE-2026-23198)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: cls_u32: use skb_header_pointer_careful()\n\nskb_header_pointer() does not fully validate negative @offset values.\n\nUse skb_header_pointer_careful() instead.\n\nGangMin Kim provided a report and a repro fooling u32_classify():\n\nBUG: KASAN: slab-out-of-bounds in u32_classify+0x1180/0x11b0\nnet/sched/cls_u32.c:221(CVE-2026-23204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nALSA: usb-audio: Prevent excessive number of frames\n\nIn this case, the user constructed the parameters with maxpacksize 40\nfor rate 22050 / pps 1000, and packsize[0] 22 packsize[1] 23. The buffer\nsize for each data URB is maxpacksize * packets, which in this example\nis 40 * 6 = 240; When the user performs a write operation to send audio\ndata into the ALSA PCM playback stream, the calculated number of frames\nis packsize[0] * packets = 264, which exceeds the allocated URB buffer\nsize, triggering the out-of-bounds (OOB) issue reported by syzbot [1].\n\nAdded a check for the number of single data URB frames when calculating\nthe number of frames to prevent [1].\n\n[1]\nBUG: KASAN: slab-out-of-bounds in copy_to_urb+0x261/0x460 sound/usb/pcm.c:1487\nWrite of size 264 at addr ffff88804337e800 by task syz.0.17/5506\nCall Trace:\n copy_to_urb+0x261/0x460 sound/usb/pcm.c:1487\n prepare_playback_urb+0x953/0x13d0 sound/usb/pcm.c:1611\n prepare_outbound_urb+0x377/0xc50 sound/usb/endpoint.c:333(CVE-2026-23208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbonding: annotate data-races around slave-\u0026gt;last_rx\n\nslave-\u0026gt;last_rx and slave-\u0026gt;target_last_arp_rx[...] can be read and written\nlocklessly. Add READ_ONCE() and WRITE_ONCE() annotations.\n\nsyzbot reported:\n\nBUG: KCSAN: data-race in bond_rcv_validate / bond_rcv_validate\n\nwrite to 0xffff888149f0d428 of 8 bytes by interrupt on cpu 1:\n  bond_rcv_validate+0x202/0x7a0 drivers/net/bonding/bond_main.c:3335\n  bond_handle_frame+0xde/0x5e0 drivers/net/bonding/bond_main.c:1533\n  __netif_receive_skb_core+0x5b1/0x1950 net/core/dev.c:6039\n  __netif_receive_skb_one_core net/core/dev.c:6150 [inline]\n  __netif_receive_skb+0x59/0x270 net/core/dev.c:6265\n  netif_receive_skb_internal net/core/dev.c:6351 [inline]\n  netif_receive_skb+0x4b/0x2d0 net/core/dev.c:6410\n...\n\nwrite to 0xffff888149f0d428 of 8 bytes by interrupt on cpu 0:\n  bond_rcv_validate+0x202/0x7a0 drivers/net/bonding/bond_main.c:3335\n  bond_handle_frame+0xde/0x5e0 drivers/net/bonding/bond_main.c:1533\n  __netif_receive_skb_core+0x5b1/0x1950 net/core/dev.c:6039\n  __netif_receive_skb_one_core net/core/dev.c:6150 [inline]\n  __netif_receive_skb+0x59/0x270 net/core/dev.c:6265\n  netif_receive_skb_internal net/core/dev.c:6351 [inline]\n  netif_receive_skb+0x4b/0x2d0 net/core/dev.c:6410\n  br_netif_receive_skb net/bridge/br_input.c:30 [inline]\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n...\n\nvalue changed: 0x0000000100005365 -\u0026gt; 0x0000000100005366(CVE-2026-23212)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbus: fsl-mc: fix use-after-free in driver_override_show()\n\nThe driver_override_show() function reads the driver_override string\nwithout holding the device_lock. However, driver_override_store() uses\ndriver_set_override(), which modifies and frees the string while holding\nthe device_lock.\n\nThis can result in a concurrent use-after-free if the string is freed\nby the store function while being read by the show function.\n\nFix this by holding the device_lock around the read operation.(CVE-2026-23221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: split cached_fid bitfields to avoid shared-byte RMW races\n\nis_open, has_lease and on_list are stored in the same bitfield byte in\nstruct cached_fid but are updated in different code paths that may run\nconcurrently. Bitfield assignments generate byte read–modify–write\noperations (e.g. `orb $mask, addr` on x86_64), so updating one flag can\nrestore stale values of the others.\n\nA possible interleaving is:\n    CPU1: load old byte (has_lease=1, on_list=1)\n    CPU2: clear both flags (store 0)\n    CPU1: RMW store (old | IS_OPEN) -\u0026gt; reintroduces cleared bits\n\nTo avoid this class of races, convert these flags to separate bool\nfields.(CVE-2026-23230)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:55.317925454Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1761","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/s390: Implement blocking domain\n\nThis fixes a crash when surprise hot-unplugging a PCI device. This crash\nhappens because during hot-unplug __iommu_group_set_domain_nofail()\nattaching the default domain fails when the platform no longer\nrecognizes the device as it has already been removed and we end up with\na NULL domain pointer and UAF. This is exactly the case referred to in\nthe second comment in __iommu_device_set_domain() and just as stated\nthere if we can instead attach the blocking domain the UAF is prevented\nas this can handle the already removed device. Implement the blocking\ndomain to use this handling.  With this change, the crash is fixed but\nwe still hit a warning attempting to change DMA ownership on a blocked\ndevice.(CVE-2024-53232)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu: Fix two issues in iommu_copy_struct_from_user()\n\nIn the review for iommu_copy_struct_to_user() helper, Matt pointed out that\na NULL pointer should be rejected prior to dereferencing it:\nhttps://lore.kernel.org/all/(CVE-2025-37900)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb: client: Avoid race in open_cached_dir with lease breaks\n\nA pre-existing valid cfid returned from find_or_create_cached_dir might\nrace with a lease break, meaning open_cached_dir doesn\u0026apos;t consider it\nvalid, and thinks it\u0026apos;s newly-constructed. This leaks a dentry reference\nif the allocation occurs before the queued lease break work runs.\n\nAvoid the race by extending holding the cfid_list_lock across\nfind_or_create_cached_dir and when the result is checked.(CVE-2025-37954)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet_sched: prio: fix a race in prio_tune()\n\nGerrard Tai reported a race condition in PRIO, whenever SFQ perturb timer\nfires at the wrong time.\n\nThe race is as follows:\n\nCPU 0                                 CPU 1\n[1]: lock root\n[2]: qdisc_tree_flush_backlog()\n[3]: unlock root\n |\n |                                    [5]: lock root\n |                                    [6]: rehash\n |                                    [7]: qdisc_tree_reduce_backlog()\n |\n[4]: qdisc_put()\n\nThis can be abused to underflow a parent\u0026apos;s qlen.\n\nCalling qdisc_purge_queue() instead of qdisc_tree_flush_backlog()\nshould fix the race, because all packets will be purged from the qdisc\nbefore releasing the lock.(CVE-2025-38083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nIB/mlx5: Fix potential deadlock in MR deregistration\n\nThe issue arises when kzalloc() is invoked while holding umem_mutex or\nany other lock acquired under umem_mutex. This is problematic because\nkzalloc() can trigger fs_reclaim_aqcuire(), which may, in turn, invoke\nmmu_notifier_invalidate_range_start(). This function can lead to\nmlx5_ib_invalidate_range(), which attempts to acquire umem_mutex again,\nresulting in a deadlock.\n\nThe problematic flow:\n             CPU0                      |              CPU1\n---------------------------------------|------------------------------------------------\nmlx5_ib_dereg_mr()                     |\n → revoke_mr()                         |\n   → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex) |\n                                       | mlx5_mkey_cache_init()\n                                       |  → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock)\n                                       |  → mlx5r_cache_create_ent_locked()\n                                       |    → kzalloc(GFP_KERNEL)\n                                       |      → fs_reclaim()\n                                       |        → mmu_notifier_invalidate_range_start()\n                                       |          → mlx5_ib_invalidate_range()\n                                       |            → mutex_lock(\u0026amp;umem_odp-\u0026gt;umem_mutex)\n   → cache_ent_find_and_store()        |\n     → mutex_lock(\u0026amp;dev-\u0026gt;cache.rb_lock) |\n\nAdditionally, when kzalloc() is called from within\ncache_ent_find_and_store(), we encounter the same deadlock due to\nre-acquisition of umem_mutex.\n\nSolve by releasing umem_mutex in dereg_mr() after umr_revoke_mr()\nand before acquiring rb_lock. This ensures that we don\u0026apos;t hold\numem_mutex while performing memory allocations that could trigger\nthe reclaim path.\n\nThis change prevents the deadlock by ensuring proper lock ordering and\navoiding holding locks during memory allocation operations that could\ntrigger the reclaim path.\n\nThe following lockdep warning demonstrates the deadlock:\n\n python3/20557 is trying to acquire lock:\n ffff888387542128 (\u0026amp;umem_odp-\u0026gt;umem_mutex){+.+.}-{4:4}, at:\n mlx5_ib_invalidate_range+0x5b/0x550 [mlx5_ib]\n\n but task is already holding lock:\n ffffffff82f6b840 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}, at:\n unmap_vmas+0x7b/0x1a0\n\n which lock already depends on the new lock.\n\n the existing dependency chain (in reverse order) is:\n\n -\u0026gt; #3 (mmu_notifier_invalidate_range_start){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x60/0xd0\n       mem_cgroup_css_alloc+0x6f/0x9b0\n       cgroup_init_subsys+0xa4/0x240\n       cgroup_init+0x1c8/0x510\n       start_kernel+0x747/0x760\n       x86_64_start_reservations+0x25/0x30\n       x86_64_start_kernel+0x73/0x80\n       common_startup_64+0x129/0x138\n\n -\u0026gt; #2 (fs_reclaim){+.+.}-{0:0}:\n       fs_reclaim_acquire+0x91/0xd0\n       __kmalloc_cache_noprof+0x4d/0x4c0\n       mlx5r_cache_create_ent_locked+0x75/0x620 [mlx5_ib]\n       mlx5_mkey_cache_init+0x186/0x360 [mlx5_ib]\n       mlx5_ib_stage_post_ib_reg_umr_init+0x3c/0x60 [mlx5_ib]\n       __mlx5_ib_add+0x4b/0x190 [mlx5_ib]\n       mlx5r_probe+0xd9/0x320 [mlx5_ib]\n       auxiliary_bus_probe+0x42/0x70\n       really_probe+0xdb/0x360\n       __driver_probe_device+0x8f/0x130\n       driver_probe_device+0x1f/0xb0\n       __driver_attach+0xd4/0x1f0\n       bus_for_each_dev+0x79/0xd0\n       bus_add_driver+0xf0/0x200\n       driver_register+0x6e/0xc0\n       __auxiliary_driver_register+0x6a/0xc0\n       do_one_initcall+0x5e/0x390\n       do_init_module+0x88/0x240\n       init_module_from_file+0x85/0xc0\n       idempotent_init_module+0x104/0x300\n       __x64_sys_finit_module+0x68/0xc0\n       do_syscall_64+0x6d/0x140\n       entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n -\u0026gt; #1 (\u0026amp;dev-\u0026gt;cache.rb_lock){+.+.}-{4:4}:\n       __mutex_lock+0x98/0xf10\n       __mlx5_ib_dereg_mr+0x6f2/0x890 [mlx5_ib]\n       mlx5_ib_dereg_mr+0x21/0x110 [mlx5_ib]\n       ib_dereg_mr_user+0x85/0x1f0 [ib_core]\n  \n---truncated---(CVE-2025-38373)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nHID: core: Harden s32ton() against conversion to 0 bits\n\nTesting by the syzbot fuzzer showed that the HID core gets a\nshift-out-of-bounds exception when it tries to convert a 32-bit\nquantity to a 0-bit quantity.  Ideally this should never occur, but\nthere are buggy devices and some might have a report field with size\nset to zero; we shouldn\u0026apos;t reject the report or the device just because\nof that.\n\nInstead, harden the s32ton() routine so that it returns a reasonable\nresult instead of crashing when it is called with the number of bits\nset to 0 -- the same as what snto32() does.(CVE-2025-38556)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Reject narrower access to pointer ctx fields\n\nThe following BPF program, simplified from a syzkaller repro, causes a\nkernel warning:\n\n    r0 = *(u8 *)(r1 + 169);\n    exit;\n\nWith pointer field sk being at offset 168 in __sk_buff. This access is\ndetected as a narrower read in bpf_skb_is_valid_access because it\ndoesn\u0026apos;t match offsetof(struct __sk_buff, sk). It is therefore allowed\nand later proceeds to bpf_convert_ctx_access. Note that for the\n\u0026quot;is_narrower_load\u0026quot; case in the convert_ctx_accesses(), the insn-\u0026gt;off\nis aligned, so the cnt may not be 0 because it matches the\noffsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However,\nthe target_size stays 0 and the verifier errors with a kernel warning:\n\n    verifier bug: error during ctx access conversion(1)\n\nThis patch fixes that to return a proper \u0026quot;invalid bpf_context access\noff=X size=Y\u0026quot; error on the load instruction.\n\nThe same issue affects multiple other fields in context structures that\nallow narrow access. Some other non-affected fields (for sk_msg,\nsk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for\nconsistency.\n\nNote this syzkaller crash was reported in the \u0026quot;Closes\u0026quot; link below, which\nused to be about a different bug, fixed in\ncommit fce7bd8e385a (\u0026quot;bpf/verifier: Handle BPF_LOAD_ACQ instructions\nin insn_def_regno()\u0026quot;). Because syzbot somehow confused the two bugs,\nthe new crash and repro didn\u0026apos;t get reported to the mailing list.(CVE-2025-38591)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: No more self recovery\n\nWhen a node withdraws and it turns out that it is the only node that has\nthe filesystem mounted, gfs2 currently tries to replay the local journal\nto bring the filesystem back into a consistent state.  Not only is that\na very bad idea, it has also never worked because gfs2_recover_func()\nwill refuse to do anything during a withdraw.\n\nHowever, before even getting to this point, gfs2_recover_func()\ndereferences sdp-\u0026gt;sd_jdesc-\u0026gt;jd_inode.  This was a use-after-free before\ncommit 04133b607a78 (\u0026quot;gfs2: Prevent double iput for journal on error\u0026quot;)\nand is a NULL pointer dereference since then.\n\nSimply get rid of self recovery to fix that.(CVE-2025-38659)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/net: commit partial buffers on retry\n\nRing provided buffers are potentially only valid within the single\nexecution context in which they were acquired. io_uring deals with this\nand invalidates them on retry. But on the networking side, if\nMSG_WAITALL is set, or if the socket is of the streaming type and too\nlittle was processed, then it will hang on to the buffer rather than\nrecycle or commit it. This is problematic for two reasons:\n\n1) If someone unregisters the provided buffer ring before a later retry,\n   then the req-\u0026gt;buf_list will no longer be valid.\n\n2) If multiple sockers are using the same buffer group, then multiple\n   receives can consume the same memory. This can cause data corruption\n   in the application, as either receive could land in the same\n   userspace buffer.\n\nFix this by disallowing partial retries from pinning a provided buffer\nacross multiple executions, if ring provided buffers are used.(CVE-2025-38730)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: rainshadow-cec: fix TOCTOU race condition in rain_interrupt()\n\nIn the interrupt handler rain_interrupt(), the buffer full check on\nrain-\u0026gt;buf_len is performed before acquiring rain-\u0026gt;buf_lock. This\ncreates a Time-of-Check to Time-of-Use (TOCTOU) race condition, as\nrain-\u0026gt;buf_len is concurrently accessed and modified in the work\nhandler rain_irq_work_handler() under the same lock.\n\nMultiple interrupt invocations can race, with each reading buf_len\nbefore it becomes full and then proceeding. This can lead to both\ninterrupts attempting to write to the buffer, incrementing buf_len\nbeyond its capacity (DATA_SIZE) and causing a buffer overflow.\n\nFix this bug by moving the spin_lock() to before the buffer full\ncheck. This ensures that the check and the subsequent buffer modification\nare performed atomically, preventing the race condition. An corresponding\nspin_unlock() is added to the overflow path to correctly release the\nlock.\n\nThis possible bug was found by an experimental static analysis tool\ndeveloped by our team.(CVE-2025-39713)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niommu/amd/pgtbl: Fix possible race while increase page table level\n\nThe AMD IOMMU host page table implementation supports dynamic page table levels\n(up to 6 levels), starting with a 3-level configuration that expands based on\nIOVA address. The kernel maintains a root pointer and current page table level\nto enable proper page table walks in alloc_pte()/fetch_pte() operations.\n\nThe IOMMU IOVA allocator initially starts with 32-bit address and onces its\nexhuasted it switches to 64-bit address (max address is determined based\non IOMMU and device DMA capability). To support larger IOVA, AMD IOMMU\ndriver increases page table level.\n\nBut in unmap path (iommu_v1_unmap_pages()), fetch_pte() reads\npgtable-\u0026gt;[root/mode] without lock. So its possible that in exteme corner case,\nwhen increase_address_space() is updating pgtable-\u0026gt;[root/mode], fetch_pte()\nreads wrong page table level (pgtable-\u0026gt;mode). It does compare the value with\nlevel encoded in page table and returns NULL. This will result is\niommu_unmap ops to fail and upper layer may retry/log WARN_ON.\n\nCPU 0                                         CPU 1\n------                                       ------\nmap pages                                    unmap pages\nalloc_pte() -\u0026gt; increase_address_space()      iommu_v1_unmap_pages() -\u0026gt; fetch_pte()\n  pgtable-\u0026gt;root = pte (new root value)\n                                             READ pgtable-\u0026gt;[mode/root]\n\t\t\t\t\t       Reads new root, old mode\n  Updates mode (pgtable-\u0026gt;mode += 1)\n\nSince Page table level updates are infrequent and already synchronized with a\nspinlock, implement seqcount to enable lock-free read operations on the read path.(CVE-2025-39961)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npinctrl: check the return value of pinmux_ops::get_function_name()\n\nWhile the API contract in docs doesn\u0026apos;t specify it explicitly, the\ngeneric implementation of the get_function_name() callback from struct\npinmux_ops - pinmux_generic_get_function_name() - can fail and return\nNULL. This is already checked in pinmux_check_ops() so add a similar\ncheck in pinmux_func_name_to_selector() instead of passing the returned\npointer right down to strcmp() where the NULL can get dereferenced. This\nis normal operation when adding new pinfunctions.(CVE-2025-40030)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix potential double free in drm_sched_job_add_resv_dependencies\n\nWhen adding dependencies with drm_sched_job_add_dependency(), that\nfunction consumes the fence reference both on success and failure, so in\nthe latter case the dma_fence_put() on the error path (xarray failed to\nexpand) is a double free.\n\nInterestingly this bug appears to have been present ever since\ncommit ebd5f74255b9 (\u0026quot;drm/sched: Add dependency tracking\u0026quot;), since the code\nback then looked like this:\n\ndrm_sched_job_add_implicit_dependencies():\n...\n       for (i = 0; i \u0026lt; fence_count; i++) {\n               ret = drm_sched_job_add_dependency(job, fences[i]);\n               if (ret)\n                       break;\n       }\n\n       for (; i \u0026lt; fence_count; i++)\n               dma_fence_put(fences[i]);\n\nWhich means for the failing \u0026apos;i\u0026apos; the dma_fence_put was already a double\nfree. Possibly there were no users at that time, or the test cases were\ninsufficient to hit it.\n\nThe bug was then only noticed and fixed after\ncommit 9c2ba265352a (\u0026quot;drm/scheduler: use new iterator in drm_sched_job_add_implicit_dependencies v2\u0026quot;)\nlanded, with its fixup of\ncommit 4eaf02d6076c (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies\u0026quot;).\n\nAt that point it was a slightly different flavour of a double free, which\ncommit 963d0b356935 (\u0026quot;drm/scheduler: fix drm_sched_job_add_implicit_dependencies harder\u0026quot;)\nnoticed and attempted to fix.\n\nBut it only moved the double free from happening inside the\ndrm_sched_job_add_dependency(), when releasing the reference not yet\nobtained, to the caller, when releasing the reference already released by\nthe former in the failure case.\n\nAs such it is not easy to identify the right target for the fixes tag so\nlets keep it simple and just continue the chain.\n\nWhile fixing we also improve the comment and explain the reason for taking\nthe reference and not dropping it.(CVE-2025-40096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nxfrm: delete x-\u0026gt;tunnel as we delete x\n\nThe ipcomp fallback tunnels currently get deleted (from the various\nlists and hashtables) as the last user state that needed that fallback\nis destroyed (not deleted). If a reference to that user state still\nexists, the fallback state will remain on the hashtables/lists,\ntriggering the WARN in xfrm_state_fini. Because of those remaining\nreferences, the fix in commit f75a2804da39 (\u0026quot;xfrm: destroy xfrm_state\nsynchronously on net exit path\u0026quot;) is not complete.\n\nWe recently fixed one such situation in TCP due to defered freeing of\nskbs (commit 9b6412e6979f (\u0026quot;tcp: drop secpath at the same time as we\ncurrently drop dst\u0026quot;)). This can also happen due to IP reassembly: skbs\nwith a secpath remain on the reassembly queue until netns\ndestruction. If we can\u0026apos;t guarantee that the queues are flushed by the\ntime xfrm_state_fini runs, there may still be references to a (user)\nxfrm_state, preventing the timely deletion of the corresponding\nfallback state.\n\nInstead of chasing each instance of skbs holding a secpath one by one,\nthis patch fixes the issue directly within xfrm, by deleting the\nfallback state as soon as the last user state depending on it has been\ndeleted. Destruction will still happen when the final reference is\ndropped.\n\nA separate lockdep class for the fallback state is required since\nwe\u0026apos;re going to lock x-\u0026gt;tunnel while x is locked.(CVE-2025-40215)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfuse: fix livelock in synchronous file put from fuseblk workers\n\nI observed a hang when running generic/323 against a fuseblk server.\nThis test opens a file, initiates a lot of AIO writes to that file\ndescriptor, and closes the file descriptor before the writes complete.\nUnsurprisingly, the AIO exerciser threads are mostly stuck waiting for\nresponses from the fuseblk server:\n\n# cat /proc/372265/task/372313/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_do_getattr+0xfc/0x1f0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_read_iter+0xbe/0x1c0 [fuse]\n[\u0026lt;0\u0026gt;] aio_read+0x130/0x1e0\n[\u0026lt;0\u0026gt;] io_submit_one+0x542/0x860\n[\u0026lt;0\u0026gt;] __x64_sys_io_submit+0x98/0x1a0\n[\u0026lt;0\u0026gt;] do_syscall_64+0x37/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nBut the /weird/ part is that the fuseblk server threads are waiting for\nresponses from itself:\n\n# cat /proc/372210/task/372232/stack\n[\u0026lt;0\u0026gt;] request_wait_answer+0x1fe/0x2a0 [fuse]\n[\u0026lt;0\u0026gt;] __fuse_simple_request+0xd3/0x2b0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_file_put+0x9a/0xd0 [fuse]\n[\u0026lt;0\u0026gt;] fuse_release+0x36/0x50 [fuse]\n[\u0026lt;0\u0026gt;] __fput+0xec/0x2b0\n[\u0026lt;0\u0026gt;] task_work_run+0x55/0x90\n[\u0026lt;0\u0026gt;] syscall_exit_to_user_mode+0xe9/0x100\n[\u0026lt;0\u0026gt;] do_syscall_64+0x43/0xf0\n[\u0026lt;0\u0026gt;] entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe fuseblk server is fuse2fs so there\u0026apos;s nothing all that exciting in\nthe server itself.  So why is the fuse server calling fuse_file_put?\nThe commit message for the fstest sheds some light on that:\n\n\u0026quot;By closing the file descriptor before calling io_destroy, you pretty\nmuch guarantee that the last put on the ioctx will be done in interrupt\ncontext (during I/O completion).\n\nAha.  AIO fgets a new struct file from the fd when it queues the ioctx.\nThe completion of the FUSE_WRITE command from userspace causes the fuse\nserver to call the AIO completion function.  The completion puts the\nstruct file, queuing a delayed fput to the fuse server task.  When the\nfuse server task returns to userspace, it has to run the delayed fput,\nwhich in the case of a fuseblk server, it does synchronously.\n\nSending the FUSE_RELEASE command sychronously from fuse server threads\nis a bad idea because a client program can initiate enough simultaneous\nAIOs such that all the fuse server threads end up in delayed_fput, and\nnow there aren\u0026apos;t any threads left to handle the queued fuse commands.\n\nFix this by only using asynchronous fputs when closing files, and leave\na comment explaining why.(CVE-2025-40220)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/notify: call exportfs_encode_fid with s_umount\n\nCalling intotify_show_fdinfo() on fd watching an overlayfs inode, while\nthe overlayfs is being unmounted, can lead to dereferencing NULL ptr.\n\nThis issue was found by syzkaller.\n\nRace Condition Diagram:\n\nThread 1                           Thread 2\n--------                           --------\n\ngeneric_shutdown_super()\n shrink_dcache_for_umount\n  sb-\u0026gt;s_root = NULL\n\n                    |\n                    |             vfs_read()\n                    |              inotify_fdinfo()\n                    |               * inode get from mark *\n                    |               show_mark_fhandle(m, inode)\n                    |                exportfs_encode_fid(inode, ..)\n                    |                 ovl_encode_fh(inode, ..)\n                    |                  ovl_check_encode_origin(inode)\n                    |                   * deref i_sb-\u0026gt;s_root *\n                    |\n                    |\n                    v\n fsnotify_sb_delete(sb)\n\nWhich then leads to:\n\n[   32.133461] Oops: general protection fault, probably for non-canonical address 0xdffffc0000000006: 0000 [#1] SMP DEBUG_PAGEALLOC KASAN NOPTI\n[   32.134438] KASAN: null-ptr-deref in range [0x0000000000000030-0x0000000000000037]\n[   32.135032] CPU: 1 UID: 0 PID: 4468 Comm: systemd-coredum Not tainted 6.17.0-rc6 #22 PREEMPT(none)\n\n\u0026lt;snip registers, unreliable trace\u0026gt;\n\n[   32.143353] Call Trace:\n[   32.143732]  ovl_encode_fh+0xd5/0x170\n[   32.144031]  exportfs_encode_inode_fh+0x12f/0x300\n[   32.144425]  show_mark_fhandle+0xbe/0x1f0\n[   32.145805]  inotify_fdinfo+0x226/0x2d0\n[   32.146442]  inotify_show_fdinfo+0x1c5/0x350\n[   32.147168]  seq_show+0x530/0x6f0\n[   32.147449]  seq_read_iter+0x503/0x12a0\n[   32.148419]  seq_read+0x31f/0x410\n[   32.150714]  vfs_read+0x1f0/0x9e0\n[   32.152297]  ksys_read+0x125/0x240\n\nIOW ovl_check_encode_origin derefs inode-\u0026gt;i_sb-\u0026gt;s_root, after it was set\nto NULL in the unmount path.\n\nFix it by protecting calling exportfs_encode_fid() from\nshow_mark_fhandle() with s_umount lock.\n\nThis form of fix was suggested by Amir in [1].\n\n[1]: https://lore.kernel.org/all/CAOQ4uxhbDwhb+2Brs1UdkoF0a3NSdBAOQPNfEHjahrgoKJpLEw@mail.gmail.com/(CVE-2025-40237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Fix unlikely race in gdlm_put_lock\n\nIn gdlm_put_lock(), there is a small window of time in which the\nDFL_UNMOUNT flag has been set but the lockspace hasn\u0026apos;t been released,\nyet.  In that window, dlm may still call gdlm_ast() and gdlm_bast().\nTo prevent it from dereferencing freed glock objects, only free the\nglock if the lockspace has actually been released.(CVE-2025-40242)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndevlink: rate: Unset parent pointer in devl_rate_nodes_destroy\n\nThe function devl_rate_nodes_destroy is documented to \u0026quot;Unset parent for\nall rate objects\u0026quot;. However, it was only calling the driver-specific\n`rate_leaf_parent_set` or `rate_node_parent_set` ops and decrementing\nthe parent\u0026apos;s refcount, without actually setting the\n`devlink_rate-\u0026gt;parent` pointer to NULL.\n\nThis leaves a dangling pointer in the `devlink_rate` struct, which cause\nrefcount error in netdevsim[1] and mlx5[2]. In addition, this is\ninconsistent with the behavior of `devlink_nl_rate_parent_node_set`,\nwhere the parent pointer is correctly cleared.\n\nThis patch fixes the issue by explicitly setting `devlink_rate-\u0026gt;parent`\nto NULL after notifying the driver, thus fulfilling the function\u0026apos;s\ndocumented behavior for all rate objects.\n\n[1]\nrepro steps:\necho 1 \u0026gt; /sys/bus/netdevsim/new_device\ndevlink dev eswitch set netdevsim/netdevsim1 mode switchdev\necho 1 \u0026gt; /sys/bus/netdevsim/devices/netdevsim1/sriov_numvfs\ndevlink port function rate add netdevsim/netdevsim1/test_node\ndevlink port function rate set netdevsim/netdevsim1/128 parent test_node\necho 1 \u0026gt; /sys/bus/netdevsim/del_device\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 8 PID: 1530 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 8 UID: 0 PID: 1530 Comm: bash Not tainted 6.18.0-rc4+ #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.0-0-gd239552ce722-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n __nsim_dev_port_del+0x6c/0x70 [netdevsim]\n nsim_dev_reload_destroy+0x11c/0x140 [netdevsim]\n nsim_drv_remove+0x2b/0xb0 [netdevsim]\n device_release_driver_internal+0x194/0x1f0\n bus_remove_device+0xc6/0x130\n device_del+0x159/0x3c0\n device_unregister+0x1a/0x60\n del_device_store+0x111/0x170 [netdevsim]\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x55/0x10f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\n[2]\ndevlink dev eswitch set pci/0000:08:00.0 mode switchdev\ndevlink port add pci/0000:08:00.0 flavour pcisf pfnum 0 sfnum 1000\ndevlink port function rate add pci/0000:08:00.0/group1\ndevlink port function rate set pci/0000:08:00.0/32768 parent group1\nmodprobe -r mlx5_ib mlx5_fwctl mlx5_core\n\ndmesg:\nrefcount_t: decrement hit 0; leaking memory.\nWARNING: CPU: 7 PID: 16151 at lib/refcount.c:31 refcount_warn_saturate+0x42/0xe0\nCPU: 7 UID: 0 PID: 16151 Comm: bash Not tainted 6.17.0-rc7_for_upstream_min_debug_2025_10_02_12_44 #1 NONE\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\nRIP: 0010:refcount_warn_saturate+0x42/0xe0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n devl_rate_leaf_destroy+0x8d/0x90\n mlx5_esw_offloads_devlink_port_unregister+0x33/0x60 [mlx5_core]\n mlx5_esw_offloads_unload_rep+0x3f/0x50 [mlx5_core]\n mlx5_eswitch_unload_sf_vport+0x40/0x90 [mlx5_core]\n mlx5_sf_esw_event+0xc4/0x120 [mlx5_core]\n notifier_call_chain+0x33/0xa0\n blocking_notifier_call_chain+0x3b/0x50\n mlx5_eswitch_disable_locked+0x50/0x110 [mlx5_core]\n mlx5_eswitch_disable+0x63/0x90 [mlx5_core]\n mlx5_unload+0x1d/0x170 [mlx5_core]\n mlx5_uninit_one+0xa2/0x130 [mlx5_core]\n remove_one+0x78/0xd0 [mlx5_core]\n pci_device_remove+0x39/0xa0\n device_release_driver_internal+0x194/0x1f0\n unbind_store+0x99/0xa0\n kernfs_fop_write_iter+0x12e/0x1e0\n vfs_write+0x215/0x3d0\n ksys_write+0x5f/0xd0\n do_syscall_64+0x53/0x1f0\n entry_SYSCALL_64_after_hwframe+0x4b/0x53(CVE-2025-40251)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfs/proc: fix uaf in proc_readdir_de()\n\nPde is erased from subdir rbtree through rb_erase(), but not set the node\nto EMPTY, which may result in uaf access.  We should use RB_CLEAR_NODE()\nset the erased node to EMPTY, then pde_subdir_next() will return NULL to\navoid uaf access.\n\nWe found an uaf issue while using stress-ng testing, need to run testcase\ngetdent and tun in the same time.  The steps of the issue is as follows:\n\n1) use getdent to traverse dir /proc/pid/net/dev_snmp6/, and current\n   pde is tun3;\n\n2) in the [time windows] unregister netdevice tun3 and tun2, and erase\n   them from rbtree.  erase tun3 first, and then erase tun2.  the\n   pde(tun2) will be released to slab;\n\n3) continue to getdent process, then pde_subdir_next() will return\n   pde(tun2) which is released, it will case uaf access.\n\nCPU 0                                      |    CPU 1\n-------------------------------------------------------------------------\ntraverse dir /proc/pid/net/dev_snmp6/      |   unregister_netdevice(tun-\u0026gt;dev)   //tun3 tun2\nsys_getdents64()                           |\n  iterate_dir()                            |\n    proc_readdir()                         |\n      proc_readdir_de()                    |     snmp6_unregister_dev()\n        pde_get(de);                       |       proc_remove()\n        read_unlock(\u0026amp;proc_subdir_lock);    |         remove_proc_subtree()\n                                           |           write_lock(\u0026amp;proc_subdir_lock);\n        [time window]                      |           rb_erase(\u0026amp;root-\u0026gt;subdir_node, \u0026amp;parent-\u0026gt;subdir);\n                                           |           write_unlock(\u0026amp;proc_subdir_lock);\n        read_lock(\u0026amp;proc_subdir_lock);      |\n        next = pde_subdir_next(de);        |\n        pde_put(de);                       |\n        de = next;    //UAF                |\n\nrbtree of dev_snmp6\n                        |\n                    pde(tun3)\n                     /    \\\n                  NULL  pde(tun2)(CVE-2025-40271)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/secretmem: fix use-after-free race in fault handler\n\nWhen a page fault occurs in a secret memory file created with\n`memfd_secret(2)`, the kernel will allocate a new folio for it, mark the\nunderlying page as not-present in the direct map, and add it to the file\nmapping.\n\nIf two tasks cause a fault in the same page concurrently, both could end\nup allocating a folio and removing the page from the direct map, but only\none would succeed in adding the folio to the file mapping.  The task that\nfailed undoes the effects of its attempt by (a) freeing the folio again\nand (b) putting the page back into the direct map.  However, by doing\nthese two operations in this order, the page becomes available to the\nallocator again before it is placed back in the direct mapping.\n\nIf another task attempts to allocate the page between (a) and (b), and the\nkernel tries to access it via the direct map, it would result in a\nsupervisor not-present page fault.\n\nFix the ordering to restore the direct map before the folio is freed.(CVE-2025-40272)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: Validate command header size against SVGA_CMD_MAX_DATASIZE\n\nThis data originates from userspace and is used in buffer offset\ncalculations which could potentially overflow causing an out-of-bounds\naccess.(CVE-2025-40277)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: MGMT: Fix OOB access in parse_adv_monitor_pattern()\n\nIn the parse_adv_monitor_pattern() function, the value of\nthe \u0026apos;length\u0026apos; variable is currently limited to HCI_MAX_EXT_AD_LENGTH(251).\nThe size of the \u0026apos;value\u0026apos; array in the mgmt_adv_pattern structure is 31.\nIf the value of \u0026apos;pattern[i].length\u0026apos; is set in the user space\nand exceeds 31, the \u0026apos;patterns[i].value\u0026apos; array can be accessed\nout of bound when copied.\n\nIncreasing the size of the \u0026apos;value\u0026apos; array in\nthe \u0026apos;mgmt_adv_pattern\u0026apos; structure will break the userspace.\nConsidering this, and to avoid OOB access revert the limits for \u0026apos;offset\u0026apos;\nand \u0026apos;length\u0026apos; back to the value of HCI_MAX_AD_LENGTH.\n\nFound by InfoTeCS on behalf of Linux Verification Center\n(linuxtesting.org) with SVACE.(CVE-2025-40294)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_event: validate skb length for unknown CC opcode\n\nIn hci_cmd_complete_evt(), if the command complete event has an unknown\nopcode, we assume the first byte of the remaining skb-\u0026gt;data contains the\nreturn status. However, parameter data has previously been pulled in\nhci_event_func(), which may leave the skb empty. If so, using skb-\u0026gt;data[0]\nfor the return status uses un-init memory.\n\nThe fix is to check skb-\u0026gt;len before using skb-\u0026gt;data.(CVE-2025-40301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: bcsp: receive data only if registered\n\nCurrently, bcsp_recv() can be called even when the BCSP protocol has not\nbeen registered. This leads to a NULL pointer dereference, as shown in\nthe following stack trace:\n\n    KASAN: null-ptr-deref in range [0x0000000000000108-0x000000000000010f]\n    RIP: 0010:bcsp_recv+0x13d/0x1740 drivers/bluetooth/hci_bcsp.c:590\n    Call Trace:\n     \u0026lt;TASK\u0026gt;\n     hci_uart_tty_receive+0x194/0x220 drivers/bluetooth/hci_ldisc.c:627\n     tiocsti+0x23c/0x2c0 drivers/tty/tty_io.c:2290\n     tty_ioctl+0x626/0xde0 drivers/tty/tty_io.c:2706\n     vfs_ioctl fs/ioctl.c:51 [inline]\n     __do_sys_ioctl fs/ioctl.c:907 [inline]\n     __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893\n     do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n     do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94\n     entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nTo prevent this, ensure that the HCI_UART_REGISTERED flag is set before\nprocessing received data. If the protocol is not registered, return\n-EUNATCH.(CVE-2025-40308)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: hci_sync: fix race in hci_cmd_sync_dequeue_once\n\nhci_cmd_sync_dequeue_once() does lookup and then cancel\nthe entry under two separate lock sections. Meanwhile,\nhci_cmd_sync_work() can also delete the same entry,\nleading to double list_del() and \u0026quot;UAF\u0026quot;.\n\nFix this by holding cmd_sync_work_lock across both\nlookup and cancel, so that the entry cannot be removed\nconcurrently.(CVE-2025-40318)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfutex: Don\u0026apos;t leak robust_list pointer on exec race\n\nsys_get_robust_list() and compat_get_robust_list() use ptrace_may_access()\nto check if the calling task is allowed to access another task\u0026apos;s\nrobust_list pointer. This check is racy against a concurrent exec() in the\ntarget process.\n\nDuring exec(), a task may transition from a non-privileged binary to a\nprivileged one (e.g., setuid binary) and its credentials/memory mappings\nmay change. If get_robust_list() performs ptrace_may_access() before\nthis transition, it may erroneously allow access to sensitive information\nafter the target becomes privileged.\n\nA racy access allows an attacker to exploit a window during which\nptrace_may_access() passes before a target process transitions to a\nprivileged state via exec().\n\nFor example, consider a non-privileged task T that is about to execute a\nsetuid-root binary. An attacker task A calls get_robust_list(T) while T\nis still unprivileged. Since ptrace_may_access() checks permissions\nbased on current credentials, it succeeds. However, if T begins exec\nimmediately afterwards, it becomes privileged and may change its memory\nmappings. Because get_robust_list() proceeds to access T-\u0026gt;robust_list\nwithout synchronizing with exec() it may read user-space pointers from a\nnow-privileged process.\n\nThis violates the intended post-exec access restrictions and could\nexpose sensitive memory addresses or be used as a primitive in a larger\nexploit chain. Consequently, the race can lead to unauthorized\ndisclosure of information across privilege boundaries and poses a\npotential security risk.\n\nTake a read lock on signal-\u0026gt;exec_update_lock prior to invoking\nptrace_may_access() and accessing the robust_list/compat_robust_list.\nThis ensures that the target task\u0026apos;s exec state remains stable during the\ncheck, allowing for consistent and synchronized validation of\ncredentials.(CVE-2025-40341)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-fc: use lock accessing port_state and rport state\n\nnvme_fc_unregister_remote removes the remote port on a lport object at\nany point in time when there is no active association. This races with\nwith the reconnect logic, because nvme_fc_create_association is not\ntaking a lock to check the port_state and atomically increase the\nactive count on the rport.(CVE-2025-40342)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: avoid scheduling association deletion twice\n\nWhen forcefully shutting down a port via the configfs interface,\nnvmet_port_subsys_drop_link() first calls nvmet_port_del_ctrls() and\nthen nvmet_disable_port(). Both functions will eventually schedule all\nremaining associations for deletion.\n\nThe current implementation checks whether an association is about to be\nremoved, but only after the work item has already been scheduled. As a\nresult, it is possible for the first scheduled work item to free all\nresources, and then for the same work item to be scheduled again for\ndeletion.\n\nBecause the association list is an RCU list, it is not possible to take\na lock and remove the list entry directly, so it cannot be looked up\nagain. Instead, a flag (terminating) must be used to determine whether\nthe association is already in the process of being deleted.(CVE-2025-40343)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\narch_topology: Fix incorrect error check in topology_parse_cpu_capacity()\n\nFix incorrect use of PTR_ERR_OR_ZERO() in topology_parse_cpu_capacity()\nwhich causes the code to proceed with NULL clock pointers. The current\nlogic uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both\nvalid pointers and NULL, leading to potential NULL pointer dereference\nin clk_get_rate().\n\nPer include/linux/err.h documentation, PTR_ERR_OR_ZERO(ptr) returns:\n\u0026quot;The error code within @ptr if it is an error pointer; 0 otherwise.\u0026quot;\n\nThis means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL\npointers. Therefore !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed)\nwhen cpu_clk is either valid or NULL, causing clk_get_rate(NULL) to be\ncalled when of_clk_get() returns NULL.\n\nReplace with !IS_ERR_OR_NULL(cpu_clk) which only proceeds for valid\npointers, preventing potential NULL pointer dereference in clk_get_rate().(CVE-2025-40346)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nhfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n\nThe syzbot reported issue in hfsplus_delete_cat():\n\n[   70.682285][ T9333] =====================================================\n[   70.682943][ T9333] BUG: KMSAN: uninit-value in hfsplus_subfolders_dec+0x1d7/0x220\n[   70.683640][ T9333]  hfsplus_subfolders_dec+0x1d7/0x220\n[   70.684141][ T9333]  hfsplus_delete_cat+0x105d/0x12b0\n[   70.684621][ T9333]  hfsplus_rmdir+0x13d/0x310\n[   70.685048][ T9333]  vfs_rmdir+0x5ba/0x810\n[   70.685447][ T9333]  do_rmdir+0x964/0xea0\n[   70.685833][ T9333]  __x64_sys_rmdir+0x71/0xb0\n[   70.686260][ T9333]  x64_sys_call+0xcd8/0x3cf0\n[   70.686695][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.687119][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.687646][ T9333]\n[   70.687856][ T9333] Uninit was stored to memory at:\n[   70.688311][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.688779][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.689231][ T9333]  hfsplus_mknod+0x27f/0x600\n[   70.689730][ T9333]  hfsplus_mkdir+0x5a/0x70\n[   70.690146][ T9333]  vfs_mkdir+0x483/0x7a0\n[   70.690545][ T9333]  do_mkdirat+0x3f2/0xd30\n[   70.690944][ T9333]  __x64_sys_mkdir+0x9a/0xf0\n[   70.691380][ T9333]  x64_sys_call+0x2f89/0x3cf0\n[   70.691816][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.692229][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.692773][ T9333]\n[   70.692990][ T9333] Uninit was stored to memory at:\n[   70.693469][ T9333]  hfsplus_subfolders_inc+0x1c2/0x1d0\n[   70.693960][ T9333]  hfsplus_create_cat+0x148e/0x1800\n[   70.694438][ T9333]  hfsplus_fill_super+0x21c1/0x2700\n[   70.694911][ T9333]  mount_bdev+0x37b/0x530\n[   70.695320][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.695729][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.696167][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.696588][ T9333]  do_new_mount+0x73e/0x1630\n[   70.697013][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.697425][ T9333]  __se_sys_mount+0x733/0x830\n[   70.697857][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.698269][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.698704][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.699117][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.699730][ T9333]\n[   70.699946][ T9333] Uninit was created at:\n[   70.700378][ T9333]  __alloc_pages_noprof+0x714/0xe60\n[   70.700843][ T9333]  alloc_pages_mpol_noprof+0x2a2/0x9b0\n[   70.701331][ T9333]  alloc_pages_noprof+0xf8/0x1f0\n[   70.701774][ T9333]  allocate_slab+0x30e/0x1390\n[   70.702194][ T9333]  ___slab_alloc+0x1049/0x33a0\n[   70.702635][ T9333]  kmem_cache_alloc_lru_noprof+0x5ce/0xb20\n[   70.703153][ T9333]  hfsplus_alloc_inode+0x5a/0xd0\n[   70.703598][ T9333]  alloc_inode+0x82/0x490\n[   70.703984][ T9333]  iget_locked+0x22e/0x1320\n[   70.704428][ T9333]  hfsplus_iget+0x5c/0xba0\n[   70.704827][ T9333]  hfsplus_btree_open+0x135/0x1dd0\n[   70.705291][ T9333]  hfsplus_fill_super+0x1132/0x2700\n[   70.705776][ T9333]  mount_bdev+0x37b/0x530\n[   70.706171][ T9333]  hfsplus_mount+0x4d/0x60\n[   70.706579][ T9333]  legacy_get_tree+0x113/0x2c0\n[   70.707019][ T9333]  vfs_get_tree+0xb3/0x5c0\n[   70.707444][ T9333]  do_new_mount+0x73e/0x1630\n[   70.707865][ T9333]  path_mount+0x6e3/0x1eb0\n[   70.708270][ T9333]  __se_sys_mount+0x733/0x830\n[   70.708711][ T9333]  __x64_sys_mount+0xe4/0x150\n[   70.709158][ T9333]  x64_sys_call+0x2691/0x3cf0\n[   70.709630][ T9333]  do_syscall_64+0xd9/0x1d0\n[   70.710053][ T9333]  entry_SYSCALL_64_after_hwframe+0x77/0x7f\n[   70.710611][ T9333]\n[   70.710842][ T9333] CPU: 3 UID: 0 PID: 9333 Comm: repro Not tainted 6.12.0-rc6-dirty #17\n[   70.711568][ T9333] Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n[   70.712490][ T9333] =====================================================\n[   70.713085][ T9333] Disabling lock debugging due to kernel taint\n[   70.713618][ T9333] Kernel panic - not syncing: kmsan.panic set ...\n[   70.714159][ T9333] \n---truncated---(CVE-2025-40351)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nriscv: stacktrace: Disable KASAN checks for non-current tasks\n\nUnwinding the stack of a task other than current, KASAN would report\n\u0026quot;BUG: KASAN: out-of-bounds in walk_stackframe+0x41c/0x460\u0026quot;\n\nThere is a same issue on x86 and has been resolved by the commit\n84936118bdf3 (\u0026quot;x86/unwind: Disable KASAN checks for non-current tasks\u0026quot;)\nThe solution could be applied to RISC-V too.\n\nThis patch also can solve the issue:\nhttps://seclists.org/oss-sec/2025/q4/23\n\n[(CVE-2025-40358)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nperf/x86/intel: Fix KASAN global-out-of-bounds warning\n\nWhen running \u0026quot;perf mem record\u0026quot; command on CWF, the below KASAN\nglobal-out-of-bounds warning is seen.\n\n  ==================================================================\n  BUG: KASAN: global-out-of-bounds in cmt_latency_data+0x176/0x1b0\n  Read of size 4 at addr ffffffffb721d000 by task dtlb/9850\n\n  Call Trace:\n\n   kasan_report+0xb8/0xf0\n   cmt_latency_data+0x176/0x1b0\n   setup_arch_pebs_sample_data+0xf49/0x2560\n   intel_pmu_drain_arch_pebs+0x577/0xb00\n   handle_pmi_common+0x6c4/0xc80\n\nThe issue is caused by below code in __grt_latency_data(). The code\ntries to access x86_hybrid_pmu structure which doesn\u0026apos;t exist on\nnon-hybrid platform like CWF.\n\n        WARN_ON_ONCE(hybrid_pmu(event-\u0026gt;pmu)-\u0026gt;pmu_type == hybrid_big)\n\nSo add is_hybrid() check before calling this WARN_ON_ONCE to fix the\nglobal-out-of-bounds access issue.(CVE-2025-40359)\n\nRejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.(CVE-2025-40361)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Ensure XFD state on signal delivery\n\nSean reported [1] the following splat when running KVM tests:\n\n   WARNING: CPU: 232 PID: 15391 at xfd_validate_state+0x65/0x70\n   Call Trace:\n    \u0026lt;TASK\u0026gt;\n    fpu__clear_user_states+0x9c/0x100\n    arch_do_signal_or_restart+0x142/0x210\n    exit_to_user_mode_loop+0x55/0x100\n    do_syscall_64+0x205/0x2c0\n    entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nChao further identified [2] a reproducible scenario involving signal\ndelivery: a non-AMX task is preempted by an AMX-enabled task which\nmodifies the XFD MSR.\n\nWhen the non-AMX task resumes and reloads XSTATE with init values,\na warning is triggered due to a mismatch between fpstate::xfd and the\nCPU\u0026apos;s current XFD state. fpu__clear_user_states() does not currently\nre-synchronize the XFD state after such preemption.\n\nInvoke xfd_update_state() which detects and corrects the mismatch if\nthere is a dynamic feature.\n\nThis also benefits the sigreturn path, as fpu__restore_sig() may call\nfpu__clear_user_states() when the sigframe is inaccessible.\n\n[ dhansen: minor changelog munging ](CVE-2025-68171)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\u0026quot;ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\u0026quot;) and commit 42ea22e754ba (\u0026quot;ftrace: Add cond_resched() to\nftrace_graph_set_hash()\u0026quot;).\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.(CVE-2025-68173)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\namd/amdkfd: enhance kfd process check in switch partition\n\ncurrent switch partition only check if kfd_processes_table is empty.\nkfd_prcesses_table entry is deleted in kfd_process_notifier_release, but\nkfd_process tear down is in kfd_process_wq_release.\n\nconsider two processes:\n\nProcess A (workqueue) -\u0026gt; kfd_process_wq_release -\u0026gt; Access kfd_node member\nProcess B switch partition -\u0026gt; amdgpu_xcp_pre_partition_switch -\u0026gt; amdgpu_amdkfd_device_fini_sw\n-\u0026gt; kfd_node tear down.\n\nProcess A and B may trigger a race as shown in dmesg log.\n\nThis patch is to resolve the race by adding an atomic kfd_process counter\nkfd_processes_count, it increment as create kfd process, decrement as\nfinish kfd_process_wq_release.\n\nv2: Put kfd_processes_count per kfd_dev, move decrement to kfd_process_destroy_pdds\nand bug fix. (Philip Yang)\n\n[3966658.307702] divide error: 0000 [#1] SMP NOPTI\n[3966658.350818]  i10nm_edac\n[3966658.356318] CPU: 124 PID: 38435 Comm: kworker/124:0 Kdump: loaded Tainted\n[3966658.356890] Workqueue: kfd_process_wq kfd_process_wq_release [amdgpu]\n[3966658.362839]  nfit\n[3966658.366457] RIP: 0010:kfd_get_num_sdma_engines+0x17/0x40 [amdgpu]\n[3966658.366460] Code: 00 00 e9 ac 81 02 00 66 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 48 8b 4f 08 48 8b b7 00 01 00 00 8b 81 58 26 03 00 99 \u0026lt;f7\u0026gt; be b8 01 00 00 80 b9 70 2e 00 00 00 74 0b 83 f8 02 ba 02 00 00\n[3966658.380967]  x86_pkg_temp_thermal\n[3966658.391529] RSP: 0018:ffffc900a0edfdd8 EFLAGS: 00010246\n[3966658.391531] RAX: 0000000000000008 RBX: ffff8974e593b800 RCX: ffff888645900000\n[3966658.391531] RDX: 0000000000000000 RSI: ffff888129154400 RDI: ffff888129151c00\n[3966658.391532] RBP: ffff8883ad79d400 R08: 0000000000000000 R09: ffff8890d2750af4\n[3966658.391532] R10: 0000000000000018 R11: 0000000000000018 R12: 0000000000000000\n[3966658.391533] R13: ffff8883ad79d400 R14: ffffe87ff662ba00 R15: ffff8974e593b800\n[3966658.391533] FS:  0000000000000000(0000) GS:ffff88fe7f600000(0000) knlGS:0000000000000000\n[3966658.391534] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[3966658.391534] CR2: 0000000000d71000 CR3: 000000dd0e970004 CR4: 0000000002770ee0\n[3966658.391535] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\n[3966658.391535] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400\n[3966658.391536] PKRU: 55555554\n[3966658.391536] Call Trace:\n[3966658.391674]  deallocate_sdma_queue+0x38/0xa0 [amdgpu]\n[3966658.391762]  process_termination_cpsch+0x1ed/0x480 [amdgpu]\n[3966658.399754]  intel_powerclamp\n[3966658.402831]  kfd_process_dequeue_from_all_devices+0x5b/0xc0 [amdgpu]\n[3966658.402908]  kfd_process_wq_release+0x1a/0x1a0 [amdgpu]\n[3966658.410516]  coretemp\n[3966658.434016]  process_one_work+0x1ad/0x380\n[3966658.434021]  worker_thread+0x49/0x310\n[3966658.438963]  kvm_intel\n[3966658.446041]  ? process_one_work+0x380/0x380\n[3966658.446045]  kthread+0x118/0x140\n[3966658.446047]  ? __kthread_bind_mask+0x60/0x60\n[3966658.446050]  ret_from_fork+0x1f/0x30\n[3966658.446053] Modules linked in: kpatch_20765354(OEK)\n[3966658.455310]  kvm\n[3966658.464534]  mptcp_diag xsk_diag raw_diag unix_diag af_packet_diag netlink_diag udp_diag act_pedit act_mirred act_vlan cls_flower kpatch_21951273(OEK) kpatch_18424469(OEK) kpatch_19749756(OEK)\n[3966658.473462]  idxd_mdev\n[3966658.482306]  kpatch_17971294(OEK) sch_ingress xt_conntrack amdgpu(OE) amdxcp(OE) amddrm_buddy(OE) amd_sched(OE) amdttm(OE) amdkcl(OE) intel_ifs iptable_mangle tcm_loop target_core_pscsi tcp_diag target_core_file inet_diag target_core_iblock target_core_user target_core_mod coldpgs kpatch_18383292(OEK) ip6table_nat ip6table_filter ip6_tables ip_set_hash_ipportip ip_set_hash_ipportnet ip_set_hash_ipport ip_set_bitmap_port xt_comment iptable_nat nf_nat iptable_filter ip_tables ip_set ip_vs_sh ip_vs_wrr ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 sn_core_odd(OE) i40e overlay binfmt_misc tun bonding(OE) aisqos(OE) aisqo\n---truncated---(CVE-2025-68174)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI: cadence: Check for the existence of cdns_pcie::ops before using it\n\ncdns_pcie::ops might not be populated by all the Cadence glue drivers. This\nis going to be true for the upcoming Sophgo platform which doesn\u0026apos;t set the\nops.\n\nHence, add a check to prevent NULL pointer dereference.\n\n[mani: reworded subject and description](CVE-2025-68176)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntcp: use dst_dev_rcu() in tcp_fastopen_active_disable_ofo_check()\n\nUse RCU to avoid a pair of atomic operations and a potential\nUAF on dst_dev()-\u0026gt;flags.(CVE-2025-68188)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Add bpf_prog_run_data_pointers()\n\nsyzbot found that cls_bpf_classify() is able to change\ntc_skb_cb(skb)-\u0026gt;drop_reason triggering a warning in sk_skb_reason_drop().\n\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 __sk_skb_reason_drop net/core/skbuff.c:1189 [inline]\nWARNING: CPU: 0 PID: 5965 at net/core/skbuff.c:1192 sk_skb_reason_drop+0x76/0x170 net/core/skbuff.c:1214\n\nstruct tc_skb_cb has been added in commit ec624fe740b4 (\u0026quot;net/sched:\nExtend qdisc control block with tc control block\u0026quot;), which added a wrong\ninteraction with db58ba459202 (\u0026quot;bpf: wire in data and data_end for\ncls_act_bpf\u0026quot;).\n\ndrop_reason was added later.\n\nAdd bpf_prog_run_data_pointers() helper to save/restore the net_sched\nstorage colliding with BPF data_meta/data_end.(CVE-2025-68200)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nft_ct: add seqadj extension for natted connections\n\nSequence adjustment may be required for FTP traffic with PASV/EPSV modes.\ndue to need to re-write packet payload (IP, port) on the ftp control\nconnection. This can require changes to the TCP length and expected\nseq / ack_seq.\n\nThe easiest way to reproduce this issue is with PASV mode.\nExample ruleset:\ntable inet ftp_nat {\n        ct helper ftp_helper {\n                type \u0026quot;ftp\u0026quot; protocol tcp\n                l3proto inet\n        }\n\n        chain prerouting {\n                type filter hook prerouting priority 0; policy accept;\n                tcp dport 21 ct state new ct helper set \u0026quot;ftp_helper\u0026quot;\n        }\n}\ntable ip nat {\n        chain prerouting {\n                type nat hook prerouting priority -100; policy accept;\n                tcp dport 21 dnat ip prefix to ip daddr map {\n\t\t\t192.168.100.1 : 192.168.13.2/32 }\n        }\n\n        chain postrouting {\n                type nat hook postrouting priority 100 ; policy accept;\n                tcp sport 21 snat ip prefix to ip saddr map {\n\t\t\t192.168.13.2 : 192.168.100.1/32 }\n        }\n}\n\nNote that the ftp helper gets assigned *after* the dnat setup.\n\nThe inverse (nat after helper assign) is handled by an existing\ncheck in nf_nat_setup_info() and will not show the problem.\n\nTopoloy:\n\n +-------------------+     +----------------------------------+\n | FTP: 192.168.13.2 | \u0026lt;-\u0026gt; | NAT: 192.168.13.3, 192.168.100.1 |\n +-------------------+     +----------------------------------+\n                                      |\n                         +-----------------------+\n                         | Client: 192.168.100.2 |\n                         +-----------------------+\n\nftp nat changes do not work as expected in this case:\nConnected to 192.168.100.1.\n[..]\nftp\u0026gt; epsv\nEPSV/EPRT on IPv4 off.\nftp\u0026gt; ls\n227 Entering passive mode (192,168,100,1,209,129).\n421 Service not available, remote server has closed connection.\n\nKernel logs:\nMissing nfct_seqadj_ext_add() setup call\nWARNING: CPU: 1 PID: 0 at net/netfilter/nf_conntrack_seqadj.c:41\n[..]\n __nf_nat_mangle_tcp_packet+0x100/0x160 [nf_nat]\n nf_nat_ftp+0x142/0x280 [nf_nat_ftp]\n help+0x4d1/0x880 [nf_conntrack_ftp]\n nf_confirm+0x122/0x2e0 [nf_conntrack]\n nf_hook_slow+0x3c/0xb0\n ..\n\nFix this by adding the required extension when a conntrack helper is assigned\nto a connection that has a nat binding.(CVE-2025-68206)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: account for current allocated stack depth in widen_imprecise_scalars()\n\nThe usage pattern for widen_imprecise_scalars() looks as follows:\n\n    prev_st = find_prev_entry(env, ...);\n    queued_st = push_stack(...);\n    widen_imprecise_scalars(env, prev_st, queued_st);\n\nWhere prev_st is an ancestor of the queued_st in the explored states\ntree. This ancestor is not guaranteed to have same allocated stack\ndepth as queued_st. E.g. in the following case:\n\n    def main():\n      for i in 1..2:\n        foo(i)        // same callsite, differnt param\n\n    def foo(i):\n      if i == 1:\n        use 128 bytes of stack\n      iterator based loop\n\nHere, for a second \u0026apos;foo\u0026apos; call prev_st-\u0026gt;allocated_stack is 128,\nwhile queued_st-\u0026gt;allocated_stack is much smaller.\nwiden_imprecise_scalars() needs to take this into account and avoid\naccessing bpf_verifier_state-\u0026gt;frame[*]-\u0026gt;stack out of bounds.(CVE-2025-68208)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnouveau/firmware: Add missing kfree() of nvkm_falcon_fw::boot\n\nnvkm_falcon_fw::boot is allocated, but no one frees it. This causes a\nkmemleak warning.\n\nMake sure this data is deallocated.(CVE-2025-68235)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: SVM: Don\u0026apos;t skip unrelated instruction if INT3/INTO is replaced\n\nWhen re-injecting a soft interrupt from an INT3, INT0, or (select) INTn\ninstruction, discard the exception and retry the instruction if the code\nstream is changed (e.g. by a different vCPU) between when the CPU\nexecutes the instruction and when KVM decodes the instruction to get the\nnext RIP.\n\nAs effectively predicted by commit 6ef88d6e36c2 (\u0026quot;KVM: SVM: Re-inject\nINT3/INTO instead of retrying the instruction\u0026quot;), failure to verify that\nthe correct INTn instruction was decoded can effectively clobber guest\nstate due to decoding the wrong instruction and thus specifying the\nwrong next RIP.\n\nThe bug most often manifests as \u0026quot;Oops: int3\u0026quot; panics on static branch\nchecks in Linux guests.  Enabling or disabling a static branch in Linux\nuses the kernel\u0026apos;s \u0026quot;text poke\u0026quot; code patching mechanism.  To modify code\nwhile other CPUs may be executing that code, Linux (temporarily)\nreplaces the first byte of the original instruction with an int3 (opcode\n0xcc), then patches in the new code stream except for the first byte,\nand finally replaces the int3 with the first byte of the new code\nstream.  If a CPU hits the int3, i.e. executes the code while it\u0026apos;s being\nmodified, then the guest kernel must look up the RIP to determine how to\nhandle the #BP, e.g. by emulating the new instruction.  If the RIP is\nincorrect, then this lookup fails and the guest kernel panics.\n\nThe bug reproduces almost instantly by hacking the guest kernel to\nrepeatedly check a static branch[1] while running a drgn script[2] on\nthe host to constantly swap out the memory containing the guest\u0026apos;s TSS.\n\n[1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a\n[2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b(CVE-2025-68259)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: add i_data_sem protection in ext4_destroy_inline_data_nolock()\n\nFix a race between inline data destruction and block mapping.\n\nThe function ext4_destroy_inline_data_nolock() changes the inode data\nlayout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS.\nAt the same time, another thread may execute ext4_map_blocks(), which\ntests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks()\nor ext4_ind_map_blocks().\n\nWithout i_data_sem protection, ext4_ind_map_blocks() may receive inode\nwith EXT4_INODE_EXTENTS flag and triggering assert.\n\nkernel BUG at fs/ext4/indirect.c:546!\nEXT4-fs (loop2): unmounting filesystem.\ninvalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nRIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546\n\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681\n _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822\n ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124\n ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255\n ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000\n generic_perform_write+0x259/0x5d0 mm/filemap.c:3846\n ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285\n ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679\n call_write_iter include/linux/fs.h:2271 [inline]\n do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735\n do_iter_write+0x186/0x710 fs/read_write.c:861\n vfs_iter_write+0x70/0xa0 fs/read_write.c:902\n iter_file_splice_write+0x73b/0xc90 fs/splice.c:685\n do_splice_from fs/splice.c:763 [inline]\n direct_splice_actor+0x10f/0x170 fs/splice.c:950\n splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896\n do_splice_direct+0x1a9/0x280 fs/splice.c:1002\n do_sendfile+0xb13/0x12c0 fs/read_write.c:1255\n __do_sys_sendfile64 fs/read_write.c:1323 [inline]\n __se_sys_sendfile64 fs/read_write.c:1309 [inline]\n __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309\n do_syscall_x64 arch/x86/entry/common.c:51 [inline]\n do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81\n entry_SYSCALL_64_after_hwframe+0x6e/0xd8(CVE-2025-68261)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\next4: refresh inline data size before write operations\n\nThe cached ei-\u0026gt;i_inline_size can become stale between the initial size\ncheck and when ext4_update_inline_data()/ext4_create_inline_data() use\nit. Although ext4_get_max_inline_size() reads the correct value at the\ntime of the check, concurrent xattr operations can modify i_inline_size\nbefore ext4_write_lock_xattr() is acquired.\n\nThis causes ext4_update_inline_data() and ext4_create_inline_data() to\nwork with stale capacity values, leading to a BUG_ON() crash in\next4_write_inline_data():\n\n  kernel BUG at fs/ext4/inline.c:1331!\n  BUG_ON(pos + len \u0026gt; EXT4_I(inode)-\u0026gt;i_inline_size);\n\nThe race window:\n1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct)\n2. Size check passes for 50-byte write\n3. [Another thread adds xattr, i_inline_size changes to 40]\n4. ext4_write_lock_xattr() acquires lock\n5. ext4_update_inline_data() uses stale i_inline_size = 60\n6. Attempts to write 50 bytes but only 40 bytes actually available\n7. BUG_ON() triggers\n\nFix this by recalculating i_inline_size via ext4_find_inline_data_nolock()\nimmediately after acquiring xattr_sem. This ensures ext4_update_inline_data()\nand ext4_create_inline_data() work with current values that are protected\nfrom concurrent modifications.\n\nThis is similar to commit a54c4613dac1 (\u0026quot;ext4: fix race writing to an\ninline_data file while its xattrs are changing\u0026quot;) which fixed i_inline_off\nstaleness. This patch addresses the related i_inline_size staleness issue.(CVE-2025-68264)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme: fix admin request_queue lifetime\n\nThe namespaces can access the controller\u0026apos;s admin request_queue, and\nstale references on the namespaces may exist after tearing down the\ncontroller. Ensure the admin request_queue is active by moving the\ncontroller\u0026apos;s \u0026apos;put\u0026apos; to after all controller references have been released\nto ensure no one is can access the request_queue. This fixes a reported\nuse-after-free bug:\n\n  BUG: KASAN: slab-use-after-free in blk_queue_enter+0x41c/0x4a0\n  Read of size 8 at addr ffff88c0a53819f8 by task nvme/3287\n  CPU: 67 UID: 0 PID: 3287 Comm: nvme Tainted: G            E       6.13.2-ga1582f1a031e #15\n  Tainted: [E]=UNSIGNED_MODULE\n  Hardware name: Jabil /EGS 2S MB1, BIOS 1.00 06/18/2025\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   dump_stack_lvl+0x4f/0x60\n   print_report+0xc4/0x620\n   ? _raw_spin_lock_irqsave+0x70/0xb0\n   ? _raw_read_unlock_irqrestore+0x30/0x30\n   ? blk_queue_enter+0x41c/0x4a0\n   kasan_report+0xab/0xe0\n   ? blk_queue_enter+0x41c/0x4a0\n   blk_queue_enter+0x41c/0x4a0\n   ? __irq_work_queue_local+0x75/0x1d0\n   ? blk_queue_start_drain+0x70/0x70\n   ? irq_work_queue+0x18/0x20\n   ? vprintk_emit.part.0+0x1cc/0x350\n   ? wake_up_klogd_work_func+0x60/0x60\n   blk_mq_alloc_request+0x2b7/0x6b0\n   ? __blk_mq_alloc_requests+0x1060/0x1060\n   ? __switch_to+0x5b7/0x1060\n   nvme_submit_user_cmd+0xa9/0x330\n   nvme_user_cmd.isra.0+0x240/0x3f0\n   ? force_sigsegv+0xe0/0xe0\n   ? nvme_user_cmd64+0x400/0x400\n   ? vfs_fileattr_set+0x9b0/0x9b0\n   ? cgroup_update_frozen_flag+0x24/0x1c0\n   ? cgroup_leave_frozen+0x204/0x330\n   ? nvme_ioctl+0x7c/0x2c0\n   blkdev_ioctl+0x1a8/0x4d0\n   ? blkdev_common_ioctl+0x1930/0x1930\n   ? fdget+0x54/0x380\n   __x64_sys_ioctl+0x129/0x190\n   do_syscall_64+0x5b/0x160\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n  RIP: 0033:0x7f765f703b0b\n  Code: ff ff ff 85 c0 79 9b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 8b 0d dd 52 0f 00 f7 d8 64 89 01 48\n  RSP: 002b:00007ffe2cefe808 EFLAGS: 00000202 ORIG_RAX: 0000000000000010\n  RAX: ffffffffffffffda RBX: 00007ffe2cefe860 RCX: 00007f765f703b0b\n  RDX: 00007ffe2cefe860 RSI: 00000000c0484e41 RDI: 0000000000000003\n  RBP: 0000000000000000 R08: 0000000000000003 R09: 0000000000000000\n  R10: 00007f765f611d50 R11: 0000000000000202 R12: 0000000000000003\n  R13: 00000000c0484e41 R14: 0000000000000001 R15: 00007ffe2cefea60\n   \u0026lt;/TASK\u0026gt;(CVE-2025-68265)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nceph: fix crash in process_v2_sparse_read() for encrypted directories\n\nThe crash in process_v2_sparse_read() for fscrypt-encrypted directories\nhas been reported. Issue takes place for Ceph msgr2 protocol in secure\nmode. It can be reproduced by the steps:\n\nsudo mount -t ceph :/ /mnt/cephfs/ -o name=admin,fs=cephfs,ms_mode=secure\n\n(1) mkdir /mnt/cephfs/fscrypt-test-3\n(2) cp area_decrypted.tar /mnt/cephfs/fscrypt-test-3\n(3) fscrypt encrypt --source=raw_key --key=./my.key /mnt/cephfs/fscrypt-test-3\n(4) fscrypt lock /mnt/cephfs/fscrypt-test-3\n(5) fscrypt unlock --key=my.key /mnt/cephfs/fscrypt-test-3\n(6) cat /mnt/cephfs/fscrypt-test-3/area_decrypted.tar\n(7) Issue has been triggered\n\n[  408.072247] ------------[ cut here ]------------\n[  408.072251] WARNING: CPU: 1 PID: 392 at net/ceph/messenger_v2.c:865\nceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072267] Modules linked in: intel_rapl_msr intel_rapl_common\nintel_uncore_frequency_common intel_pmc_core pmt_telemetry pmt_discovery\npmt_class intel_pmc_ssram_telemetry intel_vsec kvm_intel joydev kvm irqbypass\npolyval_clmulni ghash_clmulni_intel aesni_intel rapl input_leds psmouse\nserio_raw i2c_piix4 vga16fb bochs vgastate i2c_smbus floppy mac_hid qemu_fw_cfg\npata_acpi sch_fq_codel rbd msr parport_pc ppdev lp parport efi_pstore\n[  408.072304] CPU: 1 UID: 0 PID: 392 Comm: kworker/1:3 Not tainted 6.17.0-rc7+\n[  408.072307] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS\n1.17.0-5.fc42 04/01/2014\n[  408.072310] Workqueue: ceph-msgr ceph_con_workfn\n[  408.072314] RIP: 0010:ceph_con_v2_try_read+0x4b39/0x72f0\n[  408.072317] Code: c7 c1 20 f0 d4 ae 50 31 d2 48 c7 c6 60 27 d5 ae 48 c7 c7 f8\n8e 6f b0 68 60 38 d5 ae e8 00 47 61 fe 48 83 c4 18 e9 ac fc ff ff \u0026lt;0f\u0026gt; 0b e9 06\nfe ff ff 4c 8b 9d 98 fd ff ff 0f 84 64 e7 ff ff 89 85\n[  408.072319] RSP: 0018:ffff88811c3e7a30 EFLAGS: 00010246\n[  408.072322] RAX: ffffed1024874c6f RBX: ffffea00042c2b40 RCX: 0000000000000f38\n[  408.072324] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  408.072325] RBP: ffff88811c3e7ca8 R08: 0000000000000000 R09: 00000000000000c8\n[  408.072326] R10: 00000000000000c8 R11: 0000000000000000 R12: 00000000000000c8\n[  408.072327] R13: dffffc0000000000 R14: ffff8881243a6030 R15: 0000000000003000\n[  408.072329] FS:  0000000000000000(0000) GS:ffff88823eadf000(0000)\nknlGS:0000000000000000\n[  408.072331] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  408.072332] CR2: 000000c0003c6000 CR3: 000000010c106005 CR4: 0000000000772ef0\n[  408.072336] PKRU: 55555554\n[  408.072337] Call Trace:\n[  408.072338]  \u0026lt;TASK\u0026gt;\n[  408.072340]  ? sched_clock_noinstr+0x9/0x10\n[  408.072344]  ? __pfx_ceph_con_v2_try_read+0x10/0x10\n[  408.072347]  ? _raw_spin_unlock+0xe/0x40\n[  408.072349]  ? finish_task_switch.isra.0+0x15d/0x830\n[  408.072353]  ? __kasan_check_write+0x14/0x30\n[  408.072357]  ? mutex_lock+0x84/0xe0\n[  408.072359]  ? __pfx_mutex_lock+0x10/0x10\n[  408.072361]  ceph_con_workfn+0x27e/0x10e0\n[  408.072364]  ? metric_delayed_work+0x311/0x2c50\n[  408.072367]  process_one_work+0x611/0xe20\n[  408.072371]  ? __kasan_check_write+0x14/0x30\n[  408.072373]  worker_thread+0x7e3/0x1580\n[  408.072375]  ? __pfx__raw_spin_lock_irqsave+0x10/0x10\n[  408.072378]  ? __pfx_worker_thread+0x10/0x10\n[  408.072381]  kthread+0x381/0x7a0\n[  408.072383]  ? __pfx__raw_spin_lock_irq+0x10/0x10\n[  408.072385]  ? __pfx_kthread+0x10/0x10\n[  408.072387]  ? __kasan_check_write+0x14/0x30\n[  408.072389]  ? recalc_sigpending+0x160/0x220\n[  408.072392]  ? _raw_spin_unlock_irq+0xe/0x50\n[  408.072394]  ? calculate_sigpending+0x78/0xb0\n[  408.072395]  ? __pfx_kthread+0x10/0x10\n[  408.072397]  ret_from_fork+0x2b6/0x380\n[  408.072400]  ? __pfx_kthread+0x10/0x10\n[  408.072402]  ret_from_fork_asm+0x1a/0x30\n[  408.072406]  \u0026lt;/TASK\u0026gt;\n[  408.072407] ---[ end trace 0000000000000000 ]---\n[  408.072418] Oops: general protection fault, probably for non-canonical\naddress 0xdffffc00000000\n---truncated---(CVE-2025-68297)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: atlantic: fix fragment overflow handling in RX path\n\nThe atlantic driver can receive packets with more than MAX_SKB_FRAGS (17)\nfragments when handling large multi-descriptor packets. This causes an\nout-of-bounds write in skb_add_rx_frag_netmem() leading to kernel panic.\n\nThe issue occurs because the driver doesn\u0026apos;t check the total number of\nfragments before calling skb_add_rx_frag(). When a packet requires more\nthan MAX_SKB_FRAGS fragments, the fragment index exceeds the array bounds.\n\nFix by assuming there will be an extra frag if buff-\u0026gt;len \u0026gt; AQ_CFG_RX_HDR_SIZE,\nthen all fragments are accounted for. And reusing the existing check to\nprevent the overflow earlier in the code path.\n\nThis crash occurred in production with an Aquantia AQC113 10G NIC.\n\nStack trace from production environment:\n```\nRIP: 0010:skb_add_rx_frag_netmem+0x29/0xd0\nCode: 90 f3 0f 1e fa 0f 1f 44 00 00 48 89 f8 41 89\nca 48 89 d7 48 63 ce 8b 90 c0 00 00 00 48 c1 e1 04 48 01 ca 48 03 90\nc8 00 00 00 \u0026lt;48\u0026gt; 89 7a 30 44 89 52 3c 44 89 42 38 40 f6 c7 01 75 74 48\n89 fa 83\nRSP: 0018:ffffa9bec02a8d50 EFLAGS: 00010287\nRAX: ffff925b22e80a00 RBX: ffff925ad38d2700 RCX:\nfffffffe0a0c8000\nRDX: ffff9258ea95bac0 RSI: ffff925ae0a0c800 RDI:\n0000000000037a40\nRBP: 0000000000000024 R08: 0000000000000000 R09:\n0000000000000021\nR10: 0000000000000848 R11: 0000000000000000 R12:\nffffa9bec02a8e24\nR13: ffff925ad8615570 R14: 0000000000000000 R15:\nffff925b22e80a00\nFS: 0000000000000000(0000)\nGS:ffff925e47880000(0000) knlGS:0000000000000000\nCS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffff9258ea95baf0 CR3: 0000000166022004 CR4:\n0000000000f72ef0\nPKRU: 55555554\nCall Trace:\n\u0026lt;IRQ\u0026gt;\naq_ring_rx_clean+0x175/0xe60 [atlantic]\n? aq_ring_rx_clean+0x14d/0xe60 [atlantic]\n? aq_ring_tx_clean+0xdf/0x190 [atlantic]\n? kmem_cache_free+0x348/0x450\n? aq_vec_poll+0x81/0x1d0 [atlantic]\n? __napi_poll+0x28/0x1c0\n? net_rx_action+0x337/0x420\n```\n\nChanges in v4:\n- Add Fixes: tag to satisfy patch validation requirements.\n\nChanges in v3:\n- Fix by assuming there will be an extra frag if buff-\u0026gt;len \u0026gt; AQ_CFG_RX_HDR_SIZE,\n  then all fragments are accounted for.(CVE-2025-68301)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nPCI/AER: Fix NULL pointer access by aer_info\n\nThe kzalloc(GFP_KERNEL) may return NULL, so all accesses to aer_info-\u0026gt;xxx\nwill result in kernel panic. Fix it.(CVE-2025-68309)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer\n\nWhen a UAS device is unplugged during data transfer, there is\na probability of a system panic occurring. The root cause is\nan access to an invalid memory address during URB callback handling.\nSpecifically, this happens when the dma_direct_unmap_sg() function\nis called within the usb_hcd_unmap_urb_for_dma() interface, but the\nsg-\u0026gt;dma_address field is 0 and the sg data structure has already been\nfreed.\n\nThe SCSI driver sends transfer commands by invoking uas_queuecommand_lck()\nin uas.c, using the uas_submit_urbs() function to submit requests to USB.\nWithin the uas_submit_urbs() implementation, three URBs (sense_urb,\ndata_urb, and cmd_urb) are sequentially submitted. Device removal may\noccur at any point during uas_submit_urbs execution, which may result\nin URB submission failure. However, some URBs might have been successfully\nsubmitted before the failure, and uas_submit_urbs will return the -ENODEV\nerror code in this case. The current error handling directly calls\nscsi_done(). In the SCSI driver, this eventually triggers scsi_complete()\nto invoke scsi_end_request() for releasing the sgtable. The successfully\nsubmitted URBs, when being unlinked to giveback, call\nusb_hcd_unmap_urb_for_dma() in hcd.c, leading to exceptions during sg\nunmapping operations since the sg data structure has already been freed.\n\nThis patch modifies the error condition check in the uas_submit_urbs()\nfunction. When a UAS device is removed but one or more URBs have already\nbeen successfully submitted to USB, it avoids immediately invoking\nscsi_done() and save the cmnd to devinfo-\u0026gt;cmnd array. If the successfully\nsubmitted URBs is completed before devinfo-\u0026gt;resetting being set, then\nthe scsi_done() function will be called within uas_try_complete() after\nall pending URB operations are finalized. Otherwise, the scsi_done()\nfunction will be called within uas_zap_pending(), which is executed after\nusb_kill_anchored_urbs().\n\nThe error handling only takes effect when uas_queuecommand_lck() calls\nuas_submit_urbs() and returns the error value -ENODEV . In this case,\nthe device is disconnected, and the flow proceeds to uas_disconnect(),\nwhere uas_zap_pending() is invoked to call uas_try_complete().(CVE-2025-68331)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\njbd2: avoid bug_on in jbd2_journal_get_create_access() when file system corrupted\n\nThere\u0026apos;s issue when file system corrupted:\n------------[ cut here ]------------\nkernel BUG at fs/jbd2/transaction.c:1289!\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 5 UID: 0 PID: 2031 Comm: mkdir Not tainted 6.18.0-rc1-next\nRIP: 0010:jbd2_journal_get_create_access+0x3b6/0x4d0\nRSP: 0018:ffff888117aafa30 EFLAGS: 00010202\nRAX: 0000000000000000 RBX: ffff88811a86b000 RCX: ffffffff89a63534\nRDX: 1ffff110200ec602 RSI: 0000000000000004 RDI: ffff888100763010\nRBP: ffff888100763000 R08: 0000000000000001 R09: ffff888100763028\nR10: 0000000000000003 R11: 0000000000000000 R12: 0000000000000000\nR13: ffff88812c432000 R14: ffff88812c608000 R15: ffff888120bfc000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007f91d6970c99 CR3: 00000001159c4000 CR4: 00000000000006f0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __ext4_journal_get_create_access+0x42/0x170\n ext4_getblk+0x319/0x6f0\n ext4_bread+0x11/0x100\n ext4_append+0x1e6/0x4a0\n ext4_init_new_dir+0x145/0x1d0\n ext4_mkdir+0x326/0x920\n vfs_mkdir+0x45c/0x740\n do_mkdirat+0x234/0x2f0\n __x64_sys_mkdir+0xd6/0x120\n do_syscall_64+0x5f/0xfa0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nThe above issue occurs with us in errors=continue mode when accompanied by\nstorage failures. There have been many inconsistencies in the file system\ndata.\nIn the case of file system data inconsistency, for example, if the block\nbitmap of a referenced block is not set, it can lead to the situation where\na block being committed is allocated and used again. As a result, the\nfollowing condition will not be satisfied then trigger BUG_ON. Of course,\nit is entirely possible to construct a problematic image that can trigger\nthis BUG_ON through specific operations. In fact, I have constructed such\nan image and easily reproduced this issue.\nTherefore, J_ASSERT() holds true only under ideal conditions, but it may\nnot necessarily be satisfied in exceptional scenarios. Using J_ASSERT()\ndirectly in abnormal situations would cause the system to crash, which is\nclearly not what we want. So here we directly trigger a JBD abort instead\nof immediately invoking BUG_ON.(CVE-2025-68337)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSv4/pNFS: Clear NFS_INO_LAYOUTCOMMIT in pnfs_mark_layout_stateid_invalid\n\nFixes a crash when layout is null during this call stack:\n\nwrite_inode\n    -\u0026gt; nfs4_write_inode\n        -\u0026gt; pnfs_layoutcommit_inode\n\npnfs_set_layoutcommit relies on the lseg refcount to keep the layout\naround. Need to clear NFS_INO_LAYOUTCOMMIT otherwise we might attempt\nto reference a null layout.(CVE-2025-68349)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nregulator: core: Protect regulator_supply_alias_list with regulator_list_mutex\n\nregulator_supply_alias_list was accessed without any locking in\nregulator_supply_alias(), regulator_register_supply_alias(), and\nregulator_unregister_supply_alias(). Concurrent registration,\nunregistration and lookups can race, leading to:\n\n1 use-after-free if an alias entry is removed while being read,\n2 duplicate entries when two threads register the same alias,\n3 inconsistent alias mappings observed by consumers.\n\nProtect all traversals, insertions and deletions on\nregulator_supply_alias_list with the existing regulator_list_mutex.(CVE-2025-68354)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ngfs2: Prevent recursive memory reclaim\n\nFunction new_inode() returns a new inode with inode-\u0026gt;i_mapping-\u0026gt;gfp_mask\nset to GFP_HIGHUSER_MOVABLE.  This value includes the __GFP_FS flag, so\nallocations in that address space can recurse into filesystem memory\nreclaim.  We don\u0026apos;t want that to happen because it can consume a\nsignificant amount of stack memory.\n\nWorse than that is that it can also deadlock: for example, in several\nplaces, gfs2_unstuff_dinode() is called inside filesystem transactions.\nThis calls filemap_grab_folio(), which can allocate a new folio, which\ncan trigger memory reclaim.  If memory reclaim recurses into the\nfilesystem and starts another transaction, a deadlock will ensue.\n\nTo fix these kinds of problems, prevent memory reclaim from recursing\ninto filesystem code by making sure that the gfp_mask of inode address\nspaces doesn\u0026apos;t include __GFP_FS.\n\nThe \u0026quot;meta\u0026quot; and resource group address spaces were already using GFP_NOFS\nas their gfp_mask (which doesn\u0026apos;t include __GFP_FS).  The default value\nof GFP_HIGHUSER_MOVABLE is less restrictive than GFP_NOFS, though.  To\navoid being overly limiting, use the default value and only knock off\nthe __GFP_FS flag.  I\u0026apos;m not sure if this will actually make a\ndifference, but it also shouldn\u0026apos;t hurt.\n\nThis patch is loosely based on commit ad22c7a043c2 (\u0026quot;xfs: prevent stack\noverflows from page cache allocation\u0026quot;).\n\nFixes xfstest generic/273.(CVE-2025-68356)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtl818x: rtl8187: Fix potential buffer underflow in rtl8187_rx_cb()\n\nThe rtl8187_rx_cb() calculates the rx descriptor header address\nby subtracting its size from the skb tail pointer.\nHowever, it does not validate if the received packet\n(skb-\u0026gt;len from urb-\u0026gt;actual_length) is large enough to contain this\nheader.\n\nIf a truncated packet is received, this will lead to a buffer\nunderflow, reading memory before the start of the skb data area,\nand causing a kernel panic.\n\nAdd length checks for both rtl8187 and rtl8187b descriptor headers\nbefore attempting to access them, dropping the packet cleanly if the\ncheck fails.(CVE-2025-68362)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Check skb-\u0026gt;transport_header is set in bpf_skb_check_mtu\n\nThe bpf_skb_check_mtu helper needs to use skb-\u0026gt;transport_header when\nthe BPF_MTU_CHK_SEGS flag is used:\n\n\tbpf_skb_check_mtu(skb, ifindex, \u0026amp;mtu_len, 0, BPF_MTU_CHK_SEGS)\n\nThe transport_header is not always set. There is a WARN_ON_ONCE\nreport when CONFIG_DEBUG_NET is enabled + skb-\u0026gt;gso_size is set +\nbpf_prog_test_run is used:\n\nWARNING: CPU: 1 PID: 2216 at ./include/linux/skbuff.h:3071\n skb_gso_validate_network_len\n bpf_skb_check_mtu\n bpf_prog_3920e25740a41171_tc_chk_segs_flag # A test in the next patch\n bpf_test_run\n bpf_prog_test_run_skb\n\nFor a normal ingress skb (not test_run), skb_reset_transport_header\nis performed but there is plan to avoid setting it as described in\ncommit 2170a1f09148 (\u0026quot;net: no longer reset transport_header in __netif_receive_skb_core()\u0026quot;).\n\nThis patch fixes the bpf helper by checking\nskb_transport_header_was_set(). The check is done just before\nskb-\u0026gt;transport_header is used, to avoid breaking the existing bpf prog.\nThe WARN_ON_ONCE is limited to bpf_prog_test_run, so targeting bpf-next.(CVE-2025-68363)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncoresight: ETR: Fix ETR buffer use-after-free issue\n\nWhen ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed\nand enabled again, currently sysfs_buf will point to the newly\nallocated memory(buf_new) and free the old memory(buf_old). But the\netr_buf that is being used by the ETR remains pointed to buf_old, not\nupdated to buf_new. In this case, it will result in a memory\nuse-after-free issue.\n\nFix this by checking ETR\u0026apos;s mode before updating and releasing buf_old,\nif the mode is CS_MODE_SYSFS, then skip updating and releasing it.(CVE-2025-68376)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Fix stackmap overflow check in __bpf_get_stackid()\n\nSyzkaller reported a KASAN slab-out-of-bounds write in __bpf_get_stackid()\nwhen copying stack trace data. The issue occurs when the perf trace\n contains more stack entries than the stack map bucket can hold,\n leading to an out-of-bounds write in the bucket\u0026apos;s data array.(CVE-2025-68378)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: asymmetric_keys - prevent overflow in asymmetric_key_generate_id\n\nUse check_add_overflow() to guard against potential integer overflows\nwhen adding the binary blob lengths and the size of an asymmetric_key_id\nstructure and return ERR_PTR(-EOVERFLOW) accordingly. This prevents a\npossible buffer overflow when copying data from potentially malicious\nX.509 certificate fields that can be arbitrarily large, such as ASN.1\nINTEGER serial numbers, issuer names, etc.(CVE-2025-68724)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Do not let BPF test infra emit invalid GSO types to stack\n\nYinhao et al. reported that their fuzzer tool was able to trigger a\nskb_warn_bad_offload() from netif_skb_features() -\u0026gt; gso_features_check().\nWhen a BPF program - triggered via BPF test infra - pushes the packet\nto the loopback device via bpf_clone_redirect() then mentioned offload\nwarning can be seen. GSO-related features are then rightfully disabled.\n\nWe get into this situation due to convert___skb_to_skb() setting\ngso_segs and gso_size but not gso_type. Technically, it makes sense\nthat this warning triggers since the GSO properties are malformed due\nto the gso_type. Potentially, the gso_type could be marked non-trustworthy\nthrough setting it at least to SKB_GSO_DODGY without any other specific\nassumptions, but that also feels wrong given we should not go further\ninto the GSO engine in the first place.\n\nThe checks were added in 121d57af308d (\u0026quot;gso: validate gso_type in GSO\nhandlers\u0026quot;) because there were malicious (syzbot) senders that combine\na protocol with a non-matching gso_type. If we would want to drop such\npackets, gso_features_check() currently only returns feature flags via\nnetif_skb_features(), so one location for potentially dropping such skbs\ncould be validate_xmit_unreadable_skb(), but then otoh it would be\nan additional check in the fast-path for a very corner case. Given\nbpf_clone_redirect() is the only place where BPF test infra could emit\nsuch packets, lets reject them right there.(CVE-2025-68725)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nisdn: mISDN: hfcsusb: fix memory leak in hfcsusb_probe()\n\nIn hfcsusb_probe(), the memory allocated for ctrl_urb gets leaked when\nsetup_instance() fails with an error code. Fix that by freeing the urb\nbefore freeing the hw structure. Also change the error paths to use the\ngoto ladder style.\n\nCompile tested only. Issue found using a prototype static analysis tool.(CVE-2025-68734)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Fix improper freeing of purex item\n\nIn qla2xxx_process_purls_iocb(), an item is allocated via\nqla27xx_copy_multiple_pkt(), which internally calls\nqla24xx_alloc_purex_item().\n\nThe qla24xx_alloc_purex_item() function may return a pre-allocated item\nfrom a per-adapter pool for small allocations, instead of dynamically\nallocating memory with kzalloc().\n\nAn error handling path in qla2xxx_process_purls_iocb() incorrectly uses\nkfree() to release the item. If the item was from the pre-allocated\npool, calling kfree() on it is a bug that can lead to memory corruption.\n\nFix this by using the correct deallocation function,\nqla24xx_free_purex_item(), which properly handles both dynamically\nallocated and pre-allocated items.(CVE-2025-68741)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Free special fields when update [lru_,]percpu_hash maps\n\nAs [lru_,]percpu_hash maps support BPF_KPTR_{REF,PERCPU}, missing\ncalls to \u0026apos;bpf_obj_free_fields()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos; could cause the\nmemory referenced by BPF_KPTR_{REF,PERCPU} fields to be held until the\nmap gets freed.\n\nFix this by calling \u0026apos;bpf_obj_free_fields()\u0026apos; after\n\u0026apos;copy_map_value[,_long]()\u0026apos; in \u0026apos;pcpu_copy_value()\u0026apos;.(CVE-2025-68744)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Clear cmds after chip reset\n\nCommit aefed3e5548f (\u0026quot;scsi: qla2xxx: target: Fix offline port handling\nand host reset handling\u0026quot;) caused two problems:\n\n1. Commands sent to FW, after chip reset got stuck and never freed as FW\n   is not going to respond to them anymore.\n\n2. BUG_ON(cmd-\u0026gt;sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a\n   (\u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot;)\n   attempted to fix this, but introduced another bug under different\n   circumstances when two different CPUs were racing to call\n   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in\n   dma_unmap_sg_attrs().\n\nSo revert \u0026quot;scsi: qla2xxx: Fix missed DMA unmap for aborted commands\u0026quot; and\npartially revert \u0026quot;scsi: qla2xxx: target: Fix offline port handling and\nhost reset handling\u0026quot; at __qla2x00_abort_all_cmds.(CVE-2025-68745)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nblock: Use RCU in blk_mq_[un]quiesce_tagset() instead of set-\u0026gt;tag_list_lock\n\nblk_mq_{add,del}_queue_tag_set() functions add and remove queues from\ntagset, the functions make sure that tagset and queues are marked as\nshared when two or more queues are attached to the same tagset.\nInitially a tagset starts as unshared and when the number of added\nqueues reaches two, blk_mq_add_queue_tag_set() marks it as shared along\nwith all the queues attached to it. When the number of attached queues\ndrops to 1 blk_mq_del_queue_tag_set() need to mark both the tagset and\nthe remaining queues as unshared.\n\nBoth functions need to freeze current queues in tagset before setting on\nunsetting BLK_MQ_F_TAG_QUEUE_SHARED flag. While doing so, both functions\nhold set-\u0026gt;tag_list_lock mutex, which makes sense as we do not want\nqueues to be added or deleted in the process. This used to work fine\nuntil commit 98d81f0df70c (\u0026quot;nvme: use blk_mq_[un]quiesce_tagset\u0026quot;)\nmade the nvme driver quiesce tagset instead of quiscing individual\nqueues. blk_mq_quiesce_tagset() does the job and quiesce the queues in\nset-\u0026gt;tag_list while holding set-\u0026gt;tag_list_lock also.\n\nThis results in deadlock between two threads with these stacktraces:\n\n  __schedule+0x47c/0xbb0\n  ? timerqueue_add+0x66/0xb0\n  schedule+0x1c/0xa0\n  schedule_preempt_disabled+0xa/0x10\n  __mutex_lock.constprop.0+0x271/0x600\n  blk_mq_quiesce_tagset+0x25/0xc0\n  nvme_dev_disable+0x9c/0x250\n  nvme_timeout+0x1fc/0x520\n  blk_mq_handle_expired+0x5c/0x90\n  bt_iter+0x7e/0x90\n  blk_mq_queue_tag_busy_iter+0x27e/0x550\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __blk_mq_complete_request_remote+0x10/0x10\n  ? __call_rcu_common.constprop.0+0x1c0/0x210\n  blk_mq_timeout_work+0x12d/0x170\n  process_one_work+0x12e/0x2d0\n  worker_thread+0x288/0x3a0\n  ? rescuer_thread+0x480/0x480\n  kthread+0xb8/0xe0\n  ? kthread_park+0x80/0x80\n  ret_from_fork+0x2d/0x50\n  ? kthread_park+0x80/0x80\n  ret_from_fork_asm+0x11/0x20\n\n  __schedule+0x47c/0xbb0\n  ? xas_find+0x161/0x1a0\n  schedule+0x1c/0xa0\n  blk_mq_freeze_queue_wait+0x3d/0x70\n  ? destroy_sched_domains_rcu+0x30/0x30\n  blk_mq_update_tag_set_shared+0x44/0x80\n  blk_mq_exit_queue+0x141/0x150\n  del_gendisk+0x25a/0x2d0\n  nvme_ns_remove+0xc9/0x170\n  nvme_remove_namespaces+0xc7/0x100\n  nvme_remove+0x62/0x150\n  pci_device_remove+0x23/0x60\n  device_release_driver_internal+0x159/0x200\n  unbind_store+0x99/0xa0\n  kernfs_fop_write_iter+0x112/0x1e0\n  vfs_write+0x2b1/0x3d0\n  ksys_write+0x4e/0xb0\n  do_syscall_64+0x5b/0x160\n  entry_SYSCALL_64_after_hwframe+0x4b/0x53\n\nThe top stacktrace is showing nvme_timeout() called to handle nvme\ncommand timeout. timeout handler is trying to disable the controller and\nas a first step, it needs to blk_mq_quiesce_tagset() to tell blk-mq not\nto call queue callback handlers. The thread is stuck waiting for\nset-\u0026gt;tag_list_lock as it tries to walk the queues in set-\u0026gt;tag_list.\n\nThe lock is held by the second thread in the bottom stack which is\nwaiting for one of queues to be frozen. The queue usage counter will\ndrop to zero after nvme_timeout() finishes, and this will not happen\nbecause the thread will wait for this mutex forever.\n\nGiven that [un]quiescing queue is an operation that does not need to\nsleep, update blk_mq_[un]quiesce_tagset() to use RCU instead of taking\nset-\u0026gt;tag_list_lock, update blk_mq_{add,del}_queue_tag_set() to use RCU\nsafe list operations. Also, delete INIT_LIST_HEAD(\u0026amp;q-\u0026gt;tag_set_list)\nin blk_mq_del_queue_tag_set() because we can not re-initialize it while\nthe list is being traversed under RCU. The deleted queue will not be\nadded/deleted to/from a tagset and it will be freed in blk_free_queue()\nafter the end of RCU grace period.(CVE-2025-68756)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsched/deadline: only set free_cpus for online runqueues\n\nCommit 16b269436b72 (\u0026quot;sched/deadline: Modify cpudl::free_cpus\nto reflect rd-\u0026gt;online\u0026quot;) introduced the cpudl_set/clear_freecpu\nfunctions to allow the cpu_dl::free_cpus mask to be manipulated\nby the deadline scheduler class rq_on/offline callbacks so the\nmask would also reflect this state.\n\nCommit 9659e1eeee28 (\u0026quot;sched/deadline: Remove cpu_active_mask\nfrom cpudl_find()\u0026quot;) removed the check of the cpu_active_mask to\nsave some processing on the premise that the cpudl::free_cpus\nmask already reflected the runqueue online state.\n\nUnfortunately, there are cases where it is possible for the\ncpudl_clear function to set the free_cpus bit for a CPU when the\ndeadline runqueue is offline. When this occurs while a CPU is\nconnected to the default root domain the flag may retain the bad\nstate after the CPU has been unplugged. Later, a different CPU\nthat is transitioning through the default root domain may push a\ndeadline task to the powered down CPU when cpudl_find sees its\nfree_cpus bit is set. If this happens the task will not have the\nopportunity to run.\n\nOne example is outlined here:\nhttps://lore.kernel.org/lkml/(CVE-2025-68780)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: Reset t_task_cdb pointer in error case\n\nIf allocation of cmd-\u0026gt;t_task_cdb fails, it remains NULL but is later\ndereferenced in the \u0026apos;err\u0026apos; path.\n\nIn case of error, reset NULL t_task_cdb value to point at the default\nfixed-size buffer.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.(CVE-2025-68782)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\niomap: adjust read range correctly for non-block-aligned positions\n\niomap_adjust_read_range() assumes that the position and length passed in\nare block-aligned. This is not always the case however, as shown in the\nsyzbot generated case for erofs. This causes too many bytes to be\nskipped for uptodate blocks, which results in returning the incorrect\nposition and length to read in. If all the blocks are uptodate, this\nunderflows length and returns a position beyond the folio.\n\nFix the calculation to also take into account the block offset when\ncalculating how many bytes can be skipped for uptodate blocks.(CVE-2025-68794)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: NFSv4 file creation neglects setting ACL\n\nAn NFSv4 client that sets an ACL with a named principal during file\ncreation retrieves the ACL afterwards, and finds that it is only a\ndefault ACL (based on the mode bits) and not the ACL that was\nrequested during file creation. This violates RFC 8881 section\n6.4.1.3: \u0026quot;the ACL attribute is set as given\u0026quot;.\n\nThe issue occurs in nfsd_create_setattr(), which calls\nnfsd_attrs_valid() to determine whether to call nfsd_setattr().\nHowever, nfsd_attrs_valid() checks only for iattr changes and\nsecurity labels, but not POSIX ACLs. When only an ACL is present,\nthe function returns false, nfsd_setattr() is skipped, and the\nPOSIX ACL is never applied to the inode.\n\nSubsequently, when the client retrieves the ACL, the server finds\nno POSIX ACL on the inode and returns one generated from the file\u0026apos;s\nmode bits rather than returning the originally-specified ACL.(CVE-2025-68803)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring: fix filename leak in __io_openat_prep()\n\n __io_openat_prep() allocates a struct filename using getname(). However,\nfor the condition of the file being installed in the fixed file table as\nwell as having O_CLOEXEC flag set, the function returns early. At that\npoint, the request doesn\u0026apos;t have REQ_F_NEED_CLEANUP flag set. Due to this,\nthe memory for the newly allocated struct filename is not cleaned up,\ncausing a memory leak.\n\nFix this by setting the REQ_F_NEED_CLEANUP for the request just after the\nsuccessful getname() call, so that when the request is torn down, the\nfilename will be cleaned up, along with other resources needing cleanup.(CVE-2025-68814)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5: fw_tracer, Validate format string parameters\n\nAdd validation for format string parameters in the firmware tracer to\nprevent potential security vulnerabilities and crashes from malformed\nformat strings received from firmware.\n\nThe firmware tracer receives format strings from the device firmware and\nuses them to format trace messages. Without proper validation, bad\nfirmware could provide format strings with invalid format specifiers\n(e.g., %s, %p, %n) that could lead to crashes, or other undefined\nbehavior.\n\nAdd mlx5_tracer_validate_params() to validate that all format specifiers\nin trace strings are limited to safe integer/hex formats (%x, %d, %i,\n%u, %llx, %lx, etc.). Reject strings containing other format types that\ncould be used to access arbitrary memory or cause crashes.\nInvalid format strings are added to the trace output for visibility with\n\u0026quot;BAD_FORMAT: \u0026quot; prefix.(CVE-2025-68816)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: Revert \u0026quot;scsi: qla2xxx: Perform lockless command completion in abort path\u0026quot;\n\nThis reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9.\n\nThe commit being reverted added code to __qla2x00_abort_all_cmds() to\ncall sp-\u0026gt;done() without holding a spinlock.  But unlike the older code\nbelow it, this new code failed to check sp-\u0026gt;cmd_type and just assumed\nTYPE_SRB, which results in a jump to an invalid pointer in target-mode\nwith TYPE_TGT_CMD:\n\nqla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success\n  0000000009f7a79b\nqla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h\n  mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h.\nqla2xxx [0000:65:00.0]-d01e:8: -\u0026gt; fwdump no buffer\nqla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event\n  0x8002 occurred\nqla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery -\n  ha=0000000058183fda.\nBUG: kernel NULL pointer dereference, address: 0000000000000000\nPF: supervisor instruction fetch in kernel mode\nPF: error_code(0x0010) - not-present page\nPGD 0 P4D 0\nOops: 0010 [#1] SMP\nCPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G           O       6.1.133 #1\nHardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023\nRIP: 0010:0x0\nCode: Unable to access opcode bytes at 0xffffffffffffffd6.\nRSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206\nRAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000\nRDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0\nRBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045\nR10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40\nR13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400\nFS:  0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nCall Trace:\n \u0026lt;TASK\u0026gt;\n ? __die+0x4d/0x8b\n ? page_fault_oops+0x91/0x180\n ? trace_buffer_unlock_commit_regs+0x38/0x1a0\n ? exc_page_fault+0x391/0x5e0\n ? asm_exc_page_fault+0x22/0x30\n __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst]\n qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst]\n qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst]\n qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst]\n qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst]\n kthread+0xa8/0xd0\n \u0026lt;/TASK\u0026gt;\n\nThen commit 4475afa2646d (\u0026quot;scsi: qla2xxx: Complete command early within\nlock\u0026quot;) added the spinlock back, because not having the lock caused a\nrace and a crash.  But qla2x00_abort_srb() in the switch below already\nchecks for qla2x00_chip_is_down() and handles it the same way, so the\ncode above the switch is now redundant and still buggy in target-mode.\nRemove it.(CVE-2025-68818)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nshmem: fix recovery on rename failures\n\nmaple_tree insertions can fail if we are seriously short on memory;\nsimple_offset_rename() does not recover well if it runs into that.\nThe same goes for simple_offset_rename_exchange().\n\nMoreover, shmem_whiteout() expects that if it succeeds, the caller will\nprogress to d_move(), i.e. that shmem_rename2() won\u0026apos;t fail past the\nsuccessful call of shmem_whiteout().\n\nNot hard to fix, fortunately - mtree_store() can\u0026apos;t fail if the index we\nare trying to store into is already present in the tree as a singleton.\n\nFor simple_offset_rename_exchange() that\u0026apos;s enough - we just need to be\ncareful about the order of operations.\n\nFor simple_offset_rename() solution is to preinsert the target into the\ntree for new_dir; the rest can be done without any potentially failing\noperations.\n\nThat preinsertion has to be done in shmem_rename2() rather than in\nsimple_offset_rename() itself - otherwise we\u0026apos;d need to deal with the\npossibility of failure after successful shmem_whiteout().(CVE-2025-71072)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer\n\nWhen advancing the target expiration for the guest\u0026apos;s APIC timer in periodic\nmode, set the expiration to \u0026quot;now\u0026quot; if the target expiration is in the past\n(similar to what is done in update_target_expiration()).  Blindly adding\nthe period to the previous target expiration can result in KVM generating\na practically unbounded number of hrtimer IRQs due to programming an\nexpired timer over and over.  In extreme scenarios, e.g. if userspace\npauses/suspends a VM for an extended duration, this can even cause hard\nlockups in the host.\n\nCurrently, the bug only affects Intel CPUs when using the hypervisor timer\n(HV timer), a.k.a. the VMX preemption timer.  Unlike the software timer,\na.k.a. hrtimer, which KVM keeps running even on exits to userspace, the\nHV timer only runs while the guest is active.  As a result, if the vCPU\ndoes not run for an extended duration, there will be a huge gap between\nthe target expiration and the current time the vCPU resumes running.\nBecause the target expiration is incremented by only one period on each\ntimer expiration, this leads to a series of timer expirations occurring\nrapidly after the vCPU/VM resumes.\n\nMore critically, when the vCPU first triggers a periodic HV timer\nexpiration after resuming, advancing the expiration by only one period\nwill result in a target expiration in the past.  As a result, the delta\nmay be calculated as a negative value.  When the delta is converted into\nan absolute value (tscdeadline is an unsigned u64), the resulting value\ncan overflow what the HV timer is capable of programming.  I.e. the large\nvalue will exceed the VMX Preemption Timer\u0026apos;s maximum bit width of\ncpu_preemption_timer_multi + 32, and thus cause KVM to switch from the\nHV timer to the software timer (hrtimers).\n\nAfter switching to the software timer, periodic timer expiration callbacks\nmay be executed consecutively within a single clock interrupt handler,\nbecause hrtimers honors KVM\u0026apos;s request for an expiration in the past and\nimmediately re-invokes KVM\u0026apos;s callback after reprogramming.  And because\nthe interrupt handler runs with IRQs disabled, restarting KVM\u0026apos;s hrtimer\nover and over until the target expiration is advanced to \u0026quot;now\u0026quot; can result\nin a hard lockup.\n\nE.g. the following hard lockup was triggered in the host when running a\nWindows VM (only relevant because it used the APIC timer in periodic mode)\nafter resuming the VM from a long suspend (in the host).\n\n  NMI watchdog: Watchdog detected hard LOCKUP on cpu 45\n  ...\n  RIP: 0010:advance_periodic_target_expiration+0x4d/0x80 [kvm]\n  ...\n  RSP: 0018:ff4f88f5d98d8ef0 EFLAGS: 00000046\n  RAX: fff0103f91be678e RBX: fff0103f91be678e RCX: 00843a7d9e127bcc\n  RDX: 0000000000000002 RSI: 0052ca4003697505 RDI: ff440d5bfbdbd500\n  RBP: ff440d5956f99200 R08: ff2ff2a42deb6a84 R09: 000000000002a6c0\n  R10: 0122d794016332b3 R11: 0000000000000000 R12: ff440db1af39cfc0\n  R13: ff440db1af39cfc0 R14: ffffffffc0d4a560 R15: ff440db1af39d0f8\n  FS:  00007f04a6ffd700(0000) GS:ff440db1af380000(0000) knlGS:000000e38a3b8000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000d5651feff8 CR3: 000000684e038002 CR4: 0000000000773ee0\n  PKRU: 55555554\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   apic_timer_fn+0x31/0x50 [kvm]\n   __hrtimer_run_queues+0x100/0x280\n   hrtimer_interrupt+0x100/0x210\n   ? ttwu_do_wakeup+0x19/0x160\n   smp_apic_timer_interrupt+0x6a/0x130\n   apic_timer_interrupt+0xf/0x20\n   \u0026lt;/IRQ\u0026gt;\n\nMoreover, if the suspend duration of the virtual machine is not long enough\nto trigger a hard lockup in this scenario, since commit 98c25ead5eda\n(\u0026quot;KVM: VMX: Move preemption timer \u0026lt;=\u0026gt; hrtimer dance to common x86\u0026quot;), KVM\nwill continue using the software timer until the guest reprograms the APIC\ntimer in some way.  Since the periodic timer does not require frequent APIC\ntimer register programming, the guest may continue to use the software\ntimer in \n---truncated---(CVE-2025-71104)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make decode_pool() more resilient against corrupted osdmaps\n\nIf the osdmap is (maliciously) corrupted such that the encoded length\nof ceph_pg_pool envelope is less than what is expected for a particular\nencoding version, out-of-bounds reads may ensue because the only bounds\ncheck that is there is based on that length value.\n\nThis patch adds explicit bounds checks for each field that is decoded\nor skipped.(CVE-2025-71116)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ncrypto: seqiv - Do not use req-\u0026gt;iv after crypto_aead_encrypt\n\nAs soon as crypto_aead_encrypt is called, the underlying request\nmay be freed by an asynchronous completion.  Thus dereferencing\nreq-\u0026gt;iv after it returns is invalid.\n\nInstead of checking req-\u0026gt;iv against info, create a new variable\nunaligned_info and use it for that purpose instead.(CVE-2025-71131)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nKEYS: trusted: Fix a memory leak in tpm2_load_cmd\n\n\u0026apos;tpm2_load_cmd\u0026apos; allocates a tempoary blob indirectly via \u0026apos;tpm2_key_decode\u0026apos;\nbut it is not freed in the failure paths. Address this by wrapping the blob\ninto with a cleanup helper.(CVE-2025-71147)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nio_uring/poll: correctly handle io_poll_add() return value on update\n\nWhen the core of io_uring was updated to handle completions\nconsistently and with fixed return codes, the POLL_REMOVE opcode\nwith updates got slightly broken. If a POLL_ADD is pending and\nthen POLL_REMOVE is used to update the events of that request, if that\nupdate causes the POLL_ADD to now trigger, then that completion is lost\nand a CQE is never posted.\n\nAdditionally, ensure that if an update does cause an existing POLL_ADD\nto complete, that the completion value isn\u0026apos;t always overwritten with\n-ECANCELED. For that case, whatever io_poll_add() set the value to\nshould just be retained.(CVE-2025-71149)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksmbd: Fix refcount leak when invalid session is found on session lookup\n\nWhen a session is found but its state is not SMB2_SESSION_VALID, It\nindicates that no valid session was found, but it is missing to decrement\nthe reference count acquired by the session lookup, which results in\na reference count leak. This patch fixes the issue by explicitly calling\nksmbd_user_session_put to release the reference to the session.(CVE-2025-71150)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Don\u0026apos;t store mlx5e_priv in mlx5e_dev devlink priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails, mlx5e_priv in mlx5e_dev devlink private is used to\nreference the netdev and mdev associated with that struct. Instead,\nstore netdev directly into mlx5e_dev and get mdev from the containing\nmlx5_adev aux device structure.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000520\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 3 UID: 0 PID: 521 Comm: devlink Not tainted 6.18.0-rc5+ #117 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_remove+0x68/0x130\nRSP: 0018:ffffc900034838f0 EFLAGS: 00010246\nRAX: ffff88810283c380 RBX: ffff888101874400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000\nRBP: ffff888102d789c0 R08: ffff8881007137f0 R09: ffff888100264e10\nR10: ffffc90003483898 R11: ffffc900034838a0 R12: ffff888100d261a0\nR13: ffff888100d261a0 R14: ffff8881018749a0 R15: ffff888101874400\nFS:  00007f8565fea740(0000) GS:ffff88856a759000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000520 CR3: 000000010b11a004 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-22996)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec\n\nCommit efa56305908b (\u0026quot;nvmet-tcp: Fix a kernel panic when host sends an invalid H2C PDU length\u0026quot;)\nadded ttag bounds checking and data_offset\nvalidation in nvmet_tcp_handle_h2c_data_pdu(), but it did not validate\nwhether the command\u0026apos;s data structures (cmd-\u0026gt;req.sg and cmd-\u0026gt;iov) have\nbeen properly initialized before processing H2C_DATA PDUs.\n\nThe nvmet_tcp_build_pdu_iovec() function dereferences these pointers\nwithout NULL checks. This can be triggered by sending H2C_DATA PDU\nimmediately after the ICREQ/ICRESP handshake, before\nsending a CONNECT command or NVMe write command.\n\nAttack vectors that trigger NULL pointer dereferences:\n1. H2C_DATA PDU sent before CONNECT → both pointers NULL\n2. H2C_DATA PDU for READ command → cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n3. H2C_DATA PDU for uninitialized command slot → both pointers NULL\n\nThe fix validates both cmd-\u0026gt;req.sg and cmd-\u0026gt;iov before calling\nnvmet_tcp_build_pdu_iovec(). Both checks are required because:\n- Uninitialized commands: both NULL\n- READ commands: cmd-\u0026gt;req.sg allocated, cmd-\u0026gt;iov NULL\n- WRITE commands: both allocated(CVE-2026-22998)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Fix crash on profile change rollback failure\n\nmlx5e_netdev_change_profile can fail to attach a new profile and can\nfail to rollback to old profile, in such case, we could end up with a\ndangling netdev with a fully reset netdev_priv. A retry to change\nprofile, e.g. another attempt to call mlx5e_netdev_change_profile via\nswitchdev mode change, will crash trying to access the now NULL\npriv-\u0026gt;mdev.\n\nThis fix allows mlx5e_netdev_change_profile() to handle previous\nfailures and an empty priv, by not assuming priv is valid.\n\nPass netdev and mdev to all flows requiring\nmlx5e_netdev_change_profile() and avoid passing priv.\nIn mlx5e_netdev_change_profile() check if current priv is valid, and if\nnot, just attach the new profile without trying to access the old one.\n\nThis fixes the following oops, when enabling switchdev mode for the 2nd\ntime after first time failure:\n\n ## Enabling switchdev mode first time:\n\nmlx5_core 0012:03:00.1: E-Switch: Supported tc chains and prios offload\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n                                                                         ^^^^^^^^\nmlx5_core 0000:00:03.0: E-Switch: Disable: mode(LEGACY), nvfs(0), necvfs(0), active vports(0)\n\n ## retry: Enabling switchdev mode 2nd time:\n\nmlx5_core 0000:00:03.0: E-Switch: Supported tc chains and prios offload\nBUG: kernel NULL pointer dereference, address: 0000000000000038\n #PF: supervisor read access in kernel mode\n #PF: error_code(0x0000) - not-present page\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 13 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc4+ #91 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_detach_netdev+0x3c/0x90\nCode: 50 00 00 f0 80 4f 78 02 48 8b bf e8 07 00 00 48 85 ff 74 16 48 8b 73 78 48 d1 ee 83 e6 01 83 f6 01 40 0f b6 f6 e8 c4 42 00 00 \u0026lt;48\u0026gt; 8b 45 38 48 85 c0 74 08 48 89 df e8 cc 47 40 1e 48 8b bb f0 07\nRSP: 0018:ffffc90000673890 EFLAGS: 00010246\nRAX: 0000000000000000 RBX: ffff8881036a89c0 RCX: 0000000000000000\nRDX: ffff888113f63800 RSI: ffffffff822fe720 RDI: 0000000000000000\nRBP: 0000000000000000 R08: 0000000000002dcd R09: 0000000000000000\nR10: ffffc900006738e8 R11: 00000000ffffffff R12: 0000000000000000\nR13: 0000000000000000 R14: ffff8881036a89c0 R15: 0000000000000000\nFS:  00007fdfb8384740(0000) GS:ffff88856a9d6000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000038 CR3: 0000000112ae0005 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_netdev_change_profile+0x45/0xb0\n mlx5e_vport_rep_load+0x27b/0x2d0\n mlx5_esw_offloads_rep_load+0x72/0xf0\n esw_offloads_enable+0x5d0/0x970\n mlx5_eswitch_enable_locked+0x349/0x430\n ? is_mp_supported+0x57/0xb0\n mlx5_devlink_eswitch_mode_set+0x26b/0x430\n devlink_nl_eswitch_set_doit+0x6f/0xf0\n genl_family_rcv_msg_doit+0xe8/0x140\n genl_rcv_msg+0x18b/0x290\n ? __pfx_devlink_nl_pre_doit+0x10/0x10\n ? __pfx_devlink_nl_eswitch_set_doit+0x10/0x10\n ? __pfx_devlink_nl_post_doit+0x10/0x10\n ? __pfx_genl_rcv_msg+0x10/0x10\n netlink_rcv_skb+0x52/0x100\n genl_rcv+0x28/0x40\n netlink_unicast+0x282/0x3e0\n ? __alloc_skb+0xd6/0x190\n netlink_sendmsg+0x1f7/0x430\n __sys_sendto+0x213/0x220\n ? __sys_recvmsg+0x6a/0xd0\n __x64_sys_sendto+0x24/0x30\n do_syscall_64+0x50/0x1f0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\nRIP: 0033:0x7fdfb8495047(CVE-2026-23000)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1\n\nWhen loading guest XSAVE state via KVM_SET_XSAVE, and when updating XFD in\nresponse to a guest WRMSR, clear XFD-disabled features in the saved (or to\nbe restored) XSTATE_BV to ensure KVM doesn\u0026apos;t attempt to load state for\nfeatures that are disabled via the guest\u0026apos;s XFD.  Because the kernel\nexecutes XRSTOR with the guest\u0026apos;s XFD, saving XSTATE_BV[i]=1 with XFD[i]=1\nwill cause XRSTOR to #NM and panic the kernel.\n\nE.g. if fpu_update_guest_xfd() sets XFD without clearing XSTATE_BV:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#29: amx_test/848\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 29 UID: 1000 PID: 848 Comm: amx_test Not tainted 6.19.0-rc2-ffa07f7fd437-x86_amx_nm_xfd_non_init-vm #171 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   switch_fpu_return+0x4a/0xb0\n   kvm_arch_vcpu_ioctl_run+0x1245/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThis can happen if the guest executes WRMSR(MSR_IA32_XFD) to set XFD[18] = 1,\nand a host IRQ triggers kernel_fpu_begin() prior to the vmexit handler\u0026apos;s\ncall to fpu_update_guest_xfd().\n\nand if userspace stuffs XSTATE_BV[i]=1 via KVM_SET_XSAVE:\n\n  ------------[ cut here ]------------\n  WARNING: arch/x86/kernel/traps.c:1524 at exc_device_not_available+0x101/0x110, CPU#14: amx_test/867\n  Modules linked in: kvm_intel kvm irqbypass\n  CPU: 14 UID: 1000 PID: 867 Comm: amx_test Not tainted 6.19.0-rc2-2dace9faccd6-x86_amx_nm_xfd_non_init-vm #168 NONE\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015\n  RIP: 0010:exc_device_not_available+0x101/0x110\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   asm_exc_device_not_available+0x1a/0x20\n  RIP: 0010:restore_fpregs_from_fpstate+0x36/0x90\n   fpu_swap_kvm_fpstate+0x6b/0x120\n   kvm_load_guest_fpu+0x30/0x80 [kvm]\n   kvm_arch_vcpu_ioctl_run+0x85/0x1e40 [kvm]\n   kvm_vcpu_ioctl+0x2c3/0x8f0 [kvm]\n   __x64_sys_ioctl+0x8f/0xd0\n   do_syscall_64+0x62/0x940\n   entry_SYSCALL_64_after_hwframe+0x4b/0x53\n   \u0026lt;/TASK\u0026gt;\n  ---[ end trace 0000000000000000 ]---\n\nThe new behavior is consistent with the AMX architecture.  Per Intel\u0026apos;s SDM,\nXSAVE saves XSTATE_BV as \u0026apos;0\u0026apos; for components that are disabled via XFD\n(and non-compacted XSAVE saves the initial configuration of the state\ncomponent):\n\n  If XSAVE, XSAVEC, XSAVEOPT, or XSAVES is saving the state component i,\n  the instruction does not generate #NM when XCR0[i] = IA32_XFD[i] = 1;\n  instead, it operates as if XINUSE[i] = 0 (and the state component was\n  in its initial state): it saves bit i of XSTATE_BV field of the XSAVE\n  header as 0; in addition, XSAVE saves the initial configuration of the\n  state component (the other instructions do not save state component i).\n\nAlternatively, KVM could always do XRSTOR with XFD=0, e.g. by using\na constant XFD based on the set of enabled features when XSAVEing for\na struct fpu_guest.  However, having XSTATE_BV[i]=1 for XFD-disabled\nfeatures can only happen in the above interrupt case, or in similar\nscenarios involving preemption on preemptible kernels, because\nfpu_swap_kvm_fpstate()\u0026apos;s call to save_fpregs_to_fpstate() saves the\noutgoing FPU state with the current XFD; and that is (on all but the\nfirst WRMSR to XFD) the guest XFD.\n\nTherefore, XFD can only go out of sync with XSTATE_BV in the above\ninterrupt case, or in similar scenarios involving preemption on\npreemptible kernels, and it we can consider it (de facto) part of KVM\nABI that KVM_GET_XSAVE returns XSTATE_BV[i]=0 for XFD-disabled features.\n\n[Move clea\n---truncated---(CVE-2026-23005)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv\n\nmlx5e_priv is an unstable structure that can be memset(0) if profile\nattaching fails.\n\nPass netdev to mlx5e_destroy_netdev() to guarantee it will work on a\nvalid netdev.\n\nOn mlx5e_remove: Check validity of priv-\u0026gt;profile, before attempting\nto cleanup any resources that might be not there.\n\nThis fixes a kernel oops in mlx5e_remove when switchdev mode fails due\nto change profile failure.\n\n$ devlink dev eswitch set pci/0000:00:03.0 mode switchdev\nError: mlx5_core: Failed setting eswitch to offloads.\ndmesg:\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: new profile init failed, -12\nworkqueue: Failed to create a rescuer kthread for wq \u0026quot;mlx5e\u0026quot;: -EINTR\nmlx5_core 0012:03:00.1: mlx5e_netdev_init_profile:6214:(pid 37199): mlx5e_priv_init failed, err=-12\nmlx5_core 0012:03:00.1 gpu3rdma1: mlx5e_netdev_change_profile: failed to rollback to orig profile, -12\n\n$ devlink dev reload pci/0000:00:03.0 ==\u0026gt; oops\n\nBUG: kernel NULL pointer dereference, address: 0000000000000370\nPGD 0 P4D 0\nOops: Oops: 0000 [#1] SMP NOPTI\nCPU: 15 UID: 0 PID: 520 Comm: devlink Not tainted 6.18.0-rc5+ #115 PREEMPT(voluntary)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\nRIP: 0010:mlx5e_dcbnl_dscp_app+0x23/0x100\nRSP: 0018:ffffc9000083f8b8 EFLAGS: 00010286\nRAX: ffff8881126fc380 RBX: ffff8881015ac400 RCX: ffffffff826ffc45\nRDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff8881035109c0\nRBP: ffff8881035109c0 R08: ffff888101e3e838 R09: ffff888100264e10\nR10: ffffc9000083f898 R11: ffffc9000083f8a0 R12: ffff888101b921a0\nR13: ffff888101b921a0 R14: ffff8881015ac9a0 R15: ffff8881015ac400\nFS:  00007f789a3c8740(0000) GS:ffff88856aa59000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 0000000000000370 CR3: 000000010b6c0001 CR4: 0000000000370ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n mlx5e_remove+0x57/0x110\n device_release_driver_internal+0x19c/0x200\n bus_remove_device+0xc6/0x130\n device_del+0x160/0x3d0\n ? devl_param_driverinit_value_get+0x2d/0x90\n mlx5_detach_device+0x89/0xe0\n mlx5_unload_one_devl_locked+0x3a/0x70\n mlx5_devlink_reload_down+0xc8/0x220\n devlink_reload+0x7d/0x260\n devlink_nl_reload_doit+0x45b/0x5a0\n genl_family_rcv_msg_doit+0xe8/0x140(CVE-2026-23035)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ntracing: Add recursion protection in kernel stack trace recording\n\nA bug was reported about an infinite recursion caused by tracing the rcu\nevents with the kernel stack trace trigger enabled. The stack trace code\ncalled back into RCU which then called the stack trace again.\n\nExpand the ftrace recursion protection to add a set of bits to protect\nevents from recursion. Each bit represents the context that the event is\nin (normal, softirq, interrupt and NMI).\n\nHave the stack trace code use the interrupt context to protect against\nrecursion.\n\nNote, the bug showed an issue in both the RCU code as well as the tracing\nstacktrace code. This only handles the tracing stack trace side of the\nbug. The RCU fix will be handled separately.(CVE-2026-23138)","status":"published","published":"2026-03-27T11:10:47Z","modified":"2026-08-18T01:19:45.881631165Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"BELL-CVE-2025-68173","status":"published","published":"2025-12-17T06:06:13.46315Z","modified":"2026-06-25T07:18:39.774262369Z","updated_at":"2026-11-02T15:28:22.495824Z"},{"id":"CLSA-2026-1791132991","title":"Fix of 400 CVEs","description":"   * CVE-2026-53266\n     - netfilter: bridge: make ebt_snat ARP rewrite writable {CVE-2026-53266}\n   * CVE-2025-39964\n     - crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg\n       {CVE-2025-39964}\n   * CVE-2025-39827\n     - net: rose: include node references in rose_neigh refcount {CVE-2025-39827}\n   * CVE-2026-93140\n     - udf: Mark LVID buffer as uptodate before marking it dirty {CVE-2026-93140}\n   * CVE-2026-90112\n     - net: qlcnic: validate unified ROM sections before loading {CVE-2026-90112}\n   * CVE-2026-90237\n     - netfilter: nft_ct: move custom expectation support to helper\n       {CVE-2026-90237}\n   * CVE-2026-93051\n     - misc: ad525x_dpot: use driver core groups for sysfs files {CVE-2026-93051}\n   * CVE-2026-90379\n     - wifi: mt76: mt7921: Add PCIe AER handler support to prevent system crash\n       {CVE-2026-90379}\n   * CVE-2026-90302\n     - ocfs2: synchronize heartbeat callbacks with o2net teardown\n       {CVE-2026-90302}\n   * CVE-2026-90383\n     - misc: sgi-gru: remove interrupt-context page-table walks {CVE-2026-90383}\n   * CVE-2026-90320\n     - ocfs2: validate external xattr entries when reading metadata\n       {CVE-2026-90320}\n   * CVE-2026-93047\n     - drm/v3d: Associate BOs with every job that accesses them {CVE-2026-93047}\n   * CVE-2026-93192\n     - drm/v3d: Clear queue-\u003eactive_job when v3d_fence_create() fails\n       {CVE-2026-93192}\n   * CVE-2026-93050\n     - ipack: ipoctal: fix UAF, null-ptr-deref, and use-after-free in cleanup on\n       remove {CVE-2026-93050}\n   * CVE-2026-90311\n     - thermal: hwmon: Remove hwmon class device along with its parent\n       {CVE-2026-90311}\n   * CVE-2026-93191\n     - smack: fix incorrect task context in smack_msg_queue_msgrcv\n       {CVE-2026-93191}\n   * CVE-2026-93042\n     - dmaengine: dw-edma: Terminate all descriptors without callbacks\n       {CVE-2026-93042}\n   * CVE-2026-93056\n     - usb: gadget: f_uac1_legacy: remove broken string configfs attributes\n       {CVE-2026-93056}\n   * CVE-2026-93203\n     - batman-adv: bla: avoid CRC corruption due to parallel claim add\n       {CVE-2026-93203}\n   * CVE-2026-93204\n     - batman-adv: dat: atomically update mac addresses {CVE-2026-93204}\n   * CVE-2026-90000\n     - HID: rmi: fix OOB access with undersized RMI reports {CVE-2026-90000}\n   * CVE-2026-90431\n     - remoteproc: Prevent crash handling to race with rproc_del()\n       {CVE-2026-90431}\n   * CVE-2026-93202\n     - i3c: master: Fix recursive locking during device registration\n       {CVE-2026-93202}\n   * CVE-2026-90347\n     - arm64: ptrace: Keep 'orig_x0' in-sync with x0 on syscall entry\n       {CVE-2026-90347}\n   * CVE-2026-90267\n     - scsi: sd: Fix special_vec mempool leak when scsi_alloc_sgtables() fails\n       {CVE-2026-90267}\n   * CVE-2026-92500\n     - ext4: use fsdata to track inline data write state and fix race\n       {CVE-2026-92500}\n   * CVE-2026-93196\n     - nvdimm: virtio_pmem: refcount requests for token lifetime {CVE-2026-93196}\n   * CVE-2026-90207\n     - ALSA: seq: midi: Serialize input teardown with event_input\n       {CVE-2026-90207}\n   * CVE-2026-90307\n     - RDMA/srp: fix heap information leak on a truncated SRP_CRED_REQ\n       {CVE-2026-90307}\n   * CVE-2026-90110\n     - inetpeer: randomize RB-tree node comparison using SipHash {CVE-2026-90110}\n   * CVE-2026-90293\n     - IB/isert: post the full-feature receive buffers after session registration\n       {CVE-2026-90293}\n   * CVE-2026-89838\n     - f2fs: limit recovery filename logging to stored length {CVE-2026-89838}\n   * CVE-2026-93177\n     - drm/amdgpu/pm/powerplay: bounds-check voltage index in Vega10 lookup\n       {CVE-2026-93177}\n   * CVE-2026-89823\n     - drm: fix race between partial drm_dev_register() failure and ioctl\n       {CVE-2026-89823}\n   * CVE-2026-90041\n     - HID: sony: clean up device list on probe failure {CVE-2026-90041}\n   * CVE-2026-90015\n     - xhci: fix lost bounce buffers on TDs spanning several ring segments\n       {CVE-2026-90015}\n   * CVE-2026-93095\n     - hfsplus: validate thread record before delete key rebuild {CVE-2026-93095}\n   * CVE-2026-92522\n     - ACPI: processor: validate MADT IOAPIC entry bounds {CVE-2026-92522}\n   * CVE-2026-90328\n     - HID: steam: Reject short reads {CVE-2026-90328}\n   * CVE-2026-92481\n     - pinctrl: mediatek: free EINT resources on unbind {CVE-2026-92481}\n   * CVE-2026-90421\n     - PCI: Fix UAF when probe runs concurrent to dyn ID removal {CVE-2026-90421}\n   * CVE-2026-89952\n     - mtd: rawnand: validate ONFI extended parameter page sections\n       {CVE-2026-89952}\n   * CVE-2026-89927\n     - KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock\n       {CVE-2026-89927}\n   * CVE-2026-90245\n     - fbdev: kyro: Validate overlay viewport coordinates {CVE-2026-90245}\n   * CVE-2026-90102\n     - NFSv4/pnfs: key the data server cache on the NFS version {CVE-2026-90102}\n   * CVE-2026-93178\n     - drm/amdgpu/pm/powerplay: bounds-check voltage index in SMU7 lookup\n       {CVE-2026-93178}\n   * CVE-2026-92480\n     - scsi: ufs: core: Validate string descriptors {CVE-2026-92480}\n   * CVE-2026-90106\n     - net: bridge: arp/nd proxy: fix reading neigh ha {CVE-2026-90106}\n   * CVE-2026-89847\n     - scsi: qla2xxx: Avoid double completion in async IOCB timeout\n       {CVE-2026-89847}\n   * CVE-2026-90036\n     - NFSD: Prevent client use-after-free during blocked-lock reaping\n       {CVE-2026-90036}\n   * CVE-2026-93179\n     - drm/amd/powerplay: fix VoltageObjectInfo zero-stride loop and OOB read\n       {CVE-2026-93179}\n   * CVE-2026-89856\n     - scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation\n       {CVE-2026-89856}\n   * CVE-2026-92482\n     - pinctrl: mediatek: use devm_gpiochip_add_data() for GPIO chip\n       {CVE-2026-92482}\n   * CVE-2026-90294\n     - IB/isert: delay the final Login Response until the session is registered\n       {CVE-2026-90294}\n   * CVE-2026-92499\n     - ext4: validate readdir offset before accessing dirent {CVE-2026-92499}\n   * CVE-2026-90150\n     - pnfs/blocklayout: Fix device leaks on parse failure {CVE-2026-90150}\n   * CVE-2026-90222\n     - nfc: pn533: hold a reference to the request skb during send_frame\n       {CVE-2026-90222}\n   * CVE-2026-90235\n     - sunrpc: xprtsock: annotate shared socket callbacks with\n       READ_ONCE/WRITE_ONCE {CVE-2026-90235}\n   * CVE-2026-90105\n     - vxlan: fix reading neigh ha {CVE-2026-90105}\n   * CVE-2026-93172\n     - mm/mm_init: handle alloc_percpu failure in free_area_init_core_hotplug\n       {CVE-2026-93172}\n   * CVE-2026-90149\n     - NFSv4/flexfiles: fix NULL dereference for NFSv4.0 data servers\n       {CVE-2026-90149}\n   * CVE-2026-90248\n     - net/sched: cls_api: fix teardown of an adopted proto on insert-race loss\n       {CVE-2026-90248}\n   * CVE-2026-90196\n     - ASoC: SOF: validate topology volume range before allocation\n       {CVE-2026-90196}\n   * CVE-2026-90234\n     - NFS: Return a delegation the client fails to record {CVE-2026-90234}\n   * CVE-2026-90298\n     - drm/sun4i: tcon: Drop TCON TOP device reference {CVE-2026-90298}\n   * CVE-2026-93151\n     - nvmet-rdma: fix response resource leak on queue teardown {CVE-2026-93151}\n   * CVE-2026-90259\n     - btrfs: qgroup: fix a wrong length calculation in\n       qgroup_free_reserved_data() {CVE-2026-90259}\n   * CVE-2026-89881\n     - media: rtl2832_sdr: use vb2_video_unregister_device() on remove to fix DMA\n       leak {CVE-2026-89881}\n   * CVE-2026-90418\n     - nilfs2: fix BUG in nilfs_copy_dirty_pages() on dirty state mismatch\n       {CVE-2026-90418}\n   * CVE-2026-93053\n     - speakup: keyhelp: guard letter_offsets possible out-of-range indexing\n       {CVE-2026-93053}\n   * CVE-2026-90314\n     - remoteproc: fix OOB read via signed offset in rsc_table_for_each_entry()\n       {CVE-2026-90314}\n   * CVE-2026-92498\n     - wifi: ath6kl: avoid buffer overreads in WMI event handlers\n       {CVE-2026-92498}\n   * CVE-2026-93039\n     - ASoC: meson: Keep link pointers valid on realloc failure {CVE-2026-93039}\n   * CVE-2026-89936\n     - iio: dac: m62332: Fix regulator reference count imbalance {CVE-2026-89936}\n   * CVE-2026-89901\n     - media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL\n       deref {CVE-2026-89901}\n   * CVE-2026-89848\n     - scsi: qla2xxx: Quiesce response IRQ before freeing request queue\n       {CVE-2026-89848}\n   * CVE-2026-90303\n     - ARM: 9485/1: mm: acquire mmap write lock around show_pte() for user faults\n       {CVE-2026-90303}\n   * CVE-2026-90187\n     - null_blk: free zones array on device power-off {CVE-2026-90187}\n   * CVE-2026-90151\n     - NFSv4: remove callback IDR entry on client allocation failure\n       {CVE-2026-90151}\n   * CVE-2026-90125\n     - smb: client: fix request buffer leak in smb2_new_read_req()\n       {CVE-2026-90125}\n   * CVE-2026-89840\n     - f2fs: validate MOVE_RANGE destination size {CVE-2026-89840}\n   * CVE-2026-90160\n     - lwt_bpf: Restore reserved headroom after xmit program {CVE-2026-90160}\n   * CVE-2026-92525\n     - RDMA/rxe: Validate num_sge/cur_sge before indexing wqe-\u003edma.sge[]\n       {CVE-2026-92525}\n   * CVE-2026-90315\n     - PCI/sysfs: Add lockdown checks to legacy I/O and memory handlers\n       {CVE-2026-90315}\n   * CVE-2026-90414\n     - IB/isert: reject PDUs declaring more data than was received\n       {CVE-2026-90414}\n   * CVE-2026-93117\n     - usb: fix UAF when probe runs concurrent to dyn ID removal {CVE-2026-93117}\n   * CVE-2026-90062\n     - netfilter: nf_tables: move hardware offload step after building the chain\n       blob {CVE-2026-90062}\n   * CVE-2026-90214\n     - ASoC: xilinx: formatter_pcm: fix stream_data leak on open error\n       {CVE-2026-90214}\n   * CVE-2026-89946\n     - ASoC: cs35l33: drain threaded IRQ before runtime suspend {CVE-2026-89946}\n   * CVE-2026-89945\n     - ASoC: cs35l34: drain threaded IRQ before runtime suspend {CVE-2026-89945}\n   * CVE-2026-90194\n     - ACPI: scan: fix bus ID cleanup on device_add() failures {CVE-2026-90194}\n   * CVE-2026-93037\n     - RDMA/hfi1: Propagate sdma_txinit_ahg() errors {CVE-2026-93037}\n   * CVE-2026-89938\n     - iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove\n       UAF {CVE-2026-89938}\n   * CVE-2026-89999\n     - HID: wacom: validate report length in wacom_intuos_pro2_bt_irq\n       {CVE-2026-89999}\n   * CVE-2026-93170\n     - dmaengine: xilinx_dma: Fix channel idle state management in AXIDMA and\n       MCDMA interrupt handlers {CVE-2026-93170}\n   * CVE-2026-89846\n     - scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read\n       {CVE-2026-89846}\n   * CVE-2026-89813\n     - drm/amdgpu: force complete the KIQ ring fences on reset {CVE-2026-89813}\n   * CVE-2026-89913\n     - KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables\n       {CVE-2026-89913}\n   * CVE-2026-89864\n     - scsi: qla2xxx: Bound i2c-\u003elength in I2C bsg handlers {CVE-2026-89864}\n   * CVE-2026-92524\n     - irqchip/gic-v3-its: Prevent leak in its_vpe_irq_domain_alloc()\n       {CVE-2026-92524}\n   * CVE-2026-90032\n     - media: usbtv: keep device alive while ALSA card exists {CVE-2026-90032}\n   * CVE-2026-89929\n     - KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU\n       {CVE-2026-89929}\n   * CVE-2026-90386\n     - i3c: dw: avoid shift-out-of-bounds when DAA assigns no devices\n       {CVE-2026-90386}\n   * CVE-2026-90225\n     - nfc: llcp: read llcp_sock-\u003elocal under the socket lock in getsockopt\n       {CVE-2026-90225}\n   * CVE-2026-90138\n     - vsock: don't check the listener's sk_err in vsock_accept()\n       {CVE-2026-90138}\n   * CVE-2026-93040\n     - dmaengine: dw-edma: Serialize channel state checks {CVE-2026-93040}\n   * CVE-2026-90141\n     - ipvs: fix integer overflow in ftp helper port/address parsing\n       {CVE-2026-90141}\n   * CVE-2026-89932\n     - KVM: nVMX: Always flush vpid02 on first use {CVE-2026-89932}\n   * CVE-2026-89890\n     - media: go7007: defer the ALSA v4l2 put until card release {CVE-2026-89890}\n   * CVE-2026-89948\n     - batman-adv: bla: fix freeing of claims on meshif deletion {CVE-2026-89948}\n   * CVE-2026-89865\n     - scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers\n       {CVE-2026-89865}\n   * CVE-2026-89843\n     - scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak\n       {CVE-2026-89843}\n   * CVE-2026-90180\n     - block: mtip32xx: synchronize ioctls with device removal {CVE-2026-90180}\n   * CVE-2026-90227\n     - nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() {CVE-2026-90227}\n   * CVE-2026-89883\n     - media: rc: sunxi-cir: Unregister rc device on probe failure\n       {CVE-2026-89883}\n   * CVE-2026-89912\n     - KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save\n       {CVE-2026-89912}\n   * CVE-2026-93175\n     - drm/amd/display: Fix dangling pointer in CRTC reset function\n       {CVE-2026-93175}\n   * CVE-2026-90109\n     - net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueue\n       {CVE-2026-90109}\n   * CVE-2026-90058\n     - net/sched: bound qdisc_pkt_len to prevent qdisc soft lockup\n       {CVE-2026-90058}\n   * CVE-2026-93188\n     - HID: roccat: bound device-supplied profile index {CVE-2026-93188}\n   * CVE-2026-90057\n     - slip: remove slip_hangup() to fix use-after-free in slip_receive_buf()\n       {CVE-2026-90057}\n   * CVE-2026-89949\n     - batman-adv: dat: avoid unaligned fault in IP extraction {CVE-2026-89949}\n   * CVE-2026-89965\n     - nvdimm/btt: reject an arena whose nfree is below the lane count\n       {CVE-2026-89965}\n   * CVE-2026-89854\n     - scsi: qla2xxx: Fix cs84xx use-after-free on host teardown {CVE-2026-89854}\n   * CVE-2026-89968\n     - nvmet-tcp: reject unsolicited H2CData PDUs {CVE-2026-89968}\n   * CVE-2026-89871\n     - media: video-i2c: fix kthread error pointer left in kthread_vid_cap on\n       failure {CVE-2026-89871}\n   * CVE-2026-89897\n     - media: cec: Serialize exclusive follower delivery {CVE-2026-89897}\n   * CVE-2026-89877\n     - media: saa7164: fix cleanup on resource allocation failure\n       {CVE-2026-89877}\n   * CVE-2026-93189\n     - HID: core: quiesce input in hid_hw_stop() to prevent use-after-free\n       {CVE-2026-93189}\n   * CVE-2026-90053\n     - net/sched: sch_htb: limit htb_classify inner-class filter hops\n       {CVE-2026-90053}\n   * CVE-2026-90182\n     - blk-iocost: clear delay state when freeing policy data {CVE-2026-90182}\n   * CVE-2026-89954\n     - mtd: afs: validate v2 image info bounds {CVE-2026-89954}\n   * CVE-2026-89858\n     - scsi: qla2xxx: Bound image count in qla2x00_update_fru_versions()\n       {CVE-2026-89858}\n   * CVE-2026-89973\n     - nvme-tcp: check the data direction of a C2HData PDU {CVE-2026-89973}\n   * CVE-2026-90419\n     - nilfs2: prevent out-of-bounds read in super root block parsing\n       {CVE-2026-90419}\n   * CVE-2026-90075\n     - net/sched: fq_codel: clamp default quantum and mtu {CVE-2026-90075}\n   * CVE-2026-90416\n     - RDMA/mlx5: Fix stack out-of-bounds read in cc_params debugfs\n       {CVE-2026-90416}\n   * CVE-2026-90226\n     - nfc: llcp: avoid userspace overflow on invalid optlen {CVE-2026-90226}\n   * CVE-2026-90076\n     - net/sched: fq: add overflow bounds to quantum and initial quantum\n       {CVE-2026-90076}\n   * CVE-2026-90056\n     - net: fec: only stop PTP if it was initialized {CVE-2026-90056}\n   * CVE-2026-90411\n     - nvme-fc: unmap cmd_iu DMA on rsp_iu mapping failure in init_request\n       {CVE-2026-90411}\n   * CVE-2026-93159\n     - crypto: atmel-sha204a - fix heap info leak on I2C transfer failure\n       {CVE-2026-93159}\n   * CVE-2026-90360\n     - regulator: core: use system_freezable_wq for init complete work\n       {CVE-2026-90360}\n   * CVE-2026-90403\n     - wifi: rtlwifi: pci: fix error path in rtl_pci_probe() {CVE-2026-90403}\n   * CVE-2026-89879\n     - media: s2255: bound JPEG frame size before copying into the buffer\n       {CVE-2026-89879}\n   * CVE-2026-89821\n     - drm/amd/display: avoid divide-by-zero in __is_lut_linear()\n       {CVE-2026-89821}\n   * CVE-2026-53176\n     - IB/isert: Reject login PDUs shorter than ISER_HEADERS_LEN {CVE-2026-53176}\n   * CVE-2026-92509\n     - RDMA/core: Fix potential use after free in counter_release()\n       {CVE-2026-92509}\n   * CVE-2026-93163\n     - hwrng: core - fix rng list on registration error {CVE-2026-93163}\n   * CVE-2026-90055\n     - usb: atm: usbatm: fix invalid ci_range initialization {CVE-2026-90055}\n   * CVE-2026-90088\n     - Bluetooth: RFCOMM: Validate MTU in rfcomm_apply_pn() to prevent infinite\n       loop {CVE-2026-90088}\n   * CVE-2026-90318\n     - fat: release buffer head after rebuilding parent {CVE-2026-90318}\n   * CVE-2026-90126\n     - rtc: pcf8563: fix clock provider leak on unbind {CVE-2026-90126}\n   * CVE-2026-90345\n     - wifi: brcmfmac: fix P2P action frame handling without device vif\n       {CVE-2026-90345}\n   * CVE-2026-90073\n     - net/sched: hhf: clamp quantum before hhf_change() to avoid overflow\n       {CVE-2026-90073}\n   * CVE-2026-90263\n     - btrfs: check if root is readonly when setting posix acl {CVE-2026-90263}\n   * CVE-2026-90334\n     - tty: clear cdev pointer after cdev_add() failure {CVE-2026-90334}\n   * CVE-2026-93104\n     - RDMA/rvt: Return NULL after port allocation failure {CVE-2026-93104}\n   * CVE-2026-90216\n     - ubi: Fix rollback for explicit UBI device numbers {CVE-2026-90216}\n   * CVE-2026-93120\n     - usb: gadget: configfs: fix out-of-bounds read of qw_sign {CVE-2026-93120}\n   * CVE-2026-89876\n     - media: tda18250: fix possible integer overflow {CVE-2026-89876}\n   * CVE-2026-89887\n     - media: i2c: ov7740: fix use-after-destroy in remove {CVE-2026-89887}\n   * CVE-2026-89951\n     - batman-adv: fix stale receive device on merged fragments {CVE-2026-89951}\n   * CVE-2026-89850\n     - scsi: qla2xxx: Don't query firmware state while chip is down\n       {CVE-2026-89850}\n   * CVE-2026-90034\n     - usb: image: mdc800: change kmalloc() to kzalloc() {CVE-2026-90034}\n   * CVE-2026-80786\n     - fbdev: Wrap user-invoked calls to fb_set_var() in helper {CVE-2026-80786}\n   * CVE-2023-54023\n     - btrfs: fix race between balance and cancel/pause {CVE-2023-54023}\n   * CVE-2025-68173\n     - ftrace: Fix softlockup in ftrace_module_enable {CVE-2025-68173}\n   * CVE-2026-80757\n     - selinux: reject a class permission count below its inherited common\n       {CVE-2026-80757}\n   * CVE-2026-74256\n     - bpf, sockmap: fix integer overflow in bpf_msg_pop_data() bounds check\n       {CVE-2026-74256}\n   * CVE-2026-80830\n     - usb: core: Add lock to usb_wakeup_notification() {CVE-2026-80830}\n   * CVE-2026-80886\n     - serial: msm: Disable DMA for kernel console UART {CVE-2026-80886}\n   * CVE-2026-80824\n     - usb: usbfs: fix use-after-free of usb_device in usbdev_release()\n       {CVE-2026-80824}\n   * CVE-2026-80814\n     - rndis_host: add overflow check in rndis_rx_fixup() {CVE-2026-80814}\n   * CVE-2025-38584\n     - padata: Fix pd UAF once and for all {CVE-2025-38584}\n   * CVE-2025-38259\n     - ASoC: codecs: wcd9335: Fix missing free of regulator supplies\n       {CVE-2025-38259}\n   * CVE-2024-50067\n     - uprobe: avoid out-of-bounds memory access of fetching args\n       {CVE-2024-50067}\n   * CVE-2026-80854\n     - usb: gadget: f_tcm: keep port count until LUN teardown completes\n       {CVE-2026-80854}\n   * CVE-2026-89740\n     - serial: imx: serialize imx_uart_ports[] lifetime {CVE-2026-89740}\n   * CVE-2026-89666\n     - nfsd: reject out-of-range nseconds in NFSv3 SETATTR and create ops\n       {CVE-2026-89666}\n   * CVE-2026-80847\n     - tcp: clamp route advmss to TCP_MIN_MSS {CVE-2026-80847}\n   * CVE-2026-80861\n     - usb: xhci: bail out of setup if the controller is inaccessible\n       {CVE-2026-80861}\n   * CVE-2026-89468\n     - power: supply: lp8788-charger: fix use-after-free on remove\n       {CVE-2026-89468}\n   * CVE-2026-80974\n     - mfd: sm501: Fix potential memory leaks during remove {CVE-2026-80974}\n   * CVE-2026-89528\n     - svcrdma: Reject Read lists that exceed the page budget {CVE-2026-89528}\n   * CVE-2026-89531\n     - svcrdma: Reject connection when transport allocation fails\n       {CVE-2026-89531}\n   * CVE-2026-89527\n     - svcrdma: Use svc_xprt_put to free listener on create failure\n       {CVE-2026-89527}\n   * CVE-2026-89492\n     - ocfs2: validate directory-index entry counts when reading metadata\n       {CVE-2026-89492}\n   * CVE-2026-89441\n     - mmc: via-sdmmc: cancel card-detect work on remove {CVE-2026-89441}\n   * CVE-2026-89719\n     - zram: fix out-of-bounds access in read_block_state() {CVE-2026-89719}\n   * CVE-2026-89718\n     - zram: fix out-of-bounds access in writeback_store() {CVE-2026-89718}\n   * CVE-2026-80996\n     - net: l2tp: do not propagate multicast notification errors {CVE-2026-80996}\n   * CVE-2026-80841\n     - net/packet: defer vmalloc TX_RING free until skbs finish {CVE-2026-80841}\n   * CVE-2026-80925\n     - vlan: fix skb_under_panic and races when toggling HW VLAN offload\n       {CVE-2026-80925}\n   * CVE-2026-89484\n     - lockd: fix NULL dereference on lockowner allocation failure\n       {CVE-2026-89484}\n   * CVE-2026-89462\n     - power: supply: max17040: propagate register read errors {CVE-2026-89462}\n   * CVE-2026-80901\n     - ipvs: fix the checksum validations {CVE-2026-80901}\n   * CVE-2026-74395\n     - RDMA/mlx5: Fix devx subscribe-event unwind NULL dereference\n       {CVE-2026-74395}\n   * CVE-2026-80884\n     - ntb: Store original DMA address for future release {CVE-2026-80884}\n   * CVE-2026-80789\n     - nvmet-tcp: bound SGL data length before allocating command buffers\n       {CVE-2026-80789}\n   * CVE-2026-80913\n     - selinux: require every boolean value to be defined {CVE-2026-80913}\n   * CVE-2026-80797\n     - nfc: pn533: purge fragmented skbs during cleanup {CVE-2026-80797}\n   * CVE-2026-80738\n     - bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie\n       {CVE-2026-80738}\n   * CVE-2026-80737\n     - serial: amba-pl011: synchronize DMA teardown {CVE-2026-80737}\n   * CVE-2026-80798\n     - nfc: llcp: reject PDUs shorter than the LLCP header {CVE-2026-80798}\n   * CVE-2026-80840\n     - ipv6: seg6: clear IPv4 control block on IPIP decapsulation\n       {CVE-2026-80840}\n   * CVE-2026-80764\n     - Bluetooth: hci_event: fix LE list UAF on reset {CVE-2026-80764}\n   * CVE-2026-80851\n     - gtp: serialize PDP context updates {CVE-2026-80851}\n   * CVE-2026-80828\n     - ALSA: usb-audio: Complete cleanup after system-resume errors\n       {CVE-2026-80828}\n   * CVE-2026-80807\n     - nilfs2: reject invalid block index in GC ioctl {CVE-2026-80807}\n   * CVE-2026-80852\n     - tls: device: fix out-of-bounds write in tls_append_frag() {CVE-2026-80852}\n   * CVE-2026-80733\n     - net: remove WARN_ON_ONCE() from sk_mc_loop() {CVE-2026-80733}\n   * CVE-2026-80782\n     - HID: magicmouse: do not keep a stale msc-\u003einput if no input is claimed\n       {CVE-2026-80782}\n   * CVE-2026-80843\n     - xfrm: fix xfrm_state_construct() auth-trunc leak {CVE-2026-80843}\n   * CVE-2023-53834\n     - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match\n       {CVE-2023-53834}\n   * CVE-2022-50774\n     - crypto: qat - fix DMA transfer direction {CVE-2022-50774}\n   * CVE-2023-53799\n     - crypto: api - Use work queue in crypto_destroy_instance {CVE-2023-53799}\n   * CVE-2024-50135\n     - nvme-pci: fix race condition between reset and nvme_dev_disable()\n       {CVE-2024-50135}\n   * CVE-2022-50766\n     - btrfs: set generation before calling btrfs_clean_tree_block in\n       btrfs_init_new_buffer {CVE-2022-50766}\n   * CVE-2025-40100\n     - btrfs: do not assert we found block group item when creating free space\n       tree {CVE-2025-40100}\n   * CVE-2025-40180\n     - mailbox: zynqmp-ipi: Fix out-of-bounds access in mailbox cleanup loop\n       {CVE-2025-40180}\n   * CVE-2025-68344\n     - ALSA: wavefront: Fix integer overflow in sample size validation\n       {CVE-2025-68344}\n   * CVE-2024-50166\n     - fsl/fman: Fix refcount handling of fman-related devices {CVE-2024-50166}\n   * CVE-2025-71193\n     - phy: qcom-qusb2: Fix NULL pointer dereference on early suspend\n       {CVE-2025-71193}\n   * CVE-2023-53815\n     - posix-timers: Prevent RT livelock in itimer_delete() {CVE-2023-53815}\n   * CVE-2026-80742\n     - af_packet: Don't send zero-byte data in tpacket_snd(). {CVE-2026-80742}\n   * CVE-2026-80875\n     - ipvs: use parsed transport offset in TCP state lookup {CVE-2026-80875}\n   * CVE-2026-80809\n     - ocfs2: fix missing metadata reservation for large xattrs {CVE-2026-80809}\n   * CVE-2026-74321\n     - btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs()\n       {CVE-2026-74321}\n   * CVE-2026-80731\n     - net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header\n       {CVE-2026-80731}\n   * CVE-2026-72378\n     - afs: Fix error code in afs_extract_vl_addrs() {CVE-2026-72378}\n   * CVE-2026-80752\n     - Input: psxpad-spi - set driver data before use {CVE-2026-80752}\n   * CVE-2026-80801\n     - nfc: microread: validate target discovery payload lengths {CVE-2026-80801}\n   * CVE-2026-72165\n     - mtd: rawnand: fix condition in 'nand_select_target()' {CVE-2026-72165}\n   * CVE-2026-80877\n     - afs: Fix vllist leak {CVE-2026-80877}\n   * CVE-2026-80819\n     - Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept\n       {CVE-2026-80819}\n   * CVE-2026-63934\n     - iio: gyro: itg3200: fix i2c read into the wrong stack location\n       {CVE-2026-63934}\n   * CVE-2025-68777\n     - Input: ti_am335x_tsc - fix off-by-one error in wire_order validation\n       {CVE-2025-68777}\n   * CVE-2026-63908\n     - Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem\n       {CVE-2026-63908}\n   * CVE-2025-40116\n     - usb: host: max3421-hcd: Fix error pointer dereference in probe cleanup\n       {CVE-2025-40116}\n   * CVE-2025-68339\n     - atm/fore200e: Fix possible data race in fore200e_open() {CVE-2025-68339}\n   * CVE-2026-63957\n     - USB: serial: safe_serial: fix memory corruption with small endpoint\n       {CVE-2026-63957}\n   * CVE-2023-53840\n     - usb: early: xhci-dbc: Fix a potential out-of-bound memory access\n       {CVE-2023-53840}\n   * CVE-2025-68328\n     - firmware: stratix10-svc: fix bug in saving controller data\n       {CVE-2025-68328}\n   * CVE-2026-63915\n     - nfc: hci: fix out-of-bounds read in HCP header parsing {CVE-2026-63915}\n   * CVE-2026-63893\n     - thunderbolt: property: Reject u32 wrap in tb_property_entry_valid()\n       {CVE-2026-63893}\n   * CVE-2026-63927\n     - usb: dwc2: Fix use after free in debug code {CVE-2026-63927}\n   * CVE-2026-63954\n     - hpfs: fix a crash if hpfs_map_dnode_bitmap fails {CVE-2026-63954}\n   * CVE-2026-64010\n     - nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() {CVE-2026-64010}\n   * CVE-2026-63892\n     - thunderbolt: property: Reject dir_len \u003c 4 to prevent size_t underflow\n       {CVE-2026-63892}\n   * CVE-2026-64014\n     - Input: usbtouchscreen - clamp NEXIO data_len/x_len to URB buffer size\n       {CVE-2026-64014}\n   * CVE-2025-68364\n     - ocfs2: relax BUG() to ocfs2_error() in __ocfs2_move_extent()\n       {CVE-2025-68364}\n   * CVE-2026-63991\n     - Bluetooth: 6lowpan: check skb_clone() return value in send_mcast_pkt()\n       {CVE-2026-63991}\n   * CVE-2026-63971\n     - sctp: fix race between sctp_wait_for_connect and peeloff {CVE-2026-63971}\n   * CVE-2025-71069\n     - f2fs: invalidate dentry cache on failed whiteout creation {CVE-2025-71069}\n   * CVE-2026-64011\n     - nfc: llcp: Fix use-after-free in llcp_sock_release() {CVE-2026-64011}\n   * CVE-2026-63888\n     - scsi: target: iscsi: Fix CRC overread and double-free in\n       iscsit_handle_text_cmd() {CVE-2026-63888}\n   * CVE-2026-89476\n     - sctp: fix stream-\u003eoutcnt underflow on duplicate RECONF responses\n       {CVE-2026-89476}\n   * CVE-2026-89574\n     - dm array: validate array block headers on read {CVE-2026-89574}\n   * CVE-2026-63962\n     - usb: typec: tcpm: bound altmode_desc[] per iteration in\n       svdm_consume_modes() {CVE-2026-63962}\n   * CVE-2026-63983\n     - net/sched: fix packet loop on netem when duplicate is on {CVE-2026-63983}\n   * CVE-2026-80994\n     - net: openvswitch: fix flow mask use-after-free on flow deletion\n       {CVE-2026-80994}\n   * CVE-2026-80928\n     - smack: fix cred UAF in smack_file_send_sigiotask() {CVE-2026-80928}\n   * CVE-2026-89448\n     - iommu/vt-d: Force requesting ACS when tboot is enabled {CVE-2026-89448}\n   * CVE-2026-89633\n     - smb: client: fix OOB read/write from unvalidated DataOffset in\n       coalesce_t2() {CVE-2026-89633}\n   * CVE-2026-80976\n     - seg6: reset IP6CB after IPv6 decapsulation {CVE-2026-80976}\n   * CVE-2026-63922\n     - ipv6: exthdrs: refresh nh after handling HAO option {CVE-2026-63922}\n   * CVE-2026-80982\n     - net/smc: fix use-after-free in smc_rx_pipe_buf_release() {CVE-2026-80982}\n   * CVE-2026-89487\n     - openvswitch: only skb_tx_error() a packet we are about to drop\n       {CVE-2026-89487}\n   * CVE-2026-89478\n     - sctp: drop a chunk if its transport was removed {CVE-2026-89478}\n   * CVE-2026-81001\n     - slip: fix use-after-free in sl_sync() {CVE-2026-81001}\n   * CVE-2026-89537\n     - SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2\n       {CVE-2026-89537}\n   * CVE-2026-80971\n     - ALSA: bcd2000: clear the URB pointers on disconnect {CVE-2026-80971}\n   * CVE-2026-63930\n     - iio: buffer: hw-consumer: fix use-after-free in error path\n       {CVE-2026-63930}\n   * CVE-2026-72389\n     - bridge: stp: Fix a potential use-after-free when deleting a bridge\n       {CVE-2026-72389}\n   * CVE-2025-40351\n     - hfsplus: fix KMSAN uninit-value issue in hfsplus_delete_cat()\n       {CVE-2025-40351}\n   * CVE-2026-64009\n     - xfrm: Check for underflow in xfrm_state_mtu {CVE-2026-64009}\n   * CVE-2026-81000\n     - net: tun: bound receive headroom {CVE-2026-81000}\n   * CVE-2026-80676\n     - Drivers: hv: vmbus: use generic driver_override infrastructure\n       {CVE-2026-80676}\n   * CVE-2026-74510\n     - Bluetooth: mgmt: fix UAF in pair command cancellation {CVE-2026-74510}\n   * CVE-2026-72472\n     - nfs: use nfsi-\u003erwsem to protect traversal of the file lock list\n       {CVE-2026-72472}\n   * CVE-2026-68367\n     - usb: gadget: f_tcm: synchronize delayed set_alt with teardown\n       {CVE-2026-68367}\n   * CVE-2026-74450\n     - drm/amd/pm: fix pptable use-after-free {CVE-2026-74450}\n   * CVE-2026-74637\n     - perf/core: Fix group leader use-after-free after sibling detach\n       {CVE-2026-74637}\n   * CVE-2026-68404\n     - wifi: cfg80211: use wiphy work for socket owner autodisconnect\n       {CVE-2026-68404}\n   * CVE-2026-89480\n     - nvme-tcp: reject a read that transferred too few bytes {CVE-2026-89480}\n   * CVE-2026-72084\n     - scsi: target: Bound PR-OUT TransportID parsing to the received buffer\n       {CVE-2026-72084}\n   * CVE-2026-74720\n     - bpf: Preserve pointer state for commuted arithmetic {CVE-2026-74720}\n   * CVE-2026-74631\n     - net: smc: fix splice entry lifetime imbalance in smc_rx_splice\n       {CVE-2026-74631}\n   * CVE-2026-89762\n     - apparmor: fix cred UAF caused by begin_current_label_crit_section()\n       {CVE-2026-89762}\n   * CVE-2026-89659\n     - NFSD: Prevent client use-after-free during delegation revoke\n       {CVE-2026-89659}\n   * CVE-2026-89488\n     - openvswitch: Fix CT limit teardown use-after-free {CVE-2026-89488}\n   * CVE-2026-72390\n     - net/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF\n       {CVE-2026-72390}\n   * CVE-2026-72255\n     - netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst\n       {CVE-2026-72255}\n   * CVE-2026-74387\n     - ALSA: seq: midi: Serialize output teardown with event_input\n       {CVE-2026-74387}\n   * CVE-2026-74565\n     - netfilter: nf_tables: make nft_object rhltable per table {CVE-2026-74565}\n   * CVE-2026-74575\n     - thunderbolt: Prevent XDomain delayed work use-after-free on disconnect\n       {CVE-2026-74575}\n   * CVE-2026-80536\n     - xfs: bounds-check buffer log item's dirty bitmap {CVE-2026-80536}\n   * CVE-2026-89637\n     - smb: client: fix UAF and buffer leak in cifs_check_trans2() for malformed\n       secondary T2 {CVE-2026-89637}\n   * CVE-2026-68398\n     - ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF\n       {CVE-2026-68398}\n   * CVE-2026-68426\n     - xfrm: fix stale skb-\u003eprev after async crypto steals a GSO segment\n       {CVE-2026-68426}\n   * CVE-2026-89708\n     - nfsd: RCU-protect cl_cb_session to fix use-after-free on session teardown\n       {CVE-2026-89708}\n   * CVE-2026-74752\n     - sctp: validate cookie AUTH state before use {CVE-2026-74752}\n   * CVE-2026-64557\n     - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb()\n       {CVE-2026-64557}\n   * CVE-2026-72336\n     - Bluetooth: 6lowpan: hold L2CAP conn across debugfs control\n       {CVE-2026-72336}\n   * CVE-2026-64550\n     - net: qualcomm: rmnet: validate MAP frame length before ingress parsing\n       {CVE-2026-64550}\n   * CVE-2026-74345\n     - RDMA/siw: Fix endpoint/socket association handling {CVE-2026-74345}\n   * CVE-2026-72404\n     - tipc: fix UAF in cleanup_bearer() due to premature dst_cache_destroy()\n       {CVE-2026-72404}\n   * CVE-2026-64543\n     - tipc: fix use-after-free of the discoverer in tipc_disc_rcv()\n       {CVE-2026-64543}\n   * CVE-2026-72157\n     - net: thunderbolt: Fix frags[] overflow by bounding frame_count\n       {CVE-2026-72157}\n   * CVE-2026-74589\n     - bpf, sockmap: Fix sk_redir use-after-free in send verdict {CVE-2026-74589}\n   * CVE-2026-74651\n     - staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() {CVE-2026-74651}\n   * CVE-2026-68190\n     - staging: rtl8723bs: fix OOB reads in rtw_get_wps_ie() {CVE-2026-68190}\n   * CVE-2026-74649\n     - staging: rtl8723bs: fix missing shared-key auth challenge length check\n       {CVE-2026-74649}\n   * CVE-2026-74582\n     - packet: use consistent hard_header_len in non-ring send paths\n       {CVE-2026-74582}\n   * CVE-2026-74669\n     - ipvs: clear IPv4 options after rebasing tunnel ICMP errors\n       {CVE-2026-74669}\n   * CVE-2026-89553\n     - nouveau/gem: reserve the bo in the info ioctl around the vma lookup\n       {CVE-2026-89553}\n   * CVE-2026-74550\n     - net: do not send ICMP/NDISC Redirects when peer allocation fails\n       {CVE-2026-74550}\n   * CVE-2026-74569\n     - netfilter: nf_conntrack_sip: widen NAT rewrite delta to s32 in\n       sip_help_tcp() {CVE-2026-74569}\n   * CVE-2026-68108\n     - drm/amdgpu/vce: fix integer overflow in image size {CVE-2026-68108}\n   * CVE-2026-72129\n     - nvmet-rdma: handle inline data with a nonzero offset {CVE-2026-72129}\n   * CVE-2026-74700\n     - net/sched: cls_api: Always acquire rtnl_lock when destroying locked\n       classifiers {CVE-2026-74700}\n   * CVE-2026-63826\n     - fbdev: fix use-after-free in store_modes() {CVE-2026-63826}\n   * CVE-2026-68138\n     - net/sched: serialize qdisc_rtab_list against concurrent get/put\n       {CVE-2026-68138}\n   * CVE-2026-89549\n     - sunrpc: route to a populated pool in svc_pool_for_cpu() {CVE-2026-89549}\n   * CVE-2026-74377\n     - RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path\n       {CVE-2026-74377}\n   * CVE-2026-64470\n     - Bluetooth: btusb: fix use-after-free on marvell probe failure\n       {CVE-2026-64470}\n   * CVE-2026-89550\n     - SUNRPC: svcauth_gss: enforce krb5 token minimum length {CVE-2026-89550}\n   * CVE-2026-89655\n     - ceph: fix UAF in __kick_flushing_caps() on cf entry freed during unlock\n       {CVE-2026-89655}\n   * CVE-2026-64541\n     - net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket\n       {CVE-2026-64541}\n   * CVE-2026-72322\n     - ipv6: mcast: Fix potential UAF in MLD delayed work {CVE-2026-72322}\n   * CVE-2026-68236\n     - drm/amd/display: set new_stream to NULL after release {CVE-2026-68236}\n   * CVE-2026-89699\n     - nfsd: validate symlink target length in NFSv4 CREATE {CVE-2026-89699}\n   * CVE-2026-89481\n     - nvme-tcp: fix host memory disclosure on R2T for a read command\n       {CVE-2026-89481}\n   * CVE-2026-68093\n     - KVM: SVM: Bump asid_generation on CPU online to avoid ASID collision after\n       hotplug {CVE-2026-68093}\n   * CVE-2026-74704\n     - net/sched: sch_cake: drop WARN_ON(1) for malformed packets in ACK filter\n       {CVE-2026-74704}\n   * CVE-2026-74289\n     - ipv4: fib: Don't dump dying fib_info in fib_leaf_notify().\n       {CVE-2026-74289}\n   * CVE-2026-74436\n     - rxrpc: serialize kernel accept preallocation with socket teardown\n       {CVE-2026-74436}\n   * CVE-2026-64583\n     - usb: gadget: udc: bdc: free IRQ and drain func_wake_notify before teardown\n       {CVE-2026-64583}\n   * CVE-2026-74283\n     - tipc: require net admin for TIPCv2 netlink mutators {CVE-2026-74283}\n   * CVE-2026-74479\n     - net: pktgen: fix proc entry use-after-free {CVE-2026-74479}\n   * CVE-2026-74341\n     - wifi: wcn36xx: fix heap overflow from oversized firmware HAL response\n       {CVE-2026-74341}\n   * CVE-2026-74628\n     - net/x25: fix use-after-free of the socket by its timers {CVE-2026-74628}\n   * CVE-2026-64468\n     - binder: fix UAF in binder_free_transaction() {CVE-2026-64468}\n   * CVE-2026-74746\n     - netfilter: flowtable: publish GC-visible tuple last {CVE-2026-74746}\n   * CVE-2026-89656\n     - libceph: reject buckets with mismatched CRUSH ids {CVE-2026-89656}\n   * CVE-2026-89475\n     - power: supply: bq24257: fix use-after-free on remove {CVE-2026-89475}\n     - devm-helpers: Fix devm_delayed_work_autocancel() kerneldoc\n       {CVE-2026-89475}\n     - devm-helpers: Add resource managed version of work init {CVE-2026-89475}\n     - workqueue: Add resource managed version of delayed work init\n       {CVE-2026-89475}\n   * CVE-2026-68142\n     - geneve: require CAP_NET_ADMIN in the device netns for changelink\n       {CVE-2026-68142}\n   * CVE-2026-74688\n     - sctp: clear control chunk transport if it is being removed\n       {CVE-2026-74688}\n   * CVE-2026-68399\n     - bpf: Fix UAF in sock clone early bailouts {CVE-2026-68399}\n   * CVE-2026-72085\n     - scsi: xen: scsiback: Free unsubmitted command instead of double-putting it\n       {CVE-2026-72085}\n   * CVE-2026-72413\n     - sctp: fix err_chunk memory leaks in INIT handling {CVE-2026-72413}\n   * CVE-2026-74689\n     - net/atm: fix slab-out-of-bounds read in vcc_setsockopt() {CVE-2026-74689}\n   * CVE-2026-72323\n     - ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() {CVE-2026-72323}\n   * CVE-2026-74359\n     - configfs_lookup(): don't leave -\u003es_dentry dangling on failure\n       {CVE-2026-74359}\n   * CVE-2026-74454\n     - drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO size\n       {CVE-2026-74454}\n   * CVE-2026-74496\n     - fou: Fix use-after-free in fou_create() {CVE-2026-74496}\n   * CVE-2026-80681\n     - vxlan: re-fetch eth header after route_shortcircuit() {CVE-2026-80681}\n   * CVE-2026-68414\n     - wifi: cfg80211: cancel sched scan results work on unregister\n       {CVE-2026-68414}\n   * CVE-2026-64582\n     - RDMA/rxe: Fix a use-after-free problem in rxe_mmap {CVE-2026-64582}\n   * CVE-2026-72288\n     - KVM: arm64: vgic: Handle race between interrupt affinity change and LPI\n       disabling {CVE-2026-72288}\n   * CVE-2026-68202\n     - ALSA: seq: close a re-opened queue timer in the destructor\n       {CVE-2026-68202}\n   * CVE-2026-64546\n     - drm/edid: fix OOB read in drm_parse_tiled_block() {CVE-2026-64546}\n   * CVE-2026-89559\n     - libnvdimm/labels: Prevent integer overflow in __nd_label_validate()\n       {CVE-2026-89559}\n   * CVE-2026-89469\n     - power: supply: lp8727: fix use-after-free in lp8727_release_irq()\n       {CVE-2026-89469}\n   * CVE-2026-89575\n     - dm raid1: reserve space for NUL-terminator in build_constructor_string()\n       {CVE-2026-89575}\n   * CVE-2026-89555\n     - mpls: reload header after pskb_may_pull() {CVE-2026-89555}\n   * CVE-2026-89504\n     - regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving\n       dangling of_node pointer {CVE-2026-89504}\n   * CVE-2026-89569\n     - Bluetooth: RFCOMM: serialize security confirmation handling\n       {CVE-2026-89569}\n   * CVE-2026-89761\n     - apparmor: fix out-of-bounds write when null terminating a label vec\n       {CVE-2026-89761}\n   * CVE-2026-89494\n     - ocfs2: validate lengths in dlm_mig_lockres_handler {CVE-2026-89494}\n   * CVE-2026-89548\n     - SUNRPC: always drain cache_cleaner before destroying a cache_detail\n       {CVE-2026-89548}\n   * CVE-2026-89477\n     - sctp: fix NULL deref on untransmitted RECONF completion {CVE-2026-89477}\n   * CVE-2026-89495\n     - ocfs2: bound namelen in dlm_migrate_request_handler {CVE-2026-89495}\n   * CVE-2026-74744\n     - ipvlan: inherit needed_headroom and needed_tailroom from phy_dev\n       {CVE-2026-74744}\n   * CVE-2026-74282\n     - tipc: prevent snt_unacked underflow on CONN_ACK {CVE-2026-74282}\n   * CVE-2026-68198\n     - wifi: ath6kl: fix use-after-free in aggr_reset_state() {CVE-2026-68198}\n   * CVE-2026-74386\n     - nvmet-tcp: fix page fragment cache leak in error path {CVE-2026-74386}\n   * CVE-2026-68155\n     - libceph: Reject monmaps advertising zero monitors {CVE-2026-68155}\n   * CVE-2026-72383\n     - sctp: fix addr_wq_timer race in sctp_free_addr_wq() {CVE-2026-72383}\n   * CVE-2026-72476\n     - dmaengine: Fix possible use after free {CVE-2026-72476}\n   * CVE-2026-74597\n     - ip6_tunnel: clear skb2-\u003ecb[] in ip6ip6_err() {CVE-2026-74597}\n   * CVE-2026-74587\n     - sctp: fix use-after-free of cached ASCONF chunk {CVE-2026-74587}\n   * CVE-2026-72491\n     - net/9p: fix race condition on rdma-\u003estate in trans_rdma.c {CVE-2026-72491}\n   * CVE-2026-80619\n     - apparmor: fix potential UAF in aa_replace_profiles {CVE-2026-80619}\n   * CVE-2026-64548\n     - bpf, sockmap: reject overflowing copy + len in bpf_msg_push_data()\n       {CVE-2026-64548}\n   * CVE-2026-74499\n     - ALSA: usb-audio: fix OOB write in snd_usbmidi_akai_output()\n       {CVE-2026-74499}\n   * CVE-2026-68365\n     - USB: serial: io_edgeport: cap received transmit credits {CVE-2026-68365}\n   * CVE-2026-68320\n     - sctp: fix auth_chunk_list capacity check in sctp_auth_ep_add_chunkid\n       {CVE-2026-68320}\n   * CVE-2026-74498\n     - ALSA: usb-audio: Fix DMA buffer out-of-bounds write when fill_max is set\n       {CVE-2026-74498}\n   * CVE-2026-74682\n     - ALSA: usb-audio: fix OOB write on Type II inbound URBs {CVE-2026-74682}\n   * CVE-2026-72226\n     - batman-adv: tt: prevent TVLV OOB check overflow {CVE-2026-72226}\n   * CVE-2026-74469\n     - sctp: prevent peer transport count overflow {CVE-2026-74469}\n   * CVE-2026-74287\n     - sctp: validate embedded address parameter length {CVE-2026-74287}\n   * CVE-2026-63887\n     - scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf\n       {CVE-2026-63887}\n   * CVE-2026-90413\n     - IB/isert: reject login PDUs declaring more data than was received\n       {CVE-2026-90413}\n   * Miscellaneous upstream changes\n     - net: rose: fix a typo in rose_clear_routes()\n     - lockdep: fix build of the preemption assertion macros on 5.4\n   * Bump ABI 5.4.0-239","status":"published","published":"2026-10-19T13:48:34Z","modified":"2026-10-26T09:43:46.423323835Z","updated_at":"2026-11-02T15:43:49.016976Z"},{"id":"CLSA-2026-1791876326","title":"Fix of 274 CVEs","description":"   * CVE-2026-53091\n     - xfrm: Don't clobber inner headers when already set {CVE-2026-53091}\n     - net: account for encap headers in qdisc pkt len {CVE-2026-53091}\n   * CVE-2026-93803\n     - wifi: libipw: fix key index receive bound checks {CVE-2026-93803}\n   * CVE-2026-93286\n     - net: appletalk: fix NULL pointer dereference in aarp_send_ddp()\n       {CVE-2026-93286}\n   * CVE-2026-93280\n     - greybus: audio: bound the topology section sizes against the fetched size\n       {CVE-2026-93280}\n   * CVE-2026-93213\n     - of: fix out-of-bounds read in of_alias_scan() stem parser {CVE-2026-93213}\n   * CVE-2026-93802\n     - wifi: rsi: validate beacon length before fixed buffer copy\n       {CVE-2026-93802}\n   * CVE-2026-93206\n     - PCI/proc: Use file_ns_capable() when checking config space read access\n       {CVE-2026-93206}\n   * CVE-2026-97448\n     - ACPICA: Add validation for node in acpi_ns_build_normalized_path()\n       {CVE-2026-97448}\n   * CVE-2026-97408\n     - Bluetooth: L2CAP: validate connectionless PSM length {CVE-2026-97408}\n   * CVE-2026-93268\n     - ext4: skip extra isize expansion during mount to prevent deadlock\n       {CVE-2026-93268}\n   * CVE-2026-93782\n     - vhost-scsi: flush backend after device ioctls {CVE-2026-93782}\n   * CVE-2026-93783\n     - Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame\n       {CVE-2026-93783}\n   * CVE-2026-97455\n     - ACPICA: Fix use-after-free in acpi_ds_terminate_control_method()\n       {CVE-2026-97455}\n   * CVE-2026-93807\n     - wifi: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers\n       {CVE-2026-93807}\n   * CVE-2026-93808\n     - ALSA: usb-audio: caiaq: validate EP1 reply lengths {CVE-2026-93808}\n   * CVE-2026-89938\n     - iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove\n       UAF {CVE-2026-89938}\n   * CVE-2026-89927\n     - KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock\n       {CVE-2026-89927}\n   * CVE-2026-89949\n     - batman-adv: dat: avoid unaligned fault in IP extraction {CVE-2026-89949}\n   * CVE-2026-89912\n     - KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save\n       {CVE-2026-89912}\n   * CVE-2026-89932\n     - KVM: nVMX: Always flush vpid02 on first use {CVE-2026-89932}\n   * CVE-2026-89833\n     - f2fs: fix to avoid potential deadloop in f2fs_fsync_node_pages()\n       {CVE-2026-89833}\n   * CVE-2026-90045\n     - USB: gadget: ffs: fix mm lifetime handling {CVE-2026-90045}\n   * CVE-2026-89854\n     - scsi: qla2xxx: Fix cs84xx use-after-free on host teardown {CVE-2026-89854}\n   * CVE-2026-90015\n     - xhci: fix lost bounce buffers on TDs spanning several ring segments\n       {CVE-2026-90015}\n   * CVE-2026-89979\n     - ALSA: pcm: Fix race between non-atomic ops and trigger-start\n       {CVE-2026-89979}\n   * CVE-2026-89852\n     - scsi: qla2xxx: Zero mailbox struct in qla2x00_get_firmware_state()\n       {CVE-2026-89852}\n   * CVE-2026-89861\n     - scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition()\n       {CVE-2026-89861}\n   * CVE-2026-89859\n     - scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak\n       {CVE-2026-89859}\n   * CVE-2026-90036\n     - NFSD: Prevent client use-after-free during blocked-lock reaping\n       {CVE-2026-90036}\n   * CVE-2026-89987\n     - mm/huge_memory: transfer the pmd dirty bit to the folio on zap\n       {CVE-2026-89987}\n   * CVE-2026-89799\n     - bpf: Disable preemption in bpf_get_stackid {CVE-2026-89799}\n   * CVE-2026-90032\n     - media: usbtv: keep device alive while ALSA card exists {CVE-2026-90032}\n   * CVE-2026-89822\n     - drm/i915: Guard against NULL driver_data in i915_pci_probe()\n       {CVE-2026-89822}\n   * CVE-2026-89929\n     - KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU\n       {CVE-2026-89929}\n   * CVE-2026-89840\n     - f2fs: validate MOVE_RANGE destination size {CVE-2026-89840}\n   * CVE-2026-89913\n     - KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables\n       {CVE-2026-89913}\n   * CVE-2026-89865\n     - scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers\n       {CVE-2026-89865}\n   * CVE-2026-90000\n     - HID: rmi: fix OOB access with undersized RMI reports {CVE-2026-90000}\n   * CVE-2026-89972\n     - nvme: add missing SRCU grace period in error path {CVE-2026-89972}\n   * CVE-2026-90049\n     - net: skbuff: don't skb_tx_error() the source skb in skb_zerocopy()\n       {CVE-2026-90049}\n   * CVE-2026-89856\n     - scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation\n       {CVE-2026-89856}\n   * CVE-2026-90037\n     - NFSD: Prevent client use-after-free during close_lru reaping\n       {CVE-2026-90037}\n   * CVE-2026-89948\n     - batman-adv: bla: fix freeing of claims on meshif deletion {CVE-2026-89948}\n   * CVE-2026-90023\n     - usb: gadget: f_mass_storage: fix null pointer dereference in\n       fsg_common_set_num_buffers() {CVE-2026-90023}\n   * CVE-2026-90020\n     - USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl()\n       {CVE-2026-90020}\n   * CVE-2026-89838\n     - f2fs: limit recovery filename logging to stored length {CVE-2026-89838}\n   * CVE-2026-89848\n     - scsi: qla2xxx: Quiesce response IRQ before freeing request queue\n       {CVE-2026-89848}\n   * CVE-2026-90017\n     - staging: rtl8723bs: fix OOB read in rtw_action_frame_parse()\n       {CVE-2026-90017}\n   * CVE-2026-89897\n     - media: cec: Serialize exclusive follower delivery {CVE-2026-89897}\n   * CVE-2026-89877\n     - media: saa7164: fix cleanup on resource allocation failure\n       {CVE-2026-89877}\n   * CVE-2026-89952\n     - mtd: rawnand: validate ONFI extended parameter page sections\n       {CVE-2026-89952}\n   * CVE-2026-90016\n     - staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie() {CVE-2026-90016}\n   * CVE-2026-89999\n     - HID: wacom: validate report length in wacom_intuos_pro2_bt_irq\n       {CVE-2026-89999}\n   * CVE-2026-90044\n     - usb: gadget: f_fs: Fix Use-After-Free in AIO error path {CVE-2026-90044}\n   * CVE-2026-90029\n     - usb: storage: realtek_cr: fix use-after-free on disconnect\n       {CVE-2026-90029}\n   * CVE-2026-89783\n     - xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full\n       {CVE-2026-89783}\n   * CVE-2026-89778\n     - isofs: fix out-of-bounds page array access on empty zisofs block\n       {CVE-2026-89778}\n   * CVE-2026-89845\n     - scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry()\n       {CVE-2026-89845}\n   * CVE-2026-89946\n     - ASoC: cs35l33: drain threaded IRQ before runtime suspend {CVE-2026-89946}\n   * CVE-2026-89846\n     - scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read\n       {CVE-2026-89846}\n   * CVE-2026-89965\n     - nvdimm/btt: reject an arena whose nfree is below the lane count\n       {CVE-2026-89965}\n   * CVE-2026-89945\n     - ASoC: cs35l34: drain threaded IRQ before runtime suspend {CVE-2026-89945}\n   * CVE-2026-89953\n     - mtd: mtdoops: free page bitmap when the backing MTD is removed\n       {CVE-2026-89953}\n   * CVE-2026-89855\n     - scsi: qla2xxx: Serialize flash version read in reset handler\n       {CVE-2026-89855}\n   * CVE-2026-89936\n     - iio: dac: m62332: Fix regulator reference count imbalance {CVE-2026-89936}\n   * CVE-2026-90031\n     - usb-storage: ene_ub6250: fix race between scan work and probe\n       {CVE-2026-90031}\n   * CVE-2026-89901\n     - media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL\n       deref {CVE-2026-89901}\n   * CVE-2026-89878\n     - media: s2255: check firmware size before reading trailing marker\n       {CVE-2026-89878}\n   * CVE-2026-89890\n     - media: go7007: defer the ALSA v4l2 put until card release {CVE-2026-89890}\n   * CVE-2026-89893\n     - media: cx23885: cancel NetUP CI work before teardown {CVE-2026-89893}\n   * CVE-2026-89951\n     - batman-adv: fix stale receive device on merged fragments {CVE-2026-89951}\n   * CVE-2026-90034\n     - usb: image: mdc800: change kmalloc() to kzalloc() {CVE-2026-90034}\n   * CVE-2026-90033\n     - ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output()\n       {CVE-2026-90033}\n   * CVE-2026-90007\n     - scsi: pm8001: Use rollback index when freeing MSI-X vectors\n       {CVE-2026-90007}\n   * CVE-2026-90011\n     - scsi: target: iscsi: Reserve a terminator byte for the login payload\n       {CVE-2026-90011}\n   * CVE-2026-90013\n     - tracing: Take trace_array reference when opening options file\n       {CVE-2026-90013}\n   * CVE-2026-89843\n     - scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak\n       {CVE-2026-89843}\n   * CVE-2026-89982\n     - i2c: mux: Fix channel node leak on adapter add failure {CVE-2026-89982}\n   * CVE-2026-89997\n     - dm: fix resume-vs-remove race {CVE-2026-89997}\n   * CVE-2026-90019\n     - usb: gadget: fix null pointer dereference in usb_put_function_instance()\n       {CVE-2026-90019}\n   * CVE-2026-89895\n     - media: cobalt: Avoid freeing ALSA private data twice {CVE-2026-89895}\n   * CVE-2026-89858\n     - scsi: qla2xxx: Bound image count in qla2x00_update_fru_versions()\n       {CVE-2026-89858}\n   * CVE-2026-89864\n     - scsi: qla2xxx: Bound i2c-\u003elength in I2C bsg handlers {CVE-2026-89864}\n   * CVE-2026-89784\n     - SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6\n       {CVE-2026-89784}\n   * CVE-2026-89789\n     - gtp: add synchronize_net() in gtp_newlink() error path to prevent\n       use-after-free {CVE-2026-89789}\n   * CVE-2026-89786\n     - ext4: fix out-of-bounds read in ext4_read_inline_dir() {CVE-2026-89786}\n   * CVE-2023-54047\n     - drm/rockchip: dw_hdmi: cleanup drm encoder during unbind {CVE-2023-54047}\n   * CVE-2025-40146\n     - blk-mq: fix potential deadlock while nr_requests grown {CVE-2025-40146}\n   * CVE-2026-68367\n     - usb: gadget: f_tcm: synchronize delayed set_alt with teardown\n       {CVE-2026-68367}\n   * CVE-2026-89659\n     - NFSD: Prevent client use-after-free during delegation revoke\n       {CVE-2026-89659}\n   * CVE-2026-80841\n     - net/packet: defer vmalloc TX_RING free until skbs finish {CVE-2026-80841}\n   * CVE-2026-80925\n     - vlan: fix skb_under_panic and races when toggling HW VLAN offload\n       {CVE-2026-80925}\n   * CVE-2026-64557\n     - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb()\n       {CVE-2026-64557}\n   * CVE-2026-72390\n     - net/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF\n       {CVE-2026-72390}\n   * CVE-2026-80994\n     - net: openvswitch: fix flow mask use-after-free on flow deletion\n       {CVE-2026-80994}\n   * CVE-2026-74752\n     - sctp: validate cookie AUTH state before use {CVE-2026-74752}\n   * CVE-2026-68404\n     - wifi: cfg80211: use wiphy work for socket owner autodisconnect\n       {CVE-2026-68404}\n   * CVE-2026-72413\n     - sctp: fix err_chunk memory leaks in INIT handling {CVE-2026-72413}\n   * CVE-2026-63921\n     - ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate(). {CVE-2026-63921}\n   * CVE-2026-23050\n     - pNFS: Fix a deadlock when returning a delegation during open()\n       {CVE-2026-23050}\n   * CVE-2025-68190\n     - drm/amdgpu/atom: Check kcalloc() for WS buffer in\n       amdgpu_atom_execute_table_locked() {CVE-2025-68190}\n   * CVE-2026-63933\n     - iio: gyro: adis16260: fix division by zero in write_raw {CVE-2026-63933}\n   * CVE-2023-54287\n     - tty: serial: imx: disable Ageing Timer interrupt request irq\n       {CVE-2023-54287}\n   * CVE-2026-63891\n     - thunderbolt: property: Cap recursion depth in __tb_property_parse_dir()\n       {CVE-2026-63891}\n   * CVE-2024-50076\n     - vt: prevent kernel-infoleak in con_font_get() {CVE-2024-50076}\n   * CVE-2021-47659\n     - drm/plane: Move range check for format_count earlier {CVE-2021-47659}\n   * CVE-2026-63983\n     - net/sched: fix packet loop on netem when duplicate is on {CVE-2026-63983}\n   * CVE-2025-68342\n     - can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before\n       accessing data {CVE-2025-68342}\n   * CVE-2026-63922\n     - ipv6: exthdrs: refresh nh after handling HAO option {CVE-2026-63922}\n   * CVE-2023-54007\n     - vmci_host: fix a race condition in vmci_host_poll() causing GPF\n       {CVE-2023-54007}\n   * CVE-2025-68173\n     - ftrace: Fix softlockup in ftrace_module_enable {CVE-2025-68173}\n   * CVE-2022-50864\n     - nilfs2: fix shift-out-of-bounds due to too large exponent of block size\n       {CVE-2022-50864}\n   * CVE-2026-63905\n     - usbip: vudc: Fix use after free bug in vudc_remove due to race condition\n       {CVE-2026-63905}\n   * CVE-2025-40100\n     - btrfs: do not assert we found block group item when creating free space\n       tree {CVE-2025-40100}\n   * CVE-2025-40333\n     - f2fs: fix infinite loop in __insert_extent_tree() {CVE-2025-40333}\n   * CVE-2025-40160\n     - xen/events: Return -EEXIST for bound VIRQs {CVE-2025-40160}\n   * CVE-2026-63888\n     - scsi: target: iscsi: Fix CRC overread and double-free in\n       iscsit_handle_text_cmd() {CVE-2026-63888}\n   * CVE-2025-68778\n     - btrfs: don't log conflicting inode if it's a dir moved in the current\n       transaction {CVE-2025-68778}\n   * CVE-2023-53799\n     - crypto: api - Use work queue in crypto_destroy_instance {CVE-2023-53799}\n   * CVE-2026-64009\n     - xfrm: Check for underflow in xfrm_state_mtu {CVE-2026-64009}\n   * CVE-2023-54226\n     - af_unix: Fix data races around sk-\u003esk_shutdown. {CVE-2023-54226}\n   * CVE-2022-50770\n     - ocfs2: fix memory leak in ocfs2_mount_volume() {CVE-2022-50770}\n   * CVE-2022-4994\n     - KVM: x86: wean fast IN from emulator_pio_in {CVE-2022-4994}\n   * CVE-2024-50135\n     - nvme-pci: fix race condition between reset and nvme_dev_disable()\n       {CVE-2024-50135}\n   * CVE-2026-64011\n     - nfc: llcp: Fix use-after-free in llcp_sock_release() {CVE-2026-64011}\n   * CVE-2026-80786\n     - fbdev: Wrap user-invoked calls to fb_set_var() in helper {CVE-2026-80786}\n   * CVE-2022-50774\n     - crypto: qat - fix DMA transfer direction {CVE-2022-50774}\n   * CVE-2023-53834\n     - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match\n       {CVE-2023-53834}\n   * CVE-2026-74444\n     - drm/vmwgfx: validate DRAW_PRIMITIVES header size before division\n       {CVE-2026-74444}\n   * CVE-2022-50764\n     - ipv6/sit: use DEV_STATS_INC() to avoid data-races {CVE-2022-50764}\n   * CVE-2026-80794\n     - nfc: nci: fix uninit-value in the RF discover/activated NTF handlers\n       {CVE-2026-80794}\n   * CVE-2026-80854\n     - usb: gadget: f_tcm: keep port count until LUN teardown completes\n       {CVE-2026-80854}\n   * CVE-2026-80576\n     - drm/amdgpu: reject oversized IBs with per-ring packet limits\n       {CVE-2026-80576}\n   * CVE-2026-80843\n     - xfrm: fix xfrm_state_construct() auth-trunc leak {CVE-2026-80843}\n   * CVE-2026-74540\n     - Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp {CVE-2026-74540}\n   * CVE-2026-74510\n     - Bluetooth: mgmt: fix UAF in pair command cancellation {CVE-2026-74510}\n   * CVE-2026-68108\n     - drm/amdgpu/vce: fix integer overflow in image size {CVE-2026-68108}\n   * CVE-2026-74283\n     - tipc: require net admin for TIPCv2 netlink mutators {CVE-2026-74283}\n   * CVE-2026-64470\n     - Bluetooth: btusb: fix use-after-free on marvell probe failure\n       {CVE-2026-64470}\n   * CVE-2026-80783\n     - HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event()\n       {CVE-2026-80783}\n   * CVE-2026-72336\n     - Bluetooth: 6lowpan: hold L2CAP conn across debugfs control\n       {CVE-2026-72336}\n   * CVE-2026-74637\n     - perf/core: Fix group leader use-after-free after sibling detach\n       {CVE-2026-74637}\n   * CVE-2026-72398\n     - sctp: add INIT verification after cookie unpacking {CVE-2026-72398}\n   * CVE-2026-72323\n     - ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() {CVE-2026-72323}\n   * CVE-2026-72084\n     - scsi: target: Bound PR-OUT TransportID parsing to the received buffer\n       {CVE-2026-72084}\n   * CVE-2026-80807\n     - nilfs2: reject invalid block index in GC ioctl {CVE-2026-80807}\n   * CVE-2026-80890\n     - sctp: reject stale cookies with mismatched verification tags\n       {CVE-2026-80890}\n   * CVE-2026-80733\n     - net: remove WARN_ON_ONCE() from sk_mc_loop() {CVE-2026-80733}\n   * CVE-2026-80742\n     - af_packet: Don't send zero-byte data in tpacket_snd(). {CVE-2026-80742}\n   * CVE-2026-64550\n     - net: qualcomm: rmnet: validate MAP frame length before ingress parsing\n       {CVE-2026-64550}\n   * CVE-2026-80828\n     - ALSA: usb-audio: Complete cleanup after system-resume errors\n       {CVE-2026-80828}\n   * CVE-2026-72047\n     - ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit\n       {CVE-2026-72047}\n   * CVE-2026-74479\n     - net: pktgen: fix proc entry use-after-free {CVE-2026-74479}\n   * CVE-2026-80764\n     - Bluetooth: hci_event: fix LE list UAF on reset {CVE-2026-80764}\n   * CVE-2026-74341\n     - wifi: wcn36xx: fix heap overflow from oversized firmware HAL response\n       {CVE-2026-74341}\n   * CVE-2026-63826\n     - fbdev: fix use-after-free in store_modes() {CVE-2026-63826}\n   * CVE-2026-80782\n     - HID: magicmouse: do not keep a stale msc-\u003einput if no input is claimed\n       {CVE-2026-80782}\n   * CVE-2026-80798\n     - nfc: llcp: reject PDUs shorter than the LLCP header {CVE-2026-80798}\n   * CVE-2026-74649\n     - staging: rtl8723bs: fix missing shared-key auth challenge length check\n       {CVE-2026-74649}\n   * CVE-2026-68398\n     - ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF\n       {CVE-2026-68398}\n   * CVE-2026-80907\n     - drm/amdgpu: Fix UVD dpb min size calculation for H264 {CVE-2026-80907}\n   * CVE-2026-74651\n     - staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() {CVE-2026-74651}\n   * CVE-2026-72070\n     - wifi: libertas_tf: fix use-after-free in lbtf_free_adapter()\n       {CVE-2026-72070}\n   * CVE-2026-74580\n     - vhost: reset the vring metadata cache on vring reconfiguration\n       {CVE-2026-74580}\n   * CVE-2026-64583\n     - usb: gadget: udc: bdc: free IRQ and drain func_wake_notify before teardown\n       {CVE-2026-64583}\n   * CVE-2026-72255\n     - netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst\n       {CVE-2026-72255}\n   * CVE-2026-72374\n     - afs: Fix callback service message parsers to pass through -EAGAIN\n       {CVE-2026-72374}\n   * CVE-2026-68190\n     - staging: rtl8723bs: fix OOB reads in rtw_get_wps_ie() {CVE-2026-68190}\n   * CVE-2026-74689\n     - net/atm: fix slab-out-of-bounds read in vcc_setsockopt() {CVE-2026-74689}\n   * CVE-2026-80599\n     - batman-adv: dat: ensure accessible eth_hdr proto field {CVE-2026-80599}\n   * CVE-2026-74609\n     - tipc: read le-\u003elink under the node lock in tipc_node_link_down()\n       {CVE-2026-74609}\n   * CVE-2026-68414\n     - wifi: cfg80211: cancel sched scan results work on unregister\n       {CVE-2026-68414}\n   * CVE-2026-72472\n     - nfs: use nfsi-\u003erwsem to protect traversal of the file lock list\n       {CVE-2026-72472}\n   * CVE-2026-80796\n     - nfc: nci: add data_len bound checks to activation parameter extractors\n       {CVE-2026-80796}\n   * CVE-2026-80864\n     - RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp\n       {CVE-2026-80864}\n   * CVE-2026-80797\n     - nfc: pn533: purge fragmented skbs during cleanup {CVE-2026-80797}\n   * CVE-2026-72085\n     - scsi: xen: scsiback: Free unsubmitted command instead of double-putting it\n       {CVE-2026-72085}\n   * CVE-2026-74436\n     - rxrpc: serialize kernel accept preallocation with socket teardown\n       {CVE-2026-74436}\n   * CVE-2026-64582\n     - RDMA/rxe: Fix a use-after-free problem in rxe_mmap {CVE-2026-64582}\n   * CVE-2026-74641\n     - ALSA: usx2y: bound the hwdep mmap fault offset {CVE-2026-74641}\n   * CVE-2026-74744\n     - ipvlan: inherit needed_headroom and needed_tailroom from phy_dev\n       {CVE-2026-74744}\n   * CVE-2026-74282\n     - tipc: prevent snt_unacked underflow on CONN_ACK {CVE-2026-74282}\n   * CVE-2026-80800\n     - nfc: llcp: bound the connect_sn TLV walk to the skb {CVE-2026-80800}\n   * CVE-2026-74730\n     - NFS: Pin the 'struct nfs_server' during a FREE_STATEID call\n       {CVE-2026-74730}\n   * CVE-2026-80863\n     - RDMA/rxe: Fix OOB in free_rd_atomic_resources() {CVE-2026-80863}\n   * CVE-2026-68198\n     - wifi: ath6kl: fix use-after-free in aggr_reset_state() {CVE-2026-68198}\n   * CVE-2026-74550\n     - net: do not send ICMP/NDISC Redirects when peer allocation fails\n       {CVE-2026-74550}\n   * CVE-2026-80785\n     - fbdev: serialize mode sysfs access with lock_fb_info() {CVE-2026-80785}\n   * CVE-2026-80755\n     - selinux: reject a permission value exceeding the class permission count\n       {CVE-2026-80755}\n   * CVE-2026-68155\n     - libceph: Reject monmaps advertising zero monitors {CVE-2026-68155}\n   * CVE-2026-68160\n     - ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()\n       {CVE-2026-68160}\n   * CVE-2026-74628\n     - net/x25: fix use-after-free of the socket by its timers {CVE-2026-74628}\n   * CVE-2026-74569\n     - netfilter: nf_conntrack_sip: widen NAT rewrite delta to s32 in\n       sip_help_tcp() {CVE-2026-74569}\n   * CVE-2026-74289\n     - ipv4: fib: Don't dump dying fib_info in fib_leaf_notify().\n       {CVE-2026-74289}\n   * CVE-2026-80908\n     - drm/amdgpu: Reject UVD message with dimensions above 4096 {CVE-2026-80908}\n   * CVE-2026-74359\n     - configfs_lookup(): don't leave -\u003es_dentry dangling on failure\n       {CVE-2026-74359}\n   * CVE-2026-72322\n     - ipv6: mcast: Fix potential UAF in MLD delayed work {CVE-2026-72322}\n   * CVE-2026-74350\n     - ocfs2: validate fast symlink target during inode read {CVE-2026-74350}\n   * CVE-2026-80812\n     - ALSA: dummy: Check card index validity at probe {CVE-2026-80812}\n   * CVE-2026-68142\n     - geneve: require CAP_NET_ADMIN in the device netns for changelink\n       {CVE-2026-68142}\n   * CVE-2026-72383\n     - sctp: fix addr_wq_timer race in sctp_free_addr_wq() {CVE-2026-72383}\n   * CVE-2026-80824\n     - usb: usbfs: fix use-after-free of usb_device in usbdev_release()\n       {CVE-2026-80824}\n   * CVE-2026-74387\n     - ALSA: seq: midi: Serialize output teardown with event_input\n       {CVE-2026-74387}\n   * CVE-2026-80847\n     - tcp: clamp route advmss to TCP_MIN_MSS {CVE-2026-80847}\n   * CVE-2026-80570\n     - Input: synaptics-rmi4 - zero report size on F54 work error\n       {CVE-2026-80570}\n   * CVE-2026-72476\n     - dmaengine: Fix possible use after free {CVE-2026-72476}\n   * CVE-2026-89476\n     - sctp: fix stream-\u003eoutcnt underflow on duplicate RECONF responses\n       {CVE-2026-89476}\n   * CVE-2026-89574\n     - dm array: validate array block headers on read {CVE-2026-89574}\n   * CVE-2026-89545\n     - sunrpc: defer rq_argp and rq_resp free until after RCU grace period\n       {CVE-2026-89545}\n   * CVE-2026-89462\n     - power: supply: max17040: propagate register read errors {CVE-2026-89462}\n   * CVE-2026-89733\n     - usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and\n       uvc_function_unbind() {CVE-2026-89733}\n   * CVE-2026-89484\n     - lockd: fix NULL dereference on lockowner allocation failure\n       {CVE-2026-89484}\n   * CVE-2026-80996\n     - net: l2tp: do not propagate multicast notification errors {CVE-2026-80996}\n   * CVE-2026-89656\n     - libceph: reject buckets with mismatched CRUSH ids {CVE-2026-89656}\n   * CVE-2026-89531\n     - svcrdma: Reject connection when transport allocation fails\n       {CVE-2026-89531}\n   * CVE-2026-89441\n     - mmc: via-sdmmc: cancel card-detect work on remove {CVE-2026-89441}\n   * CVE-2026-89537\n     - SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2\n       {CVE-2026-89537}\n   * CVE-2026-80976\n     - seg6: reset IP6CB after IPv6 decapsulation {CVE-2026-80976}\n   * CVE-2026-89553\n     - nouveau/gem: reserve the bo in the info ioctl around the vma lookup\n       {CVE-2026-89553}\n   * CVE-2026-89492\n     - ocfs2: validate directory-index entry counts when reading metadata\n       {CVE-2026-89492}\n   * CVE-2026-80974\n     - mfd: sm501: Fix potential memory leaks during remove {CVE-2026-80974}\n   * CVE-2026-89550\n     - SUNRPC: svcauth_gss: enforce krb5 token minimum length {CVE-2026-89550}\n   * CVE-2026-89542\n     - SUNRPC: harden gss_krb5_unwrap_v2 against short tokens {CVE-2026-89542}\n   * CVE-2026-64014\n     - Input: usbtouchscreen - clamp NEXIO data_len/x_len to URB buffer size\n       {CVE-2026-64014}\n   * CVE-2026-63916\n     - HID: wacom: Fix OOB write in wacom_hid_set_device_mode() {CVE-2026-63916}\n   * CVE-2026-63892\n     - thunderbolt: property: Reject dir_len \u003c 4 to prevent size_t underflow\n       {CVE-2026-63892}\n   * CVE-2026-64010\n     - nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() {CVE-2026-64010}\n   * CVE-2026-63954\n     - hpfs: fix a crash if hpfs_map_dnode_bitmap fails {CVE-2026-63954}\n   * CVE-2026-63927\n     - usb: dwc2: Fix use after free in debug code {CVE-2026-63927}\n   * CVE-2026-63893\n     - thunderbolt: property: Reject u32 wrap in tb_property_entry_valid()\n       {CVE-2026-63893}\n   * CVE-2026-63915\n     - nfc: hci: fix out-of-bounds read in HCP header parsing {CVE-2026-63915}\n   * CVE-2026-63904\n     - usb: usbtmc: check URB actual_length for interrupt-IN notifications\n       {CVE-2026-63904}\n   * CVE-2026-63957\n     - USB: serial: safe_serial: fix memory corruption with small endpoint\n       {CVE-2026-63957}\n   * CVE-2025-68750\n     - usb: potential integer overflow in usbg_make_tpg() {CVE-2025-68750}\n   * CVE-2023-54150\n     - drm/amd: Fix an out of bounds error in BIOS parser {CVE-2023-54150}\n   * CVE-2026-63908\n     - Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem\n       {CVE-2026-63908}\n   * CVE-2026-63934\n     - iio: gyro: itg3200: fix i2c read into the wrong stack location\n       {CVE-2026-63934}\n   * CVE-2026-80819\n     - Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept\n       {CVE-2026-80819}\n   * CVE-2026-72234\n     - batman-adv: access unicast_ttvn skb-\u003edata only after skb realloc\n       {CVE-2026-72234}\n   * CVE-2026-68357\n     - watchdog: pretimeout: Fix UAF in watchdog_unregister_governor()\n       {CVE-2026-68357}\n   * CVE-2026-74588\n     - sctp: keep chunk-\u003etransport in step with the list it is queued on\n       {CVE-2026-74588}\n   * CVE-2026-68373\n     - wifi: at76c50x-usb: avoid length underflow in at76_guess_freq()\n       {CVE-2026-68373}\n   * CVE-2026-74556\n     - scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection\n       buffer {CVE-2026-74556}\n   * CVE-2026-64483\n     - ALSA: firewire: isight: bound the sample count to the packet payload\n       {CVE-2026-64483}\n   * CVE-2026-63814\n     - f2fs: validate ACL entry sizes in f2fs_acl_from_disk() {CVE-2026-63814}\n   * CVE-2026-64505\n     - usb: gadget: function: rndis: add length check for header {CVE-2026-64505}\n   * CVE-2026-72233\n     - batman-adv: bla: reacquire gw address after skb realloc {CVE-2026-72233}\n   * CVE-2026-80801\n     - nfc: microread: validate target discovery payload lengths {CVE-2026-80801}\n   * CVE-2026-68121\n     - pppoe: reload header pointer after dev_hard_header() {CVE-2026-68121}\n   * CVE-2026-74597\n     - ip6_tunnel: clear skb2-\u003ecb[] in ip6ip6_err() {CVE-2026-74597}\n   * CVE-2026-80752\n     - Input: psxpad-spi - set driver data before use {CVE-2026-80752}\n   * CVE-2026-89555\n     - mpls: reload header after pskb_may_pull() {CVE-2026-89555}\n   * CVE-2026-89504\n     - regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving\n       dangling of_node pointer {CVE-2026-89504}\n   * CVE-2026-81001\n     - slip: fix use-after-free in sl_sync() {CVE-2026-81001}\n   * CVE-2026-89569\n     - Bluetooth: RFCOMM: serialize security confirmation handling\n       {CVE-2026-89569}\n   * CVE-2026-89539\n     - SUNRPC: reject duplicate CREDS_VALUE options {CVE-2026-89539}\n   * CVE-2026-89761\n     - apparmor: fix out-of-bounds write when null terminating a label vec\n       {CVE-2026-89761}\n   * CVE-2026-89494\n     - ocfs2: validate lengths in dlm_mig_lockres_handler {CVE-2026-89494}\n   * CVE-2026-89548\n     - SUNRPC: always drain cache_cleaner before destroying a cache_detail\n       {CVE-2026-89548}\n   * CVE-2026-89478\n     - sctp: drop a chunk if its transport was removed {CVE-2026-89478}\n   * CVE-2026-89487\n     - openvswitch: only skb_tx_error() a packet we are about to drop\n       {CVE-2026-89487}\n   * CVE-2026-89477\n     - sctp: fix NULL deref on untransmitted RECONF completion {CVE-2026-89477}\n   * CVE-2026-89495\n     - ocfs2: bound namelen in dlm_migrate_request_handler {CVE-2026-89495}\n   * CVE-2026-89729\n     - HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature\n       {CVE-2026-89729}\n   * CVE-2026-89742\n     - rapidio: mport_cdev: fix use-after-free in dma_req_free() {CVE-2026-89742}\n   * CVE-2026-89607\n     - ecryptfs: reject oversized encrypted_key_size in parse_tag_3_packet\n       {CVE-2026-89607}\n   * CVE-2026-80918\n     - HID: core: fix number/pointer type confusion on long items\n       {CVE-2026-80918}\n   * CVE-2026-64372\n     - cpufreq: pcc: fix use-after-free and double free in _OSC evaluation\n       {CVE-2026-64372}\n   * CVE-2026-64423\n     - ipv4: igmp: remove multicast group from hash table on device destruction\n       {CVE-2026-64423}\n   * CVE-2026-64323\n     - udf: validate VAT header length against the VAT inode size\n       {CVE-2026-64323}\n   * CVE-2026-64322\n     - udf: validate sparing table length as an entry count, not a byte count\n       {CVE-2026-64322}\n   * CVE-2026-64452\n     - 6lowpan: fix NHC entry use-after-free on error path {CVE-2026-64452}\n   * CVE-2026-64351\n     - net: usb: kalmia: bound RX frame length in kalmia_rx_fixup()\n       {CVE-2026-64351}\n   * CVE-2026-64343\n     - USB: ldusb: fix use-after-free on disconnect race {CVE-2026-64343}\n   * CVE-2026-64318\n     - partitions: aix: bound the pp_count scan to the ppe array {CVE-2026-64318}\n   * CVE-2026-46208\n     - batman-adv: correct the del_timer_sync() rationale in batadv_tp_stop_all()\n       {CVE-2026-46208}\n   * CVE-2023-53039\n     - HID: intel-ish-hid: ipc: set dev-\u003edevc before the first dev_err()\n       {CVE-2023-53039}\n   * Miscellaneous upstream changes\n     - driver core: generalize driver_override in struct device\n   * Bump ABI 4.15.0-266","status":"published","published":"2026-10-13T07:29:42Z","modified":"2026-10-26T09:43:23.934683476Z","updated_at":"2026-11-02T15:43:50.599064Z"},{"id":"CLSA-2026-1791878869","title":"Fix of 274 CVEs","description":"   * CVE-2026-53091\n     - xfrm: Don't clobber inner headers when already set {CVE-2026-53091}\n     - net: account for encap headers in qdisc pkt len {CVE-2026-53091}\n   * CVE-2026-93803\n     - wifi: libipw: fix key index receive bound checks {CVE-2026-93803}\n   * CVE-2026-93286\n     - net: appletalk: fix NULL pointer dereference in aarp_send_ddp()\n       {CVE-2026-93286}\n   * CVE-2026-93280\n     - greybus: audio: bound the topology section sizes against the fetched size\n       {CVE-2026-93280}\n   * CVE-2026-93213\n     - of: fix out-of-bounds read in of_alias_scan() stem parser {CVE-2026-93213}\n   * CVE-2026-93802\n     - wifi: rsi: validate beacon length before fixed buffer copy\n       {CVE-2026-93802}\n   * CVE-2026-93206\n     - PCI/proc: Use file_ns_capable() when checking config space read access\n       {CVE-2026-93206}\n   * CVE-2026-97448\n     - ACPICA: Add validation for node in acpi_ns_build_normalized_path()\n       {CVE-2026-97448}\n   * CVE-2026-97408\n     - Bluetooth: L2CAP: validate connectionless PSM length {CVE-2026-97408}\n   * CVE-2026-93268\n     - ext4: skip extra isize expansion during mount to prevent deadlock\n       {CVE-2026-93268}\n   * CVE-2026-93782\n     - vhost-scsi: flush backend after device ioctls {CVE-2026-93782}\n   * CVE-2026-93783\n     - Bluetooth: RFCOMM: validate skb length in rfcomm_recv_frame\n       {CVE-2026-93783}\n   * CVE-2026-97455\n     - ACPICA: Fix use-after-free in acpi_ds_terminate_control_method()\n       {CVE-2026-97455}\n   * CVE-2026-93807\n     - wifi: rsi: avoid reading TKIP MIC keys for non-TKIP ciphers\n       {CVE-2026-93807}\n   * CVE-2026-93808\n     - ALSA: usb-audio: caiaq: validate EP1 reply lengths {CVE-2026-93808}\n   * CVE-2026-89938\n     - iio: chemical: atlas-sensor: use iio_trigger_poll_nested() to fix remove\n       UAF {CVE-2026-89938}\n   * CVE-2026-89927\n     - KVM: x86: hyper-v: Clamp stimer deadline to avoid livelock\n       {CVE-2026-89927}\n   * CVE-2026-89949\n     - batman-adv: dat: avoid unaligned fault in IP extraction {CVE-2026-89949}\n   * CVE-2026-89912\n     - KVM: arm64: vgic-its: Don't dereference a NULL collection on ITT save\n       {CVE-2026-89912}\n   * CVE-2026-89932\n     - KVM: nVMX: Always flush vpid02 on first use {CVE-2026-89932}\n   * CVE-2026-89833\n     - f2fs: fix to avoid potential deadloop in f2fs_fsync_node_pages()\n       {CVE-2026-89833}\n   * CVE-2026-90045\n     - USB: gadget: ffs: fix mm lifetime handling {CVE-2026-90045}\n   * CVE-2026-89854\n     - scsi: qla2xxx: Fix cs84xx use-after-free on host teardown {CVE-2026-89854}\n   * CVE-2026-90015\n     - xhci: fix lost bounce buffers on TDs spanning several ring segments\n       {CVE-2026-90015}\n   * CVE-2026-89979\n     - ALSA: pcm: Fix race between non-atomic ops and trigger-start\n       {CVE-2026-89979}\n   * CVE-2026-89852\n     - scsi: qla2xxx: Zero mailbox struct in qla2x00_get_firmware_state()\n       {CVE-2026-89852}\n   * CVE-2026-89861\n     - scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition()\n       {CVE-2026-89861}\n   * CVE-2026-89859\n     - scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak\n       {CVE-2026-89859}\n   * CVE-2026-90036\n     - NFSD: Prevent client use-after-free during blocked-lock reaping\n       {CVE-2026-90036}\n   * CVE-2026-89987\n     - mm/huge_memory: transfer the pmd dirty bit to the folio on zap\n       {CVE-2026-89987}\n   * CVE-2026-89799\n     - bpf: Disable preemption in bpf_get_stackid {CVE-2026-89799}\n   * CVE-2026-90032\n     - media: usbtv: keep device alive while ALSA card exists {CVE-2026-90032}\n   * CVE-2026-89822\n     - drm/i915: Guard against NULL driver_data in i915_pci_probe()\n       {CVE-2026-89822}\n   * CVE-2026-89929\n     - KVM: nVM: Ensure INVVPID is emulated on the correct physical CPU\n       {CVE-2026-89929}\n   * CVE-2026-89840\n     - f2fs: validate MOVE_RANGE destination size {CVE-2026-89840}\n   * CVE-2026-89913\n     - KVM: arm64: vgic-v3: take an LPI reference in vgic_v3_save_pending_tables\n       {CVE-2026-89913}\n   * CVE-2026-89865\n     - scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers\n       {CVE-2026-89865}\n   * CVE-2026-90000\n     - HID: rmi: fix OOB access with undersized RMI reports {CVE-2026-90000}\n   * CVE-2026-89972\n     - nvme: add missing SRCU grace period in error path {CVE-2026-89972}\n   * CVE-2026-90049\n     - net: skbuff: don't skb_tx_error() the source skb in skb_zerocopy()\n       {CVE-2026-90049}\n   * CVE-2026-89856\n     - scsi: qla2xxx: Clamp MSI-X derived queue counts to avoid truncation\n       {CVE-2026-89856}\n   * CVE-2026-90037\n     - NFSD: Prevent client use-after-free during close_lru reaping\n       {CVE-2026-90037}\n   * CVE-2026-89948\n     - batman-adv: bla: fix freeing of claims on meshif deletion {CVE-2026-89948}\n   * CVE-2026-90023\n     - usb: gadget: f_mass_storage: fix null pointer dereference in\n       fsg_common_set_num_buffers() {CVE-2026-90023}\n   * CVE-2026-90020\n     - USB: gadget: fix NULL pointer dereference in gadget_dev_ioctl()\n       {CVE-2026-90020}\n   * CVE-2026-89838\n     - f2fs: limit recovery filename logging to stored length {CVE-2026-89838}\n   * CVE-2026-89848\n     - scsi: qla2xxx: Quiesce response IRQ before freeing request queue\n       {CVE-2026-89848}\n   * CVE-2026-90017\n     - staging: rtl8723bs: fix OOB read in rtw_action_frame_parse()\n       {CVE-2026-90017}\n   * CVE-2026-89897\n     - media: cec: Serialize exclusive follower delivery {CVE-2026-89897}\n   * CVE-2026-89877\n     - media: saa7164: fix cleanup on resource allocation failure\n       {CVE-2026-89877}\n   * CVE-2026-89952\n     - mtd: rawnand: validate ONFI extended parameter page sections\n       {CVE-2026-89952}\n   * CVE-2026-90016\n     - staging: rtl8723bs: fix OOB read in rtw_restruct_wmm_ie() {CVE-2026-90016}\n   * CVE-2026-89999\n     - HID: wacom: validate report length in wacom_intuos_pro2_bt_irq\n       {CVE-2026-89999}\n   * CVE-2026-90044\n     - usb: gadget: f_fs: Fix Use-After-Free in AIO error path {CVE-2026-90044}\n   * CVE-2026-90029\n     - usb: storage: realtek_cr: fix use-after-free on disconnect\n       {CVE-2026-90029}\n   * CVE-2026-89783\n     - xfrm6: fix out-of-bounds write in xfrm6_input_addr() when secpath is full\n       {CVE-2026-89783}\n   * CVE-2026-89778\n     - isofs: fix out-of-bounds page array access on empty zisofs block\n       {CVE-2026-89778}\n   * CVE-2026-89845\n     - scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry()\n       {CVE-2026-89845}\n   * CVE-2026-89946\n     - ASoC: cs35l33: drain threaded IRQ before runtime suspend {CVE-2026-89946}\n   * CVE-2026-89846\n     - scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read\n       {CVE-2026-89846}\n   * CVE-2026-89965\n     - nvdimm/btt: reject an arena whose nfree is below the lane count\n       {CVE-2026-89965}\n   * CVE-2026-89945\n     - ASoC: cs35l34: drain threaded IRQ before runtime suspend {CVE-2026-89945}\n   * CVE-2026-89953\n     - mtd: mtdoops: free page bitmap when the backing MTD is removed\n       {CVE-2026-89953}\n   * CVE-2026-89855\n     - scsi: qla2xxx: Serialize flash version read in reset handler\n       {CVE-2026-89855}\n   * CVE-2026-89936\n     - iio: dac: m62332: Fix regulator reference count imbalance {CVE-2026-89936}\n   * CVE-2026-90031\n     - usb-storage: ene_ub6250: fix race between scan work and probe\n       {CVE-2026-90031}\n   * CVE-2026-89901\n     - media: airspy: use vb2_video_unregister_device() on disconnect to fix NULL\n       deref {CVE-2026-89901}\n   * CVE-2026-89878\n     - media: s2255: check firmware size before reading trailing marker\n       {CVE-2026-89878}\n   * CVE-2026-89890\n     - media: go7007: defer the ALSA v4l2 put until card release {CVE-2026-89890}\n   * CVE-2026-89893\n     - media: cx23885: cancel NetUP CI work before teardown {CVE-2026-89893}\n   * CVE-2026-89951\n     - batman-adv: fix stale receive device on merged fragments {CVE-2026-89951}\n   * CVE-2026-90034\n     - usb: image: mdc800: change kmalloc() to kzalloc() {CVE-2026-90034}\n   * CVE-2026-90033\n     - ALSA: usb-audio: fix OOB write in snd_usbmidi_us122l_output()\n       {CVE-2026-90033}\n   * CVE-2026-90007\n     - scsi: pm8001: Use rollback index when freeing MSI-X vectors\n       {CVE-2026-90007}\n   * CVE-2026-90011\n     - scsi: target: iscsi: Reserve a terminator byte for the login payload\n       {CVE-2026-90011}\n   * CVE-2026-90013\n     - tracing: Take trace_array reference when opening options file\n       {CVE-2026-90013}\n   * CVE-2026-89843\n     - scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak\n       {CVE-2026-89843}\n   * CVE-2026-89982\n     - i2c: mux: Fix channel node leak on adapter add failure {CVE-2026-89982}\n   * CVE-2026-89997\n     - dm: fix resume-vs-remove race {CVE-2026-89997}\n   * CVE-2026-90019\n     - usb: gadget: fix null pointer dereference in usb_put_function_instance()\n       {CVE-2026-90019}\n   * CVE-2026-89895\n     - media: cobalt: Avoid freeing ALSA private data twice {CVE-2026-89895}\n   * CVE-2026-89858\n     - scsi: qla2xxx: Bound image count in qla2x00_update_fru_versions()\n       {CVE-2026-89858}\n   * CVE-2026-89864\n     - scsi: qla2xxx: Bound i2c-\u003elength in I2C bsg handlers {CVE-2026-89864}\n   * CVE-2026-89784\n     - SUNRPC: check rpc_sockaddr2uaddr() return value in rpcb_register_inet4/6\n       {CVE-2026-89784}\n   * CVE-2026-89789\n     - gtp: add synchronize_net() in gtp_newlink() error path to prevent\n       use-after-free {CVE-2026-89789}\n   * CVE-2026-89786\n     - ext4: fix out-of-bounds read in ext4_read_inline_dir() {CVE-2026-89786}\n   * CVE-2023-54047\n     - drm/rockchip: dw_hdmi: cleanup drm encoder during unbind {CVE-2023-54047}\n   * CVE-2025-40146\n     - blk-mq: fix potential deadlock while nr_requests grown {CVE-2025-40146}\n   * CVE-2026-68367\n     - usb: gadget: f_tcm: synchronize delayed set_alt with teardown\n       {CVE-2026-68367}\n   * CVE-2026-89659\n     - NFSD: Prevent client use-after-free during delegation revoke\n       {CVE-2026-89659}\n   * CVE-2026-80841\n     - net/packet: defer vmalloc TX_RING free until skbs finish {CVE-2026-80841}\n   * CVE-2026-80925\n     - vlan: fix skb_under_panic and races when toggling HW VLAN offload\n       {CVE-2026-80925}\n   * CVE-2026-64557\n     - Bluetooth: L2CAP: Fix use-after-free in l2cap_sock_new_connection_cb()\n       {CVE-2026-64557}\n   * CVE-2026-72390\n     - net/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF\n       {CVE-2026-72390}\n   * CVE-2026-80994\n     - net: openvswitch: fix flow mask use-after-free on flow deletion\n       {CVE-2026-80994}\n   * CVE-2026-74752\n     - sctp: validate cookie AUTH state before use {CVE-2026-74752}\n   * CVE-2026-68404\n     - wifi: cfg80211: use wiphy work for socket owner autodisconnect\n       {CVE-2026-68404}\n   * CVE-2026-72413\n     - sctp: fix err_chunk memory leaks in INIT handling {CVE-2026-72413}\n   * CVE-2026-63921\n     - ip6: vti: Use ip6_tnl.net in vti6_siocdevprivate(). {CVE-2026-63921}\n   * CVE-2026-23050\n     - pNFS: Fix a deadlock when returning a delegation during open()\n       {CVE-2026-23050}\n   * CVE-2025-68190\n     - drm/amdgpu/atom: Check kcalloc() for WS buffer in\n       amdgpu_atom_execute_table_locked() {CVE-2025-68190}\n   * CVE-2026-63933\n     - iio: gyro: adis16260: fix division by zero in write_raw {CVE-2026-63933}\n   * CVE-2023-54287\n     - tty: serial: imx: disable Ageing Timer interrupt request irq\n       {CVE-2023-54287}\n   * CVE-2026-63891\n     - thunderbolt: property: Cap recursion depth in __tb_property_parse_dir()\n       {CVE-2026-63891}\n   * CVE-2024-50076\n     - vt: prevent kernel-infoleak in con_font_get() {CVE-2024-50076}\n   * CVE-2021-47659\n     - drm/plane: Move range check for format_count earlier {CVE-2021-47659}\n   * CVE-2026-63983\n     - net/sched: fix packet loop on netem when duplicate is on {CVE-2026-63983}\n   * CVE-2025-68342\n     - can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before\n       accessing data {CVE-2025-68342}\n   * CVE-2026-63922\n     - ipv6: exthdrs: refresh nh after handling HAO option {CVE-2026-63922}\n   * CVE-2023-54007\n     - vmci_host: fix a race condition in vmci_host_poll() causing GPF\n       {CVE-2023-54007}\n   * CVE-2025-68173\n     - ftrace: Fix softlockup in ftrace_module_enable {CVE-2025-68173}\n   * CVE-2022-50864\n     - nilfs2: fix shift-out-of-bounds due to too large exponent of block size\n       {CVE-2022-50864}\n   * CVE-2026-63905\n     - usbip: vudc: Fix use after free bug in vudc_remove due to race condition\n       {CVE-2026-63905}\n   * CVE-2025-40100\n     - btrfs: do not assert we found block group item when creating free space\n       tree {CVE-2025-40100}\n   * CVE-2025-40333\n     - f2fs: fix infinite loop in __insert_extent_tree() {CVE-2025-40333}\n   * CVE-2025-40160\n     - xen/events: Return -EEXIST for bound VIRQs {CVE-2025-40160}\n   * CVE-2026-63888\n     - scsi: target: iscsi: Fix CRC overread and double-free in\n       iscsit_handle_text_cmd() {CVE-2026-63888}\n   * CVE-2025-68778\n     - btrfs: don't log conflicting inode if it's a dir moved in the current\n       transaction {CVE-2025-68778}\n   * CVE-2023-53799\n     - crypto: api - Use work queue in crypto_destroy_instance {CVE-2023-53799}\n   * CVE-2026-64009\n     - xfrm: Check for underflow in xfrm_state_mtu {CVE-2026-64009}\n   * CVE-2023-54226\n     - af_unix: Fix data races around sk-\u003esk_shutdown. {CVE-2023-54226}\n   * CVE-2022-50770\n     - ocfs2: fix memory leak in ocfs2_mount_volume() {CVE-2022-50770}\n   * CVE-2022-4994\n     - KVM: x86: wean fast IN from emulator_pio_in {CVE-2022-4994}\n   * CVE-2024-50135\n     - nvme-pci: fix race condition between reset and nvme_dev_disable()\n       {CVE-2024-50135}\n   * CVE-2026-64011\n     - nfc: llcp: Fix use-after-free in llcp_sock_release() {CVE-2026-64011}\n   * CVE-2026-80786\n     - fbdev: Wrap user-invoked calls to fb_set_var() in helper {CVE-2026-80786}\n   * CVE-2022-50774\n     - crypto: qat - fix DMA transfer direction {CVE-2022-50774}\n   * CVE-2023-53834\n     - iio: adc: ina2xx: avoid NULL pointer dereference on OF device match\n       {CVE-2023-53834}\n   * CVE-2026-74444\n     - drm/vmwgfx: validate DRAW_PRIMITIVES header size before division\n       {CVE-2026-74444}\n   * CVE-2022-50764\n     - ipv6/sit: use DEV_STATS_INC() to avoid data-races {CVE-2022-50764}\n   * CVE-2026-80794\n     - nfc: nci: fix uninit-value in the RF discover/activated NTF handlers\n       {CVE-2026-80794}\n   * CVE-2026-80854\n     - usb: gadget: f_tcm: keep port count until LUN teardown completes\n       {CVE-2026-80854}\n   * CVE-2026-80576\n     - drm/amdgpu: reject oversized IBs with per-ring packet limits\n       {CVE-2026-80576}\n   * CVE-2026-80843\n     - xfrm: fix xfrm_state_construct() auth-trunc leak {CVE-2026-80843}\n   * CVE-2026-74540\n     - Bluetooth: L2CAP: fix UAF in l2cap_le_connect_rsp {CVE-2026-74540}\n   * CVE-2026-74510\n     - Bluetooth: mgmt: fix UAF in pair command cancellation {CVE-2026-74510}\n   * CVE-2026-68108\n     - drm/amdgpu/vce: fix integer overflow in image size {CVE-2026-68108}\n   * CVE-2026-74283\n     - tipc: require net admin for TIPCv2 netlink mutators {CVE-2026-74283}\n   * CVE-2026-64470\n     - Bluetooth: btusb: fix use-after-free on marvell probe failure\n       {CVE-2026-64470}\n   * CVE-2026-80783\n     - HID: magicmouse: prevent unbounded recursion in magicmouse_raw_event()\n       {CVE-2026-80783}\n   * CVE-2026-72336\n     - Bluetooth: 6lowpan: hold L2CAP conn across debugfs control\n       {CVE-2026-72336}\n   * CVE-2026-74637\n     - perf/core: Fix group leader use-after-free after sibling detach\n       {CVE-2026-74637}\n   * CVE-2026-72398\n     - sctp: add INIT verification after cookie unpacking {CVE-2026-72398}\n   * CVE-2026-72323\n     - ipv4: igmp: Fix potential UAF in igmp_gq_start_timer() {CVE-2026-72323}\n   * CVE-2026-72084\n     - scsi: target: Bound PR-OUT TransportID parsing to the received buffer\n       {CVE-2026-72084}\n   * CVE-2026-80807\n     - nilfs2: reject invalid block index in GC ioctl {CVE-2026-80807}\n   * CVE-2026-80890\n     - sctp: reject stale cookies with mismatched verification tags\n       {CVE-2026-80890}\n   * CVE-2026-80733\n     - net: remove WARN_ON_ONCE() from sk_mc_loop() {CVE-2026-80733}\n   * CVE-2026-80742\n     - af_packet: Don't send zero-byte data in tpacket_snd(). {CVE-2026-80742}\n   * CVE-2026-64550\n     - net: qualcomm: rmnet: validate MAP frame length before ingress parsing\n       {CVE-2026-64550}\n   * CVE-2026-80828\n     - ALSA: usb-audio: Complete cleanup after system-resume errors\n       {CVE-2026-80828}\n   * CVE-2026-72047\n     - ieee802154: ca8210: fix pointer truncation in kfifo on 64-bit\n       {CVE-2026-72047}\n   * CVE-2026-74479\n     - net: pktgen: fix proc entry use-after-free {CVE-2026-74479}\n   * CVE-2026-80764\n     - Bluetooth: hci_event: fix LE list UAF on reset {CVE-2026-80764}\n   * CVE-2026-74341\n     - wifi: wcn36xx: fix heap overflow from oversized firmware HAL response\n       {CVE-2026-74341}\n   * CVE-2026-63826\n     - fbdev: fix use-after-free in store_modes() {CVE-2026-63826}\n   * CVE-2026-80782\n     - HID: magicmouse: do not keep a stale msc-\u003einput if no input is claimed\n       {CVE-2026-80782}\n   * CVE-2026-80798\n     - nfc: llcp: reject PDUs shorter than the LLCP header {CVE-2026-80798}\n   * CVE-2026-74649\n     - staging: rtl8723bs: fix missing shared-key auth challenge length check\n       {CVE-2026-74649}\n   * CVE-2026-68398\n     - ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF\n       {CVE-2026-68398}\n   * CVE-2026-80907\n     - drm/amdgpu: Fix UVD dpb min size calculation for H264 {CVE-2026-80907}\n   * CVE-2026-74651\n     - staging: rtl8723bs: fix OOB read in rtw_get_wpa_ie() {CVE-2026-74651}\n   * CVE-2026-72070\n     - wifi: libertas_tf: fix use-after-free in lbtf_free_adapter()\n       {CVE-2026-72070}\n   * CVE-2026-74580\n     - vhost: reset the vring metadata cache on vring reconfiguration\n       {CVE-2026-74580}\n   * CVE-2026-64583\n     - usb: gadget: udc: bdc: free IRQ and drain func_wake_notify before teardown\n       {CVE-2026-64583}\n   * CVE-2026-72255\n     - netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst\n       {CVE-2026-72255}\n   * CVE-2026-72374\n     - afs: Fix callback service message parsers to pass through -EAGAIN\n       {CVE-2026-72374}\n   * CVE-2026-68190\n     - staging: rtl8723bs: fix OOB reads in rtw_get_wps_ie() {CVE-2026-68190}\n   * CVE-2026-74689\n     - net/atm: fix slab-out-of-bounds read in vcc_setsockopt() {CVE-2026-74689}\n   * CVE-2026-80599\n     - batman-adv: dat: ensure accessible eth_hdr proto field {CVE-2026-80599}\n   * CVE-2026-74609\n     - tipc: read le-\u003elink under the node lock in tipc_node_link_down()\n       {CVE-2026-74609}\n   * CVE-2026-68414\n     - wifi: cfg80211: cancel sched scan results work on unregister\n       {CVE-2026-68414}\n   * CVE-2026-72472\n     - nfs: use nfsi-\u003erwsem to protect traversal of the file lock list\n       {CVE-2026-72472}\n   * CVE-2026-80796\n     - nfc: nci: add data_len bound checks to activation parameter extractors\n       {CVE-2026-80796}\n   * CVE-2026-80864\n     - RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp\n       {CVE-2026-80864}\n   * CVE-2026-80797\n     - nfc: pn533: purge fragmented skbs during cleanup {CVE-2026-80797}\n   * CVE-2026-72085\n     - scsi: xen: scsiback: Free unsubmitted command instead of double-putting it\n       {CVE-2026-72085}\n   * CVE-2026-74436\n     - rxrpc: serialize kernel accept preallocation with socket teardown\n       {CVE-2026-74436}\n   * CVE-2026-64582\n     - RDMA/rxe: Fix a use-after-free problem in rxe_mmap {CVE-2026-64582}\n   * CVE-2026-74641\n     - ALSA: usx2y: bound the hwdep mmap fault offset {CVE-2026-74641}\n   * CVE-2026-74744\n     - ipvlan: inherit needed_headroom and needed_tailroom from phy_dev\n       {CVE-2026-74744}\n   * CVE-2026-74282\n     - tipc: prevent snt_unacked underflow on CONN_ACK {CVE-2026-74282}\n   * CVE-2026-80800\n     - nfc: llcp: bound the connect_sn TLV walk to the skb {CVE-2026-80800}\n   * CVE-2026-74730\n     - NFS: Pin the 'struct nfs_server' during a FREE_STATEID call\n       {CVE-2026-74730}\n   * CVE-2026-80863\n     - RDMA/rxe: Fix OOB in free_rd_atomic_resources() {CVE-2026-80863}\n   * CVE-2026-68198\n     - wifi: ath6kl: fix use-after-free in aggr_reset_state() {CVE-2026-68198}\n   * CVE-2026-74550\n     - net: do not send ICMP/NDISC Redirects when peer allocation fails\n       {CVE-2026-74550}\n   * CVE-2026-80785\n     - fbdev: serialize mode sysfs access with lock_fb_info() {CVE-2026-80785}\n   * CVE-2026-80755\n     - selinux: reject a permission value exceeding the class permission count\n       {CVE-2026-80755}\n   * CVE-2026-68155\n     - libceph: Reject monmaps advertising zero monitors {CVE-2026-68155}\n   * CVE-2026-68160\n     - ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps()\n       {CVE-2026-68160}\n   * CVE-2026-74628\n     - net/x25: fix use-after-free of the socket by its timers {CVE-2026-74628}\n   * CVE-2026-74569\n     - netfilter: nf_conntrack_sip: widen NAT rewrite delta to s32 in\n       sip_help_tcp() {CVE-2026-74569}\n   * CVE-2026-74289\n     - ipv4: fib: Don't dump dying fib_info in fib_leaf_notify().\n       {CVE-2026-74289}\n   * CVE-2026-80908\n     - drm/amdgpu: Reject UVD message with dimensions above 4096 {CVE-2026-80908}\n   * CVE-2026-74359\n     - configfs_lookup(): don't leave -\u003es_dentry dangling on failure\n       {CVE-2026-74359}\n   * CVE-2026-72322\n     - ipv6: mcast: Fix potential UAF in MLD delayed work {CVE-2026-72322}\n   * CVE-2026-74350\n     - ocfs2: validate fast symlink target during inode read {CVE-2026-74350}\n   * CVE-2026-80812\n     - ALSA: dummy: Check card index validity at probe {CVE-2026-80812}\n   * CVE-2026-68142\n     - geneve: require CAP_NET_ADMIN in the device netns for changelink\n       {CVE-2026-68142}\n   * CVE-2026-72383\n     - sctp: fix addr_wq_timer race in sctp_free_addr_wq() {CVE-2026-72383}\n   * CVE-2026-80824\n     - usb: usbfs: fix use-after-free of usb_device in usbdev_release()\n       {CVE-2026-80824}\n   * CVE-2026-74387\n     - ALSA: seq: midi: Serialize output teardown with event_input\n       {CVE-2026-74387}\n   * CVE-2026-80847\n     - tcp: clamp route advmss to TCP_MIN_MSS {CVE-2026-80847}\n   * CVE-2026-80570\n     - Input: synaptics-rmi4 - zero report size on F54 work error\n       {CVE-2026-80570}\n   * CVE-2026-72476\n     - dmaengine: Fix possible use after free {CVE-2026-72476}\n   * CVE-2026-89476\n     - sctp: fix stream-\u003eoutcnt underflow on duplicate RECONF responses\n       {CVE-2026-89476}\n   * CVE-2026-89574\n     - dm array: validate array block headers on read {CVE-2026-89574}\n   * CVE-2026-89545\n     - sunrpc: defer rq_argp and rq_resp free until after RCU grace period\n       {CVE-2026-89545}\n   * CVE-2026-89462\n     - power: supply: max17040: propagate register read errors {CVE-2026-89462}\n   * CVE-2026-89733\n     - usb: gadget: uvc: fix dangling pointers in uvc_function_bind() and\n       uvc_function_unbind() {CVE-2026-89733}\n   * CVE-2026-89484\n     - lockd: fix NULL dereference on lockowner allocation failure\n       {CVE-2026-89484}\n   * CVE-2026-80996\n     - net: l2tp: do not propagate multicast notification errors {CVE-2026-80996}\n   * CVE-2026-89656\n     - libceph: reject buckets with mismatched CRUSH ids {CVE-2026-89656}\n   * CVE-2026-89531\n     - svcrdma: Reject connection when transport allocation fails\n       {CVE-2026-89531}\n   * CVE-2026-89441\n     - mmc: via-sdmmc: cancel card-detect work on remove {CVE-2026-89441}\n   * CVE-2026-89537\n     - SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2\n       {CVE-2026-89537}\n   * CVE-2026-80976\n     - seg6: reset IP6CB after IPv6 decapsulation {CVE-2026-80976}\n   * CVE-2026-89553\n     - nouveau/gem: reserve the bo in the info ioctl around the vma lookup\n       {CVE-2026-89553}\n   * CVE-2026-89492\n     - ocfs2: validate directory-index entry counts when reading metadata\n       {CVE-2026-89492}\n   * CVE-2026-80974\n     - mfd: sm501: Fix potential memory leaks during remove {CVE-2026-80974}\n   * CVE-2026-89550\n     - SUNRPC: svcauth_gss: enforce krb5 token minimum length {CVE-2026-89550}\n   * CVE-2026-89542\n     - SUNRPC: harden gss_krb5_unwrap_v2 against short tokens {CVE-2026-89542}\n   * CVE-2026-64014\n     - Input: usbtouchscreen - clamp NEXIO data_len/x_len to URB buffer size\n       {CVE-2026-64014}\n   * CVE-2026-63916\n     - HID: wacom: Fix OOB write in wacom_hid_set_device_mode() {CVE-2026-63916}\n   * CVE-2026-63892\n     - thunderbolt: property: Reject dir_len \u003c 4 to prevent size_t underflow\n       {CVE-2026-63892}\n   * CVE-2026-64010\n     - nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() {CVE-2026-64010}\n   * CVE-2026-63954\n     - hpfs: fix a crash if hpfs_map_dnode_bitmap fails {CVE-2026-63954}\n   * CVE-2026-63927\n     - usb: dwc2: Fix use after free in debug code {CVE-2026-63927}\n   * CVE-2026-63893\n     - thunderbolt: property: Reject u32 wrap in tb_property_entry_valid()\n       {CVE-2026-63893}\n   * CVE-2026-63915\n     - nfc: hci: fix out-of-bounds read in HCP header parsing {CVE-2026-63915}\n   * CVE-2026-63904\n     - usb: usbtmc: check URB actual_length for interrupt-IN notifications\n       {CVE-2026-63904}\n   * CVE-2026-63957\n     - USB: serial: safe_serial: fix memory corruption with small endpoint\n       {CVE-2026-63957}\n   * CVE-2025-68750\n     - usb: potential integer overflow in usbg_make_tpg() {CVE-2025-68750}\n   * CVE-2023-54150\n     - drm/amd: Fix an out of bounds error in BIOS parser {CVE-2023-54150}\n   * CVE-2026-63908\n     - Input: atmel_mxt_ts - fix boundary check in mxt_prepare_cfg_mem\n       {CVE-2026-63908}\n   * CVE-2026-63934\n     - iio: gyro: itg3200: fix i2c read into the wrong stack location\n       {CVE-2026-63934}\n   * CVE-2026-80819\n     - Bluetooth: RFCOMM: take rfcomm_mutex for the deferred setup accept\n       {CVE-2026-80819}\n   * CVE-2026-72234\n     - batman-adv: access unicast_ttvn skb-\u003edata only after skb realloc\n       {CVE-2026-72234}\n   * CVE-2026-68357\n     - watchdog: pretimeout: Fix UAF in watchdog_unregister_governor()\n       {CVE-2026-68357}\n   * CVE-2026-74588\n     - sctp: keep chunk-\u003etransport in step with the list it is queued on\n       {CVE-2026-74588}\n   * CVE-2026-68373\n     - wifi: at76c50x-usb: avoid length underflow in at76_guess_freq()\n       {CVE-2026-68373}\n   * CVE-2026-74556\n     - scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection\n       buffer {CVE-2026-74556}\n   * CVE-2026-64483\n     - ALSA: firewire: isight: bound the sample count to the packet payload\n       {CVE-2026-64483}\n   * CVE-2026-63814\n     - f2fs: validate ACL entry sizes in f2fs_acl_from_disk() {CVE-2026-63814}\n   * CVE-2026-64505\n     - usb: gadget: function: rndis: add length check for header {CVE-2026-64505}\n   * CVE-2026-72233\n     - batman-adv: bla: reacquire gw address after skb realloc {CVE-2026-72233}\n   * CVE-2026-80801\n     - nfc: microread: validate target discovery payload lengths {CVE-2026-80801}\n   * CVE-2026-68121\n     - pppoe: reload header pointer after dev_hard_header() {CVE-2026-68121}\n   * CVE-2026-74597\n     - ip6_tunnel: clear skb2-\u003ecb[] in ip6ip6_err() {CVE-2026-74597}\n   * CVE-2026-80752\n     - Input: psxpad-spi - set driver data before use {CVE-2026-80752}\n   * CVE-2026-89555\n     - mpls: reload header after pskb_may_pull() {CVE-2026-89555}\n   * CVE-2026-89504\n     - regulator: as3722_get_regulator_dt_data: fix premature of_node_put leaving\n       dangling of_node pointer {CVE-2026-89504}\n   * CVE-2026-81001\n     - slip: fix use-after-free in sl_sync() {CVE-2026-81001}\n   * CVE-2026-89569\n     - Bluetooth: RFCOMM: serialize security confirmation handling\n       {CVE-2026-89569}\n   * CVE-2026-89539\n     - SUNRPC: reject duplicate CREDS_VALUE options {CVE-2026-89539}\n   * CVE-2026-89761\n     - apparmor: fix out-of-bounds write when null terminating a label vec\n       {CVE-2026-89761}\n   * CVE-2026-89494\n     - ocfs2: validate lengths in dlm_mig_lockres_handler {CVE-2026-89494}\n   * CVE-2026-89548\n     - SUNRPC: always drain cache_cleaner before destroying a cache_detail\n       {CVE-2026-89548}\n   * CVE-2026-89478\n     - sctp: drop a chunk if its transport was removed {CVE-2026-89478}\n   * CVE-2026-89487\n     - openvswitch: only skb_tx_error() a packet we are about to drop\n       {CVE-2026-89487}\n   * CVE-2026-89477\n     - sctp: fix NULL deref on untransmitted RECONF completion {CVE-2026-89477}\n   * CVE-2026-89495\n     - ocfs2: bound namelen in dlm_migrate_request_handler {CVE-2026-89495}\n   * CVE-2026-89729\n     - HID: sensor-hub: Fix out-of-bounds write in sensor_hub_get_feature\n       {CVE-2026-89729}\n   * CVE-2026-89742\n     - rapidio: mport_cdev: fix use-after-free in dma_req_free() {CVE-2026-89742}\n   * CVE-2026-89607\n     - ecryptfs: reject oversized encrypted_key_size in parse_tag_3_packet\n       {CVE-2026-89607}\n   * CVE-2026-80918\n     - HID: core: fix number/pointer type confusion on long items\n       {CVE-2026-80918}\n   * CVE-2026-64372\n     - cpufreq: pcc: fix use-after-free and double free in _OSC evaluation\n       {CVE-2026-64372}\n   * CVE-2026-64423\n     - ipv4: igmp: remove multicast group from hash table on device destruction\n       {CVE-2026-64423}\n   * CVE-2026-64323\n     - udf: validate VAT header length against the VAT inode size\n       {CVE-2026-64323}\n   * CVE-2026-64322\n     - udf: validate sparing table length as an entry count, not a byte count\n       {CVE-2026-64322}\n   * CVE-2026-64452\n     - 6lowpan: fix NHC entry use-after-free on error path {CVE-2026-64452}\n   * CVE-2026-64351\n     - net: usb: kalmia: bound RX frame length in kalmia_rx_fixup()\n       {CVE-2026-64351}\n   * CVE-2026-64343\n     - USB: ldusb: fix use-after-free on disconnect race {CVE-2026-64343}\n   * CVE-2026-64318\n     - partitions: aix: bound the pp_count scan to the ppe array {CVE-2026-64318}\n   * CVE-2026-46208\n     - batman-adv: correct the del_timer_sync() rationale in batadv_tp_stop_all()\n       {CVE-2026-46208}\n   * CVE-2023-53039\n     - HID: intel-ish-hid: ipc: set dev-\u003edevc before the first dev_err()\n       {CVE-2023-53039}\n   * Miscellaneous upstream changes\n     - driver core: generalize driver_override in struct device\n   * Bump ABI 4.15.0-266","status":"published","published":"2026-10-21T23:59:33Z","modified":"2026-10-26T09:43:39.657580087Z","updated_at":"2026-11-02T15:43:50.599064Z"},{"id":"CVE-2025-68173","title":"ftrace: Fix softlockup in ftrace_module_enable","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nftrace: Fix softlockup in ftrace_module_enable\n\nA soft lockup was observed when loading amdgpu module.\nIf a module has a lot of tracable functions, multiple calls\nto kallsyms_lookup can spend too much time in RCU critical\nsection and with disabled preemption, causing kernel panic.\nThis is the same issue that was fixed in\ncommit d0b24b4e91fc (\"ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY\nkernels\") and commit 42ea22e754ba (\"ftrace: Add cond_resched() to\nftrace_graph_set_hash()\").\n\nFix it the same way by adding cond_resched() in ftrace_module_enable.","status":"published","published":"2025-12-16T13:42:53.106Z","modified":"2026-10-28T02:31:01.035422714Z","updated_at":"2026-11-02T15:44:52.53036Z"},{"id":"DEBIAN-CVE-2025-68173","description":"In the Linux kernel, the following vulnerability has been resolved:  ftrace: Fix softlockup in ftrace_module_enable  A soft lockup was observed when loading amdgpu module. If a module has a lot of tracable functions, multiple calls to kallsyms_lookup can spend too much time in RCU critical section and with disabled preemption, causing kernel panic. This is the same issue that was fixed in commit d0b24b4e91fc (\"ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY kernels\") and commit 42ea22e754ba (\"ftrace: Add cond_resched() to ftrace_graph_set_hash()\").  Fix it the same way by adding cond_resched() in ftrace_module_enable.","status":"published","published":"2025-12-16T14:15:49.213Z","modified":"2026-10-15T10:01:52.676771374Z","updated_at":"2026-11-02T15:45:48.025964Z"},{"id":"DLA-4436-1","title":"linux-6.1 - security update","status":"published","published":"2026-01-14T00:00:00Z","modified":"2026-01-14T13:15:02.066506Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"MGASA-2026-0017","title":"Updated kernel, kmod-virtualbox \u0026 kmod-xtables-addons packages fix security vulnerabilities","description":"Upstream kernel version 6.6.120 fixes bugs and vulnerabilities.\nThe kmod-virtualbox \u0026 kmod-xtables-addons packages have been updated to\nwork with this new kernel.\n","status":"published","published":"2026-01-24T20:25:04Z","modified":"2026-04-16T04:43:32.882687097Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"MGASA-2026-0018","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.120 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2026-01-26T20:03:34Z","modified":"2026-04-16T04:42:12.477260681Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"openSUSE-SU-2026:20416-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\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-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (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-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (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-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-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\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-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (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-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\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-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:49:52Z","modified":"2026-03-29T17:26:19.135696Z","updated_at":"2026-11-02T16:58:41.463445Z"},{"id":"ROOT-OS-DEBIAN-11-CVE-2025-68173","title":"CVE-2025-68173 in linux - Patched by Root","description":"Root has patched CVE-2025-68173 in the linux package for Root:Debian:11. Multiple fixed versions available.","status":"published","published":"2026-08-23T09:13:41Z","modified":"2026-08-23T10:18:30.318102911Z","updated_at":"2026-11-02T15:53:29.631993Z"},{"id":"ROOT-OS-DEBIAN-12-CVE-2025-68173","title":"CVE-2025-68173 in linux - Patched by Root","description":"Root has patched CVE-2025-68173 in the linux package for Root:Debian:12. Multiple fixed versions available.","status":"published","published":"2026-10-18T03:18:11Z","modified":"2026-10-18T04:16:36.124194407Z","updated_at":"2026-11-02T15:53:31.514195Z"},{"id":"ROOT-OS-UBUNTU-2204-CVE-2025-68173","title":"CVE-2025-68173 in linux - Patched by Root","description":"Root has patched CVE-2025-68173 in the linux package for Root:Ubuntu:22.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T13:52:25Z","modified":"2026-11-06T14:17:01.519504205Z","updated_at":"2026-11-06T14:57:22.237547Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2025-68173","title":"CVE-2025-68173 in linux - Patched by Root","description":"Root has patched CVE-2025-68173 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:56.2724662Z","updated_at":"2026-11-06T16:59:13.24938Z"},{"id":"SUSE-SU-2026:20838-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\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-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (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-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (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-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-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\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-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (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-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\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-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:48:43Z","modified":"2026-03-28T17:24:39.090411Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20873-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\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-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (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-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (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-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-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\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-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (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-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\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-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:52:20Z","modified":"2026-07-09T18:24:05.527764914Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:20931-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\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-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (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-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (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-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-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\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-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (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-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\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-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:48:43Z","modified":"2026-04-02T17:24:40.319019Z","updated_at":"2026-11-02T15:54:01.953589Z"},{"id":"SUSE-SU-2026:21284-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 16.0 kernel was updated to fix various security issues.\n\nThe following security issues were fixed:\n\n- CVE-2025-39753: gfs2: Set .migrate_folio in gfs2_{rgrp,meta}_aops (bsc#1249590).\n- CVE-2025-39964: crypto: af_alg - Disallow concurrent writes in af_alg_sendmsg (bsc#1251966).\n- CVE-2025-40099: cifs: parse_dfs_referrals: prevent oob on malformed input (bsc#1252911).\n- CVE-2025-40103: smb: client: Fix refcount leak for cifs_sb_tlink (bsc#1252924).\n- CVE-2025-40230: mm: prevent poison consumption when splitting THP (bsc#1254817).\n- CVE-2025-68173: ftrace: Fix softlockup in ftrace_module_enable (bsc#1255311).\n- CVE-2025-68186: ring-buffer: Do not warn in ring_buffer_map_get_reader() when reader catches up (bsc#1255144).\n- CVE-2025-68292: mm/memfd: fix information leak in hugetlb folios (bsc#1255148).\n- CVE-2025-68295: smb: client: fix memory leak in cifs_construct_tcon() (bsc#1255129).\n- CVE-2025-68329: tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs (bsc#1255490).\n- CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal (bsc#1255572).\n- CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset (bsc#1255721).\n- CVE-2025-68785: net: openvswitch: fix middle attribute validation in push_nsh() action (bsc#1256640).\n- CVE-2025-68810: KVM: Disallow toggling KVM_MEM_GUEST_MEMFD on an existing memslot (bsc#1256679).\n- CVE-2025-71071: iommu/mediatek: fix use-after-free on probe deferral (bsc#1256802).\n- CVE-2025-71104: KVM: x86: Fix VM hard lockup after prolonged inactivity with periodic HV timer (bsc#1256708).\n- CVE-2025-71125: tracing: Do not register unsupported perf events (bsc#1256784).\n- CVE-2025-71134: mm/page_alloc: change all pageblocks migrate type on coalescing (bsc#1256732).\n- CVE-2025-71161: dm-verity: disable recursive forward error correction (bsc#1257174).\n- CVE-2025-71184: btrfs: tracepoints: use btrfs_root_id() to get the id of a root (bsc#1257635).\n- CVE-2025-71193: phy: qcom-qusb2: Fix NULL pointer dereference on early suspend (bsc#1257686).\n- CVE-2025-71225: md: suspend array while updating raid_disks via sysfs (bsc#1258411).\n- CVE-2026-22979: net: fix memory leak in skb_segment_list for GRO packets (bsc#1257228).\n- CVE-2026-22998: nvme-tcp: fix NULL pointer dereferences in nvmet_tcp_build_pdu_iovec (bsc#1257209).\n- CVE-2026-23003: ip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv() (bsc#1257246).\n- CVE-2026-23004: dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list() (bsc#1257231).\n- CVE-2026-23010: ipv6: Fix use-after-free in inet6_addr_del() (bsc#1257332).\n- CVE-2026-23017: idpf: fix error handling in the init_task on load (bsc#1257552).\n- CVE-2026-23022: idpf: fix memory leak in idpf_vc_core_deinit() (bsc#1257581).\n- CVE-2026-23023: idpf: fix memory leak in idpf_vport_rel() (bsc#1257556).\n- CVE-2026-23024: idpf: fix memory leak of flow steer list on rmmod (bsc#1257572).\n- CVE-2026-23035: net/mlx5e: Pass netdev to mlx5e_destroy_netdev instead of priv (bsc#1257559).\n- CVE-2026-23042: idpf: fix aux device unplugging when rdma is not supported by vport (bsc#1257705).\n- CVE-2026-23047: libceph: make calc_target() set t-\u003epaused, not just clear it (bsc#1257682).\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-23064: net/sched: act_ife: avoid possible NULL deref (bsc#1257765).\n- CVE-2026-23066: rxrpc: Fix recvmsg() unconditional requeue (bsc#1257726).\n- CVE-2026-23068: spi: spi-sprd-adi: Fix double free in probe error path (bsc#1257805).\n- CVE-2026-23069: vsock/virtio: fix potential underflow in virtio_transport_get_credit() (bsc#1257755).\n- CVE-2026-23070: Octeontx2-af: Add proper checks for fwdata (bsc#1257709).\n- CVE-2026-23074: net/sched: Enforce that teql can only be used as root qdisc (bsc#1257749).\n- CVE-2026-23083: tools: ynl-gen: use big-endian netlink attribute types (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-23088: tracing: Fix crash on synthetic stacktrace field usage (bsc#1257814).\n- CVE-2026-23095: gue: Fix skb memleak with inner IP protocol 0 (bsc#1257808).\n- CVE-2026-23097: migrate: correct lock ordering for hugetlb file folios (bsc#1257815).\n- CVE-2026-23099: bonding: limit BOND_MODE_8023AD to Ethernet devices (bsc#1257816).\n- CVE-2026-23100: mm/hugetlb: fix hugetlb_pmd_shared() (bsc#1257817).\n- CVE-2026-23102: arm64/fpsimd: signal: Fix restoration of SVE context (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-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-23136: libceph: reset sparse-read state in osd_fault() (bsc#1258303).\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-23142: mm/damon/sysfs-scheme: cleanup access_pattern subdirs on scheme dir setup failure (bsc#1258289).\n- CVE-2026-23144: mm/damon/sysfs: cleanup attrs subdirs on context dir setup failure (bsc#1258290).\n- CVE-2026-23148: nvmet: fix race in nvmet_bio_done() leading to NULL pointer dereference (bsc#1258258).\n- CVE-2026-23154: net: fix segmentation of forwarding fraglist GRO (bsc#1258286).\n- CVE-2026-23161: mm/shmem, swap: fix race of truncate and swap entry split (bsc#1258355).\n- CVE-2026-23166: ice: Fix NULL pointer dereference in ice_vsi_set_napi_queues (bsc#1258272).\n- CVE-2026-23169: mptcp: fix race in mptcp_pm_nl_flush_addrs_doit() (bsc#1258389).\n- CVE-2026-23171: bonding: fix use-after-free due to enslave fail after slave array update (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-23189: ceph: fix NULL pointer dereference in ceph_mds_auth_match() (bsc#1258308).\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-23210: ice: Fix PTP NULL pointer dereference during VSI rebuild (bsc#1258517).\n- CVE-2026-23214: btrfs: reject new transactions if the fs is fully read-only (bsc#1258464).\n- CVE-2026-23223: xfs: fix UAF in xchk_btree_check_block_owner (bsc#1258483).\n- CVE-2026-23224: erofs: fix UAF issue for file-backed mounts w/ directio option (bsc#1258461).\n\nThe following non security issues were fixed:\n\n- ALSA: usb-audio: Update the number of packets properly at receiving (stable-fixes).\n- ALSA: usb-audio: fix broken logic in snd_audigy2nx_led_update() (git-fixes).\n- ASoC: SOF: ipc4-control: If there is no data do not send bytes update (git-fixes).\n- Add bugnumber to existing mana and mana_ib changes (bsc#1251135 bsc#1251971).\n- HID: apple: Add EPOMAKER TH87 to the non-apple keyboards list (bsc#1258455).\n- HID: intel-ish-hid: Update ishtp bus match to support device ID table (stable-fixes).\n- PCI/DOE: Poll DOE Busy bit for up to 1 second in pci_doe_send_req() (bsc#1255868).\n- PCI: Add ASPEED vendor ID to pci_ids.h (bsc#1258672)\n- PCI: Add PCI_BRIDGE_NO_ALIAS quirk for ASPEED AST1150 (bsc#1258672)\n- PM: sleep: wakeirq: Update outdated documentation comments (git-fixes).\n- Refresh and move upstreamed ath12k patch into sorted section\n- Update \"drm/mgag200: fix mgag200_bmc_stop_scanout()\" bug number (bsc#1258153)\n- add bugnumber to existing mana change (bsc#1252266).\n- arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS (bsc#1259329)\n- bonding: only set speed/duplex to unknown, if getting speed failed (bsc#1253691).\n- can: bcm: fix locking for bcm_op runtime updates (git-fixes).\n- clk: qcom: gcc-sm8450: Update the SDCC RCGs to use shared_floor_ops (git-fixes).\n- clocksource: Fix the CPUs' choice in the watchdog per CPU verification (bsc#1257818).\n- clocksource: Print durations for sync check unconditionally (bsc#1257818).\n- clocksource: Reduce watchdog readout delay limit to prevent false positives (bsc#1257818).\n- clocksource: Use pr_info() for \"Checking clocksource synchronization\" message (bsc#1257818).\n- dm: Fix deadlock when reloading a multipath table (bsc#1254928).\n- drm/i915/display: Add quirk to skip retraining of dp link (bsc#1253129).\n- ext4: fix iloc.bh leak in ext4_xattr_inode_update_ref (git-fixes).\n- gpiolib-acpi: Update file references in the Documentation and MAINTAINERS (git-fixes).\n- i3c: master: Update hot-join flag only on success (git-fixes).\n- ktls, sockmap: Fix missing uncharge operation (bsc#1252008).\n- media: qcom: camss: vfe: Fix out-of-bounds access in vfe_isr_reg_update() (git-fixes).\n- modpost: Ensure exported symbol namespaces are not quoted (bsc#1258489).\n- net: mana: Handle hardware recovery events when probing the device (bsc#1257466).\n- net: mana: Implement ndo_tx_timeout and serialize queue resets per port (bsc#1257472).\n- platform/x86/amd: amd_3d_vcache: Add AMD 3D V-Cache optimizer driver (jsc#PED-11563).\n- sched/core: Avoid direct access to hrtimer clockbase (bsc#1234634).\n- sched/deadline: Fix race in push_dl_task() (bsc#1234634).\n- sched/deadline: Stop dl_server before CPU goes offline (bsc#1234634).\n- sched/fair: Fix pelt clock sync when entering idle (bsc#1234634).\n- sched/fair: Fix pelt lost idle time detection (bsc#1234634).\n- staging: rtl8723bs: fix missing status update on sdio_alloc_irq() failure (stable-fixes).\n- wifi: cfg80211: Fix use_for flag update on BSS refresh (git-fixes).\n","status":"published","published":"2026-03-25T08:43:53Z","modified":"2026-04-28T18:24:35.206923Z","updated_at":"2026-11-02T15:54:02.312556Z"},{"id":"UBUNTU-CVE-2025-68173","description":"In the Linux kernel, the following vulnerability has been resolved: ftrace: Fix softlockup in ftrace_module_enable A soft lockup was observed when loading amdgpu module. If a module has a lot of tracable functions, multiple calls to kallsyms_lookup can spend too much time in RCU critical section and with disabled preemption, causing kernel panic. This is the same issue that was fixed in commit d0b24b4e91fc (\"ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY kernels\") and commit 42ea22e754ba (\"ftrace: Add cond_resched() to ftrace_graph_set_hash()\"). Fix it the same way by adding cond_resched() in ftrace_module_enable.","status":"published","published":"2025-12-16T14:15:00Z","modified":"2026-11-11T09:39:18.791944066Z","updated_at":"2026-11-11T10:01:08.538864Z"},{"id":"USN-8029-1","title":"linux, linux-raspi, 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  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Device frequency scaling framework;\n  - ARM SCMI message protocol;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - PCI Endpoint Test driver;\n  - VMware Balloon Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Mellanox platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - Memory management;\n  - Virtio network driver;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - io_uring subsystem;\n  - Kernel crash support code;\n  - Perf events;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - AMD SoC Alsa drivers;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045,\nCVE-2025-40046, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,\nCVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,\nCVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40072, CVE-2025-40073,\nCVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40082, CVE-2025-40084, CVE-2025-40085, CVE-2025-40086,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40097, CVE-2025-40098, CVE-2025-40099,\nCVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40113, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,\nCVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136,\nCVE-2025-40137, CVE-2025-40138, CVE-2025-40139, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,\nCVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149,\nCVE-2025-40150, CVE-2025-40152, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163,\nCVE-2025-40164, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175,\nCVE-2025-40176, CVE-2025-40177, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183,\nCVE-2025-40184, CVE-2025-40185, CVE-2025-40186, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40189, CVE-2025-40191, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40199, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40203, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210,\nCVE-2025-40211, CVE-2025-40212, CVE-2025-40213, CVE-2025-40217,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225,\nCVE-2025-40226, CVE-2025-40227, CVE-2025-40228, CVE-2025-40229,\nCVE-2025-40230, CVE-2025-40231, CVE-2025-40233, CVE-2025-40234,\nCVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40239, CVE-2025-40240, CVE-2025-40241, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40256,\nCVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40274,\nCVE-2025-40275, CVE-2025-40276, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40291,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295,\nCVE-2025-40296, CVE-2025-40297, CVE-2025-40298, CVE-2025-40299,\nCVE-2025-40301, CVE-2025-40302, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40316,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40326, CVE-2025-40327, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333,\nCVE-2025-40334, CVE-2025-40335, CVE-2025-40336, CVE-2025-40337,\nCVE-2025-40338, CVE-2025-40339, CVE-2025-40340, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40352, CVE-2025-40353, CVE-2025-40354, CVE-2025-40355,\nCVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359,\nCVE-2025-40360, CVE-2025-40362, CVE-2025-40363, CVE-2025-68167,\nCVE-2025-68168, CVE-2025-68169, CVE-2025-68170, CVE-2025-68171,\nCVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68181, CVE-2025-68182, CVE-2025-68183,\nCVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187,\nCVE-2025-68188, CVE-2025-68189, CVE-2025-68190, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68193, CVE-2025-68194, CVE-2025-68196,\nCVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200,\nCVE-2025-68201, CVE-2025-68202, CVE-2025-68204, CVE-2025-68205,\nCVE-2025-68206, CVE-2025-68207, CVE-2025-68208, CVE-2025-68209,\nCVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240,\nCVE-2025-68241, CVE-2025-68242, CVE-2025-68243, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68246, CVE-2025-68247, CVE-2025-68248,\nCVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253,\nCVE-2025-68309, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68314, CVE-2025-68315, CVE-2025-68316,\nCVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-12T09:15:01Z","modified":"2026-11-03T14:34:42.37518646Z","updated_at":"2026-11-03T15:16:54.00292Z"},{"id":"USN-8029-2","title":"linux-aws, 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  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Device frequency scaling framework;\n  - ARM SCMI message protocol;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - PCI Endpoint Test driver;\n  - VMware Balloon Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Mellanox platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - Memory management;\n  - Virtio network driver;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - io_uring subsystem;\n  - Kernel crash support code;\n  - Perf events;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - AMD SoC Alsa drivers;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045,\nCVE-2025-40046, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,\nCVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,\nCVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40072, CVE-2025-40073,\nCVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40082, CVE-2025-40084, CVE-2025-40085, CVE-2025-40086,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40097, CVE-2025-40098, CVE-2025-40099,\nCVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40113, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,\nCVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136,\nCVE-2025-40137, CVE-2025-40138, CVE-2025-40139, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,\nCVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149,\nCVE-2025-40150, CVE-2025-40152, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163,\nCVE-2025-40164, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175,\nCVE-2025-40176, CVE-2025-40177, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183,\nCVE-2025-40184, CVE-2025-40185, CVE-2025-40186, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40189, CVE-2025-40191, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40199, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40203, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210,\nCVE-2025-40211, CVE-2025-40212, CVE-2025-40213, CVE-2025-40217,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225,\nCVE-2025-40226, CVE-2025-40227, CVE-2025-40228, CVE-2025-40229,\nCVE-2025-40230, CVE-2025-40231, CVE-2025-40233, CVE-2025-40234,\nCVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40239, CVE-2025-40240, CVE-2025-40241, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40256,\nCVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40274,\nCVE-2025-40275, CVE-2025-40276, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40291,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295,\nCVE-2025-40296, CVE-2025-40297, CVE-2025-40298, CVE-2025-40299,\nCVE-2025-40301, CVE-2025-40302, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40316,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40326, CVE-2025-40327, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333,\nCVE-2025-40334, CVE-2025-40335, CVE-2025-40336, CVE-2025-40337,\nCVE-2025-40338, CVE-2025-40339, CVE-2025-40340, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40352, CVE-2025-40353, CVE-2025-40354, CVE-2025-40355,\nCVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359,\nCVE-2025-40360, CVE-2025-40362, CVE-2025-40363, CVE-2025-68167,\nCVE-2025-68168, CVE-2025-68169, CVE-2025-68170, CVE-2025-68171,\nCVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68181, CVE-2025-68182, CVE-2025-68183,\nCVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187,\nCVE-2025-68188, CVE-2025-68189, CVE-2025-68190, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68193, CVE-2025-68194, CVE-2025-68196,\nCVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200,\nCVE-2025-68201, CVE-2025-68202, CVE-2025-68204, CVE-2025-68205,\nCVE-2025-68206, CVE-2025-68207, CVE-2025-68208, CVE-2025-68209,\nCVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240,\nCVE-2025-68241, CVE-2025-68242, CVE-2025-68243, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68246, CVE-2025-68247, CVE-2025-68248,\nCVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253,\nCVE-2025-68309, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68314, CVE-2025-68315, CVE-2025-68316,\nCVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-17T12:49:18Z","modified":"2026-11-03T14:35:03.428875576Z","updated_at":"2026-11-03T15:16:36.034517Z"},{"id":"USN-8029-3","title":"linux-azure vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Device frequency scaling framework;\n  - ARM SCMI message protocol;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - PCI Endpoint Test driver;\n  - VMware Balloon Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Mellanox platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - Memory management;\n  - Virtio network driver;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - io_uring subsystem;\n  - Kernel crash support code;\n  - Perf events;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - AMD SoC Alsa drivers;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045,\nCVE-2025-40046, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,\nCVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,\nCVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40072, CVE-2025-40073,\nCVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40082, CVE-2025-40084, CVE-2025-40085, CVE-2025-40086,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40097, CVE-2025-40098, CVE-2025-40099,\nCVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40113, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,\nCVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136,\nCVE-2025-40137, CVE-2025-40138, CVE-2025-40139, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,\nCVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149,\nCVE-2025-40150, CVE-2025-40152, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163,\nCVE-2025-40164, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175,\nCVE-2025-40176, CVE-2025-40177, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183,\nCVE-2025-40184, CVE-2025-40185, CVE-2025-40186, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40189, CVE-2025-40191, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40199, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40203, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210,\nCVE-2025-40211, CVE-2025-40212, CVE-2025-40213, CVE-2025-40217,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225,\nCVE-2025-40226, CVE-2025-40227, CVE-2025-40228, CVE-2025-40229,\nCVE-2025-40230, CVE-2025-40231, CVE-2025-40233, CVE-2025-40234,\nCVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40239, CVE-2025-40240, CVE-2025-40241, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40256,\nCVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40274,\nCVE-2025-40275, CVE-2025-40276, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40291,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295,\nCVE-2025-40296, CVE-2025-40297, CVE-2025-40298, CVE-2025-40299,\nCVE-2025-40301, CVE-2025-40302, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40316,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40326, CVE-2025-40327, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333,\nCVE-2025-40334, CVE-2025-40335, CVE-2025-40336, CVE-2025-40337,\nCVE-2025-40338, CVE-2025-40339, CVE-2025-40340, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40352, CVE-2025-40353, CVE-2025-40354, CVE-2025-40355,\nCVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359,\nCVE-2025-40360, CVE-2025-40362, CVE-2025-40363, CVE-2025-68167,\nCVE-2025-68168, CVE-2025-68169, CVE-2025-68170, CVE-2025-68171,\nCVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68181, CVE-2025-68182, CVE-2025-68183,\nCVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187,\nCVE-2025-68188, CVE-2025-68189, CVE-2025-68190, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68193, CVE-2025-68194, CVE-2025-68196,\nCVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200,\nCVE-2025-68201, CVE-2025-68202, CVE-2025-68204, CVE-2025-68205,\nCVE-2025-68206, CVE-2025-68207, CVE-2025-68208, CVE-2025-68209,\nCVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240,\nCVE-2025-68241, CVE-2025-68242, CVE-2025-68243, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68246, CVE-2025-68247, CVE-2025-68248,\nCVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253,\nCVE-2025-68309, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68314, CVE-2025-68315, CVE-2025-68316,\nCVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-24T11:20:31Z","modified":"2026-11-03T14:35:00.15213949Z","updated_at":"2026-11-03T15:16:40.267874Z"},{"id":"USN-8030-1","title":"linux-gcp vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Device frequency scaling framework;\n  - ARM SCMI message protocol;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - PCI Endpoint Test driver;\n  - VMware Balloon Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Mellanox platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - Memory management;\n  - Virtio network driver;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - io_uring subsystem;\n  - Kernel crash support code;\n  - Perf events;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - AMD SoC Alsa drivers;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045,\nCVE-2025-40046, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,\nCVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,\nCVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40072, CVE-2025-40073,\nCVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40082, CVE-2025-40084, CVE-2025-40085, CVE-2025-40086,\nCVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40097, CVE-2025-40098, CVE-2025-40099,\nCVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40113, CVE-2025-40115,\nCVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,\nCVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136,\nCVE-2025-40137, CVE-2025-40138, CVE-2025-40139, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,\nCVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149,\nCVE-2025-40150, CVE-2025-40152, CVE-2025-40153, CVE-2025-40154,\nCVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163,\nCVE-2025-40164, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175,\nCVE-2025-40176, CVE-2025-40177, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40182, CVE-2025-40183, CVE-2025-40184,\nCVE-2025-40185, CVE-2025-40186, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40189, CVE-2025-40191, CVE-2025-40192, CVE-2025-40193,\nCVE-2025-40194, CVE-2025-40195, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40199, CVE-2025-40200, CVE-2025-40201, CVE-2025-40203,\nCVE-2025-40204, CVE-2025-40205, CVE-2025-40206, CVE-2025-40207,\nCVE-2025-40208, CVE-2025-40209, CVE-2025-40210, CVE-2025-40211,\nCVE-2025-40212, CVE-2025-40213, CVE-2025-40217, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40222,\nCVE-2025-40223, CVE-2025-40224, CVE-2025-40225, CVE-2025-40226,\nCVE-2025-40227, CVE-2025-40228, CVE-2025-40229, CVE-2025-40230,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40234, CVE-2025-40235,\nCVE-2025-40236, CVE-2025-40237, CVE-2025-40238, CVE-2025-40239,\nCVE-2025-40240, CVE-2025-40241, CVE-2025-40242, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40256, CVE-2025-40267,\nCVE-2025-40268, CVE-2025-40269, CVE-2025-40270, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40274, CVE-2025-40275,\nCVE-2025-40276, CVE-2025-40277, CVE-2025-40278, CVE-2025-40279,\nCVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283,\nCVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287,\nCVE-2025-40288, CVE-2025-40289, CVE-2025-40291, CVE-2025-40292,\nCVE-2025-40293, CVE-2025-40294, CVE-2025-40295, CVE-2025-40296,\nCVE-2025-40297, CVE-2025-40298, CVE-2025-40299, CVE-2025-40301,\nCVE-2025-40302, CVE-2025-40303, CVE-2025-40304, CVE-2025-40305,\nCVE-2025-40306, CVE-2025-40307, CVE-2025-40308, CVE-2025-40309,\nCVE-2025-40310, CVE-2025-40311, CVE-2025-40312, CVE-2025-40313,\nCVE-2025-40314, CVE-2025-40315, CVE-2025-40316, CVE-2025-40317,\nCVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40326,\nCVE-2025-40327, CVE-2025-40328, CVE-2025-40329, CVE-2025-40330,\nCVE-2025-40331, CVE-2025-40332, CVE-2025-40333, CVE-2025-40334,\nCVE-2025-40335, CVE-2025-40336, CVE-2025-40337, CVE-2025-40338,\nCVE-2025-40339, CVE-2025-40340, CVE-2025-40341, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40344, CVE-2025-40346, CVE-2025-40347,\nCVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40352,\nCVE-2025-40353, CVE-2025-40354, CVE-2025-40355, CVE-2025-40356,\nCVE-2025-40357, CVE-2025-40358, CVE-2025-40359, CVE-2025-40360,\nCVE-2025-40362, CVE-2025-40363, CVE-2025-68167, CVE-2025-68168,\nCVE-2025-68169, CVE-2025-68170, CVE-2025-68171, CVE-2025-68172,\nCVE-2025-68173, CVE-2025-68174, CVE-2025-68175, CVE-2025-68176,\nCVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180,\nCVE-2025-68181, CVE-2025-68182, CVE-2025-68183, CVE-2025-68184,\nCVE-2025-68185, CVE-2025-68186, CVE-2025-68187, CVE-2025-68188,\nCVE-2025-68189, CVE-2025-68190, CVE-2025-68191, CVE-2025-68192,\nCVE-2025-68193, CVE-2025-68194, CVE-2025-68196, CVE-2025-68197,\nCVE-2025-68198, CVE-2025-68199, CVE-2025-68200, CVE-2025-68201,\nCVE-2025-68202, CVE-2025-68204, CVE-2025-68205, CVE-2025-68206,\nCVE-2025-68207, CVE-2025-68208, CVE-2025-68209, CVE-2025-68210,\nCVE-2025-68211, CVE-2025-68239, CVE-2025-68240, CVE-2025-68241,\nCVE-2025-68242, CVE-2025-68243, CVE-2025-68244, CVE-2025-68245,\nCVE-2025-68246, CVE-2025-68247, CVE-2025-68248, CVE-2025-68249,\nCVE-2025-68250, CVE-2025-68251, CVE-2025-68253, CVE-2025-68309,\nCVE-2025-68310, CVE-2025-68311, CVE-2025-68312, CVE-2025-68313,\nCVE-2025-68314, CVE-2025-68315, CVE-2025-68316, CVE-2025-68317,\nCVE-2025-68318, CVE-2025-68319, CVE-2025-68320, CVE-2025-68321,\nCVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-12T09:39:54Z","modified":"2026-11-03T14:34:59.664448895Z","updated_at":"2026-11-03T15:16:40.267874Z"},{"id":"USN-8048-1","title":"linux-oem-6.17 vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - CXL (Compute Express Link) drivers;\n  - Device frequency scaling framework;\n  - ARM SCMI message protocol;\n  - GPIO subsystem;\n  - GPU drivers;\n  - Hardware monitoring drivers;\n  - HW tracing;\n  - InfiniBand drivers;\n  - Input Device (Miscellaneous) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - PCI Endpoint Test driver;\n  - VMware Balloon Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Mellanox platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - SCSI subsystem;\n  - SPI subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EROFS file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - GFS2 file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - Memory management;\n  - Virtio network driver;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - io_uring subsystem;\n  - Kernel crash support code;\n  - Perf events;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Ethernet bridge;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - ALSA framework;\n  - HD-audio driver;\n  - AMD SoC Alsa drivers;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40034, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040,\nCVE-2025-40041, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40045, CVE-2025-40046, CVE-2025-40047, CVE-2025-40048,\nCVE-2025-40049, CVE-2025-40050, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40054, CVE-2025-40055, CVE-2025-40056,\nCVE-2025-40057, CVE-2025-40058, CVE-2025-40059, CVE-2025-40060,\nCVE-2025-40061, CVE-2025-40062, CVE-2025-40063, CVE-2025-40064,\nCVE-2025-40065, CVE-2025-40066, CVE-2025-40067, CVE-2025-40068,\nCVE-2025-40069, CVE-2025-40070, CVE-2025-40071, CVE-2025-40072,\nCVE-2025-40073, CVE-2025-40074, CVE-2025-40075, CVE-2025-40076,\nCVE-2025-40077, CVE-2025-40078, CVE-2025-40079, CVE-2025-40080,\nCVE-2025-40081, CVE-2025-40082, CVE-2025-40084, CVE-2025-40085,\nCVE-2025-40086, CVE-2025-40087, CVE-2025-40088, CVE-2025-40089,\nCVE-2025-40091, CVE-2025-40092, CVE-2025-40093, CVE-2025-40094,\nCVE-2025-40095, CVE-2025-40096, CVE-2025-40097, CVE-2025-40098,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40102,\nCVE-2025-40103, CVE-2025-40104, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40110, CVE-2025-40111, CVE-2025-40112, CVE-2025-40113,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40117, CVE-2025-40118,\nCVE-2025-40119, CVE-2025-40120, CVE-2025-40121, CVE-2025-40122,\nCVE-2025-40123, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,\nCVE-2025-40127, CVE-2025-40129, CVE-2025-40130, CVE-2025-40131,\nCVE-2025-40132, CVE-2025-40133, CVE-2025-40134, CVE-2025-40135,\nCVE-2025-40136, CVE-2025-40137, CVE-2025-40138, CVE-2025-40139,\nCVE-2025-40140, CVE-2025-40141, CVE-2025-40142, CVE-2025-40143,\nCVE-2025-40145, CVE-2025-40146, CVE-2025-40147, CVE-2025-40148,\nCVE-2025-40149, CVE-2025-40150, CVE-2025-40151, CVE-2025-40152,\nCVE-2025-40153, CVE-2025-40154, CVE-2025-40155, CVE-2025-40156,\nCVE-2025-40158, CVE-2025-40159, CVE-2025-40160, CVE-2025-40161,\nCVE-2025-40162, CVE-2025-40163, CVE-2025-40164, CVE-2025-40165,\nCVE-2025-40166, CVE-2025-40167, CVE-2025-40168, CVE-2025-40169,\nCVE-2025-40170, CVE-2025-40171, CVE-2025-40173, CVE-2025-40174,\nCVE-2025-40175, CVE-2025-40176, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183,\nCVE-2025-40184, CVE-2025-40185, CVE-2025-40186, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40189, CVE-2025-40191, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40199, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40203, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210,\nCVE-2025-40211, CVE-2025-40212, CVE-2025-40213, CVE-2025-40217,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225,\nCVE-2025-40226, CVE-2025-40227, CVE-2025-40228, CVE-2025-40229,\nCVE-2025-40230, CVE-2025-40231, CVE-2025-40233, CVE-2025-40234,\nCVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40239, CVE-2025-40240, CVE-2025-40241, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40256,\nCVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40274,\nCVE-2025-40275, CVE-2025-40276, CVE-2025-40277, CVE-2025-40278,\nCVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282,\nCVE-2025-40283, CVE-2025-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40291,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295,\nCVE-2025-40296, CVE-2025-40297, CVE-2025-40298, CVE-2025-40299,\nCVE-2025-40301, CVE-2025-40302, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40316,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40326, CVE-2025-40327, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333,\nCVE-2025-40334, CVE-2025-40335, CVE-2025-40336, CVE-2025-40337,\nCVE-2025-40338, CVE-2025-40339, CVE-2025-40340, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40352, CVE-2025-40353, CVE-2025-40354, CVE-2025-40355,\nCVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359,\nCVE-2025-40360, CVE-2025-40362, CVE-2025-40363, CVE-2025-68167,\nCVE-2025-68168, CVE-2025-68169, CVE-2025-68170, CVE-2025-68171,\nCVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68181, CVE-2025-68182, CVE-2025-68183,\nCVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187,\nCVE-2025-68188, CVE-2025-68189, CVE-2025-68190, CVE-2025-68191,\nCVE-2025-68192, CVE-2025-68193, CVE-2025-68194, CVE-2025-68196,\nCVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200,\nCVE-2025-68201, CVE-2025-68202, CVE-2025-68204, CVE-2025-68205,\nCVE-2025-68206, CVE-2025-68207, CVE-2025-68208, CVE-2025-68209,\nCVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240,\nCVE-2025-68241, CVE-2025-68242, CVE-2025-68243, CVE-2025-68244,\nCVE-2025-68245, CVE-2025-68246, CVE-2025-68247, CVE-2025-68248,\nCVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253,\nCVE-2025-68309, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68314, CVE-2025-68315, CVE-2025-68317,\nCVE-2025-68318, CVE-2025-68319, CVE-2025-68320, CVE-2025-68321,\nCVE-2025-68322, CVE-2025-68734)\n","status":"published","published":"2026-02-17T15:24:04Z","modified":"2026-11-03T14:35:01.29943175Z","updated_at":"2026-11-03T15:16:36.034517Z"},{"id":"USN-8095-1","title":"linux, linux-aws, linux-gcp, linux-gcp-6.8, linux-gke, linux-gkeop, linux-hwe-6.8, linux-ibm, linux-ibm-6.8, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-oracle, linux-oracle-6.8 vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-16T14:03:41Z","modified":"2026-11-03T14:38:36.494075469Z","updated_at":"2026-11-03T15:14:17.286738Z"},{"id":"USN-8095-2","title":"linux-fips, linux-aws-fips, linux-gcp-fips vulnerabilities","description":"\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-16T23:02:27Z","modified":"2026-11-03T14:35:38.945380735Z","updated_at":"2026-11-03T15:16:05.953168Z"},{"id":"USN-8095-3","title":"linux-realtime, linux-realtime-6.8 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-17T18:06:26Z","modified":"2026-11-03T14:34:41.040000385Z","updated_at":"2026-11-03T15:16:54.00292Z"},{"id":"USN-8095-4","title":"linux-aws-6.8 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-23T14:01:42Z","modified":"2026-11-03T14:35:07.834088684Z","updated_at":"2026-11-03T15:16:36.034517Z"},{"id":"USN-8095-5","title":"linux-raspi, linux-raspi-realtime vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-04-01T18:04:35Z","modified":"2026-11-03T14:35:15.998762447Z","updated_at":"2026-11-03T15:16:22.507285Z"},{"id":"USN-8100-1","title":"linux-nvidia, linux-nvidia-6.8, linux-nvidia-lowlatency vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40204, CVE-2025-40205,\nCVE-2025-40206, CVE-2025-40207, CVE-2025-40211, CVE-2025-40218,\nCVE-2025-40219, CVE-2025-40220, CVE-2025-40221, CVE-2025-40223,\nCVE-2025-40226, CVE-2025-40231, CVE-2025-40233, CVE-2025-40235,\nCVE-2025-40237, CVE-2025-40238, CVE-2025-40240, CVE-2025-40242,\nCVE-2025-40243, CVE-2025-40244, CVE-2025-40245, CVE-2025-40248,\nCVE-2025-40250, CVE-2025-40251, CVE-2025-40252, CVE-2025-40253,\nCVE-2025-40254, CVE-2025-40257, CVE-2025-40258, CVE-2025-40259,\nCVE-2025-40261, CVE-2025-40262, CVE-2025-40263, CVE-2025-40264,\nCVE-2025-40266, CVE-2025-40268, CVE-2025-40269, CVE-2025-40271,\nCVE-2025-40272, CVE-2025-40273, CVE-2025-40275, CVE-2025-40277,\nCVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281,\nCVE-2025-40282, CVE-2025-40283, CVE-2025-40284, CVE-2025-40285,\nCVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,\nCVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734, CVE-2026-23202,\nCVE-2026-23207)\n","status":"published","published":"2026-03-16T20:48:11Z","modified":"2026-11-04T20:01:36.961728599Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8125-1","title":"linux-azure vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - USB sound devices;\n(CVE-2025-21833, CVE-2025-22037, CVE-2025-22103, CVE-2025-22105,\nCVE-2025-22106, CVE-2025-22107, CVE-2025-22113, CVE-2025-22121,\nCVE-2025-22124, CVE-2025-22125, CVE-2025-23129, CVE-2025-23130,\nCVE-2025-23133, CVE-2025-23143, CVE-2025-37860, CVE-2025-37899,\nCVE-2025-38105, CVE-2025-38502, CVE-2025-38556, CVE-2025-38627,\nCVE-2025-38643, CVE-2025-38709, CVE-2025-39678, CVE-2025-39697,\nCVE-2025-39805, CVE-2025-39806, CVE-2025-39807, CVE-2025-39808,\nCVE-2025-39810, CVE-2025-39811, CVE-2025-39812, CVE-2025-39813,\nCVE-2025-39815, CVE-2025-39817, CVE-2025-39819, CVE-2025-39823,\nCVE-2025-39824, CVE-2025-39825, CVE-2025-39826, CVE-2025-39827,\nCVE-2025-39828, CVE-2025-39829, CVE-2025-39832, CVE-2025-39835,\nCVE-2025-39836, CVE-2025-39838, CVE-2025-39839, CVE-2025-39841,\nCVE-2025-39842, CVE-2025-39843, CVE-2025-39844, CVE-2025-39845,\nCVE-2025-39846, CVE-2025-39847, CVE-2025-39848, CVE-2025-39849,\nCVE-2025-39850, CVE-2025-39851, CVE-2025-39852, CVE-2025-39853,\nCVE-2025-39854, CVE-2025-39857, CVE-2025-39860, CVE-2025-39861,\nCVE-2025-39863, CVE-2025-39864, CVE-2025-39865, CVE-2025-39866,\nCVE-2025-39869, CVE-2025-39870, CVE-2025-39871, CVE-2025-39873,\nCVE-2025-39876, CVE-2025-39877, CVE-2025-39880, CVE-2025-39881,\nCVE-2025-39883, CVE-2025-39885, CVE-2025-39886, CVE-2025-39891,\nCVE-2025-39894, CVE-2025-39895, CVE-2025-39897, CVE-2025-39899,\nCVE-2025-39901, CVE-2025-39902, CVE-2025-39907, CVE-2025-39909,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39914, CVE-2025-39916,\nCVE-2025-39920, CVE-2025-39923, CVE-2025-39927, CVE-2025-39929,\nCVE-2025-39931, CVE-2025-39932, CVE-2025-39934, CVE-2025-39937,\nCVE-2025-39938, CVE-2025-39940, CVE-2025-39942, CVE-2025-39943,\nCVE-2025-39944, CVE-2025-39945, CVE-2025-39947, CVE-2025-39948,\nCVE-2025-39949, CVE-2025-39950, CVE-2025-39951, CVE-2025-39952,\nCVE-2025-39953, CVE-2025-39955, CVE-2025-39957, CVE-2025-39961,\nCVE-2025-39965, CVE-2025-39967, CVE-2025-39968, CVE-2025-39969,\nCVE-2025-39970, CVE-2025-39971, CVE-2025-39972, CVE-2025-39973,\nCVE-2025-39977, CVE-2025-39978, CVE-2025-39980, CVE-2025-39981,\nCVE-2025-39982, CVE-2025-39985, CVE-2025-39986, CVE-2025-39987,\nCVE-2025-39988, CVE-2025-39991, CVE-2025-39992, CVE-2025-39994,\nCVE-2025-39995, CVE-2025-39996, CVE-2025-39998, CVE-2025-40000,\nCVE-2025-40001, CVE-2025-40006, CVE-2025-40008, CVE-2025-40009,\nCVE-2025-40010, CVE-2025-40011, CVE-2025-40013, CVE-2025-40016,\nCVE-2025-40020, CVE-2025-40021, CVE-2025-40024, CVE-2025-40026,\nCVE-2025-40027, CVE-2025-40029, CVE-2025-40030, CVE-2025-40031,\nCVE-2025-40032, CVE-2025-40033, CVE-2025-40035, CVE-2025-40036,\nCVE-2025-40037, CVE-2025-40038, CVE-2025-40042, CVE-2025-40043,\nCVE-2025-40044, CVE-2025-40047, CVE-2025-40048, CVE-2025-40049,\nCVE-2025-40051, CVE-2025-40052, CVE-2025-40053, CVE-2025-40055,\nCVE-2025-40056, CVE-2025-40057, CVE-2025-40058, CVE-2025-40059,\nCVE-2025-40060, CVE-2025-40061, CVE-2025-40062, CVE-2025-40067,\nCVE-2025-40068, CVE-2025-40070, CVE-2025-40071, CVE-2025-40077,\nCVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081,\nCVE-2025-40083, CVE-2025-40084, CVE-2025-40085, CVE-2025-40087,\nCVE-2025-40088, CVE-2025-40092, CVE-2025-40093, CVE-2025-40094,\nCVE-2025-40095, CVE-2025-40096, CVE-2025-40099, CVE-2025-40100,\nCVE-2025-40101, CVE-2025-40103, CVE-2025-40104, CVE-2025-40105,\nCVE-2025-40106, CVE-2025-40107, CVE-2025-40109, CVE-2025-40110,\nCVE-2025-40111, CVE-2025-40112, CVE-2025-40115, CVE-2025-40116,\nCVE-2025-40118, CVE-2025-40120, CVE-2025-40121, CVE-2025-40123,\nCVE-2025-40124, CVE-2025-40125, CVE-2025-40126, CVE-2025-40127,\nCVE-2025-40129, CVE-2025-40134, CVE-2025-40137, CVE-2025-40140,\nCVE-2025-40141, CVE-2025-40153, CVE-2025-40154, CVE-2025-40155,\nCVE-2025-40156, CVE-2025-40159, CVE-2025-40160, CVE-2025-40165,\nCVE-2025-40166, CVE-2025-40167, CVE-2025-40169, CVE-2025-40171,\nCVE-2025-40172, CVE-2025-40173, CVE-2025-40176, CVE-2025-40178,\nCVE-2025-40179, CVE-2025-40180, CVE-2025-40183, CVE-2025-40187,\nCVE-2025-40188, CVE-2025-40192, CVE-2025-40193, CVE-2025-40194,\nCVE-2025-40196, CVE-2025-40198, CVE-2025-40200, CVE-2025-40201,\nCVE-2025-40202, CVE-2025-40204, CVE-2025-40205, CVE-2025-40206,\nCVE-2025-40207, CVE-2025-40211, CVE-2025-40218, CVE-2025-40219,\nCVE-2025-40220, CVE-2025-40221, CVE-2025-40223, CVE-2025-40226,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40235, CVE-2025-40237,\nCVE-2025-40238, CVE-2025-40240, CVE-2025-40242, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40248, CVE-2025-40250,\nCVE-2025-40251, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254,\nCVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40261,\nCVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40266,\nCVE-2025-40268, 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-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40292,\nCVE-2025-40293, CVE-2025-40294, CVE-2025-40301, CVE-2025-40303,\nCVE-2025-40304, CVE-2025-40305, CVE-2025-40306, CVE-2025-40307,\nCVE-2025-40308, CVE-2025-40309, CVE-2025-40310, CVE-2025-40311,\nCVE-2025-40312, CVE-2025-40313, CVE-2025-40314, CVE-2025-40315,\nCVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320,\nCVE-2025-40321, CVE-2025-40322, CVE-2025-40323, CVE-2025-40324,\nCVE-2025-40328, CVE-2025-40329, CVE-2025-40331, CVE-2025-40333,\nCVE-2025-40337, CVE-2025-40339, CVE-2025-40341, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40347,\nCVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40353,\nCVE-2025-40358, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168,\nCVE-2025-68171, CVE-2025-68172, CVE-2025-68173, CVE-2025-68176,\nCVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180,\nCVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68190,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68198,\nCVE-2025-68200, CVE-2025-68201, CVE-2025-68204, CVE-2025-68208,\nCVE-2025-68213, CVE-2025-68214, CVE-2025-68217, CVE-2025-68218,\nCVE-2025-68219, CVE-2025-68220, CVE-2025-68222, CVE-2025-68223,\nCVE-2025-68227, CVE-2025-68229, CVE-2025-68231, CVE-2025-68233,\nCVE-2025-68235, CVE-2025-68237, CVE-2025-68238, CVE-2025-68241,\nCVE-2025-68244, CVE-2025-68245, CVE-2025-68246, CVE-2025-68249,\nCVE-2025-68282, CVE-2025-68283, CVE-2025-68284, CVE-2025-68285,\nCVE-2025-68286, CVE-2025-68287, CVE-2025-68288, CVE-2025-68289,\nCVE-2025-68290, CVE-2025-68295, CVE-2025-68297, CVE-2025-68301,\nCVE-2025-68302, CVE-2025-68303, CVE-2025-68305, CVE-2025-68307,\nCVE-2025-68308, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68315, CVE-2025-68320, CVE-2025-68321,\nCVE-2025-68322, CVE-2025-68327, CVE-2025-68328, CVE-2025-68330,\nCVE-2025-68331, CVE-2025-68339, CVE-2025-68340, CVE-2025-68342,\nCVE-2025-68343, CVE-2025-68734)\n","status":"published","published":"2026-03-25T19:11:40Z","modified":"2026-11-03T14:35:10.177253555Z","updated_at":"2026-11-03T15:16:30.201391Z"},{"id":"USN-8126-1","title":"linux-azure-6.8 vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853)\n\nIt was discovered that improper initialization of CPU cache memory could\nallow a local attacker with hypervisor access to overwrite SEV-SNP guest\nmemory resulting in loss of data integrity. (CVE-2024-36331)\n\nOleksii Oleksenko, Cedric Fournet, Jana Hofmann, Boris Köpf, Stavros Volos,\nand Flavien Solt discovered that some AMD processors may allow an attacker\nto infer data from previous stores, potentially resulting in the leakage of\nprivileged information. A local attacker could possibly use this to expose\nsensitive information. (CVE-2024-36350, CVE-2024-36357)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM32 architecture;\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Serial ATA and Parallel ATA drivers;\n  - ATM drivers;\n  - Drivers core;\n  - ATA over ethernet (AOE) driver;\n  - DRBD Distributed Replicated Block Device drivers;\n  - Block device driver;\n  - Network block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - Buffer Sharing and Synchronization framework;\n  - DMA engine subsystem;\n  - EDAC drivers;\n  - Arm Firmware Framework for ARMv8-A(FFA);\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - FPGA Framework;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - I2C subsystem;\n  - I3C subsystem;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - MCB driver;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Fastrpc Driver;\n  - Microchip PCI driver;\n  - Intel Management Engine Interface driver;\n  - PCI Endpoint Test driver;\n  - TI TPS6594 PFSM driver;\n  - VMware VMCI Driver;\n  - MMC subsystem;\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  - NVDIMM (Non-Volatile Memory Device) drivers;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Amlogic Meson DDR PMU;\n  - Performance monitor drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - Power supply drivers;\n  - Powercap sysfs driver;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - RapidIO drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - ASPEED SoC drivers;\n  - QCOM SoC drivers;\n  - Samsung SoC drivers;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - small TFT LCD display modules;\n  - Media staging drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - Thunderbolt and USB4 drivers;\n  - TTY drivers;\n  - UFS subsystem;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - ChipIdea USB driver;\n  - USB Device Class drivers;\n  - USB core drivers;\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 support driver;\n  - USB Type-C Connector System Software Interface driver;\n  - VFIO drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - TSM Common Guest driver;\n  - Virtio drivers;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - File systems infrastructure;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFFS2 file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Overlay file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - DRM display driver;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Memory Management;\n  - Internal shared memory driver;\n  - LZO compression library;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - padata parallel execution mechanism;\n  - Memory management;\n  - Networking subsytem;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Netfilter;\n  - Network traffic control;\n  - Rose network layer;\n  - SCTP protocol;\n  - Network sockets;\n  - UDP network protocol;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Digital Audio (PCM) driver;\n  - Universal MIDI packet (UMP) support module;\n  - Tracing infrastructure;\n  - User-space API (UAPI);\n  - io_uring subsystem;\n  - IPC subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Perf events;\n  - Kernel exit() syscall;\n  - Kernel futex primitives;\n  - IRQ subsystem;\n  - Padata parallel execution mechanism;\n  - Kernel command line parsing driver;\n  - PID allocator;\n  - Hibernation control;\n  - RCU subsystem;\n  - Restartable seuqences system call mechanism;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Maple Tree data structure library;\n  - KASAN memory debugging framework;\n  - 802.1Q VLAN protocol;\n  - 9P file system network protocol;\n  - Appletalk network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - Distributed Switch Architecture;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Management Component Transport Protocol (MCTP);\n  - MultiProtocol Label Switching driver;\n  - Multipath TCP;\n  - NetLabel subsystem;\n  - Netlink;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RDS protocol;\n  - RF switch subsystem;\n  - RxRPC session sockets;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Integrity Measurement Architecture(IMA) framework;\n  - ALSA framework;\n  - WCD audio codecs;\n  - Intel ASoC drivers;\n  - MediaTek ASoC drivers;\n  - QCOM ASoC drivers;\n  - SoC audio core drivers;\n  - USB sound devices;\n  - Virtio sound driver;\n  - CPU Power monitoring subsystem;\n  - KVM subsystem;\n(CVE-2025-21833, CVE-2025-21884, CVE-2025-21931, CVE-2025-22026,\nCVE-2025-22037, CVE-2025-22101, CVE-2025-22102, CVE-2025-22103,\nCVE-2025-22105, CVE-2025-22106, CVE-2025-22107, CVE-2025-22113,\nCVE-2025-22115, CVE-2025-22120, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-22126, CVE-2025-22128, CVE-2025-23129,\nCVE-2025-23130, CVE-2025-23133, CVE-2025-23140, CVE-2025-23141,\nCVE-2025-23142, CVE-2025-23143, CVE-2025-23144, CVE-2025-23145,\nCVE-2025-23146, CVE-2025-23147, CVE-2025-23148, CVE-2025-23149,\nCVE-2025-23150, CVE-2025-23151, CVE-2025-23155, CVE-2025-23156,\nCVE-2025-23157, CVE-2025-23158, CVE-2025-23159, CVE-2025-23160,\nCVE-2025-23161, CVE-2025-23163, CVE-2025-37738, CVE-2025-37739,\nCVE-2025-37740, CVE-2025-37741, CVE-2025-37742, CVE-2025-37744,\nCVE-2025-37745, CVE-2025-37748, CVE-2025-37749, CVE-2025-37754,\nCVE-2025-37755, CVE-2025-37757, CVE-2025-37758, CVE-2025-37759,\nCVE-2025-37761, CVE-2025-37763, CVE-2025-37764, CVE-2025-37765,\nCVE-2025-37766, CVE-2025-37767, CVE-2025-37768, CVE-2025-37769,\nCVE-2025-37770, CVE-2025-37771, CVE-2025-37772, CVE-2025-37773,\nCVE-2025-37775, CVE-2025-37777, CVE-2025-37778, CVE-2025-37780,\nCVE-2025-37781, CVE-2025-37784, CVE-2025-37786, CVE-2025-37787,\nCVE-2025-37788, CVE-2025-37789, CVE-2025-37790, CVE-2025-37792,\nCVE-2025-37793, CVE-2025-37794, CVE-2025-37796, CVE-2025-37799,\nCVE-2025-37800, CVE-2025-37801, CVE-2025-37803, CVE-2025-37805,\nCVE-2025-37808, CVE-2025-37809, CVE-2025-37810, CVE-2025-37811,\nCVE-2025-37812, CVE-2025-37813, CVE-2025-37815, CVE-2025-37816,\nCVE-2025-37817, CVE-2025-37819, CVE-2025-37820, CVE-2025-37822,\nCVE-2025-37823, CVE-2025-37824, CVE-2025-37826, CVE-2025-37827,\nCVE-2025-37828, CVE-2025-37829, CVE-2025-37830, CVE-2025-37831,\nCVE-2025-37836, CVE-2025-37839, CVE-2025-37840, CVE-2025-37841,\nCVE-2025-37842, CVE-2025-37844, CVE-2025-37846, CVE-2025-37849,\nCVE-2025-37850, CVE-2025-37851, CVE-2025-37852, CVE-2025-37853,\nCVE-2025-37854, CVE-2025-37856, CVE-2025-37857, CVE-2025-37858,\nCVE-2025-37859, CVE-2025-37860, CVE-2025-37861, CVE-2025-37862,\nCVE-2025-37863, CVE-2025-37864, CVE-2025-37865, CVE-2025-37867,\nCVE-2025-37869, CVE-2025-37871, CVE-2025-37872, CVE-2025-37873,\nCVE-2025-37874, CVE-2025-37875, CVE-2025-37878, CVE-2025-37879,\nCVE-2025-37881, CVE-2025-37883, CVE-2025-37884, CVE-2025-37885,\nCVE-2025-37886, CVE-2025-37887, CVE-2025-37891, CVE-2025-37892,\nCVE-2025-37897, CVE-2025-37899, CVE-2025-37900, CVE-2025-37901,\nCVE-2025-37903, CVE-2025-37905, CVE-2025-37909, CVE-2025-37911,\nCVE-2025-37912, CVE-2025-37913, CVE-2025-37914, CVE-2025-37915,\nCVE-2025-37916, CVE-2025-37917, CVE-2025-37918, CVE-2025-37920,\nCVE-2025-37921, CVE-2025-37922, CVE-2025-37923, CVE-2025-37924,\nCVE-2025-37925, CVE-2025-37927, CVE-2025-37928, CVE-2025-37930,\nCVE-2025-37931, CVE-2025-37933, CVE-2025-37935, CVE-2025-37936,\nCVE-2025-37938, CVE-2025-37940, CVE-2025-37943, CVE-2025-37944,\nCVE-2025-37945, CVE-2025-37947, CVE-2025-37948, CVE-2025-37949,\nCVE-2025-37951, CVE-2025-37952, CVE-2025-37956, CVE-2025-37957,\nCVE-2025-37959, CVE-2025-37960, CVE-2025-37961, CVE-2025-37962,\nCVE-2025-37963, CVE-2025-37967, CVE-2025-37968, CVE-2025-37969,\nCVE-2025-37970, CVE-2025-37972, CVE-2025-37973, CVE-2025-37975,\nCVE-2025-37977, CVE-2025-37978, CVE-2025-37979, CVE-2025-37980,\nCVE-2025-37982, CVE-2025-37983, CVE-2025-37984, CVE-2025-37985,\nCVE-2025-37986, CVE-2025-37987, CVE-2025-37988, CVE-2025-37989,\nCVE-2025-37990, CVE-2025-37991, CVE-2025-37992, CVE-2025-37994,\nCVE-2025-37995, CVE-2025-37998, CVE-2025-38003, CVE-2025-38004,\nCVE-2025-38005, CVE-2025-38006, CVE-2025-38007, CVE-2025-38008,\nCVE-2025-38009, CVE-2025-38010, CVE-2025-38011, CVE-2025-38013,\nCVE-2025-38014, CVE-2025-38015, CVE-2025-38018, CVE-2025-38019,\nCVE-2025-38020, CVE-2025-38023, CVE-2025-38024, CVE-2025-38027,\nCVE-2025-38031, CVE-2025-38034, CVE-2025-38035, CVE-2025-38037,\nCVE-2025-38039, CVE-2025-38040, CVE-2025-38043, CVE-2025-38044,\nCVE-2025-38045, CVE-2025-38048, CVE-2025-38051, CVE-2025-38052,\nCVE-2025-38053, CVE-2025-38055, CVE-2025-38057, CVE-2025-38058,\nCVE-2025-38059, CVE-2025-38060, CVE-2025-38061, CVE-2025-38062,\nCVE-2025-38063, CVE-2025-38065, CVE-2025-38066, CVE-2025-38067,\nCVE-2025-38068, CVE-2025-38071, CVE-2025-38072, CVE-2025-38074,\nCVE-2025-38075, CVE-2025-38077, CVE-2025-38078, CVE-2025-38079,\nCVE-2025-38080, CVE-2025-38081, CVE-2025-38084, CVE-2025-38085,\nCVE-2025-38086, CVE-2025-38087, CVE-2025-38088, CVE-2025-38089,\nCVE-2025-38090, CVE-2025-38094, CVE-2025-38095, CVE-2025-38097,\nCVE-2025-38098, CVE-2025-38099, CVE-2025-38100, CVE-2025-38101,\nCVE-2025-38102, CVE-2025-38103, CVE-2025-38104, CVE-2025-38105,\nCVE-2025-38107, CVE-2025-38108, CVE-2025-38109, CVE-2025-38110,\nCVE-2025-38111, CVE-2025-38112, CVE-2025-38113, CVE-2025-38115,\nCVE-2025-38117, CVE-2025-38119, CVE-2025-38120, CVE-2025-38122,\nCVE-2025-38123, CVE-2025-38124, CVE-2025-38125, CVE-2025-38126,\nCVE-2025-38127, CVE-2025-38129, CVE-2025-38131, CVE-2025-38135,\nCVE-2025-38136, CVE-2025-38138, CVE-2025-38142, CVE-2025-38143,\nCVE-2025-38145, CVE-2025-38146, CVE-2025-38147, CVE-2025-38148,\nCVE-2025-38149, CVE-2025-38153, CVE-2025-38154, CVE-2025-38155,\nCVE-2025-38156, CVE-2025-38157, CVE-2025-38158, CVE-2025-38159,\nCVE-2025-38160, CVE-2025-38161, CVE-2025-38162, CVE-2025-38163,\nCVE-2025-38164, CVE-2025-38165, CVE-2025-38166, CVE-2025-38167,\nCVE-2025-38169, CVE-2025-38170, CVE-2025-38173, CVE-2025-38174,\nCVE-2025-38180, CVE-2025-38181, CVE-2025-38182, CVE-2025-38183,\nCVE-2025-38184, CVE-2025-38185, CVE-2025-38190, CVE-2025-38191,\nCVE-2025-38192, CVE-2025-38193, CVE-2025-38194, CVE-2025-38197,\nCVE-2025-38198, CVE-2025-38200, CVE-2025-38202, CVE-2025-38208,\nCVE-2025-38210, CVE-2025-38211, CVE-2025-38212, CVE-2025-38214,\nCVE-2025-38215, CVE-2025-38217, CVE-2025-38218, CVE-2025-38219,\nCVE-2025-38220, CVE-2025-38222, CVE-2025-38225, CVE-2025-38226,\nCVE-2025-38229, CVE-2025-38230, CVE-2025-38231, CVE-2025-38232,\nCVE-2025-38236, CVE-2025-38239, CVE-2025-38245, CVE-2025-38246,\nCVE-2025-38248, CVE-2025-38249, CVE-2025-38250, CVE-2025-38251,\nCVE-2025-38253, CVE-2025-38255, CVE-2025-38257, CVE-2025-38258,\nCVE-2025-38259, CVE-2025-38260, CVE-2025-38262, CVE-2025-38263,\nCVE-2025-38264, CVE-2025-38265, CVE-2025-38269, CVE-2025-38274,\nCVE-2025-38275, CVE-2025-38277, CVE-2025-38278, CVE-2025-38279,\nCVE-2025-38280, CVE-2025-38282, CVE-2025-38283, CVE-2025-38285,\nCVE-2025-38286, CVE-2025-38289, CVE-2025-38290, CVE-2025-38292,\nCVE-2025-38293, CVE-2025-38295, CVE-2025-38298, CVE-2025-38299,\nCVE-2025-38300, CVE-2025-38303, CVE-2025-38304, CVE-2025-38305,\nCVE-2025-38307, CVE-2025-38310, CVE-2025-38312, CVE-2025-38313,\nCVE-2025-38319, CVE-2025-38320, CVE-2025-38321, CVE-2025-38322,\nCVE-2025-38323, CVE-2025-38324, CVE-2025-38326, CVE-2025-38328,\nCVE-2025-38331, CVE-2025-38332, CVE-2025-38333, CVE-2025-38334,\nCVE-2025-38335, CVE-2025-38336, CVE-2025-38337, CVE-2025-38338,\nCVE-2025-38342, CVE-2025-38343, CVE-2025-38344, CVE-2025-38345,\nCVE-2025-38346, CVE-2025-38347, CVE-2025-38348, CVE-2025-38349,\nCVE-2025-38351, CVE-2025-38354, CVE-2025-38361, CVE-2025-38362,\nCVE-2025-38363, CVE-2025-38364, CVE-2025-38365, CVE-2025-38368,\nCVE-2025-38369, CVE-2025-38371, CVE-2025-38373, CVE-2025-38374,\nCVE-2025-38375, CVE-2025-38376, CVE-2025-38377, CVE-2025-38382,\nCVE-2025-38384, CVE-2025-38385, CVE-2025-38386, CVE-2025-38387,\nCVE-2025-38388, CVE-2025-38389, CVE-2025-38390, CVE-2025-38391,\nCVE-2025-38392, CVE-2025-38393, CVE-2025-38395, CVE-2025-38396,\nCVE-2025-38399, CVE-2025-38400, CVE-2025-38401, CVE-2025-38402,\nCVE-2025-38403, CVE-2025-38405, CVE-2025-38406, CVE-2025-38407,\nCVE-2025-38408, CVE-2025-38409, CVE-2025-38410, CVE-2025-38412,\nCVE-2025-38414, CVE-2025-38415, CVE-2025-38416, CVE-2025-38418,\nCVE-2025-38419, CVE-2025-38420, CVE-2025-38422, CVE-2025-38424,\nCVE-2025-38425, CVE-2025-38427, CVE-2025-38428, CVE-2025-38429,\nCVE-2025-38430, CVE-2025-38436, CVE-2025-38437, CVE-2025-38439,\nCVE-2025-38441, CVE-2025-38443, CVE-2025-38444, CVE-2025-38445,\nCVE-2025-38448, CVE-2025-38449, CVE-2025-38455, CVE-2025-38456,\nCVE-2025-38457, CVE-2025-38458, CVE-2025-38459, CVE-2025-38460,\nCVE-2025-38461, CVE-2025-38462, CVE-2025-38463, CVE-2025-38464,\nCVE-2025-38465, CVE-2025-38466, CVE-2025-38467, CVE-2025-38468,\nCVE-2025-38469, CVE-2025-38470, CVE-2025-38471, CVE-2025-38472,\nCVE-2025-38473, CVE-2025-38474, CVE-2025-38476, CVE-2025-38478,\nCVE-2025-38480, CVE-2025-38481, CVE-2025-38482, CVE-2025-38483,\nCVE-2025-38485, CVE-2025-38487, CVE-2025-38488, CVE-2025-38489,\nCVE-2025-38490, CVE-2025-38491, CVE-2025-38493, CVE-2025-38494,\nCVE-2025-38495, CVE-2025-38496, CVE-2025-38497, CVE-2025-38499,\nCVE-2025-38501, CVE-2025-38502, CVE-2025-38503, CVE-2025-38506,\nCVE-2025-38507, CVE-2025-38510, CVE-2025-38511, CVE-2025-38512,\nCVE-2025-38513, CVE-2025-38514, CVE-2025-38515, CVE-2025-38516,\nCVE-2025-38520, CVE-2025-38521, CVE-2025-38524, CVE-2025-38526,\nCVE-2025-38527, CVE-2025-38528, CVE-2025-38529, CVE-2025-38530,\nCVE-2025-38531, CVE-2025-38532, CVE-2025-38533, CVE-2025-38535,\nCVE-2025-38537, CVE-2025-38538, CVE-2025-38539, CVE-2025-38540,\nCVE-2025-38542, CVE-2025-38543, CVE-2025-38544, CVE-2025-38546,\nCVE-2025-38548, CVE-2025-38549, CVE-2025-38550, CVE-2025-38551,\nCVE-2025-38552, CVE-2025-38553, CVE-2025-38555, CVE-2025-38556,\nCVE-2025-38560, CVE-2025-38561, CVE-2025-38562, CVE-2025-38566,\nCVE-2025-38568, CVE-2025-38569, CVE-2025-38571, CVE-2025-38572,\nCVE-2025-38574, CVE-2025-38576, CVE-2025-38577, CVE-2025-38578,\nCVE-2025-38579, CVE-2025-38581, CVE-2025-38582, CVE-2025-38583,\nCVE-2025-38584, CVE-2025-38585, CVE-2025-38587, CVE-2025-38588,\nCVE-2025-38590, CVE-2025-38593, CVE-2025-38595, CVE-2025-38601,\nCVE-2025-38602, CVE-2025-38604, CVE-2025-38608, CVE-2025-38609,\nCVE-2025-38610, CVE-2025-38612, CVE-2025-38614, CVE-2025-38615,\nCVE-2025-38619, CVE-2025-38622, CVE-2025-38623, CVE-2025-38624,\nCVE-2025-38625, CVE-2025-38626, CVE-2025-38627, CVE-2025-38630,\nCVE-2025-38632, CVE-2025-38634, CVE-2025-38635, CVE-2025-38639,\nCVE-2025-38640, CVE-2025-38643, CVE-2025-38644, CVE-2025-38645,\nCVE-2025-38646, CVE-2025-38648, CVE-2025-38650, CVE-2025-38652,\nCVE-2025-38653, CVE-2025-38659, CVE-2025-38660, CVE-2025-38663,\nCVE-2025-38664, CVE-2025-38665, CVE-2025-38668, CVE-2025-38670,\nCVE-2025-38671, CVE-2025-38675, CVE-2025-38676, CVE-2025-38677,\nCVE-2025-38679, CVE-2025-38680, CVE-2025-38681, CVE-2025-38684,\nCVE-2025-38685, CVE-2025-38686, CVE-2025-38687, CVE-2025-38688,\nCVE-2025-38691, CVE-2025-38692, CVE-2025-38693, CVE-2025-38694,\nCVE-2025-38695, CVE-2025-38696, CVE-2025-38697, CVE-2025-38698,\nCVE-2025-38699, CVE-2025-38700, CVE-2025-38701, CVE-2025-38702,\nCVE-2025-38703, CVE-2025-38704, CVE-2025-38705, CVE-2025-38706,\nCVE-2025-38707, CVE-2025-38708, CVE-2025-38709, CVE-2025-38710,\nCVE-2025-38711, CVE-2025-38712, CVE-2025-38713, CVE-2025-38714,\nCVE-2025-38715, CVE-2025-38716, CVE-2025-38718, CVE-2025-38721,\nCVE-2025-38722, CVE-2025-38724, CVE-2025-38725, CVE-2025-38728,\nCVE-2025-38729, CVE-2025-38730, CVE-2025-38732, CVE-2025-38734,\nCVE-2025-38735, CVE-2025-39673, CVE-2025-39675, CVE-2025-39676,\nCVE-2025-39678, CVE-2025-39679, CVE-2025-39681, CVE-2025-39683,\nCVE-2025-39684, CVE-2025-39685, CVE-2025-39686, CVE-2025-39687,\nCVE-2025-39689, CVE-2025-39691, CVE-2025-39692, CVE-2025-39693,\nCVE-2025-39694, CVE-2025-39697, CVE-2025-39698, CVE-2025-39701,\nCVE-2025-39702, CVE-2025-39703, CVE-2025-39705, CVE-2025-39706,\nCVE-2025-39707, CVE-2025-39709, CVE-2025-39710, CVE-2025-39711,\nCVE-2025-39712, CVE-2025-39713, CVE-2025-39714, CVE-2025-39715,\nCVE-2025-39716, CVE-2025-39718, CVE-2025-39719, CVE-2025-39720,\nCVE-2025-39721, CVE-2025-39724, CVE-2025-39726, CVE-2025-39730,\nCVE-2025-39731, CVE-2025-39732, CVE-2025-39734, CVE-2025-39736,\nCVE-2025-39737, CVE-2025-39738, CVE-2025-39739, CVE-2025-39742,\nCVE-2025-39743, CVE-2025-39744, CVE-2025-39746, CVE-2025-39747,\nCVE-2025-39748, CVE-2025-39749, CVE-2025-39750, CVE-2025-39752,\nCVE-2025-39753, CVE-2025-39756, CVE-2025-39757, CVE-2025-39758,\nCVE-2025-39759, CVE-2025-39760, CVE-2025-39761, CVE-2025-39763,\nCVE-2025-39766, CVE-2025-39770, CVE-2025-39772, CVE-2025-39773,\nCVE-2025-39776, CVE-2025-39779, CVE-2025-39781, CVE-2025-39782,\nCVE-2025-39783, CVE-2025-39787, CVE-2025-39788, CVE-2025-39790,\nCVE-2025-39794, CVE-2025-39795, CVE-2025-39797, CVE-2025-39798,\nCVE-2025-39800, CVE-2025-39801, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39889, CVE-2025-39890, CVE-2025-39891,\nCVE-2025-39894, CVE-2025-39895, CVE-2025-39897, CVE-2025-39899,\nCVE-2025-39901, CVE-2025-39902, CVE-2025-39907, CVE-2025-39909,\nCVE-2025-39911, CVE-2025-39913, CVE-2025-39914, CVE-2025-39916,\nCVE-2025-39920, CVE-2025-39923, CVE-2025-39927, CVE-2025-39929,\nCVE-2025-39931, CVE-2025-39932, CVE-2025-39934, CVE-2025-39937,\nCVE-2025-39938, CVE-2025-39940, CVE-2025-39942, CVE-2025-39943,\nCVE-2025-39944, CVE-2025-39945, CVE-2025-39946, CVE-2025-39947,\nCVE-2025-39948, CVE-2025-39949, CVE-2025-39950, CVE-2025-39951,\nCVE-2025-39952, CVE-2025-39953, CVE-2025-39955, CVE-2025-39957,\nCVE-2025-39961, CVE-2025-39965, CVE-2025-39967, CVE-2025-39968,\nCVE-2025-39969, CVE-2025-39970, CVE-2025-39971, CVE-2025-39972,\nCVE-2025-39973, CVE-2025-39977, CVE-2025-39978, CVE-2025-39980,\nCVE-2025-39981, CVE-2025-39982, CVE-2025-39985, CVE-2025-39986,\nCVE-2025-39987, CVE-2025-39988, CVE-2025-39989, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40019, CVE-2025-40020,\nCVE-2025-40021, CVE-2025-40024, CVE-2025-40026, CVE-2025-40027,\nCVE-2025-40029, CVE-2025-40030, CVE-2025-40031, CVE-2025-40032,\nCVE-2025-40033, CVE-2025-40035, CVE-2025-40036, CVE-2025-40037,\nCVE-2025-40038, CVE-2025-40042, CVE-2025-40043, CVE-2025-40044,\nCVE-2025-40047, CVE-2025-40048, CVE-2025-40049, CVE-2025-40051,\nCVE-2025-40052, CVE-2025-40053, CVE-2025-40055, CVE-2025-40056,\nCVE-2025-40057, CVE-2025-40058, CVE-2025-40059, CVE-2025-40060,\nCVE-2025-40061, CVE-2025-40062, CVE-2025-40067, CVE-2025-40068,\nCVE-2025-40070, CVE-2025-40071, CVE-2025-40077, CVE-2025-40078,\nCVE-2025-40079, CVE-2025-40080, CVE-2025-40081, CVE-2025-40083,\nCVE-2025-40084, CVE-2025-40085, CVE-2025-40087, CVE-2025-40088,\nCVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095,\nCVE-2025-40096, CVE-2025-40099, CVE-2025-40100, CVE-2025-40101,\nCVE-2025-40103, CVE-2025-40104, CVE-2025-40105, CVE-2025-40106,\nCVE-2025-40107, CVE-2025-40109, CVE-2025-40110, CVE-2025-40111,\nCVE-2025-40112, CVE-2025-40115, CVE-2025-40116, CVE-2025-40118,\nCVE-2025-40120, CVE-2025-40121, CVE-2025-40123, CVE-2025-40124,\nCVE-2025-40125, CVE-2025-40126, CVE-2025-40127, CVE-2025-40129,\nCVE-2025-40134, CVE-2025-40137, CVE-2025-40140, CVE-2025-40141,\nCVE-2025-40153, CVE-2025-40154, CVE-2025-40155, CVE-2025-40156,\nCVE-2025-40159, CVE-2025-40160, CVE-2025-40165, CVE-2025-40166,\nCVE-2025-40167, CVE-2025-40169, CVE-2025-40171, CVE-2025-40172,\nCVE-2025-40173, CVE-2025-40176, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40200, CVE-2025-40201, CVE-2025-40202,\nCVE-2025-40204, CVE-2025-40205, CVE-2025-40206, CVE-2025-40207,\nCVE-2025-40211, CVE-2025-40215, CVE-2025-40218, CVE-2025-40219,\nCVE-2025-40220, CVE-2025-40221, CVE-2025-40223, CVE-2025-40226,\nCVE-2025-40231, CVE-2025-40233, CVE-2025-40235, CVE-2025-40237,\nCVE-2025-40238, CVE-2025-40240, CVE-2025-40242, CVE-2025-40243,\nCVE-2025-40244, CVE-2025-40245, CVE-2025-40248, CVE-2025-40250,\nCVE-2025-40251, CVE-2025-40252, CVE-2025-40253, CVE-2025-40254,\nCVE-2025-40257, CVE-2025-40258, CVE-2025-40259, CVE-2025-40261,\nCVE-2025-40262, CVE-2025-40263, CVE-2025-40264, CVE-2025-40266,\nCVE-2025-40268, 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-40284, CVE-2025-40285, CVE-2025-40286,\nCVE-2025-40287, CVE-2025-40288, CVE-2025-40289, CVE-2025-40292,\nCVE-2025-40293, CVE-2025-40294, CVE-2025-40297, CVE-2025-40301,\nCVE-2025-40303, CVE-2025-40304, CVE-2025-40305, CVE-2025-40306,\nCVE-2025-40307, CVE-2025-40308, CVE-2025-40309, CVE-2025-40310,\nCVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314,\nCVE-2025-40315, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319,\nCVE-2025-40320, CVE-2025-40321, CVE-2025-40322, CVE-2025-40323,\nCVE-2025-40324, CVE-2025-40328, CVE-2025-40329, CVE-2025-40331,\nCVE-2025-40333, CVE-2025-40337, CVE-2025-40339, CVE-2025-40341,\nCVE-2025-40342, CVE-2025-40343, CVE-2025-40345, CVE-2025-40346,\nCVE-2025-40347, CVE-2025-40349, CVE-2025-40350, CVE-2025-40351,\nCVE-2025-40353, CVE-2025-40358, CVE-2025-40360, CVE-2025-40363,\nCVE-2025-68168, CVE-2025-68171, CVE-2025-68172, CVE-2025-68173,\nCVE-2025-68176, CVE-2025-68177, CVE-2025-68178, CVE-2025-68179,\nCVE-2025-68180, CVE-2025-68183, CVE-2025-68184, CVE-2025-68185,\nCVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68194,\nCVE-2025-68198, CVE-2025-68200, CVE-2025-68201, CVE-2025-68204,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68282, CVE-2025-68283, CVE-2025-68284,\nCVE-2025-68285, CVE-2025-68286, CVE-2025-68287, CVE-2025-68288,\nCVE-2025-68289, CVE-2025-68290, CVE-2025-68295, CVE-2025-68297,\nCVE-2025-68301, CVE-2025-68302, CVE-2025-68303, CVE-2025-68305,\nCVE-2025-68307, CVE-2025-68308, CVE-2025-68310, CVE-2025-68311,\nCVE-2025-68312, CVE-2025-68313, CVE-2025-68315, CVE-2025-68320,\nCVE-2025-68321, CVE-2025-68322, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68734, CVE-2025-68750)\n","status":"published","published":"2026-03-25T19:13:52Z","modified":"2026-11-03T14:35:29.863770912Z","updated_at":"2026-11-03T15:16:14.724953Z"},{"id":"USN-8165-1","title":"linux-azure-fips vulnerabilities","description":"Qualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Hardware random number generator core;\n  - Character device driver;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - ISDN/mISDN subsystem;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - Ethernet bridge;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - USB sound devices;\n(CVE-2025-21833, CVE-2025-22103, CVE-2025-22105, CVE-2025-22106,\nCVE-2025-22107, CVE-2025-22113, CVE-2025-22121, CVE-2025-22124,\nCVE-2025-22125, CVE-2025-23129, CVE-2025-23130, CVE-2025-23133,\nCVE-2025-23143, CVE-2025-37860, CVE-2025-38105, CVE-2025-38502,\nCVE-2025-38556, CVE-2025-38627, CVE-2025-38643, CVE-2025-38709,\nCVE-2025-39678, CVE-2025-39697, CVE-2025-39805, CVE-2025-39806,\nCVE-2025-39807, CVE-2025-39808, CVE-2025-39810, CVE-2025-39811,\nCVE-2025-39812, CVE-2025-39813, CVE-2025-39815, CVE-2025-39817,\nCVE-2025-39819, CVE-2025-39823, CVE-2025-39824, CVE-2025-39825,\nCVE-2025-39826, CVE-2025-39827, CVE-2025-39828, CVE-2025-39829,\nCVE-2025-39832, CVE-2025-39835, CVE-2025-39836, CVE-2025-39838,\nCVE-2025-39839, CVE-2025-39841, CVE-2025-39842, CVE-2025-39843,\nCVE-2025-39844, CVE-2025-39845, CVE-2025-39846, CVE-2025-39847,\nCVE-2025-39848, CVE-2025-39849, CVE-2025-39850, CVE-2025-39851,\nCVE-2025-39852, CVE-2025-39853, CVE-2025-39854, CVE-2025-39857,\nCVE-2025-39860, CVE-2025-39861, CVE-2025-39863, CVE-2025-39864,\nCVE-2025-39865, CVE-2025-39866, CVE-2025-39869, CVE-2025-39870,\nCVE-2025-39871, CVE-2025-39873, CVE-2025-39876, CVE-2025-39877,\nCVE-2025-39880, CVE-2025-39881, CVE-2025-39883, CVE-2025-39885,\nCVE-2025-39886, CVE-2025-39891, CVE-2025-39894, CVE-2025-39895,\nCVE-2025-39897, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40165, CVE-2025-40166, CVE-2025-40167,\nCVE-2025-40169, CVE-2025-40171, CVE-2025-40172, CVE-2025-40173,\nCVE-2025-40176, CVE-2025-40178, CVE-2025-40179, CVE-2025-40180,\nCVE-2025-40183, CVE-2025-40187, CVE-2025-40188, CVE-2025-40192,\nCVE-2025-40193, CVE-2025-40194, CVE-2025-40196, CVE-2025-40198,\nCVE-2025-40200, CVE-2025-40201, CVE-2025-40202, CVE-2025-40204,\nCVE-2025-40205, CVE-2025-40206, CVE-2025-40207, CVE-2025-40211,\nCVE-2025-40218, CVE-2025-40219, CVE-2025-40220, CVE-2025-40221,\nCVE-2025-40223, CVE-2025-40226, CVE-2025-40231, CVE-2025-40233,\nCVE-2025-40235, CVE-2025-40237, CVE-2025-40238, CVE-2025-40240,\nCVE-2025-40242, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,\nCVE-2025-40248, CVE-2025-40250, CVE-2025-40251, 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-40266, CVE-2025-40268, CVE-2025-40269,\nCVE-2025-40271, CVE-2025-40272, CVE-2025-40273, CVE-2025-40275,\nCVE-2025-40277, CVE-2025-40278, CVE-2025-40279, CVE-2025-40280,\nCVE-2025-40281, CVE-2025-40282, CVE-2025-40283, CVE-2025-40284,\nCVE-2025-40285, CVE-2025-40286, CVE-2025-40287, CVE-2025-40288,\nCVE-2025-40289, CVE-2025-40292, CVE-2025-40293, CVE-2025-40294,\nCVE-2025-40301, CVE-2025-40303, CVE-2025-40304, CVE-2025-40305,\nCVE-2025-40306, CVE-2025-40307, CVE-2025-40308, CVE-2025-40309,\nCVE-2025-40310, CVE-2025-40311, CVE-2025-40312, CVE-2025-40313,\nCVE-2025-40314, CVE-2025-40315, CVE-2025-40317, CVE-2025-40318,\nCVE-2025-40319, CVE-2025-40320, CVE-2025-40321, CVE-2025-40322,\nCVE-2025-40323, CVE-2025-40324, CVE-2025-40328, CVE-2025-40329,\nCVE-2025-40331, CVE-2025-40333, CVE-2025-40337, CVE-2025-40339,\nCVE-2025-40341, CVE-2025-40342, CVE-2025-40343, CVE-2025-40345,\nCVE-2025-40346, CVE-2025-40347, CVE-2025-40349, CVE-2025-40350,\nCVE-2025-40351, CVE-2025-40353, CVE-2025-40358, CVE-2025-40360,\nCVE-2025-40363, CVE-2025-68168, CVE-2025-68171, CVE-2025-68172,\nCVE-2025-68173, CVE-2025-68176, CVE-2025-68177, CVE-2025-68178,\nCVE-2025-68179, CVE-2025-68180, CVE-2025-68183, CVE-2025-68184,\nCVE-2025-68185, CVE-2025-68190, CVE-2025-68191, CVE-2025-68192,\nCVE-2025-68194, CVE-2025-68198, CVE-2025-68200, CVE-2025-68201,\nCVE-2025-68204, CVE-2025-68208, CVE-2025-68213, CVE-2025-68214,\nCVE-2025-68217, CVE-2025-68218, CVE-2025-68219, CVE-2025-68220,\nCVE-2025-68222, CVE-2025-68223, CVE-2025-68227, CVE-2025-68229,\nCVE-2025-68231, CVE-2025-68233, CVE-2025-68235, CVE-2025-68237,\nCVE-2025-68238, CVE-2025-68241, CVE-2025-68244, CVE-2025-68245,\nCVE-2025-68246, CVE-2025-68249, CVE-2025-68282, CVE-2025-68283,\nCVE-2025-68284, CVE-2025-68285, CVE-2025-68286, CVE-2025-68287,\nCVE-2025-68288, CVE-2025-68289, CVE-2025-68290, CVE-2025-68295,\nCVE-2025-68297, CVE-2025-68301, CVE-2025-68302, CVE-2025-68303,\nCVE-2025-68305, CVE-2025-68307, CVE-2025-68308, CVE-2025-68310,\nCVE-2025-68311, CVE-2025-68312, CVE-2025-68313, CVE-2025-68315,\nCVE-2025-68320, CVE-2025-68321, CVE-2025-68322, CVE-2025-68327,\nCVE-2025-68328, CVE-2025-68330, CVE-2025-68331, CVE-2025-68339,\nCVE-2025-68340, CVE-2025-68342, CVE-2025-68343, CVE-2025-68734,\nCVE-2026-23060, CVE-2026-23074, CVE-2026-23111)\n","status":"published","published":"2026-04-09T23:38:24Z","modified":"2026-11-04T20:01:11.526209673Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8261-1","title":"linux-xilinx vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nQualys discovered that several vulnerabilities existed in the AppArmor\nLinux kernel Security Module (LSM). An unprivileged local attacker could\nuse these issues to load, replace, and remove arbitrary AppArmor profiles\ncausing denial of service, exposure of sensitive information (kernel\nmemory), local privilege escalation, or possibly escape a container.\n(LP: #2143853, CVE-2026-23268, CVE-2026-23269, CVE-2026-23403,\nCVE-2026-23404, CVE-2026-23405, CVE-2026-23406, CVE-2026-23407,\nCVE-2026-23408, CVE-2026-23409, CVE-2026-23410, CVE-2026-23411)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - Nios II architecture;\n  - PA-RISC architecture;\n  - PowerPC architecture;\n  - RISC-V architecture;\n  - S390 architecture;\n  - Sun Sparc architecture;\n  - User-Mode Linux (UML);\n  - x86 architecture;\n  - Xtensa architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Block device driver;\n  - Network block device driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - Hardware random number generator core;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - CPU frequency scaling framework;\n  - Hardware crypto device drivers;\n  - Device frequency scaling framework;\n  - DMA engine subsystem;\n  - ARM SCMI message protocol;\n  - EFI core;\n  - Intel Stratix 10 firmware drivers;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - CoreSight HW tracing drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - Input Device (Miscellaneous) drivers;\n  - Input Device (Tablet) drivers;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - ISDN/mISDN subsystem;\n  - Macintosh device drivers;\n  - Mailbox framework;\n  - Multiple devices driver;\n  - Media drivers;\n  - Fastrpc Driver;\n  - MOST (Media Oriented Systems Transport) drivers;\n  - MTD block device drivers;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Texas Instruments network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PCI subsystem;\n  - PCCARD (PCMCIA/CardBus) bus subsystem;\n  - Performance monitor drivers;\n  - Pin controllers subsystem;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - ARM PM domains;\n  - PPS (Pulse Per Second) driver;\n  - PTP clock framework;\n  - PWM drivers;\n  - Voltage and Current Regulator drivers;\n  - Remote Processor subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - Trusted Execution Environment drivers;\n  - TTY drivers;\n  - Userspace I/O drivers;\n  - Cadence USB3 driver;\n  - DesignWare USB3 driver;\n  - USB Gadget drivers;\n  - USB Host Controller drivers;\n  - Renesas USBHS Controller drivers;\n  - USB Mass Storage drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Virtio Host (VHOST) subsystem;\n  - Backlight driver;\n  - Framebuffer layer;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - AFS file system;\n  - BFS file system;\n  - BTRFS file system;\n  - Ceph distributed file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - GFS2 file system;\n  - HFS file system;\n  - HFS+ file system;\n  - HugeTLB file system;\n  - Journaling layer for block devices (JBD2);\n  - JFS file system;\n  - KERNFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - OrangeFS file system;\n  - Proc file system;\n  - Diskquota system;\n  - SMB network file system;\n  - SquashFS file system;\n  - UDF file system;\n  - XFS file system;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Mellanox drivers;\n  - NFS page cache wrapper;\n  - Memory management;\n  - Memory Management;\n  - Media input infrastructure;\n  - Bluetooth subsystem;\n  - IP tunnels definitions;\n  - Network traffic control;\n  - Rose network layer;\n  - Network sockets;\n  - io_uring subsystem;\n  - Control group (cgroup);\n  - Kernel crash support code;\n  - Kernel futex primitives;\n  - Locking primitives;\n  - PID allocator;\n  - Scheduler infrastructure;\n  - Shadow Call Stack mechanism;\n  - Syscalls implementation;\n  - Timer subsystem;\n  - Tracing infrastructure;\n  - 9P file system network protocol;\n  - Amateur Radio drivers;\n  - B.A.T.M.A.N. meshing protocol;\n  - CAIF protocol;\n  - Ceph Core library;\n  - Networking core;\n  - Devlink API;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - Netfilter;\n  - NET/ROM layer;\n  - NFC subsystem;\n  - Open vSwitch;\n  - RF switch subsystem;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TIPC protocol;\n  - TLS protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - eXpress Data Path;\n  - XFRM subsystem;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - Intel ASoC drivers;\n  - QCOM ASoC drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-57795, CVE-2025-21833, CVE-2025-22022, CVE-2025-22103,\nCVE-2025-22105, CVE-2025-22106, CVE-2025-22107, CVE-2025-22111,\nCVE-2025-22113, CVE-2025-22121, CVE-2025-22124, CVE-2025-22125,\nCVE-2025-23129, CVE-2025-23130, CVE-2025-23133, CVE-2025-23143,\nCVE-2025-37860, CVE-2025-38022, CVE-2025-38105, CVE-2025-38234,\nCVE-2025-38502, CVE-2025-38556, CVE-2025-38627, CVE-2025-38643,\nCVE-2025-38709, CVE-2025-39678, CVE-2025-39697, CVE-2025-39805,\nCVE-2025-39806, CVE-2025-39807, CVE-2025-39808, CVE-2025-39810,\nCVE-2025-39811, CVE-2025-39812, CVE-2025-39813, CVE-2025-39815,\nCVE-2025-39817, CVE-2025-39819, CVE-2025-39823, CVE-2025-39824,\nCVE-2025-39825, CVE-2025-39826, CVE-2025-39827, CVE-2025-39828,\nCVE-2025-39829, CVE-2025-39832, CVE-2025-39835, CVE-2025-39836,\nCVE-2025-39838, CVE-2025-39839, CVE-2025-39841, CVE-2025-39842,\nCVE-2025-39843, CVE-2025-39844, CVE-2025-39845, CVE-2025-39846,\nCVE-2025-39847, CVE-2025-39848, CVE-2025-39849, CVE-2025-39850,\nCVE-2025-39851, CVE-2025-39852, CVE-2025-39853, CVE-2025-39854,\nCVE-2025-39857, CVE-2025-39860, CVE-2025-39861, CVE-2025-39863,\nCVE-2025-39864, CVE-2025-39865, CVE-2025-39866, CVE-2025-39869,\nCVE-2025-39870, CVE-2025-39871, CVE-2025-39873, CVE-2025-39876,\nCVE-2025-39877, CVE-2025-39880, CVE-2025-39881, CVE-2025-39883,\nCVE-2025-39885, CVE-2025-39886, CVE-2025-39891, CVE-2025-39894,\nCVE-2025-39895, CVE-2025-39899, CVE-2025-39901, CVE-2025-39902,\nCVE-2025-39907, CVE-2025-39909, CVE-2025-39911, CVE-2025-39913,\nCVE-2025-39914, CVE-2025-39916, CVE-2025-39920, CVE-2025-39923,\nCVE-2025-39927, CVE-2025-39929, CVE-2025-39931, CVE-2025-39932,\nCVE-2025-39934, CVE-2025-39937, CVE-2025-39938, CVE-2025-39940,\nCVE-2025-39942, CVE-2025-39943, CVE-2025-39944, CVE-2025-39945,\nCVE-2025-39947, CVE-2025-39948, CVE-2025-39949, CVE-2025-39950,\nCVE-2025-39951, CVE-2025-39952, CVE-2025-39953, CVE-2025-39955,\nCVE-2025-39957, CVE-2025-39961, CVE-2025-39965, CVE-2025-39967,\nCVE-2025-39968, CVE-2025-39969, CVE-2025-39970, CVE-2025-39971,\nCVE-2025-39972, CVE-2025-39973, CVE-2025-39977, CVE-2025-39978,\nCVE-2025-39980, CVE-2025-39981, CVE-2025-39982, CVE-2025-39985,\nCVE-2025-39986, CVE-2025-39987, CVE-2025-39988, CVE-2025-39991,\nCVE-2025-39992, CVE-2025-39994, CVE-2025-39995, CVE-2025-39996,\nCVE-2025-39998, CVE-2025-40000, CVE-2025-40001, CVE-2025-40006,\nCVE-2025-40008, CVE-2025-40009, CVE-2025-40010, CVE-2025-40011,\nCVE-2025-40013, CVE-2025-40016, CVE-2025-40020, CVE-2025-40021,\nCVE-2025-40024, CVE-2025-40026, CVE-2025-40027, CVE-2025-40029,\nCVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033,\nCVE-2025-40035, CVE-2025-40036, CVE-2025-40037, CVE-2025-40038,\nCVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40047,\nCVE-2025-40048, CVE-2025-40049, CVE-2025-40051, CVE-2025-40052,\nCVE-2025-40053, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057,\nCVE-2025-40058, CVE-2025-40059, CVE-2025-40060, CVE-2025-40061,\nCVE-2025-40062, CVE-2025-40067, CVE-2025-40068, CVE-2025-40070,\nCVE-2025-40071, CVE-2025-40077, CVE-2025-40078, CVE-2025-40079,\nCVE-2025-40080, CVE-2025-40081, CVE-2025-40083, CVE-2025-40084,\nCVE-2025-40085, CVE-2025-40087, CVE-2025-40088, CVE-2025-40092,\nCVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096,\nCVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40103,\nCVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40107,\nCVE-2025-40109, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,\nCVE-2025-40115, CVE-2025-40116, CVE-2025-40118, CVE-2025-40120,\nCVE-2025-40121, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,\nCVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40134,\nCVE-2025-40137, CVE-2025-40140, CVE-2025-40141, CVE-2025-40153,\nCVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40159,\nCVE-2025-40160, CVE-2025-40164, CVE-2025-40165, CVE-2025-40166,\nCVE-2025-40167, CVE-2025-40169, CVE-2025-40171, CVE-2025-40172,\nCVE-2025-40173, CVE-2025-40176, CVE-2025-40178, CVE-2025-40179,\nCVE-2025-40180, CVE-2025-40183, CVE-2025-40187, CVE-2025-40188,\nCVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40196,\nCVE-2025-40198, CVE-2025-40200, CVE-2025-40201, CVE-2025-40202,\nCVE-2025-40204, CVE-2025-40205, CVE-2025-40206, CVE-2025-40207,\nCVE-2025-40211, CVE-2025-40218, CVE-2025-40219, CVE-2025-40220,\nCVE-2025-40221, CVE-2025-40223, CVE-2025-40226, CVE-2025-40231,\nCVE-2025-40233, CVE-2025-40235, CVE-2025-40237, CVE-2025-40238,\nCVE-2025-40240, CVE-2025-40242, CVE-2025-40243, CVE-2025-40244,\nCVE-2025-40245, CVE-2025-40248, CVE-2025-40250, CVE-2025-40251,\nCVE-2025-40252, CVE-2025-40253, CVE-2025-40254, CVE-2025-40257,\nCVE-2025-40258, CVE-2025-40259, CVE-2025-40261, CVE-2025-40262,\nCVE-2025-40263, CVE-2025-40264, CVE-2025-40266, CVE-2025-40268,\nCVE-2025-40269, CVE-2025-40271, CVE-2025-40272, CVE-2025-40273,\nCVE-2025-40275, CVE-2025-40277, CVE-2025-40278, CVE-2025-40279,\nCVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283,\nCVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287,\nCVE-2025-40288, CVE-2025-40289, CVE-2025-40292, CVE-2025-40293,\nCVE-2025-40294, CVE-2025-40301, CVE-2025-40303, CVE-2025-40304,\nCVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308,\nCVE-2025-40309, CVE-2025-40310, CVE-2025-40311, CVE-2025-40312,\nCVE-2025-40313, CVE-2025-40314, CVE-2025-40315, CVE-2025-40317,\nCVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,\nCVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40325,\nCVE-2025-40328, CVE-2025-40329, CVE-2025-40331, CVE-2025-40333,\nCVE-2025-40337, CVE-2025-40339, CVE-2025-40341, CVE-2025-40342,\nCVE-2025-40343, CVE-2025-40345, CVE-2025-40346, CVE-2025-40347,\nCVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40353,\nCVE-2025-40358, CVE-2025-40360, CVE-2025-40363, CVE-2025-68168,\nCVE-2025-68171, CVE-2025-68172, CVE-2025-68173, CVE-2025-68176,\nCVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180,\nCVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68190,\nCVE-2025-68191, CVE-2025-68192, CVE-2025-68194, CVE-2025-68198,\nCVE-2025-68200, CVE-2025-68201, CVE-2025-68204, CVE-2025-68206,\nCVE-2025-68208, CVE-2025-68213, CVE-2025-68214, CVE-2025-68217,\nCVE-2025-68218, CVE-2025-68219, CVE-2025-68220, CVE-2025-68222,\nCVE-2025-68223, CVE-2025-68227, CVE-2025-68229, CVE-2025-68231,\nCVE-2025-68233, CVE-2025-68235, CVE-2025-68237, CVE-2025-68238,\nCVE-2025-68241, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246,\nCVE-2025-68249, CVE-2025-68254, CVE-2025-68255, CVE-2025-68256,\nCVE-2025-68257, CVE-2025-68258, CVE-2025-68259, CVE-2025-68261,\nCVE-2025-68263, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266,\nCVE-2025-68282, CVE-2025-68283, CVE-2025-68284, CVE-2025-68285,\nCVE-2025-68286, CVE-2025-68287, CVE-2025-68288, CVE-2025-68289,\nCVE-2025-68290, CVE-2025-68295, CVE-2025-68297, CVE-2025-68301,\nCVE-2025-68302, CVE-2025-68303, CVE-2025-68305, CVE-2025-68307,\nCVE-2025-68308, CVE-2025-68310, CVE-2025-68311, CVE-2025-68312,\nCVE-2025-68313, CVE-2025-68315, CVE-2025-68320, CVE-2025-68321,\nCVE-2025-68322, CVE-2025-68325, CVE-2025-68327, CVE-2025-68328,\nCVE-2025-68330, CVE-2025-68331, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68339, CVE-2025-68340,\nCVE-2025-68342, CVE-2025-68343, CVE-2025-68344, CVE-2025-68345,\nCVE-2025-68346, CVE-2025-68347, CVE-2025-68349, CVE-2025-68354,\nCVE-2025-68362, CVE-2025-68363, CVE-2025-68364, CVE-2025-68366,\nCVE-2025-68367, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68727, CVE-2025-68728, CVE-2025-68732, CVE-2025-68733,\nCVE-2025-68734, CVE-2025-68740, CVE-2025-68741, CVE-2025-68742,\nCVE-2025-68744, CVE-2025-68746, CVE-2025-68753, CVE-2025-68755,\nCVE-2025-68756, CVE-2025-68757, CVE-2025-68758, CVE-2025-68759,\nCVE-2025-68763, CVE-2025-68764, CVE-2025-68765, CVE-2025-68766,\nCVE-2025-68767, CVE-2025-68769, CVE-2025-68770, CVE-2025-68771,\nCVE-2025-68772, CVE-2025-68773, CVE-2025-68774, CVE-2025-68775,\nCVE-2025-68776, CVE-2025-68777, CVE-2025-68778, CVE-2025-68780,\nCVE-2025-68782, CVE-2025-68783, CVE-2025-68785, CVE-2025-68786,\nCVE-2025-68787, CVE-2025-68788, CVE-2025-68794, CVE-2025-68795,\nCVE-2025-68796, CVE-2025-68797, CVE-2025-68798, CVE-2025-68799,\nCVE-2025-68800, CVE-2025-68801, CVE-2025-68804, CVE-2025-68806,\nCVE-2025-68808, CVE-2025-68809, CVE-2025-68810, CVE-2025-68811,\nCVE-2025-68813, CVE-2025-68814, CVE-2025-68815, CVE-2025-68816,\nCVE-2025-68817, CVE-2025-68818, CVE-2025-68819, CVE-2025-68820,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71125, CVE-2025-71126, CVE-2025-71127,\nCVE-2025-71130, CVE-2025-71131, CVE-2025-71132, CVE-2025-71133,\nCVE-2025-71135, CVE-2025-71136, CVE-2025-71137, CVE-2025-71138,\nCVE-2025-71140, CVE-2025-71141, CVE-2025-71143, CVE-2025-71147,\nCVE-2025-71148, CVE-2025-71150, CVE-2025-71151, CVE-2025-71153,\nCVE-2025-71154, CVE-2026-23060, CVE-2026-23074, CVE-2026-23111,\nCVE-2026-23112, CVE-2026-23209, CVE-2026-23231, CVE-2026-23273)\n","status":"published","published":"2026-05-07T15:54:20Z","modified":"2026-09-07T14:05:25.637433365Z","updated_at":"2026-11-02T16:58:22.951676Z"}]}}