{"id":"CVE-2026-23059","aliases":["AZL-77244","BELL-CVE-2026-23059","DEBIAN-CVE-2026-23059","DSA-6126-1","EUVD-2026-5485","GHSA-6mm8-fcwp-3g49","MGASA-2026-0097","MGASA-2026-0098","OESA-2026-1566","OESA-2026-1567","OESA-2026-1570","ROOT-OS-UBUNTU-2404-CVE-2026-23059","SUSE-SU-2026:20838-1","SUSE-SU-2026:20873-1","SUSE-SU-2026:20931-1","SUSE-SU-2026:21284-1","SUSE-SU-2026:24550-1","SUSE-SU-2026:5091-1","SUSE-SU-2026:5121-1","UBUNTU-CVE-2026-23059","USN-8278-1","USN-8278-2","USN-8289-1","USN-8289-2","USN-8296-1","USN-8296-2","USN-8393-1","USN-8440-1","USN-8499-1","USN-8570-1","USN-8570-2","USN-8594-1","USN-8604-1","USN-8605-1","USN-8669-1","openSUSE-SU-2026:20416-1"],"status":"published","title":"scsi: qla2xxx: Sanitize payload size to prevent member overflow","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Sanitize payload size to prevent member overflow\n\nIn qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size\nreported by firmware is used to calculate the copy length into\nitem-\u003eiocb. However, the iocb member is defined as a fixed-size 64-byte\narray within struct purex_item.\n\nIf the reported frame_size exceeds 64 bytes, subsequent memcpy calls will\noverflow the iocb member boundary. While extra memory might be allocated,\nthis cross-member write is unsafe and triggers warnings under\nCONFIG_FORTIFY_SOURCE.\n\nFix this by capping total_bytes to the size of the iocb member (64 bytes)\nbefore allocation and copying. This ensures all copies remain within the\nbounds of the destination structure member.","severity":{"version":"4.0","score":7.1,"vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","level":"high","from":"osv"},"epss":{"day":"2026-11-12","score":0.00201,"percentile":0.10113,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2026-02-04T16:07:42Z","modified":"2026-11-11T09:39:25Z","fixes":[{"ecosystem":"Azure Linux:3","package":"kernel","fixed_in":["6.6.126.1-1"],"sources":["osv"]},{"ecosystem":"Alpaquita:25","package":"linux-lts","fixed_in":["6.12.73-r0"],"sources":["osv"]},{"ecosystem":"Alpaquita:stream","package":"linux-lts","fixed_in":["6.18.35-r1"],"sources":["osv"]},{"ecosystem":"Linux","package":"Kernel","fixed_in":["6.6.122","6.12.68","6.18.8"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"linux","fixed_in":["6.12.69-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"linux","fixed_in":["6.18.8-1"],"sources":["osv"]},{"ecosystem":"Root: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-1057.60~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","fixed_in":["6.8.0-1059.65~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-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-1060.63~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","fixed_in":["6.8.0-124.124~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","fixed_in":["6.8.0-1055.56~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","fixed_in":["6.8.0-117.117.1~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","fixed_in":["6.8.0-1054.57~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","fixed_in":["6.8.0-1054.55~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","fixed_in":["6.8.0-117.117~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","fixed_in":["6.8.1-1051.52~22.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux","fixed_in":["6.8.0-117.117"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","fixed_in":["6.8.0-1055.58"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","fixed_in":["6.8.0-1056.62"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","fixed_in":["6.17.0-1021.21~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","fixed_in":["6.8.0-1058.65"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","fixed_in":["6.8.0-1039.42"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","fixed_in":["6.8.0-1058.61"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","fixed_in":["6.17.0-1021.24~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","fixed_in":["6.8.0-1054.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","fixed_in":["6.8.0-1041.44"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","fixed_in":["6.17.0-41.41~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","fixed_in":["6.8.0-1055.56"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","fixed_in":["6.8.0-117.117.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","fixed_in":["6.8.0-1054.57"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","fixed_in":["6.17.0-1031.31"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","fixed_in":["6.8.0-1054.57.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","fixed_in":["6.8.0-1024.24"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","fixed_in":["6.17.0-1030.30"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","fixed_in":["6.8.0-1054.55"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","fixed_in":["6.17.0-1019.19~24.04.3"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","fixed_in":["6.8.0-1056.60"],"sources":["osv"]},{"ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","fixed_in":["6.8.0-1032.33"],"sources":["osv"]},{"ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","fixed_in":["6.8.0-1022.26"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","fixed_in":["6.8.0-2045.46"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","fixed_in":["6.8.1-1051.52"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","fixed_in":["6.17.0-1018.20~24.04.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","fixed_in":["6.8.0-1055.58+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","fixed_in":["6.8.0-1059.65+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","fixed_in":["6.8.0-116.116+fips1"],"sources":["osv"]},{"ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","fixed_in":["6.8.0-1058.61+fips1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Azure Linux:3","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.126.1-1"}]}]},{"source":"osv","ecosystem":"Alpaquita:25","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.66-r0"},{"fixed":"6.12.73-r0"}]}]},{"source":"osv","ecosystem":"Alpaquita:stream","package":"linux-lts","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.12.92-r1"},{"fixed":"6.18.35-r1"}]}]},{"source":"osv","ecosystem":"Linux","package":"Kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.6.0"},{"fixed":"6.6.122"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.68"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.8"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.69-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1~bpo12+1"]},{"source":"osv","ecosystem":"Debian:14","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.18.8-1"}]}],"versions":["6.12.100-1","6.12.101-1","6.12.105-1","6.12.107-1","6.12.111-1","6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1","6.12.69-1~bpo12+1","6.12.73-1","6.12.73-1~bpo12+1","6.12.74-1","6.12.74-2","6.12.74-2~bpo12+1","6.12.85-1","6.12.85-1~bpo12+1","6.12.86-1","6.12.86-1~bpo12+1","6.12.88-1","6.12.88-1~bpo12+1","6.12.90-1","6.12.90-1~bpo12+1","6.12.90-2","6.12.90-2~bpo12+1","6.12.94-1","6.12.94-1~bpo12+1","6.12.95-1","6.12.95-1~bpo12+1","6.12.96-1","6.13.10-1~exp1","6.13.11-1~exp1","6.13.2-1~exp1","6.13.3-1~exp1","6.13.4-1~exp1","6.13.5-1~exp1","6.13.6-1~exp1","6.13.7-1~exp1","6.13.8-1~exp1","6.13.9-1~exp1","6.13~rc6-1~exp1","6.13~rc7-1~exp1","6.14.3-1~exp1","6.14.5-1~exp1","6.14.6-1~exp1","6.15-1~exp1","6.15.1-1~exp1","6.15.2-1~exp1","6.15.3-1~exp1","6.15.4-1~exp1","6.15.5-1~exp1","6.15.6-1~exp1","6.15~rc7-1~exp1","6.16-1~exp1","6.16.1-1~exp1","6.16.10-1","6.16.11-1","6.16.12-1","6.16.12-1~bpo13+1","6.16.12-2","6.16.3-1","6.16.3-1~bpo13+1","6.16.5-1","6.16.6-1","6.16.7-1","6.16.8-1","6.16.9-1","6.16~rc7-1~exp1","6.17.10-1","6.17.11-1","6.17.12-1","6.17.13-1","6.17.13-1~bpo13+1","6.17.2-1~exp1","6.17.5-1~exp1","6.17.6-1","6.17.7-1","6.17.7-2","6.17.8-1","6.17.8-1~bpo13+1","6.17.9-1","6.18.1-1~exp1","6.18.2-1~exp1","6.18.3-1","6.18.5-1","6.18.5-1~bpo13+1","6.18~rc4-1~exp1","6.18~rc4-1~exp2","6.18~rc5-1~exp1","6.18~rc6-1~exp1","6.18~rc7-1~exp1"]},{"source":"osv","ecosystem":"Debian:13","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.69-1"}]}],"versions":["6.12.38-1","6.12.41-1","6.12.43-1","6.12.43-1~bpo12+1","6.12.48-1","6.12.57-1","6.12.57-1~bpo12+1","6.12.63-1","6.12.63-1~bpo12+1","6.12.69-1~bpo12+1"],"bundled":251},{"source":"osv","ecosystem":"Mageia:9","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130-1.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-virtualbox","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.14-15.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kmod-xtables-addons","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.24-89.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"Mageia:9","package":"kernel-linus","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.130-1.mga9"}]}],"bundled":240},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP1","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-142.0.0.136.oe2403sp1"}]}],"bundled":73},{"source":"osv","ecosystem":"openEuler:24.03-LTS-SP2","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-142.0.0.137.oe2403sp2"}]}],"bundled":73},{"source":"osv","ecosystem":"openEuler:24.03-LTS","package":"kernel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.6.0-142.0.0.124.oe2403"}]}],"bundled":73},{"source":"osv","ecosystem":"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":"SUSE:Linux Micro 6.0","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.55.1"}]}],"bundled":1056},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.55.1.159998.21.42"}]}],"bundled":1056},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-kvmsmall","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.55.1"}]}],"bundled":1056},{"source":"osv","ecosystem":"SUSE:Linux Micro 6.0","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-159998.55.1"}]}],"bundled":1056},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-64kb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-default-base","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1.150700.17.51.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Basesystem 15 SP7","package":"kernel-zfcpdump","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-docs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-obs-build","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Development Tools 15 SP7","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Legacy 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 15 SP7","package":"kernel-livepatch-SLE15-SP7_Update_24","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-150700.15.3.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Module for Public Cloud 15 SP7","package":"kernel-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Workstation Extension 15 SP7","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.0-150700.53.90.1"}]}],"bundled":1077},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.339.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Live Patching 12 SP5","package":"kgraft-patch-SLE12-SP5_Update_90","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1-8.3.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.339.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.339.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP5-LTSS","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.339.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-default","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.339.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-source","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.339.1"}]}],"bundled":130},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5","package":"kernel-syms","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.12.14-122.339.1"}]}],"bundled":130},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"linux-hwe-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.8.0-28.30~16.04.1","4.8.0-30.32~16.04.1","4.8.0-32.34~16.04.1","4.8.0-34.36~16.04.1","4.10.0-14.16~16.04.1","4.10.0-19.21~16.04.1","4.10.0-20.22~16.04.1","4.10.0-21.23~16.04.1","4.10.0-22.24~16.04.1","4.10.0-24.28~16.04.1","4.10.0-26.30~16.04.1","4.11.0-13.19~16.04.1","4.11.0-14.20~16.04.1","4.13.0-16.19~16.04.3","4.13.0-17.20~16.04.1","4.13.0-19.22~16.04.1","4.13.0-21.24~16.04.1","4.13.0-25.29~16.04.2","4.15.0-13.14~16.04.1","4.15.0-15.16~16.04.1","4.15.0-20.21~16.04.1","4.15.0-22.24~16.04.1","4.15.0-23.25~16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1021.24~18.04.1","5.0.0-1022.25~18.04.1","5.0.0-1023.26~18.04.1","5.0.0-1024.27~18.04.1","5.0.0-1025.28","5.0.0-1027.30"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-aws-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1019.21~18.04.1","5.3.0-1023.25~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.2","5.3.0-1033.35","5.3.0-1034.36","5.3.0-1035.37"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.2","4.15.0-1003.3","4.15.0-1004.4","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1012.12","4.15.0-1013.13","4.15.0-1014.14","4.15.0-1018.18","4.15.0-1019.19","4.15.0-1021.21","4.15.0-1022.23","4.15.0-1023.24","4.15.0-1025.26","4.15.0-1028.29","4.15.0-1030.31","4.15.0-1031.32","4.15.0-1032.33","4.15.0-1035.36","4.15.0-1036.38","4.15.0-1037.39","4.18.0-1011.11~18.04.1","4.18.0-1013.13~18.04.1","4.18.0-1014.14~18.04.1","4.18.0-1018.18~18.04.1","4.18.0-1019.19~18.04.1","4.18.0-1020.20~18.04.1","4.18.0-1023.24~18.04.1","4.18.0-1024.25~18.04.1","4.18.0-1025.27~18.04.1","5.0.0-1014.14~18.04.1","5.0.0-1016.17~18.04.1","5.0.0-1018.19~18.04.1","5.0.0-1020.21~18.04.1","5.0.0-1022.23~18.04.1","5.0.0-1023.24~18.04.1","5.0.0-1025.27~18.04.1","5.0.0-1027.29~18.04.1","5.0.0-1028.30~18.04.1","5.0.0-1029.31~18.04.1","5.0.0-1031.33","5.0.0-1032.34","5.0.0-1035.37","5.0.0-1036.38"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8~18.04.1","5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1019.20~18.04.1","5.3.0-1020.21~18.04.1","5.3.0-1022.23~18.04.1","5.3.0-1028.29~18.04.1","5.3.0-1031.32~18.04.1","5.3.0-1032.33~18.04.1","5.3.0-1034.35~18.04.1","5.3.0-1035.36"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-azure-edge","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.18.0-1006.6~18.04.1","4.18.0-1007.7~18.04.1","4.18.0-1008.8~18.04.1","5.0.0-1012.12~18.04.2"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1001.1","4.15.0-1003.3","4.15.0-1005.5","4.15.0-1006.6","4.15.0-1008.8","4.15.0-1009.9","4.15.0-1010.10","4.15.0-1014.14","4.15.0-1015.15","4.15.0-1017.18","4.15.0-1018.19","4.15.0-1019.20","4.15.0-1021.22","4.15.0-1023.24","4.15.0-1024.25","4.15.0-1025.26","4.15.0-1026.27","4.15.0-1027.28","4.15.0-1028.29","4.15.0-1029.31","4.15.0-1030.32","4.15.0-1032.34","4.15.0-1033.35","4.15.0-1034.36","4.15.0-1036.38","4.15.0-1037.39","4.15.0-1040.42","4.15.0-1042.45","4.15.0-1044.70","5.0.0-1020.20~18.04.1","5.0.0-1021.21~18.04.1","5.0.0-1025.26~18.04.1","5.0.0-1026.27~18.04.1","5.0.0-1028.29~18.04.1","5.0.0-1029.30~18.04.1","5.0.0-1031.32","5.0.0-1033.34","5.0.0-1034.35"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-gcp-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1008.9~18.04.1","5.3.0-1009.10~18.04.1","5.3.0-1010.11~18.04.1","5.3.0-1012.13~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.17~18.04.1","5.3.0-1017.18~18.04.1","5.3.0-1018.19~18.04.1","5.3.0-1020.22~18.04.1","5.3.0-1026.28~18.04.1","5.3.0-1029.31~18.04.1","5.3.0-1030.32~18.04.1","5.3.0-1032.34~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu: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: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:18.04:LTS","package":"linux-oem","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["4.15.0-1002.3","4.15.0-1004.5","4.15.0-1006.9","4.15.0-1008.11","4.15.0-1009.12","4.15.0-1012.15","4.15.0-1013.16","4.15.0-1015.18","4.15.0-1017.20","4.15.0-1018.21","4.15.0-1021.24","4.15.0-1024.29","4.15.0-1026.31","4.15.0-1028.33","4.15.0-1030.35","4.15.0-1033.38","4.15.0-1034.39","4.15.0-1035.40","4.15.0-1036.41","4.15.0-1038.43","4.15.0-1039.44","4.15.0-1043.48","4.15.0-1045.50","4.15.0-1050.57","4.15.0-1056.65","4.15.0-1057.66","4.15.0-1059.68","4.15.0-1063.72","4.15.0-1064.73","4.15.0-1065.75","4.15.0-1066.76","4.15.0-1067.77","4.15.0-1069.79","4.15.0-1073.83","4.15.0-1076.86","4.15.0-1079.89","4.15.0-1080.90","4.15.0-1081.91","4.15.0-1087.97","4.15.0-1090.100","4.15.0-1091.101","4.15.0-1093.103","4.15.0-1094.104","4.15.0-1096.106","4.15.0-1097.107","4.15.0-1099.109","4.15.0-1100.110","4.15.0-1101.112","4.15.0-1102.113","4.15.0-1103.114"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.0","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.0.0-1007.12~18.04.1","5.0.0-1008.13~18.04.1","5.0.0-1009.14~18.04.1","5.0.0-1010.15~18.04.1","5.0.0-1011.16","5.0.0-1013.18","5.0.0-1014.19"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"linux-oracle-5.3","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1011.12~18.04.1","5.3.0-1013.14~18.04.1","5.3.0-1014.15~18.04.1","5.3.0-1016.18~18.04.1","5.3.0-1018.20~18.04.1","5.3.0-1024.26~18.04.1","5.3.0-1027.29~18.04.1","5.3.0-1028.30~18.04.1","5.3.0-1030.32~18.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.9~20.04.2","5.11.0-1014.15~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.2","5.11.0-1021.22~20.04.2","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.2","5.13.0-1011.12~20.04.1","5.13.0-1012.13~20.04.1","5.13.0-1014.15~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1019.21~20.04.1","5.13.0-1021.23~20.04.2","5.13.0-1022.24~20.04.1","5.13.0-1023.25~20.04.1","5.13.0-1025.27~20.04.1","5.13.0-1028.31~20.04.1","5.13.0-1029.32~20.04.1","5.13.0-1031.35~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-aws-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1041.43~20.04.1","5.8.0-1042.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1007.7~20.04.2","5.11.0-1012.13~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.2"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10~20.04.2","5.13.0-1012.14~20.04.1","5.13.0-1013.15~20.04.1","5.13.0-1014.16~20.04.1","5.13.0-1017.19~20.04.1","5.13.0-1021.24~20.04.1","5.13.0-1022.26~20.04.1","5.13.0-1023.27~20.04.1","5.13.0-1025.29~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1029.34~20.04.1","5.13.0-1031.37~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1033.35~20.04.1","5.8.0-1036.38~20.04.1","5.8.0-1039.42~20.04.1","5.8.0-1040.43~20.04.1","5.8.0-1041.44~20.04.1","5.8.0-1042.45~20.04.1","5.8.0-1043.46~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1063.66+cvm2.2","5.4.0-1063.66+cvm3.2","5.4.0-1064.67+cvm1.1","5.4.0-1065.68+cvm2.1","5.4.0-1067.70+cvm1.1","5.4.0-1068.71+cvm1.1","5.4.0-1069.72+cvm1.1","5.4.0-1070.73+cvm1.1","5.4.0-1072.75+cvm1.1","5.4.0-1073.76+cvm1.1","5.4.0-1074.77+cvm1.1","5.4.0-1076.79+cvm1.1","5.4.0-1078.81+cvm1.1","5.4.0-1080.83+cvm1.1","5.4.0-1083.87+cvm1.1","5.4.0-1085.90+cvm1.1","5.4.0-1085.90+cvm2.1","5.4.0-1086.91+cvm1.1","5.4.0-1089.94+cvm1.2","5.4.0-1090.95+cvm1.1","5.4.0-1091.96+cvm1.1","5.4.0-1092.97+cvm1.1","5.4.0-1095.101+cvm1.1","5.4.0-1098.104+cvm1.1","5.4.0-1100.106+cvm1.1","5.4.0-1103.109+cvm1.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1009.10~20.04.1","5.11.0-1014.16~20.04.1","5.11.0-1017.19~20.04.1","5.11.0-1018.20~20.04.2","5.11.0-1020.22~20.04.1","5.11.0-1021.23~20.04.1","5.11.0-1022.24~20.04.1","5.11.0-1023.25~20.04.1","5.11.0-1024.26~20.04.1","5.11.0-1026.29~20.04.1","5.11.0-1028.32~20.04.1","5.11.0-1029.33~20.04.3"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1008.9~20.04.3","5.13.0-1012.15~20.04.1","5.13.0-1013.16~20.04.1","5.13.0-1015.18~20.04.1","5.13.0-1019.23~20.04.1","5.13.0-1021.25~20.04.1","5.13.0-1023.28~20.04.1","5.13.0-1024.29~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1030.36~20.04.1","5.13.0-1031.37~20.04.1","5.13.0-1033.40~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gcp-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1032.34~20.04.1","5.8.0-1035.37~20.04.1","5.8.0-1038.40~20.04.1","5.8.0-1039.41"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1033.35","5.4.0-1035.37","5.4.0-1036.38","5.4.0-1037.39","5.4.0-1039.41","5.4.0-1041.43","5.4.0-1042.44","5.4.0-1043.45","5.4.0-1044.46","5.4.0-1046.48","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1055.58","5.4.0-1056.59","5.4.0-1057.60","5.4.0-1059.62","5.4.0-1061.64","5.4.0-1062.65","5.4.0-1063.66","5.4.0-1065.68","5.4.0-1066.69","5.4.0-1067.70","5.4.0-1068.71","5.4.0-1071.76","5.4.0-1072.77","5.4.0-1074.79","5.4.0-1076.82","5.4.0-1078.84","5.4.0-1080.86","5.4.0-1081.87","5.4.0-1083.89","5.4.0-1084.90","5.4.0-1086.93","5.4.0-1087.94","5.4.0-1090.97","5.4.0-1091.98","5.4.0-1094.101","5.4.0-1095.102","5.4.0-1096.103","5.4.0-1097.104","5.4.0-1098.105","5.4.0-1099.106","5.4.0-1100.107","5.4.0-1101.108","5.4.0-1102.109","5.4.0-1103.110","5.4.0-1104.111","5.4.0-1105.112"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gke-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1011.14~20.04.1","5.15.0-1014.17~20.04.1","5.15.0-1015.18~20.04.1","5.15.0-1016.19~20.04.1","5.15.0-1019.23~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1023.28~20.04.2","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1029.34~20.04.1","5.15.0-1031.36~20.04.1","5.15.0-1032.37~20.04.1","5.15.0-1033.38~20.04.1","5.15.0-1034.39~20.04.1","5.15.0-1036.41~20.04.1","5.15.0-1037.42~20.04.1","5.15.0-1038.43~20.04.1","5.15.0-1039.44~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-1008.9","5.4.0-1009.10","5.4.0-1010.11","5.4.0-1011.12","5.4.0-1012.13","5.4.0-1013.14","5.4.0-1014.15","5.4.0-1015.16","5.4.0-1016.17","5.4.0-1018.19","5.4.0-1021.22","5.4.0-1022.23","5.4.0-1023.24","5.4.0-1024.25","5.4.0-1025.26","5.4.0-1026.27","5.4.0-1027.28","5.4.0-1029.30","5.4.0-1031.32","5.4.0-1032.33","5.4.0-1033.34","5.4.0-1034.35","5.4.0-1036.37","5.4.0-1037.38","5.4.0-1038.39","5.4.0-1039.40","5.4.0-1040.41","5.4.0-1043.44","5.4.0-1046.48","5.4.0-1048.51","5.4.0-1049.52","5.4.0-1051.54","5.4.0-1052.55","5.4.0-1053.56","5.4.0-1054.57","5.4.0-1056.60","5.4.0-1057.61","5.4.0-1060.64","5.4.0-1061.65","5.4.0-1062.66","5.4.0-1064.68","5.4.0-1065.69","5.4.0-1066.70","5.4.0-1067.71","5.4.0-1068.72","5.4.0-1069.73","5.4.0-1070.74","5.4.0-1071.75","5.4.0-1072.76","5.4.0-1073.77","5.4.0-1074.78","5.4.0-1075.79","5.4.0-1076.80","5.4.0-1077.81","5.4.0-1078.82","5.4.0-1079.83","5.4.0-1080.84","5.4.0-1081.85","5.4.0-1083.87","5.4.0-1084.88","5.4.0-1085.89","5.4.0-1086.90","5.4.0-1087.91","5.4.0-1088.92","5.4.0-1089.93","5.4.0-1090.94","5.4.0-1091.95","5.4.0-1092.96","5.4.0-1093.97","5.4.0-1094.98","5.4.0-1095.99","5.4.0-1096.100","5.4.0-1097.101","5.4.0-1098.102","5.4.0-1099.103","5.4.0-1100.104","5.4.0-1101.105","5.4.0-1102.106"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-gkeop-5.15","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1003.5~20.04.2","5.15.0-1005.7~20.04.1","5.15.0-1007.10~20.04.1","5.15.0-1008.12~20.04.1","5.15.0-1011.15~20.04.2","5.15.0-1012.16~20.04.1","5.15.0-1013.17~20.04.1","5.15.0-1015.19~20.04.1","5.15.0-1016.21~20.04.1","5.15.0-1017.22~20.04.1","5.15.0-1018.23~20.04.1","5.15.0-1019.24~20.04.1","5.15.0-1020.25~20.04.1","5.15.0-1021.26~20.04.1","5.15.0-1022.27~20.04.1","5.15.0-1023.28~20.04.1","5.15.0-1024.29~20.04.1","5.15.0-1025.30~20.04.1","5.15.0-1026.31~20.04.1","5.15.0-1027.32~20.04.1","5.15.0-1028.33~20.04.1","5.15.0-1030.35~20.04.1","5.15.0-1031.37~20.04.1","5.15.0-1032.38~20.04.1","5.15.0-1033.39~20.04.1","5.15.0-1034.40~20.04.1","5.15.0-1035.41~20.04.1","5.15.0-1036.42~20.04.1","5.15.0-1037.43~20.04.1","5.15.0-1038.44~20.04.1","5.15.0-1039.45~20.04.1","5.15.0-1040.46~20.04.1","5.15.0-1043.50~20.04.1","5.15.0-1044.51~20.04.1","5.15.0-1045.52~20.04.1","5.15.0-1046.53~20.04.1","5.15.0-1047.54~20.04.1","5.15.0-1048.55~20.04.1","5.15.0-1049.56~20.04.1","5.15.0-1050.57~20.04.1","5.15.0-1051.58~20.04.1","5.15.0-1052.59~20.04.1","5.15.0-1053.60~20.04.1","5.15.0-1054.61~20.04.1","5.15.0-1055.62~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-22.23~20.04.1","5.11.0-25.27~20.04.1","5.11.0-27.29~20.04.1","5.11.0-34.36~20.04.1","5.11.0-36.40~20.04.1","5.11.0-37.41~20.04.2","5.11.0-38.42~20.04.1","5.11.0-40.44~20.04.2","5.11.0-41.45~20.04.1","5.11.0-43.47~20.04.2","5.11.0-44.48~20.04.2","5.11.0-46.51~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-21.21~20.04.1","5.13.0-22.22~20.04.1","5.13.0-23.23~20.04.2","5.13.0-25.26~20.04.1","5.13.0-27.29~20.04.1","5.13.0-28.31~20.04.1","5.13.0-30.33~20.04.1","5.13.0-35.40~20.04.1","5.13.0-37.42~20.04.1","5.13.0-39.44~20.04.1","5.13.0-40.45~20.04.1","5.13.0-41.46~20.04.1","5.13.0-44.49~20.04.1","5.13.0-48.54~20.04.1","5.13.0-51.58~20.04.1","5.13.0-52.59~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-hwe-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-23.24~20.04.1","5.8.0-25.26~20.04.1","5.8.0-28.30~20.04.1","5.8.0-29.31~20.04.1","5.8.0-31.33~20.04.1","5.8.0-33.36~20.04.1","5.8.0-34.37~20.04.2","5.8.0-36.40~20.04.1","5.8.0-38.43~20.04.1","5.8.0-40.45~20.04.1","5.8.0-41.46~20.04.1","5.8.0-43.49~20.04.1","5.8.0-44.50~20.04.1","5.8.0-45.51~20.04.1","5.8.0-48.54~20.04.1","5.8.0-49.55~20.04.1","5.8.0-50.56~20.04.1","5.8.0-53.60~20.04.1","5.8.0-55.62~20.04.1","5.8.0-59.66~20.04.1","5.8.0-63.71~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-intel-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1007.7","5.13.0-1008.8","5.13.0-1009.9","5.13.0-1010.10","5.13.0-1011.11","5.13.0-1014.15","5.13.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.10","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.10.0-1008.9","5.10.0-1011.12","5.10.0-1013.14","5.10.0-1014.15","5.10.0-1016.17","5.10.0-1017.18","5.10.0-1019.20","5.10.0-1021.22","5.10.0-1022.23","5.10.0-1023.24","5.10.0-1025.26","5.10.0-1026.27","5.10.0-1029.30","5.10.0-1032.33","5.10.0-1033.34","5.10.0-1034.35","5.10.0-1038.40","5.10.0-1044.46","5.10.0-1045.47","5.10.0-1049.51","5.10.0-1050.52","5.10.0-1051.53","5.10.0-1052.54","5.10.0-1053.55","5.10.0-1055.58","5.10.0-1057.61"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1009.10","5.13.0-1010.11","5.13.0-1012.16","5.13.0-1014.18","5.13.0-1017.21","5.13.0-1019.23","5.13.0-1020.24","5.13.0-1021.25","5.13.0-1022.26","5.13.0-1026.32","5.13.0-1028.35","5.13.0-1029.36"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.14.0-1004.4","5.14.0-1005.5","5.14.0-1007.7","5.14.0-1008.8","5.14.0-1010.10","5.14.0-1011.11","5.14.0-1013.13","5.14.0-1018.19","5.14.0-1020.22","5.14.0-1022.24","5.14.0-1024.26","5.14.0-1027.30","5.14.0-1029.32","5.14.0-1031.34","5.14.0-1032.35","5.14.0-1033.36","5.14.0-1034.37","5.14.0-1036.40","5.14.0-1038.42","5.14.0-1042.47","5.14.0-1044.49","5.14.0-1045.51","5.14.0-1046.53","5.14.0-1047.54","5.14.0-1048.55","5.14.0-1049.56","5.14.0-1050.57","5.14.0-1051.58","5.14.0-1052.59","5.14.0-1054.61","5.14.0-1055.62","5.14.0-1056.63","5.14.0-1057.64","5.14.0-1058.66","5.14.0-1059.67"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oem-5.6","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.6.0-1007.7","5.6.0-1008.8","5.6.0-1010.10","5.6.0-1011.11","5.6.0-1013.13","5.6.0-1017.17","5.6.0-1018.18","5.6.0-1020.20","5.6.0-1021.21","5.6.0-1023.23","5.6.0-1026.26","5.6.0-1027.27","5.6.0-1028.28","5.6.0-1031.32","5.6.0-1032.33","5.6.0-1033.35","5.6.0-1034.36","5.6.0-1035.37","5.6.0-1036.39","5.6.0-1039.43","5.6.0-1042.46","5.6.0-1047.51","5.6.0-1048.52","5.6.0-1050.54","5.6.0-1052.56","5.6.0-1053.57","5.6.0-1054.58","5.6.0-1055.59","5.6.0-1056.60"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1008.8~20.04.1","5.11.0-1013.14~20.04.1","5.11.0-1016.17~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1019.20~20.04.1","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1025.27~20.04.1","5.11.0-1027.30~20.04.1","5.11.0-1028.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.13","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1011.13~20.04.2","5.13.0-1015.19~20.04.1","5.13.0-1016.20~20.04.1","5.13.0-1018.22~20.04.1","5.13.0-1021.26~20.04.1","5.13.0-1025.30~20.04.1","5.13.0-1027.32~20.04.1","5.13.0-1028.33~20.04.1","5.13.0-1030.35~20.04.1","5.13.0-1033.39~20.04.1","5.13.0-1034.40~20.04.1","5.13.0-1036.43~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-oracle-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-1031.32~20.04.2","5.8.0-1033.34~20.04.1","5.8.0-1034.35~20.04.2","5.8.0-1037.38~20.04.1","5.8.0-1038.39~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-raspi2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.3.0-1007.8","5.3.0-1014.16","5.3.0-1015.17","5.3.0-1017.19","5.4.0-1004.4","5.4.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.4.0-24.28","5.4.0-26.30","5.4.0-27.31","5.4.0-28.32","5.4.0-30.34","5.4.0-31.35","5.4.0-33.37","5.4.0-34.38","5.4.0-36.41","5.4.0-37.42","5.4.0-39.44","5.4.0-40.45"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.11.0-1015.16~20.04.1","5.11.0-1017.18~20.04.1","5.11.0-1018.19~20.04.2","5.11.0-1020.21~20.04.1","5.11.0-1021.22~20.04.1","5.11.0-1022.23~20.04.1","5.11.0-1023.24~20.04.1","5.11.0-1024.25~20.04.1","5.11.0-1026.28~20.04.1","5.11.0-1028.31~20.04.1","5.11.0-1029.32~20.04.1","5.11.0-1030.34","5.11.0-1031.35"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"linux-riscv-5.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.8.0-14.16~20.04.1","5.8.0-14.16~20.04.3","5.8.0-16.18~20.04.1","5.8.0-17.19~20.04.1","5.8.0-18.20~20.04.1","5.8.0-20.22~20.04.1","5.8.0-22.24~20.04.1","5.8.0-25.27~20.04.1","5.8.0-26.28~20.04.1","5.8.0-29.31~20.04.1"]},{"source":"osv","ecosystem":"Ubuntu: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-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1019.20~22.04.1","5.19.0-1020.21~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1026.27~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1029.30~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1008.8~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1012.12~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.2","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1022.22~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-aws-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1057.60~22.04.1"}]}],"versions":["6.8.0-1009.9~22.04.2","6.8.0-1010.10~22.04.2","6.8.0-1011.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1016.17~22.04.2","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1023.25~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1035.37~22.04.1","6.8.0-1036.38~22.04.1","6.8.0-1039.41~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.44~22.04.1","6.8.0-1043.45~22.04.1","6.8.0-1044.46~22.04.1","6.8.0-1045.47~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1055.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.21~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1025.28~22.04.1","5.19.0-1026.29~22.04.1","5.19.0-1027.30~22.04.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1005.5~22.04.1","6.2.0-1006.6~22.04.1","6.2.0-1007.7~22.04.1","6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.3","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1","6.2.0-1019.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.7~22.04.1","6.5.0-1009.9~22.04.1","6.5.0-1010.10~22.04.1","6.5.0-1011.11~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.19~22.04.2","6.5.0-1019.20~22.04.1","6.5.0-1021.22~22.04.1","6.5.0-1022.23~22.04.1","6.5.0-1023.24~22.04.1","6.5.0-1024.25~22.04.1","6.5.0-1025.26~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-fde-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-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1020.22~22.04.2","5.19.0-1021.23~22.04.1","5.19.0-1022.24~22.04.1","5.19.0-1024.26~22.04.1","5.19.0-1025.27~22.04.1","5.19.0-1026.28~22.04.1","5.19.0-1027.29~22.04.1","5.19.0-1030.32~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1009.9~22.04.3","6.2.0-1010.10~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1011.11~22.04.3","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1016.18~22.04.1","6.2.0-1017.19~22.04.1","6.2.0-1018.20~22.04.1","6.2.0-1019.21~22.04.1","6.2.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1010.10~22.04.3","6.5.0-1011.11~22.04.1","6.5.0-1013.13~22.04.1","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1017.17~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1022.24~22.04.1","6.5.0-1023.25~22.04.1","6.5.0-1024.26~22.04.1","6.5.0-1025.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-gcp-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1060.63~22.04.1"}]}],"versions":["6.8.0-1010.11~22.04.1","6.8.0-1011.12~22.04.1","6.8.0-1012.13~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.1","6.8.0-1016.18~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1024.26~22.04.1","6.8.0-1025.27~22.04.1","6.8.0-1026.28~22.04.1","6.8.0-1027.29~22.04.1","6.8.0-1028.30~22.04.1","6.8.0-1029.31~22.04.1","6.8.0-1030.32~22.04.1","6.8.0-1031.33~22.04.1","6.8.0-1032.34~22.04.1","6.8.0-1033.35~22.04.1","6.8.0-1034.36~22.04.2","6.8.0-1036.38~22.04.1","6.8.0-1037.39~22.04.1","6.8.0-1040.42~22.04.1","6.8.0-1041.43~22.04.1","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.2","6.8.0-1048.51~22.04.1","6.8.0-1052.55~22.04.1","6.8.0-1053.56~22.04.1","6.8.0-1054.57~22.04.1","6.8.0-1058.61~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-28.29~22.04.1","5.19.0-32.33~22.04.1","5.19.0-35.36~22.04.1","5.19.0-38.39~22.04.1","5.19.0-40.41~22.04.1","5.19.0-41.42~22.04.1","5.19.0-42.43~22.04.1","5.19.0-43.44~22.04.1","5.19.0-45.46~22.04.1","5.19.0-46.47~22.04.1","5.19.0-50.50"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-25.25~22.04.2","6.2.0-26.26~22.04.1","6.2.0-31.31~22.04.1","6.2.0-32.32~22.04.1","6.2.0-33.33~22.04.1","6.2.0-34.34~22.04.1","6.2.0-35.35~22.04.1","6.2.0-36.37~22.04.1","6.2.0-37.38~22.04.1","6.2.0-39.40~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14~22.04.1","6.5.0-15.15~22.04.1","6.5.0-17.17~22.04.1","6.5.0-18.18~22.04.1","6.5.0-21.21~22.04.1","6.5.0-25.25~22.04.1","6.5.0-26.26~22.04.1","6.5.0-27.28~22.04.1","6.5.0-28.29~22.04.1","6.5.0-35.35~22.04.1","6.5.0-41.41~22.04.2","6.5.0-44.44~22.04.1","6.5.0-45.45~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-124.124~22.04.1"}]}],"versions":["6.8.0-38.38~22.04.1","6.8.0-39.39~22.04.1","6.8.0-40.40~22.04.3","6.8.0-45.45~22.04.1","6.8.0-47.47~22.04.1","6.8.0-48.48~22.04.1","6.8.0-49.49~22.04.1","6.8.0-50.51~22.04.1","6.8.0-51.52~22.04.1","6.8.0-52.53~22.04.1","6.8.0-57.59~22.04.1","6.8.0-58.60~22.04.1","6.8.0-59.61~22.04.1","6.8.0-60.63~22.04.1","6.8.0-64.67~22.04.1","6.8.0-65.68~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-85.85~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.2","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1","6.8.0-117.117~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-intel-iot-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1073.75"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1021.22~22.04.1","5.19.0-1022.23~22.04.1","5.19.0-1023.24~22.04.1","5.19.0-1024.25~22.04.1","5.19.0-1025.26~22.04.1","5.19.0-1027.28~22.04.1","5.19.0-1028.29~22.04.1","5.19.0-1030.30"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1008.8~22.04.1","6.2.0-1009.9~22.04.1","6.2.0-1011.11~22.04.1","6.2.0-1012.12~22.04.1","6.2.0-1013.13~22.04.1","6.2.0-1014.14~22.04.1","6.2.0-1015.15~22.04.1","6.2.0-1016.16~22.04.1","6.2.0-1017.17~22.04.1","6.2.0-1018.18~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-14.14.1~22.04.1","6.5.0-15.15.1.1~22.04.1","6.5.0-17.17.1.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-41.41.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-44.44.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1003.3~22.04.1","6.2.0-1009.9","6.2.0-1010.10","6.2.0-1011.11","6.2.0-1012.12","6.2.0-1013.13","6.2.0-1015.15"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1004.4","6.5.0-1007.7","6.5.0-1013.13","6.5.0-1014.14","6.5.0-1015.15","6.5.0-1018.18","6.5.0-1019.19","6.5.0-1021.22","6.5.0-1022.23","6.5.0-1023.24","6.5.0-1024.25"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-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-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1013.13~22.04.4","6.5.0-1014.14~22.04.1","6.5.0-1015.15~22.04.1","6.5.0-1016.16~22.04.1","6.5.0-1018.18~22.04.1","6.5.0-1019.19~22.04.1","6.5.0-1020.20~22.04.1","6.5.0-1021.21~22.04.1","6.5.0-1023.23~22.04.1","6.5.0-1024.24~22.04.1","6.5.0-1025.25~22.04.1","6.5.0-1026.26~22.04.1","6.5.0-1027.27~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-oracle-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.55~22.04.1"}]}],"versions":["6.8.0-1006.6~22.04.3","6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.17~22.04.1","6.8.0-1017.18~22.04.1","6.8.0-1018.19~22.04.1","6.8.0-1019.20~22.04.1","6.8.0-1020.21~22.04.1","6.8.0-1021.22~22.04.1","6.8.0-1022.23~22.04.1","6.8.0-1023.24~22.04.1","6.8.0-1024.25~22.04.1","6.8.0-1025.26~22.04.1","6.8.0-1026.27~22.04.1","6.8.0-1027.28~22.04.1","6.8.0-1028.29~22.04.1","6.8.0-1029.30~22.04.1","6.8.0-1030.31~22.04.1","6.8.0-1032.33~22.04.1","6.8.0-1033.34~22.04.1","6.8.0-1035.36~22.04.1","6.8.0-1037.38~22.04.1","6.8.0-1038.39~22.04.1","6.8.0-1039.40~22.04.1","6.8.0-1040.41~22.04.1","6.8.0-1041.42~22.04.1","6.8.0-1042.43~22.04.1","6.8.0-1043.44~22.04.1","6.8.0-1044.45~22.04.1","6.8.0-1047.48~22.04.1","6.8.0-1049.50~22.04.1","6.8.0-1050.51~22.04.1","6.8.0-1052.53~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.15.0-1032.35"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.13.0-1004.4","5.13.0-1006.6+22.04.1","5.13.0-1007.7+22.04.1","5.13.0-1010.11+22.04.1","5.15.0-1004.4","5.15.0-1005.5","5.15.0-1006.6","5.15.0-1007.7","5.15.0-1008.8","5.15.0-1011.12","5.15.0-1012.13","5.15.0-1014.16","5.15.0-1015.17","5.15.0-1016.18","5.15.0-1017.19","5.15.0-1018.21","5.15.0-1019.22","5.15.0-1020.23","5.15.0-1022.26","5.15.0-1023.27","5.15.0-1026.30","5.15.0-1027.31","5.15.0-1028.32"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1012.13~22.04.1","5.19.0-1015.16~22.04.1","5.19.0-1016.17~22.04.1","5.19.0-1017.18~22.04.1","5.19.0-1018.19~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1","5.19.0-1021.23~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-17.17.1.1~22.04.1","6.5.0-21.21.1~22.04.1","6.5.0-25.25.1~22.04.1","6.5.0-26.26.1~22.04.1","6.5.0-27.28.1~22.04.1","6.5.0-28.29.1~22.04.1","6.5.0-35.35.1~22.04.1","6.5.0-40.40.1~22.04.1","6.5.0-42.42.1~22.04.1","6.5.0-45.45.1~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-riscv-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.1","6.8.0-39.39.1~22.04.1","6.8.0-40.40.1~22.04.1","6.8.0-41.41.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.1~22.04.2","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-53.55.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-62.65~22.04.1","6.8.0-63.66~22.04.1","6.8.0-64.67~22.04.1","6.8.0-71.71~22.04.1","6.8.0-78.78~22.04.1","6.8.0-79.79~22.04.1","6.8.0-83.83~22.04.1","6.8.0-84.84~22.04.1","6.8.0-86.87~22.04.1","6.8.0-87.88~22.04.1","6.8.0-88.89~22.04.1","6.8.0-90.91~22.04.1","6.8.0-94.96~22.04.1","6.8.0-100.100~22.04.1","6.8.0-101.101~22.04.1","6.8.0-106.106~22.04.1","6.8.0-107.107~22.04.1","6.8.0-110.110~22.04.1","6.8.0-111.111~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-5.19","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["5.19.0-1014.16~22.04.1","5.19.0-1015.17~22.04.1","5.19.0-1016.18~22.04.1","5.19.0-1017.19~22.04.1","5.19.0-1018.20~22.04.1","5.19.0-1019.21~22.04.1","5.19.0-1020.22~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.2.0-1006.7~22.04.1","6.2.0-1007.8~22.04.1","6.2.0-1009.10~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-starfive-6.5","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-1007.8~22.04.1","6.5.0-1008.9~22.04.1","6.5.0-1009.10~22.04.1","6.5.0-1010.11~22.04.1","6.5.0-1011.12~22.04.1","6.5.0-1012.13~22.04.1","6.5.0-1014.15~22.04.1","6.5.0-1015.16~22.04.1","6.5.0-1016.17~22.04.1","6.5.0-1017.18~22.04.1","6.5.0-1018.19~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107","6.8.0-110.110","6.8.0-111.111"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1053.56"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1005.5~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.2","6.17.0-1010.10~24.04.1","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1019.19~24.04.1","6.17.0-1020.20~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.62"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58","6.8.0-1054.60"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1008.8~24.04.1","6.11.0-1012.12~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1017.17~24.04.1","6.11.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1010.10~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1021.21~24.04.1"}]}],"versions":["6.17.0-1008.8~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1011.11~24.04.2","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1018.18~24.04.1","6.17.0-1020.20~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.65"}]}],"versions":["6.8.0-1041.48","6.8.0-1044.51","6.8.0-1046.53","6.8.0-1053.60"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1039.42"}]}],"versions":["6.8.0-1013.14","6.8.0-1014.15","6.8.0-1016.17","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1022.23","6.8.0-1025.27","6.8.0-1027.30","6.8.0-1029.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-nvidia-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3","6.14.0-1006.6","6.14.0-1007.7"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1054.57","6.8.0-1055.58"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1006.6~24.04.2","6.11.0-1011.11~24.04.1","6.11.0-1013.13~24.04.1","6.11.0-1014.14~24.04.1","6.11.0-1015.15~24.04.1","6.11.0-1016.16~24.04.1","6.11.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1014.15~24.04.1","6.14.0-1015.16~24.04.1","6.14.0-1016.17~24.04.1","6.14.0-1017.18~24.04.1","6.14.0-1018.19~24.04.1","6.14.0-1019.20~24.04.1","6.14.0-1020.21~24.04.1","6.14.0-1021.22~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1021.24~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.3","6.17.0-1008.8~24.04.1","6.17.0-1009.9~24.04.3","6.17.0-1010.10~24.04.1","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1016.17~24.04.1","6.17.0-1018.19~24.04.1","6.17.0-1020.22~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54","6.8.0-1050.56","6.8.0-1051.57"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1041.44"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1037.40","6.8.0-1038.41"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-17.17~24.04.2","6.11.0-19.19~24.04.1","6.11.0-21.21~24.04.1","6.11.0-24.24~24.04.1","6.11.0-25.25~24.04.1","6.11.0-26.26~24.04.1","6.11.0-28.28~24.04.1","6.11.0-29.29~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-24.24~24.04.3","6.14.0-27.27~24.04.1","6.14.0-28.28~24.04.1","6.14.0-29.29~24.04.1","6.14.0-32.32~24.04.1","6.14.0-33.33~24.04.1","6.14.0-34.34~24.04.1","6.14.0-35.35~24.04.1","6.14.0-36.36~24.04.1","6.14.0-37.37~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-hwe-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-41.41~24.04.1"}]}],"versions":["6.17.0-14.14~24.04.1","6.17.0-19.19~24.04.2","6.17.0-20.20~24.04.1","6.17.0-22.22~24.04.1","6.17.0-23.23~24.04.1","6.17.0-29.29~24.04.1","6.17.0-35.35~24.04.1","6.17.0-40.40~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50","6.8.0-1051.51","6.8.0-1052.52"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency-hwe-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1009.10~24.04.1","6.11.0-1011.12~24.04.1","6.11.0-1012.13~24.04.1","6.11.0-1013.14~24.04.1","6.11.0-1014.15~24.04.1","6.11.0-1015.16~24.04.2","6.11.0-1016.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1002.2","6.11.0-1003.3","6.11.0-1007.7","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1016.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1031.31"}]}],"versions":["6.17.0-1004.4","6.17.0-1008.8","6.17.0-1014.14","6.17.0-1018.18","6.17.0-1021.21","6.17.0-1026.26","6.17.0-1029.29"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21","6.8.0-1022.22","6.8.0-1023.23"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.11","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.11.0-1007.7","6.11.0-1008.8","6.11.0-1009.9","6.11.0-1010.10","6.11.0-1011.11","6.11.0-1012.12","6.11.0-1013.13","6.11.0-1015.15","6.11.0-1016.16","6.11.0-1017.17","6.11.0-1018.18","6.11.0-1020.20","6.11.0-1021.21","6.11.0-1022.22","6.11.0-1023.23","6.11.0-1024.24","6.11.0-1025.25","6.11.0-1027.27"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1005.5","6.14.0-1006.6","6.14.0-1007.7","6.14.0-1008.8","6.14.0-1010.10","6.14.0-1011.11","6.14.0-1012.12","6.14.0-1013.13","6.14.0-1014.14","6.14.0-1015.15","6.14.0-1016.16","6.14.0-1017.17","6.14.0-1018.18","6.14.0-1019.19","6.14.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1030.30"}]}],"versions":["6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1017.17","6.17.0-1020.20","6.17.0-1023.23","6.17.0-1024.24","6.17.0-1025.25","6.17.0-1028.28"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1031.31","6.8.0-1032.32"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.55"}]}],"versions":["6.5.0-1010.10","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1025.26","6.8.0-1026.27","6.8.0-1027.28","6.8.0-1028.29","6.8.0-1029.30","6.8.0-1030.31","6.8.0-1032.33","6.8.0-1033.34","6.8.0-1035.36","6.8.0-1037.38","6.8.0-1038.39","6.8.0-1039.40","6.8.0-1040.41","6.8.0-1041.42","6.8.0-1042.43","6.8.0-1043.44","6.8.0-1044.45","6.8.0-1047.48","6.8.0-1049.50","6.8.0-1050.51","6.8.0-1052.53"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1007.7~24.04.1","6.14.0-1009.9~24.04.1","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1","6.14.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1019.19~24.04.3"}]}],"versions":["6.17.0-1004.4~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1011.11~24.04.1","6.17.0-1014.14~24.04.1","6.17.0-1016.16~24.04.1","6.17.0-1018.18~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.60"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55","6.8.0-1052.56","6.8.0-1053.57"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.0-2019.20"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.8.1-1015.16"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.5.0-9.9.1","6.8.0-20.20.1","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-47.47.1","6.8.0-48.48.1","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-22.22.1~24.04.1","6.14.0-23.23.1~24.04.1","6.14.0-24.24.1~24.04.1","6.14.0-27.27.1~24.04.1","6.14.0-28.28.1~24.04.1","6.14.0-29.29.1~24.04.1","6.14.0-32.32.1~24.04.1","6.14.0-33.33.1~24.04.1","6.14.0-34.34.1~24.04.1","6.14.0-35.35.1~24.04.1","6.14.0-36.36.1~24.04.1","6.14.0-37.37.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-riscv-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-14.14.1~24.04.1","6.17.0-19.19.1~24.04.1","6.17.0-20.20.1~24.04.1","6.17.0-22.22.1~24.04.1","6.17.0-23.23.1~24.04.1","6.17.0-29.29.1~24.04.1","6.17.0-35.35.1~24.04.1","6.17.0-38.38.1~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1032.33"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29","6.8.0-1029.30"]},{"source":"osv","ecosystem":"Ubuntu:Nvidia-BlueField:24.04:LTS","package":"linux-bluefield","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1022.26"}]}],"versions":["6.8.0-1011.15","6.8.0-1012.16","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1016.20","6.8.0-1017.21"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2045.46"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42","6.8.0-2042.43","6.8.0-2043.44"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47","6.8.1-1047.48","6.8.1-1048.49"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.14","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1003.3~24.04.3","6.14.0-1010.10~24.04.1","6.14.0-1011.11~24.04.1","6.14.0-1012.12~24.04.1","6.14.0-1013.13~24.04.1","6.14.0-1014.14~24.04.1","6.14.0-1015.15~24.04.1","6.14.0-1016.16~24.04.1","6.14.0-1017.17~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.20~24.04.1"}]}],"versions":["6.17.0-1004.5~24.04.2","6.17.0-1006.7~24.04.1","6.17.0-1008.9~24.04.1","6.17.0-1009.10~24.04.1","6.17.0-1010.11~24.04.1","6.17.0-1011.12~24.04.1","6.17.0-1013.15~24.04.1","6.17.0-1014.16~24.04.1","6.17.0-1017.19~24.04.1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-116.116+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1"]},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-15.15","6.15.0-3.3","6.15.0-4.4","6.16.0-13.13","6.16.0-16.16","6.17.0-3.3","6.17.0-4.4","6.17.0-5.5","6.17.0-6.6","6.17.0-7.7","6.17.0-8.8","6.17.0-12.12","6.17.0-14.14","6.17.0-19.19","6.17.0-20.20","6.17.0-22.22","6.17.0-23.23","6.17.0-29.29","6.17.0-35.35","6.17.0-40.40"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.2","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1019.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1004.4","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1013.13","6.17.0-1015.15","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1020.20"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-azure-fde","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1015.15","6.17.0-1017.17"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1006.6","6.14.0-1009.9+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1012.12","6.17.0-1013.13","6.17.0-1016.17","6.17.0-1018.19","6.17.0-1020.22"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-oracle","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.14.0-1007.7+25.10.1","6.16.0-1001.1","6.17.0-1001.1","6.17.0-1002.2","6.17.0-1003.3","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1014.14","6.17.0-1016.16","6.17.0-1018.18"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1005.5","6.17.0-1003.3","6.17.0-1004.4","6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1013.13","6.17.0-1014.14","6.17.0-1017.17","6.17.0-1018.18","6.17.0-1021.21"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-1002.2","6.17.0-1001.2","6.17.0-1002.3","6.17.0-1003.4","6.17.0-1004.5","6.17.0-1005.6","6.17.0-1006.7","6.17.0-1008.9","6.17.0-1009.10","6.17.0-1010.11","6.17.0-1011.12","6.17.0-1013.15","6.17.0-1014.16","6.17.0-1017.19"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"linux-riscv","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["6.14.0-13.13.2","6.17.0-4.4.1","6.17.0-5.5.1","6.17.0-6.6.1","6.17.0-7.7.1","6.17.0-8.8.1","6.17.0-12.12.1","6.17.0-14.14.1","6.17.0-19.19.1","6.17.0-20.20.1","6.17.0-22.22.1","6.17.0-23.23.1","6.17.0-29.29.1","6.17.0-35.35.1","6.17.0-40.40.1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"linux-vmware","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["7.0.0-1006.6"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-ibm-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.13~22.04.1","6.8.0-1014.14~22.04.1","6.8.0-1015.15~22.04.1","6.8.0-1016.16~22.04.1","6.8.0-1017.17~22.04.1","6.8.0-1018.18~22.04.1","6.8.0-1019.19~22.04.1","6.8.0-1023.23~22.04.1","6.8.0-1024.24~22.04.1","6.8.0-1025.25~22.04.1","6.8.0-1026.26~22.04.1","6.8.0-1027.27~22.04.1","6.8.0-1028.28~22.04.1","6.8.0-1029.29~22.04.1","6.8.0-1030.30~22.04.1","6.8.0-1033.33~22.04.1","6.8.0-1036.36~22.04.1","6.8.0-1037.37~22.04.1","6.8.0-1038.38~22.04.1","6.8.0-1039.39~22.04.1","6.8.0-1040.40~22.04.1","6.8.0-1041.41~22.04.1","6.8.0-1042.42~22.04.1","6.8.0-1043.43~22.04.1","6.8.0-1044.44~22.04.1","6.8.0-1045.45~22.04.1","6.8.0-1049.49~22.04.1","6.8.0-1050.50~22.04.1","6.8.0-1051.51~22.04.1","6.8.0-1052.52~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-lowlatency-hwe-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1~22.04.1"}]}],"versions":["6.8.0-38.38.1~22.04.2","6.8.0-40.40.1~22.04.1","6.8.0-44.44.1~22.04.1","6.8.0-45.45.1~22.04.1","6.8.0-47.47.1~22.04.1","6.8.0-48.48.3~22.04.1","6.8.0-49.49.1~22.04.1","6.8.0-50.51.1~22.04.1","6.8.0-51.52.1~22.04.1","6.8.0-52.53.1~22.04.1","6.8.0-54.56.1~22.04.1","6.8.0-55.57.1~22.04.1","6.8.0-56.58.1~22.04.1","6.8.0-57.59.1~22.04.1","6.8.0-58.60.1~22.04.1","6.8.0-59.61.1~22.04.1","6.8.0-60.63.1~22.04.1","6.8.0-62.65.1~22.04.1","6.8.0-63.66.1~22.04.1","6.8.0-64.67.1~22.04.1","6.8.0-65.68.1~22.04.1","6.8.0-78.78.1~22.04.1","6.8.0-79.79.1~22.04.1","6.8.0-83.83.1~22.04.1","6.8.0-84.84.1~22.04.1","6.8.0-85.85.1~22.04.1","6.8.0-86.87.1~22.04.1","6.8.0-87.88.1~22.04.1","6.8.0-88.89.1~22.04.1","6.8.0-90.91.1~22.04.1","6.8.0-94.96.1~22.04.1","6.8.0-100.100.1~22.04.1","6.8.0-101.101.1~22.04.1","6.8.0-106.106.1~22.04.1","6.8.0-107.107.1~22.04.1","6.8.0-110.110.1~22.04.1","6.8.0-111.111.1~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:22.04:LTS","package":"linux-realtime-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52~22.04.1"}]}],"versions":["6.8.1-1004.4~22.04.1","6.8.1-1005.5~22.04.2","6.8.1-1006.6~22.04.1","6.8.1-1007.7~22.04.1","6.8.1-1008.8~22.04.1","6.8.1-1009.9~22.04.1","6.8.1-1010.10~22.04.1","6.8.1-1011.11~22.04.1","6.8.1-1012.12~22.04.1","6.8.1-1013.14~22.04.1","6.8.1-1014.15~22.04.1","6.8.1-1015.16~22.04.1","6.8.1-1016.17~22.04.1","6.8.1-1017.18~22.04.1","6.8.1-1018.19~22.04.1","6.8.1-1019.20~22.04.1","6.8.1-1020.21~22.04.1","6.8.1-1021.22~22.04.1","6.8.1-1022.23~22.04.1","6.8.1-1023.24~22.04.1","6.8.1-1024.25~22.04.1","6.8.1-1025.26~22.04.1","6.8.1-1026.27~22.04.1","6.8.1-1030.31~22.04.1","6.8.1-1031.32~22.04.1","6.8.1-1034.35~22.04.1","6.8.1-1035.36~22.04.1","6.8.1-1036.37~22.04.1","6.8.1-1037.38~22.04.1","6.8.1-1038.39~22.04.1","6.8.1-1039.40~22.04.1","6.8.1-1040.41~22.04.1","6.8.1-1041.42~22.04.1","6.8.1-1042.43~22.04.1","6.8.1-1045.46~22.04.1","6.8.1-1046.47~22.04.2","6.8.1-1047.48~22.04.1","6.8.1-1048.49~22.04.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117"}]}],"versions":["6.5.0-9.9","6.6.0-14.14","6.8.0-11.11","6.8.0-20.20","6.8.0-22.22","6.8.0-28.28","6.8.0-31.31","6.8.0-35.35","6.8.0-36.36","6.8.0-38.38","6.8.0-39.39","6.8.0-40.40","6.8.0-41.41","6.8.0-44.44","6.8.0-45.45","6.8.0-47.47","6.8.0-48.48","6.8.0-49.49","6.8.0-50.51","6.8.0-51.52","6.8.0-52.53","6.8.0-53.55","6.8.0-54.56","6.8.0-55.57","6.8.0-56.58","6.8.0-57.59","6.8.0-58.60","6.8.0-59.61","6.8.0-60.63","6.8.0-62.65","6.8.0-63.66","6.8.0-64.67","6.8.0-71.71","6.8.0-78.78","6.8.0-79.79","6.8.0-83.83","6.8.0-84.84","6.8.0-85.85","6.8.0-86.87","6.8.0-87.88","6.8.0-88.89","6.8.0-90.91","6.8.0-94.96","6.8.0-100.100","6.8.0-101.101","6.8.0-106.106","6.8.0-107.107","6.8.0-110.110","6.8.0-111.111"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-aws","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58"}]}],"versions":["6.5.0-1008.8","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1006.6","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1016.17","6.8.0-1017.18","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1035.37","6.8.0-1036.38","6.8.0-1038.40","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.44","6.8.0-1043.45","6.8.0-1044.46","6.8.0-1045.47","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55","6.8.0-1053.56"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1002.2","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.9","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1024.26","6.8.0-1025.27","6.8.0-1026.28","6.8.0-1027.29","6.8.0-1028.30","6.8.0-1029.31","6.8.0-1030.32","6.8.0-1031.33","6.8.0-1032.34","6.8.0-1033.35","6.8.0-1034.36","6.8.0-1036.38","6.8.0-1037.39","6.8.0-1039.41","6.8.0-1040.42","6.8.0-1041.43","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1048.51","6.8.0-1052.55","6.8.0-1053.56","6.8.0-1054.57","6.8.0-1055.58"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gke","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.60"}]}],"versions":["6.8.0-1003.5","6.8.0-1004.7","6.8.0-1005.8","6.8.0-1006.9","6.8.0-1007.10","6.8.0-1008.11","6.8.0-1009.12","6.8.0-1010.13","6.8.0-1011.14","6.8.0-1012.15","6.8.0-1013.17","6.8.0-1014.18","6.8.0-1015.19","6.8.0-1016.20","6.8.0-1017.21","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1021.25","6.8.0-1022.26","6.8.0-1023.27","6.8.0-1024.28","6.8.0-1025.29","6.8.0-1026.30","6.8.0-1027.31","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1032.36","6.8.0-1033.37","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1037.41","6.8.0-1038.43","6.8.0-1039.44","6.8.0-1040.45","6.8.0-1041.46","6.8.0-1042.47","6.8.0-1043.48","6.8.0-1044.49","6.8.0-1048.53","6.8.0-1049.54","6.8.0-1050.56","6.8.0-1051.57"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gkeop","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1041.44"}]}],"versions":["6.8.0-1001.3","6.8.0-1002.4","6.8.0-1003.5","6.8.0-1004.6","6.8.0-1006.8","6.8.0-1007.9","6.8.0-1008.10","6.8.0-1009.11","6.8.0-1010.12","6.8.0-1011.13","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1022.24","6.8.0-1023.25","6.8.0-1024.26","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1037.40","6.8.0-1038.41"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-ibm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.56"}]}],"versions":["6.5.0-1009.9","6.8.0-1001.1","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1014.14","6.8.0-1015.15","6.8.0-1016.16","6.8.0-1017.17","6.8.0-1018.18","6.8.0-1019.19","6.8.0-1022.22","6.8.0-1023.23","6.8.0-1024.24","6.8.0-1025.25","6.8.0-1026.26","6.8.0-1027.27","6.8.0-1028.28","6.8.0-1029.29","6.8.0-1030.30","6.8.0-1033.33","6.8.0-1036.36","6.8.0-1037.37","6.8.0-1038.38","6.8.0-1039.39","6.8.0-1040.40","6.8.0-1041.41","6.8.0-1042.42","6.8.0-1043.43","6.8.0-1044.44","6.8.0-1045.45","6.8.0-1049.49","6.8.0-1050.50","6.8.0-1051.51","6.8.0-1052.52"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-117.117.1"}]}],"versions":["6.5.0-9.9.1","6.6.0-14.14.1","6.8.0-7.7.1","6.8.0-25.25.3","6.8.0-28.28.1","6.8.0-31.31.1","6.8.0-35.35.1","6.8.0-36.36.1","6.8.0-38.38.1","6.8.0-39.39.1","6.8.0-40.40.1","6.8.0-41.41.1","6.8.0-44.44.1","6.8.0-45.45.1","6.8.0-47.47.1","6.8.0-48.48.3","6.8.0-49.49.1","6.8.0-50.51.1","6.8.0-51.52.1","6.8.0-52.53.1","6.8.0-53.55.2","6.8.0-54.56.1","6.8.0-55.57.1","6.8.0-56.58.1","6.8.0-57.59.1","6.8.0-58.60.1","6.8.0-59.61.1","6.8.0-60.63.1","6.8.0-62.65.1","6.8.0-63.66.1","6.8.0-64.67.1","6.8.0-65.68.1","6.8.0-78.78.1","6.8.0-79.79.1","6.8.0-83.83.1","6.8.0-84.84.1","6.8.0-85.85.1","6.8.0-86.87.1","6.8.0-87.88.1","6.8.0-88.89.1","6.8.0-90.91.1","6.8.0-94.96.1","6.8.0-100.100.1","6.8.0-101.101.1","6.8.0-106.106.1","6.8.0-107.107.1","6.8.0-110.110.1","6.8.0-111.111.1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-raspi","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.60"}]}],"versions":["6.5.0-1005.7","6.7.0-1001.1","6.8.0-1001.1","6.8.0-1002.2","6.8.0-1003.3","6.8.0-1004.4","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.10","6.8.0-1010.11","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.23","6.8.0-1020.24","6.8.0-1024.28","6.8.0-1028.32","6.8.0-1029.33","6.8.0-1030.34","6.8.0-1031.35","6.8.0-1032.36","6.8.0-1035.39","6.8.0-1036.40","6.8.0-1038.42","6.8.0-1039.43","6.8.0-1040.44","6.8.0-1041.45","6.8.0-1042.46","6.8.0-1043.47","6.8.0-1044.48","6.8.0-1045.49","6.8.0-1047.51","6.8.0-1048.52","6.8.0-1050.54","6.8.0-1051.55","6.8.0-1052.56","6.8.0-1053.57"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-raspi-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-2045.46"}]}],"versions":["6.7.0-2001.1","6.8.0-2001.1","6.8.0-2002.2","6.8.0-2004.4","6.8.0-2005.5","6.8.0-2006.6","6.8.0-2007.7","6.8.0-2008.8","6.8.0-2009.9","6.8.0-2010.10","6.8.0-2011.11","6.8.0-2012.12","6.8.0-2013.14","6.8.0-2014.15","6.8.0-2015.16","6.8.0-2016.17","6.8.0-2017.18","6.8.0-2018.19","6.8.0-2019.20","6.8.0-2022.23","6.8.0-2023.24","6.8.0-2024.25","6.8.0-2025.26","6.8.0-2026.27","6.8.0-2028.29","6.8.0-2029.30","6.8.0-2030.31","6.8.0-2031.32","6.8.0-2032.33","6.8.0-2033.34","6.8.0-2034.35","6.8.0-2035.36","6.8.0-2036.37","6.8.0-2037.38","6.8.0-2038.39","6.8.0-2040.41","6.8.0-2041.42","6.8.0-2042.43","6.8.0-2043.44"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.1-1051.52"}]}],"versions":["6.8.0-1008.19","6.8.1-1001.1","6.8.1-1002.2","6.8.1-1003.3","6.8.1-1004.4","6.8.1-1005.5","6.8.1-1006.6","6.8.1-1007.7","6.8.1-1008.8","6.8.1-1009.9","6.8.1-1010.10","6.8.1-1011.11","6.8.1-1012.12","6.8.1-1013.14","6.8.1-1014.15","6.8.1-1015.16","6.8.1-1016.17","6.8.1-1017.18","6.8.1-1018.19","6.8.1-1019.20","6.8.1-1020.21","6.8.1-1021.22","6.8.1-1022.23","6.8.1-1023.24","6.8.1-1024.25","6.8.1-1025.26","6.8.1-1026.27","6.8.1-1030.31","6.8.1-1031.32","6.8.1-1033.34","6.8.1-1034.35","6.8.1-1035.36","6.8.1-1036.37","6.8.1-1037.38","6.8.1-1038.39","6.8.1-1039.40","6.8.1-1040.41","6.8.1-1041.42","6.8.1-1042.43","6.8.1-1045.46","6.8.1-1046.47","6.8.1-1047.48","6.8.1-1048.49"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-aws-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1055.58+fips1"}]}],"versions":["6.8.0-1035.37+fips1","6.8.0-1036.38+fips1","6.8.0-1038.40+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.44+fips1","6.8.0-1043.45+fips1","6.8.0-1044.46+fips1","6.8.0-1045.47+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1050.53+fips1","6.8.0-1051.54+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-gcp-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1058.61+fips1"}]}],"versions":["6.8.0-1036.38+fips1","6.8.0-1037.39+fips1","6.8.0-1039.41+fips1","6.8.0-1040.42+fips1","6.8.0-1041.43+fips1","6.8.0-1042.45+fips1","6.8.0-1043.46+fips1","6.8.0-1044.47+fips1","6.8.0-1045.48+fips1","6.8.0-1046.49+fips1","6.8.0-1047.50+fips1","6.8.0-1048.51+fips1","6.8.0-1052.55+fips1","6.8.0-1053.56+fips1","6.8.0-1054.57+fips1","6.8.0-1055.58+fips1"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1056.62"}]}],"versions":["6.5.0-1007.7","6.6.0-1001.1","6.8.0-1001.1","6.8.0-1005.5","6.8.0-1006.6","6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.14","6.8.0-1013.15","6.8.0-1014.16","6.8.0-1015.17","6.8.0-1016.18","6.8.0-1017.20","6.8.0-1018.21","6.8.0-1020.23","6.8.0-1021.25","6.8.0-1025.30","6.8.0-1026.31","6.8.0-1027.32","6.8.0-1028.33","6.8.0-1029.34","6.8.0-1030.35","6.8.0-1031.36","6.8.0-1034.39","6.8.0-1038.44","6.8.0-1040.46","6.8.0-1041.47","6.8.0-1042.48","6.8.0-1044.50","6.8.0-1046.52","6.8.0-1051.57","6.8.0-1052.58","6.8.0-1054.60"],"bundled":196},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57"}]}],"versions":["6.8.0-1007.7","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1011.11","6.8.0-1012.12","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.19","6.8.0-1018.20","6.8.0-1019.21","6.8.0-1020.22","6.8.0-1021.23","6.8.0-1022.25","6.8.0-1023.26","6.8.0-1024.27","6.8.0-1025.28","6.8.0-1026.29","6.8.0-1027.30","6.8.0-1028.31","6.8.0-1029.32","6.8.0-1030.33","6.8.0-1031.34","6.8.0-1032.35","6.8.0-1035.38","6.8.0-1036.39","6.8.0-1038.41","6.8.0-1039.42","6.8.0-1040.43","6.8.0-1041.44","6.8.0-1042.45","6.8.0-1043.46","6.8.0-1044.47","6.8.0-1045.48","6.8.0-1046.49","6.8.0-1047.50","6.8.0-1049.52","6.8.0-1050.53","6.8.0-1051.54","6.8.0-1052.55"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-lowlatency","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57.1"}]}],"versions":["6.8.0-1009.9.1","6.8.0-1011.11.1","6.8.0-1012.12.1","6.8.0-1013.14.1","6.8.0-1014.15.1","6.8.0-1015.16.1","6.8.0-1017.19.1","6.8.0-1018.20.1","6.8.0-1019.21.1","6.8.0-1020.22.1","6.8.0-1021.23.1","6.8.0-1022.25.2","6.8.0-1023.26.1","6.8.0-1024.27.1","6.8.0-1025.28.1","6.8.0-1026.29.1","6.8.0-1027.30.1","6.8.0-1028.31.1","6.8.0-1029.32.1","6.8.0-1030.33.1","6.8.0-1031.34.1","6.8.0-1032.35.1","6.8.0-1035.38.1","6.8.0-1036.39.1","6.8.0-1038.41.1","6.8.0-1039.42.1","6.8.0-1040.43.1","6.8.0-1041.44.1","6.8.0-1042.45.1","6.8.0-1043.46.1","6.8.0-1044.47.1","6.8.0-1045.48.1","6.8.0-1046.49.1","6.8.0-1047.50.1","6.8.0-1049.52.1","6.8.0-1050.53.1","6.8.0-1051.54.1","6.8.0-1052.55.1"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-nvidia-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1054.57~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1011.11~22.04.1","6.8.0-1012.12~22.04.1","6.8.0-1013.14~22.04.1","6.8.0-1014.15~22.04.1","6.8.0-1015.16~22.04.1","6.8.0-1017.19~22.04.1","6.8.0-1018.20~22.04.1","6.8.0-1019.21~22.04.1","6.8.0-1020.22~22.04.1","6.8.0-1021.23~22.04.1","6.8.0-1022.25~22.04.2","6.8.0-1023.26~22.04.1","6.8.0-1024.27~22.04.1","6.8.0-1025.28~22.04.1","6.8.0-1026.29~22.04.1","6.8.0-1027.30~22.04.1","6.8.0-1028.31~22.04.1","6.8.0-1029.32~22.04.1","6.8.0-1030.33~22.04.1","6.8.0-1031.34~22.04.1","6.8.0-1032.35~22.04.1","6.8.0-1035.38~22.04.1","6.8.0-1036.39~22.04.1","6.8.0-1038.41~22.04.1","6.8.0-1039.42~22.04.1","6.8.0-1040.43~22.04.1","6.8.0-1041.44~22.04.2","6.8.0-1042.45~22.04.1","6.8.0-1043.46~22.04.1","6.8.0-1044.47~22.04.1","6.8.0-1045.48~22.04.1","6.8.0-1046.49~22.04.1","6.8.0-1047.50~22.04.1","6.8.0-1049.52~22.04.1","6.8.0-1050.53~22.04.1","6.8.0-1051.54~22.04.1","6.8.0-1052.55~22.04.1"],"bundled":195},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-116.116+fips1"}]}],"versions":["6.8.0-38.38+fips4","6.8.0-78.78+fips1","6.8.0-79.79+fips1","6.8.0-83.83+fips1","6.8.0-84.84+fips1","6.8.0-85.85+fips1","6.8.0-86.87+fips1","6.8.0-87.88+fips1","6.8.0-88.89+fips1","6.8.0-90.91+fips1","6.8.0-94.96+fips1","6.8.0-100.100+fips1","6.8.0-101.101+fips1","6.8.0-106.106+fips1","6.8.0-107.107+fips1","6.8.0-110.110+fips2","6.8.0-111.111+fips1"],"bundled":189},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-tegra","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1024.24"}]}],"versions":["6.8.0-1003.3","6.8.0-1004.4","6.8.0-1008.8","6.8.0-1009.9","6.8.0-1010.10","6.8.0-1012.12","6.8.0-1013.13","6.8.0-1016.16","6.8.0-1019.19","6.8.0-1020.20","6.8.0-1021.21","6.8.0-1022.22","6.8.0-1023.23"],"bundled":189},{"source":"osv","ecosystem":"Ubuntu:Pro:FIPS-updates:24.04:LTS","package":"linux-azure-fips","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65+fips1"}]}],"versions":["6.8.0-1034.39+fips1","6.8.0-1040.46+fips1","6.8.0-1044.50+fips1","6.8.0-1046.52+fips1","6.8.0-1047.53+fips1","6.8.0-1052.58+fips1","6.8.0-1053.59+fips1","6.8.0-1054.60+fips1"],"bundled":218},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"linux-azure-6.8","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1059.65~22.04.1"}]}],"versions":["6.8.0-1008.8~22.04.1","6.8.0-1009.9~22.04.1","6.8.0-1010.10~22.04.1","6.8.0-1012.14~22.04.1","6.8.0-1013.15~22.04.1","6.8.0-1014.16~22.04.1","6.8.0-1015.17~22.04.2","6.8.0-1017.20~22.04.1","6.8.0-1018.21~22.04.1","6.8.0-1020.23~22.04.1","6.8.0-1021.25~22.04.1","6.8.0-1025.30~22.04.1","6.8.0-1026.31~22.04.1","6.8.0-1027.32~22.04.1","6.8.0-1028.33~22.04.1","6.8.0-1029.34~22.04.1","6.8.0-1030.35~22.04.1","6.8.0-1031.36~22.04.1","6.8.0-1034.39~22.04.1","6.8.0-1036.42~22.04.1","6.8.0-1040.46~22.04.1","6.8.0-1041.47~22.04.1","6.8.0-1044.50~22.04.1","6.8.0-1051.57~22.04.1","6.8.0-1052.58~22.04.1"],"bundled":393},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-xilinx","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.8.0-1032.33"}]}],"versions":["6.8.0-1008.9","6.8.0-1009.10","6.8.0-1011.12","6.8.0-1012.13","6.8.0-1013.14","6.8.0-1014.15","6.8.0-1015.16","6.8.0-1017.18","6.8.0-1018.19","6.8.0-1019.20","6.8.0-1020.21","6.8.0-1021.22","6.8.0-1022.23","6.8.0-1023.24","6.8.0-1024.25","6.8.0-1028.29","6.8.0-1029.30"],"bundled":516},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-gcp-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1021.24~24.04.1"}]}],"versions":["6.17.0-1004.4~24.04.3","6.17.0-1008.8~24.04.1","6.17.0-1009.9~24.04.3","6.17.0-1010.10~24.04.1","6.17.0-1012.12~24.04.1","6.17.0-1013.13~24.04.1","6.17.0-1016.17~24.04.1","6.17.0-1018.19~24.04.1","6.17.0-1020.22~24.04.1"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:Pro:Realtime:24.04:LTS","package":"linux-realtime-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.20~24.04.1"}]}],"versions":["6.17.0-1004.5~24.04.2","6.17.0-1006.7~24.04.1","6.17.0-1008.9~24.04.1","6.17.0-1009.10~24.04.1","6.17.0-1010.11~24.04.1","6.17.0-1011.12~24.04.1","6.17.0-1013.15~24.04.1","6.17.0-1014.16~24.04.1","6.17.0-1017.19~24.04.1"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oracle-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1019.19~24.04.3"}]}],"versions":["6.17.0-1004.4~24.04.2","6.17.0-1007.7~24.04.1","6.17.0-1009.9~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1011.11~24.04.1","6.17.0-1014.14~24.04.1","6.17.0-1016.16~24.04.1","6.17.0-1018.18~24.04.1"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-oem-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1030.30"}]}],"versions":["6.17.0-1005.5","6.17.0-1006.6","6.17.0-1007.7","6.17.0-1008.8","6.17.0-1009.9","6.17.0-1010.10","6.17.0-1011.11","6.17.0-1012.12","6.17.0-1017.17","6.17.0-1020.20","6.17.0-1023.23","6.17.0-1024.24","6.17.0-1025.25","6.17.0-1028.28"],"bundled":203},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1021.21~24.04.1"}]}],"versions":["6.17.0-1008.8~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1011.11~24.04.2","6.17.0-1013.13~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1","6.17.0-1018.18~24.04.1","6.17.0-1020.20~24.04.1"],"bundled":267},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-azure-fde-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1018.18~24.04.1"}]}],"versions":["6.17.0-1005.5~24.04.1","6.17.0-1010.10~24.04.1","6.17.0-1015.15~24.04.1","6.17.0-1017.17~24.04.1"],"bundled":266},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"linux-nvidia-6.17","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.17.0-1031.31"}]}],"versions":["6.17.0-1004.4","6.17.0-1008.8","6.17.0-1014.14","6.17.0-1018.18","6.17.0-1021.21","6.17.0-1026.26","6.17.0-1029.29"],"bundled":227},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"dtb-aarch64","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.0-160000.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/408bfa8d70f79ac696cec1bdbdfb3bf43a02e6d0","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/1922468a4a80424e5a69f7ba50adcee37f4722e9","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/aa14451fa5d5f2de919384c637e2a8c604e1a1fe","tags":["web","report"]},{"url":"https://git.kernel.org/stable/c/19bc5f2a6962dfaa0e32d0e0bc2271993d85d414","tags":["web","report"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23059","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-6mm8-fcwp-3g49"},{"url":"https://docs.bell-sw.com/security/cves/CVE-2026-23059","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23059.json","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-23059","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2026-0097.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35281","tags":["report"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.121","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.122","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.123","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.124","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.125","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.126","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.127","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.128","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.129","tags":["web"]},{"url":"https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.130","tags":["web"]},{"url":"https://advisories.mageia.org/MGASA-2026-0098.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=35282","tags":["report"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1566","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2024-57974","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-22090","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38491","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38627","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-38660","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39764","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39902","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-39948","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40323","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-40329","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68192","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68194","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68204","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68209","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68211","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68231","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68237","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68282","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68293","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68313","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68768","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68785","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68819","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68822","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71065","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71068","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71083","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71091","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71096","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71118","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71129","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71186","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71221","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71223","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71225","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71232","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71235","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-71236","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22977","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22979","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22984","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22991","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-22999","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23003","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23010","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23011","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23021","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23025","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23032","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23038","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23047","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23050","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23054","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23084","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23085","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23094","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23097","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23110","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23112","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23163","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23179","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23190","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23193","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23205","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23216","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23220","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23228","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1567","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1570","tags":["advisory"]},{"url":"https://www.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://www.suse.com/support/update/announcement/2026/suse-su-202624550-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1215199","tags":["report"]},{"url":"https://bugzilla.suse.com/1232383","tags":["report"]},{"url":"https://bugzilla.suse.com/1233187","tags":["report"]},{"url":"https://bugzilla.suse.com/1233565","tags":["report"]},{"url":"https://bugzilla.suse.com/1244337","tags":["report"]},{"url":"https://bugzilla.suse.com/1246086","tags":["report"]},{"url":"https://bugzilla.suse.com/1248354","tags":["report"]},{"url":"https://bugzilla.suse.com/1250656","tags":["report"]},{"url":"https://bugzilla.suse.com/1255222","tags":["report"]},{"url":"https://bugzilla.suse.com/1256632","tags":["report"]},{"url":"https://bugzilla.suse.com/1264022","tags":["report"]},{"url":"https://bugzilla.suse.com/1264024","tags":["report"]},{"url":"https://bugzilla.suse.com/1264267","tags":["report"]},{"url":"https://bugzilla.suse.com/1264985","tags":["report"]},{"url":"https://bugzilla.suse.com/1267203","tags":["report"]},{"url":"https://bugzilla.suse.com/1267238","tags":["report"]},{"url":"https://bugzilla.suse.com/1267373","tags":["report"]},{"url":"https://bugzilla.suse.com/1267681","tags":["report"]},{"url":"https://bugzilla.suse.com/1267720","tags":["report"]},{"url":"https://bugzilla.suse.com/1269264","tags":["report"]},{"url":"https://bugzilla.suse.com/1269364","tags":["report"]},{"url":"https://bugzilla.suse.com/1269532","tags":["report"]},{"url":"https://bugzilla.suse.com/1269655","tags":["report"]},{"url":"https://bugzilla.suse.com/1269798","tags":["report"]},{"url":"https://bugzilla.suse.com/1271349","tags":["report"]},{"url":"https://bugzilla.suse.com/1272261","tags":["report"]},{"url":"https://bugzilla.suse.com/1272296","tags":["report"]},{"url":"https://bugzilla.suse.com/1273292","tags":["report"]},{"url":"https://bugzilla.suse.com/1273557","tags":["report"]},{"url":"https://bugzilla.suse.com/1273803","tags":["report"]},{"url":"https://bugzilla.suse.com/1273805","tags":["report"]},{"url":"https://bugzilla.suse.com/1273809","tags":["report"]},{"url":"https://bugzilla.suse.com/1273839","tags":["report"]},{"url":"https://bugzilla.suse.com/1273880","tags":["report"]},{"url":"https://bugzilla.suse.com/1273970","tags":["report"]},{"url":"https://bugzilla.suse.com/1273999","tags":["report"]},{"url":"https://bugzilla.suse.com/1274080","tags":["report"]},{"url":"https://bugzilla.suse.com/1274082","tags":["report"]},{"url":"https://bugzilla.suse.com/1274261","tags":["report"]},{"url":"https://bugzilla.suse.com/1274292","tags":["report"]},{"url":"https://bugzilla.suse.com/1274550","tags":["report"]},{"url":"https://bugzilla.suse.com/1274902","tags":["report"]},{"url":"https://bugzilla.suse.com/1274949","tags":["report"]},{"url":"https://bugzilla.suse.com/1275524","tags":["report"]},{"url":"https://bugzilla.suse.com/1275568","tags":["report"]},{"url":"https://bugzilla.suse.com/1275575","tags":["report"]},{"url":"https://bugzilla.suse.com/1275671","tags":["report"]},{"url":"https://bugzilla.suse.com/1275672","tags":["report"]},{"url":"https://bugzilla.suse.com/1275678","tags":["report"]},{"url":"https://bugzilla.suse.com/1275683","tags":["report"]},{"url":"https://bugzilla.suse.com/1275689","tags":["report"]},{"url":"https://bugzilla.suse.com/1275692","tags":["report"]},{"url":"https://bugzilla.suse.com/1275810","tags":["report"]},{"url":"https://bugzilla.suse.com/1275811","tags":["report"]},{"url":"https://bugzilla.suse.com/1275813","tags":["report"]},{"url":"https://bugzilla.suse.com/1275939","tags":["report"]},{"url":"https://bugzilla.suse.com/1275944","tags":["report"]},{"url":"https://bugzilla.suse.com/1275947","tags":["report"]},{"url":"https://bugzilla.suse.com/1275951","tags":["report"]},{"url":"https://bugzilla.suse.com/1275957","tags":["report"]},{"url":"https://bugzilla.suse.com/1275958","tags":["report"]},{"url":"https://bugzilla.suse.com/1275959","tags":["report"]},{"url":"https://bugzilla.suse.com/1276271","tags":["report"]},{"url":"https://bugzilla.suse.com/1276280","tags":["report"]},{"url":"https://bugzilla.suse.com/1276321","tags":["report"]},{"url":"https://bugzilla.suse.com/1276343","tags":["report"]},{"url":"https://bugzilla.suse.com/1276363","tags":["report"]},{"url":"https://bugzilla.suse.com/1276382","tags":["report"]},{"url":"https://bugzilla.suse.com/1276384","tags":["report"]},{"url":"https://bugzilla.suse.com/1276387","tags":["report"]},{"url":"https://bugzilla.suse.com/1276393","tags":["report"]},{"url":"https://bugzilla.suse.com/1276444","tags":["report"]},{"url":"https://bugzilla.suse.com/1276450","tags":["report"]},{"url":"https://bugzilla.suse.com/1276451","tags":["report"]},{"url":"https://bugzilla.suse.com/1276453","tags":["report"]},{"url":"https://bugzilla.suse.com/1276454","tags":["report"]},{"url":"https://bugzilla.suse.com/1276457","tags":["report"]},{"url":"https://bugzilla.suse.com/1276476","tags":["report"]},{"url":"https://bugzilla.suse.com/1276479","tags":["report"]},{"url":"https://bugzilla.suse.com/1276482","tags":["report"]},{"url":"https://bugzilla.suse.com/1276483","tags":["report"]},{"url":"https://bugzilla.suse.com/1276495","tags":["report"]},{"url":"https://bugzilla.suse.com/1276499","tags":["report"]},{"url":"https://bugzilla.suse.com/1276502","tags":["report"]},{"url":"https://bugzilla.suse.com/1276517","tags":["report"]},{"url":"https://bugzilla.suse.com/1276522","tags":["report"]},{"url":"https://bugzilla.suse.com/1276574","tags":["report"]},{"url":"https://bugzilla.suse.com/1276576","tags":["report"]},{"url":"https://bugzilla.suse.com/1276585","tags":["report"]},{"url":"https://bugzilla.suse.com/1276592","tags":["report"]},{"url":"https://bugzilla.suse.com/1276765","tags":["report"]},{"url":"https://bugzilla.suse.com/1276769","tags":["report"]},{"url":"https://bugzilla.suse.com/1276770","tags":["report"]},{"url":"https://bugzilla.suse.com/1276772","tags":["report"]},{"url":"https://bugzilla.suse.com/1276773","tags":["report"]},{"url":"https://bugzilla.suse.com/1276776","tags":["report"]},{"url":"https://bugzilla.suse.com/1276778","tags":["report"]},{"url":"https://bugzilla.suse.com/1276779","tags":["report"]},{"url":"https://bugzilla.suse.com/1276798","tags":["report"]},{"url":"https://bugzilla.suse.com/1276844","tags":["report"]},{"url":"https://bugzilla.suse.com/1276925","tags":["report"]},{"url":"https://bugzilla.suse.com/1276933","tags":["report"]},{"url":"https://bugzilla.suse.com/1276934","tags":["report"]},{"url":"https://bugzilla.suse.com/1276935","tags":["report"]},{"url":"https://bugzilla.suse.com/1276940","tags":["report"]},{"url":"https://bugzilla.suse.com/1276949","tags":["report"]},{"url":"https://bugzilla.suse.com/1276956","tags":["report"]},{"url":"https://bugzilla.suse.com/1277044","tags":["report"]},{"url":"https://bugzilla.suse.com/1277046","tags":["report"]},{"url":"https://bugzilla.suse.com/1277053","tags":["report"]},{"url":"https://bugzilla.suse.com/1277067","tags":["report"]},{"url":"https://bugzilla.suse.com/1277069","tags":["report"]},{"url":"https://bugzilla.suse.com/1277071","tags":["report"]},{"url":"https://bugzilla.suse.com/1277072","tags":["report"]},{"url":"https://bugzilla.suse.com/1277075","tags":["report"]},{"url":"https://bugzilla.suse.com/1277080","tags":["report"]},{"url":"https://bugzilla.suse.com/1277082","tags":["report"]},{"url":"https://bugzilla.suse.com/1277089","tags":["report"]},{"url":"https://bugzilla.suse.com/1277091","tags":["report"]},{"url":"https://bugzilla.suse.com/1277094","tags":["report"]},{"url":"https://bugzilla.suse.com/1277103","tags":["report"]},{"url":"https://bugzilla.suse.com/1277113","tags":["report"]},{"url":"https://bugzilla.suse.com/1277121","tags":["report"]},{"url":"https://bugzilla.suse.com/1277133","tags":["report"]},{"url":"https://bugzilla.suse.com/1277158","tags":["report"]},{"url":"https://bugzilla.suse.com/1277161","tags":["report"]},{"url":"https://bugzilla.suse.com/1277163","tags":["report"]},{"url":"https://bugzilla.suse.com/1277166","tags":["report"]},{"url":"https://bugzilla.suse.com/1277167","tags":["report"]},{"url":"https://bugzilla.suse.com/1277169","tags":["report"]},{"url":"https://bugzilla.suse.com/1277170","tags":["report"]},{"url":"https://bugzilla.suse.com/1277171","tags":["report"]},{"url":"https://bugzilla.suse.com/1277173","tags":["report"]},{"url":"https://bugzilla.suse.com/1277176","tags":["report"]},{"url":"https://bugzilla.suse.com/1277177","tags":["report"]},{"url":"https://bugzilla.suse.com/1277184","tags":["report"]},{"url":"https://bugzilla.suse.com/1277190","tags":["report"]},{"url":"https://bugzilla.suse.com/1277191","tags":["report"]},{"url":"https://bugzilla.suse.com/1277192","tags":["report"]},{"url":"https://bugzilla.suse.com/1277193","tags":["report"]},{"url":"https://bugzilla.suse.com/1277194","tags":["report"]},{"url":"https://bugzilla.suse.com/1277195","tags":["report"]},{"url":"https://bugzilla.suse.com/1277196","tags":["report"]},{"url":"https://bugzilla.suse.com/1277197","tags":["report"]},{"url":"https://bugzilla.suse.com/1277201","tags":["report"]},{"url":"https://bugzilla.suse.com/1277211","tags":["report"]},{"url":"https://bugzilla.suse.com/1277214","tags":["report"]},{"url":"https://bugzilla.suse.com/1277221","tags":["report"]},{"url":"https://bugzilla.suse.com/1277222","tags":["report"]},{"url":"https://bugzilla.suse.com/1277225","tags":["report"]},{"url":"https://bugzilla.suse.com/1277240","tags":["report"]},{"url":"https://bugzilla.suse.com/1277254","tags":["report"]},{"url":"https://bugzilla.suse.com/1277264","tags":["report"]},{"url":"https://bugzilla.suse.com/1277280","tags":["report"]},{"url":"https://bugzilla.suse.com/1277282","tags":["report"]},{"url":"https://bugzilla.suse.com/1277307","tags":["report"]},{"url":"https://bugzilla.suse.com/1277312","tags":["report"]},{"url":"https://bugzilla.suse.com/1277317","tags":["report"]},{"url":"https://bugzilla.suse.com/1277319","tags":["report"]},{"url":"https://bugzilla.suse.com/1277323","tags":["report"]},{"url":"https://bugzilla.suse.com/1277325","tags":["report"]},{"url":"https://bugzilla.suse.com/1277329","tags":["report"]},{"url":"https://bugzilla.suse.com/1277330","tags":["report"]},{"url":"https://bugzilla.suse.com/1277336","tags":["report"]},{"url":"https://bugzilla.suse.com/1277337","tags":["report"]},{"url":"https://bugzilla.suse.com/1277338","tags":["report"]},{"url":"https://bugzilla.suse.com/1277339","tags":["report"]},{"url":"https://bugzilla.suse.com/1277343","tags":["report"]},{"url":"https://bugzilla.suse.com/1277344","tags":["report"]},{"url":"https://bugzilla.suse.com/1277345","tags":["report"]},{"url":"https://bugzilla.suse.com/1277355","tags":["report"]},{"url":"https://bugzilla.suse.com/1277356","tags":["report"]},{"url":"https://bugzilla.suse.com/1277357","tags":["report"]},{"url":"https://bugzilla.suse.com/1277362","tags":["report"]},{"url":"https://bugzilla.suse.com/1277364","tags":["report"]},{"url":"https://bugzilla.suse.com/1277365","tags":["report"]},{"url":"https://bugzilla.suse.com/1277383","tags":["report"]},{"url":"https://bugzilla.suse.com/1277387","tags":["report"]},{"url":"https://bugzilla.suse.com/1277389","tags":["report"]},{"url":"https://bugzilla.suse.com/1277456","tags":["report"]},{"url":"https://bugzilla.suse.com/1277457","tags":["report"]},{"url":"https://bugzilla.suse.com/1277461","tags":["report"]},{"url":"https://bugzilla.suse.com/1277467","tags":["report"]},{"url":"https://bugzilla.suse.com/1277472","tags":["report"]},{"url":"https://bugzilla.suse.com/1277487","tags":["report"]},{"url":"https://bugzilla.suse.com/1277488","tags":["report"]},{"url":"https://bugzilla.suse.com/1277497","tags":["report"]},{"url":"https://bugzilla.suse.com/1277520","tags":["report"]},{"url":"https://bugzilla.suse.com/1277522","tags":["report"]},{"url":"https://bugzilla.suse.com/1277529","tags":["report"]},{"url":"https://bugzilla.suse.com/1277530","tags":["report"]},{"url":"https://bugzilla.suse.com/1277533","tags":["report"]},{"url":"https://bugzilla.suse.com/1277538","tags":["report"]},{"url":"https://bugzilla.suse.com/1277540","tags":["report"]},{"url":"https://bugzilla.suse.com/1277541","tags":["report"]},{"url":"https://bugzilla.suse.com/1277542","tags":["report"]},{"url":"https://bugzilla.suse.com/1277543","tags":["report"]},{"url":"https://bugzilla.suse.com/1277546","tags":["report"]},{"url":"https://bugzilla.suse.com/1277554","tags":["report"]},{"url":"https://bugzilla.suse.com/1277560","tags":["report"]},{"url":"https://bugzilla.suse.com/1277566","tags":["report"]},{"url":"https://bugzilla.suse.com/1277576","tags":["report"]},{"url":"https://bugzilla.suse.com/1277578","tags":["report"]},{"url":"https://bugzilla.suse.com/1277593","tags":["report"]},{"url":"https://bugzilla.suse.com/1277599","tags":["report"]},{"url":"https://bugzilla.suse.com/1277607","tags":["report"]},{"url":"https://bugzilla.suse.com/1277609","tags":["report"]},{"url":"https://bugzilla.suse.com/1277610","tags":["report"]},{"url":"https://bugzilla.suse.com/1277612","tags":["report"]},{"url":"https://bugzilla.suse.com/1277621","tags":["report"]},{"url":"https://bugzilla.suse.com/1277623","tags":["report"]},{"url":"https://bugzilla.suse.com/1277637","tags":["report"]},{"url":"https://bugzilla.suse.com/1277645","tags":["report"]},{"url":"https://bugzilla.suse.com/1277657","tags":["report"]},{"url":"https://bugzilla.suse.com/1277663","tags":["report"]},{"url":"https://bugzilla.suse.com/1277665","tags":["report"]},{"url":"https://bugzilla.suse.com/1277677","tags":["report"]},{"url":"https://bugzilla.suse.com/1277682","tags":["report"]},{"url":"https://bugzilla.suse.com/1277690","tags":["report"]},{"url":"https://bugzilla.suse.com/1277730","tags":["report"]},{"url":"https://bugzilla.suse.com/1277741","tags":["report"]},{"url":"https://bugzilla.suse.com/1277744","tags":["report"]},{"url":"https://bugzilla.suse.com/1277746","tags":["report"]},{"url":"https://bugzilla.suse.com/1277754","tags":["report"]},{"url":"https://bugzilla.suse.com/1277770","tags":["report"]},{"url":"https://bugzilla.suse.com/1277771","tags":["report"]},{"url":"https://bugzilla.suse.com/1277772","tags":["report"]},{"url":"https://bugzilla.suse.com/1277835","tags":["report"]},{"url":"https://bugzilla.suse.com/1277836","tags":["report"]},{"url":"https://bugzilla.suse.com/1277839","tags":["report"]},{"url":"https://bugzilla.suse.com/1277875","tags":["report"]},{"url":"https://bugzilla.suse.com/1277877","tags":["report"]},{"url":"https://bugzilla.suse.com/1277879","tags":["report"]},{"url":"https://bugzilla.suse.com/1277880","tags":["report"]},{"url":"https://bugzilla.suse.com/1277881","tags":["report"]},{"url":"https://bugzilla.suse.com/1277882","tags":["report"]},{"url":"https://bugzilla.suse.com/1277884","tags":["report"]},{"url":"https://bugzilla.suse.com/1277890","tags":["report"]},{"url":"https://bugzilla.suse.com/1277893","tags":["report"]},{"url":"https://bugzilla.suse.com/1277903","tags":["report"]},{"url":"https://bugzilla.suse.com/1277934","tags":["report"]},{"url":"https://bugzilla.suse.com/1278028","tags":["report"]},{"url":"https://bugzilla.suse.com/1278030","tags":["report"]},{"url":"https://bugzilla.suse.com/1278033","tags":["report"]},{"url":"https://bugzilla.suse.com/1278041","tags":["report"]},{"url":"https://bugzilla.suse.com/1278050","tags":["report"]},{"url":"https://bugzilla.suse.com/1278057","tags":["report"]},{"url":"https://bugzilla.suse.com/1278101","tags":["report"]},{"url":"https://bugzilla.suse.com/1278123","tags":["report"]},{"url":"https://bugzilla.suse.com/1278132","tags":["report"]},{"url":"https://bugzilla.suse.com/1278139","tags":["report"]},{"url":"https://bugzilla.suse.com/1278153","tags":["report"]},{"url":"https://bugzilla.suse.com/1278160","tags":["report"]},{"url":"https://bugzilla.suse.com/1278181","tags":["report"]},{"url":"https://bugzilla.suse.com/1278194","tags":["report"]},{"url":"https://bugzilla.suse.com/1278200","tags":["report"]},{"url":"https://bugzilla.suse.com/1278201","tags":["report"]},{"url":"https://bugzilla.suse.com/1278202","tags":["report"]},{"url":"https://bugzilla.suse.com/1278207","tags":["report"]},{"url":"https://bugzilla.suse.com/1278212","tags":["report"]},{"url":"https://bugzilla.suse.com/1278214","tags":["report"]},{"url":"https://bugzilla.suse.com/1278222","tags":["report"]},{"url":"https://bugzilla.suse.com/1278241","tags":["report"]},{"url":"https://bugzilla.suse.com/1278246","tags":["report"]},{"url":"https://bugzilla.suse.com/1278296","tags":["report"]},{"url":"https://bugzilla.suse.com/1278310","tags":["report"]},{"url":"https://bugzilla.suse.com/1278313","tags":["report"]},{"url":"https://bugzilla.suse.com/1278317","tags":["report"]},{"url":"https://bugzilla.suse.com/1278319","tags":["report"]},{"url":"https://bugzilla.suse.com/1278320","tags":["report"]},{"url":"https://bugzilla.suse.com/1278323","tags":["report"]},{"url":"https://bugzilla.suse.com/1278325","tags":["report"]},{"url":"https://bugzilla.suse.com/1278326","tags":["report"]},{"url":"https://bugzilla.suse.com/1278334","tags":["report"]},{"url":"https://bugzilla.suse.com/1278337","tags":["report"]},{"url":"https://bugzilla.suse.com/1278343","tags":["report"]},{"url":"https://bugzilla.suse.com/1278377","tags":["report"]},{"url":"https://bugzilla.suse.com/1278393","tags":["report"]},{"url":"https://bugzilla.suse.com/1278400","tags":["report"]},{"url":"https://bugzilla.suse.com/1278412","tags":["report"]},{"url":"https://bugzilla.suse.com/1278415","tags":["report"]},{"url":"https://bugzilla.suse.com/1278429","tags":["report"]},{"url":"https://bugzilla.suse.com/1278430","tags":["report"]},{"url":"https://bugzilla.suse.com/1278431","tags":["report"]},{"url":"https://bugzilla.suse.com/1278704","tags":["report"]},{"url":"https://bugzilla.suse.com/1278711","tags":["report"]},{"url":"https://bugzilla.suse.com/1279455","tags":["report"]},{"url":"https://bugzilla.suse.com/1279464","tags":["report"]},{"url":"https://bugzilla.suse.com/1279467","tags":["report"]},{"url":"https://bugzilla.suse.com/1279468","tags":["report"]},{"url":"https://bugzilla.suse.com/1279471","tags":["report"]},{"url":"https://bugzilla.suse.com/1279477","tags":["report"]},{"url":"https://bugzilla.suse.com/1279483","tags":["report"]},{"url":"https://bugzilla.suse.com/1279485","tags":["report"]},{"url":"https://bugzilla.suse.com/1279493","tags":["report"]},{"url":"https://bugzilla.suse.com/1279494","tags":["report"]},{"url":"https://bugzilla.suse.com/1279496","tags":["report"]},{"url":"https://bugzilla.suse.com/1279499","tags":["report"]},{"url":"https://bugzilla.suse.com/1279504","tags":["report"]},{"url":"https://bugzilla.suse.com/1279508","tags":["report"]},{"url":"https://bugzilla.suse.com/1279510","tags":["report"]},{"url":"https://bugzilla.suse.com/1279520","tags":["report"]},{"url":"https://bugzilla.suse.com/1279533","tags":["report"]},{"url":"https://bugzilla.suse.com/1279564","tags":["report"]},{"url":"https://bugzilla.suse.com/1279592","tags":["report"]},{"url":"https://bugzilla.suse.com/1279594","tags":["report"]},{"url":"https://bugzilla.suse.com/1279605","tags":["report"]},{"url":"https://bugzilla.suse.com/1279606","tags":["report"]},{"url":"https://bugzilla.suse.com/1279607","tags":["report"]},{"url":"https://bugzilla.suse.com/1279608","tags":["report"]},{"url":"https://bugzilla.suse.com/1279614","tags":["report"]},{"url":"https://bugzilla.suse.com/1279616","tags":["report"]},{"url":"https://bugzilla.suse.com/1279624","tags":["report"]},{"url":"https://bugzilla.suse.com/1279625","tags":["report"]},{"url":"https://bugzilla.suse.com/1279627","tags":["report"]},{"url":"https://bugzilla.suse.com/1279632","tags":["report"]},{"url":"https://bugzilla.suse.com/1279698","tags":["report"]},{"url":"https://bugzilla.suse.com/1279699","tags":["report"]},{"url":"https://bugzilla.suse.com/1279777","tags":["report"]},{"url":"https://bugzilla.suse.com/1279795","tags":["report"]},{"url":"https://bugzilla.suse.com/1279798","tags":["report"]},{"url":"https://bugzilla.suse.com/1279802","tags":["report"]},{"url":"https://bugzilla.suse.com/1279805","tags":["report"]},{"url":"https://bugzilla.suse.com/1279808","tags":["report"]},{"url":"https://bugzilla.suse.com/1279809","tags":["report"]},{"url":"https://bugzilla.suse.com/1279812","tags":["report"]},{"url":"https://bugzilla.suse.com/1279814","tags":["report"]},{"url":"https://bugzilla.suse.com/1279815","tags":["report"]},{"url":"https://bugzilla.suse.com/1279816","tags":["report"]},{"url":"https://bugzilla.suse.com/1279825","tags":["report"]},{"url":"https://bugzilla.suse.com/1279920","tags":["report"]},{"url":"https://bugzilla.suse.com/1279921","tags":["report"]},{"url":"https://bugzilla.suse.com/1279971","tags":["report"]},{"url":"https://bugzilla.suse.com/1280141","tags":["report"]},{"url":"https://bugzilla.suse.com/1280142","tags":["report"]},{"url":"https://bugzilla.suse.com/1280156","tags":["report"]},{"url":"https://bugzilla.suse.com/1280157","tags":["report"]},{"url":"https://bugzilla.suse.com/1280158","tags":["report"]},{"url":"https://bugzilla.suse.com/1280162","tags":["report"]},{"url":"https://bugzilla.suse.com/1280172","tags":["report"]},{"url":"https://bugzilla.suse.com/1280178","tags":["report"]},{"url":"https://bugzilla.suse.com/1280185","tags":["report"]},{"url":"https://bugzilla.suse.com/1280215","tags":["report"]},{"url":"https://bugzilla.suse.com/1280221","tags":["report"]},{"url":"https://bugzilla.suse.com/1280230","tags":["report"]},{"url":"https://bugzilla.suse.com/1280234","tags":["report"]},{"url":"https://bugzilla.suse.com/1280244","tags":["report"]},{"url":"https://bugzilla.suse.com/1280246","tags":["report"]},{"url":"https://bugzilla.suse.com/1280247","tags":["report"]},{"url":"https://bugzilla.suse.com/1280251","tags":["report"]},{"url":"https://bugzilla.suse.com/1280253","tags":["report"]},{"url":"https://bugzilla.suse.com/1280266","tags":["report"]},{"url":"https://bugzilla.suse.com/1280273","tags":["report"]},{"url":"https://bugzilla.suse.com/1280276","tags":["report"]},{"url":"https://bugzilla.suse.com/1280301","tags":["report"]},{"url":"https://bugzilla.suse.com/1280305","tags":["report"]},{"url":"https://bugzilla.suse.com/1280306","tags":["report"]},{"url":"https://bugzilla.suse.com/1280311","tags":["report"]},{"url":"https://bugzilla.suse.com/1280315","tags":["report"]},{"url":"https://bugzilla.suse.com/1280316","tags":["report"]},{"url":"https://bugzilla.suse.com/1280319","tags":["report"]},{"url":"https://bugzilla.suse.com/1280345","tags":["report"]},{"url":"https://bugzilla.suse.com/1280378","tags":["report"]},{"url":"https://bugzilla.suse.com/1280395","tags":["report"]},{"url":"https://bugzilla.suse.com/1280397","tags":["report"]},{"url":"https://bugzilla.suse.com/1280398","tags":["report"]},{"url":"https://bugzilla.suse.com/1280399","tags":["report"]},{"url":"https://bugzilla.suse.com/1280400","tags":["report"]},{"url":"https://bugzilla.suse.com/1280402","tags":["report"]},{"url":"https://bugzilla.suse.com/1280408","tags":["report"]},{"url":"https://bugzilla.suse.com/1280410","tags":["report"]},{"url":"https://bugzilla.suse.com/1280415","tags":["report"]},{"url":"https://bugzilla.suse.com/1280416","tags":["report"]},{"url":"https://bugzilla.suse.com/1280421","tags":["report"]},{"url":"https://bugzilla.suse.com/1280423","tags":["report"]},{"url":"https://bugzilla.suse.com/1280425","tags":["report"]},{"url":"https://bugzilla.suse.com/1280428","tags":["report"]},{"url":"https://bugzilla.suse.com/1280429","tags":["report"]},{"url":"https://bugzilla.suse.com/1280431","tags":["report"]},{"url":"https://bugzilla.suse.com/1280434","tags":["report"]},{"url":"https://bugzilla.suse.com/1280463","tags":["report"]},{"url":"https://bugzilla.suse.com/1280472","tags":["report"]},{"url":"https://bugzilla.suse.com/1280476","tags":["report"]},{"url":"https://bugzilla.suse.com/1280477","tags":["report"]},{"url":"https://bugzilla.suse.com/1280479","tags":["report"]},{"url":"https://bugzilla.suse.com/1280480","tags":["report"]},{"url":"https://bugzilla.suse.com/1280492","tags":["report"]},{"url":"https://bugzilla.suse.com/1280500","tags":["report"]},{"url":"https://bugzilla.suse.com/1280501","tags":["report"]},{"url":"https://bugzilla.suse.com/1280504","tags":["report"]},{"url":"https://bugzilla.suse.com/1280505","tags":["report"]},{"url":"https://bugzilla.suse.com/1280520","tags":["report"]},{"url":"https://bugzilla.suse.com/1280539","tags":["report"]},{"url":"https://bugzilla.suse.com/1280545","tags":["report"]},{"url":"https://bugzilla.suse.com/1280554","tags":["report"]},{"url":"https://bugzilla.suse.com/1280559","tags":["report"]},{"url":"https://bugzilla.suse.com/1280560","tags":["report"]},{"url":"https://bugzilla.suse.com/1280563","tags":["report"]},{"url":"https://bugzilla.suse.com/1280569","tags":["report"]},{"url":"https://bugzilla.suse.com/1280570","tags":["report"]},{"url":"https://bugzilla.suse.com/1280571","tags":["report"]},{"url":"https://bugzilla.suse.com/1280573","tags":["report"]},{"url":"https://bugzilla.suse.com/1280581","tags":["report"]},{"url":"https://bugzilla.suse.com/1280713","tags":["report"]},{"url":"https://bugzilla.suse.com/1280735","tags":["report"]},{"url":"https://bugzilla.suse.com/1280736","tags":["report"]},{"url":"https://bugzilla.suse.com/1280745","tags":["report"]},{"url":"https://bugzilla.suse.com/1280777","tags":["report"]},{"url":"https://bugzilla.suse.com/1280785","tags":["report"]},{"url":"https://bugzilla.suse.com/1280794","tags":["report"]},{"url":"https://bugzilla.suse.com/1280804","tags":["report"]},{"url":"https://bugzilla.suse.com/1280806","tags":["report"]},{"url":"https://bugzilla.suse.com/1280813","tags":["report"]},{"url":"https://bugzilla.suse.com/1280822","tags":["report"]},{"url":"https://bugzilla.suse.com/1280826","tags":["report"]},{"url":"https://bugzilla.suse.com/1280834","tags":["report"]},{"url":"https://bugzilla.suse.com/1280918","tags":["report"]},{"url":"https://bugzilla.suse.com/1280948","tags":["report"]},{"url":"https://bugzilla.suse.com/1280960","tags":["report"]},{"url":"https://bugzilla.suse.com/1280970","tags":["report"]},{"url":"https://bugzilla.suse.com/1280976","tags":["report"]},{"url":"https://bugzilla.suse.com/1280977","tags":["report"]},{"url":"https://bugzilla.suse.com/1280978","tags":["report"]},{"url":"https://bugzilla.suse.com/1280980","tags":["report"]},{"url":"https://bugzilla.suse.com/1280981","tags":["report"]},{"url":"https://bugzilla.suse.com/1280984","tags":["report"]},{"url":"https://bugzilla.suse.com/1280987","tags":["report"]},{"url":"https://bugzilla.suse.com/1280992","tags":["report"]},{"url":"https://bugzilla.suse.com/1280996","tags":["report"]},{"url":"https://bugzilla.suse.com/1281001","tags":["report"]},{"url":"https://bugzilla.suse.com/1281003","tags":["report"]},{"url":"https://bugzilla.suse.com/1281005","tags":["report"]},{"url":"https://bugzilla.suse.com/1281008","tags":["report"]},{"url":"https://bugzilla.suse.com/1281011","tags":["report"]},{"url":"https://bugzilla.suse.com/1281018","tags":["report"]},{"url":"https://bugzilla.suse.com/1281022","tags":["report"]},{"url":"https://bugzilla.suse.com/1281027","tags":["report"]},{"url":"https://bugzilla.suse.com/1281029","tags":["report"]},{"url":"https://bugzilla.suse.com/1281030","tags":["report"]},{"url":"https://bugzilla.suse.com/1281034","tags":["report"]},{"url":"https://bugzilla.suse.com/1281052","tags":["report"]},{"url":"https://bugzilla.suse.com/1281056","tags":["report"]},{"url":"https://bugzilla.suse.com/1281058","tags":["report"]},{"url":"https://bugzilla.suse.com/1281065","tags":["report"]},{"url":"https://bugzilla.suse.com/1281130","tags":["report"]},{"url":"https://bugzilla.suse.com/1281138","tags":["report"]},{"url":"https://bugzilla.suse.com/1281149","tags":["report"]},{"url":"https://bugzilla.suse.com/1281150","tags":["report"]},{"url":"https://bugzilla.suse.com/1281151","tags":["report"]},{"url":"https://bugzilla.suse.com/1281155","tags":["report"]},{"url":"https://bugzilla.suse.com/1281156","tags":["report"]},{"url":"https://bugzilla.suse.com/1281163","tags":["report"]},{"url":"https://bugzilla.suse.com/1281164","tags":["report"]},{"url":"https://bugzilla.suse.com/1281165","tags":["report"]},{"url":"https://bugzilla.suse.com/1281173","tags":["report"]},{"url":"https://bugzilla.suse.com/1281174","tags":["report"]},{"url":"https://bugzilla.suse.com/1281179","tags":["report"]},{"url":"https://bugzilla.suse.com/1281180","tags":["report"]},{"url":"https://bugzilla.suse.com/1281181","tags":["report"]},{"url":"https://bugzilla.suse.com/1281183","tags":["report"]},{"url":"https://bugzilla.suse.com/1281184","tags":["report"]},{"url":"https://bugzilla.suse.com/1281185","tags":["report"]},{"url":"https://bugzilla.suse.com/1281189","tags":["report"]},{"url":"https://bugzilla.suse.com/1281190","tags":["report"]},{"url":"https://bugzilla.suse.com/1281191","tags":["report"]},{"url":"https://bugzilla.suse.com/1281194","tags":["report"]},{"url":"https://bugzilla.suse.com/1281204","tags":["report"]},{"url":"https://bugzilla.suse.com/1281206","tags":["report"]},{"url":"https://bugzilla.suse.com/1281211","tags":["report"]},{"url":"https://bugzilla.suse.com/1281214","tags":["report"]},{"url":"https://bugzilla.suse.com/1281216","tags":["report"]},{"url":"https://bugzilla.suse.com/1281221","tags":["report"]},{"url":"https://bugzilla.suse.com/1281222","tags":["report"]},{"url":"https://bugzilla.suse.com/1281251","tags":["report"]},{"url":"https://bugzilla.suse.com/1281253","tags":["report"]},{"url":"https://bugzilla.suse.com/1281254","tags":["report"]},{"url":"https://bugzilla.suse.com/1281257","tags":["report"]},{"url":"https://bugzilla.suse.com/1281260","tags":["report"]},{"url":"https://bugzilla.suse.com/1281265","tags":["report"]},{"url":"https://bugzilla.suse.com/1281269","tags":["report"]},{"url":"https://bugzilla.suse.com/1281270","tags":["report"]},{"url":"https://bugzilla.suse.com/1281271","tags":["report"]},{"url":"https://bugzilla.suse.com/1281272","tags":["report"]},{"url":"https://bugzilla.suse.com/1281275","tags":["report"]},{"url":"https://bugzilla.suse.com/1281277","tags":["report"]},{"url":"https://bugzilla.suse.com/1281281","tags":["report"]},{"url":"https://bugzilla.suse.com/1281292","tags":["report"]},{"url":"https://bugzilla.suse.com/1281299","tags":["report"]},{"url":"https://bugzilla.suse.com/1281300","tags":["report"]},{"url":"https://bugzilla.suse.com/1281311","tags":["report"]},{"url":"https://bugzilla.suse.com/1281315","tags":["report"]},{"url":"https://bugzilla.suse.com/1281320","tags":["report"]},{"url":"https://bugzilla.suse.com/1281332","tags":["report"]},{"url":"https://bugzilla.suse.com/1281333","tags":["report"]},{"url":"https://bugzilla.suse.com/1281334","tags":["report"]},{"url":"https://bugzilla.suse.com/1281337","tags":["report"]},{"url":"https://bugzilla.suse.com/1281346","tags":["report"]},{"url":"https://bugzilla.suse.com/1281352","tags":["report"]},{"url":"https://bugzilla.suse.com/1281353","tags":["report"]},{"url":"https://bugzilla.suse.com/1281357","tags":["report"]},{"url":"https://bugzilla.suse.com/1281360","tags":["report"]},{"url":"https://bugzilla.suse.com/1281361","tags":["report"]},{"url":"https://bugzilla.suse.com/1281363","tags":["report"]},{"url":"https://bugzilla.suse.com/1281368","tags":["report"]},{"url":"https://bugzilla.suse.com/1281382","tags":["report"]},{"url":"https://bugzilla.suse.com/1281384","tags":["report"]},{"url":"https://bugzilla.suse.com/1281391","tags":["report"]},{"url":"https://bugzilla.suse.com/1281392","tags":["report"]},{"url":"https://bugzilla.suse.com/1281394","tags":["report"]},{"url":"https://bugzilla.suse.com/1281395","tags":["report"]},{"url":"https://bugzilla.suse.com/1281396","tags":["report"]},{"url":"https://bugzilla.suse.com/1281402","tags":["report"]},{"url":"https://bugzilla.suse.com/1281418","tags":["report"]},{"url":"https://bugzilla.suse.com/1281422","tags":["report"]},{"url":"https://bugzilla.suse.com/1281429","tags":["report"]},{"url":"https://bugzilla.suse.com/1281488","tags":["report"]},{"url":"https://bugzilla.suse.com/1281490","tags":["report"]},{"url":"https://bugzilla.suse.com/1281495","tags":["report"]},{"url":"https://bugzilla.suse.com/1281500","tags":["report"]},{"url":"https://bugzilla.suse.com/1281504","tags":["report"]},{"url":"https://bugzilla.suse.com/1281509","tags":["report"]},{"url":"https://bugzilla.suse.com/1281510","tags":["report"]},{"url":"https://bugzilla.suse.com/1281535","tags":["report"]},{"url":"https://bugzilla.suse.com/1281538","tags":["report"]},{"url":"https://bugzilla.suse.com/1281547","tags":["report"]},{"url":"https://bugzilla.suse.com/1281549","tags":["report"]},{"url":"https://bugzilla.suse.com/1281551","tags":["report"]},{"url":"https://bugzilla.suse.com/1281563","tags":["report"]},{"url":"https://bugzilla.suse.com/1281568","tags":["report"]},{"url":"https://bugzilla.suse.com/1281577","tags":["report"]},{"url":"https://bugzilla.suse.com/1281579","tags":["report"]},{"url":"https://bugzilla.suse.com/1281619","tags":["report"]},{"url":"https://bugzilla.suse.com/1281620","tags":["report"]},{"url":"https://bugzilla.suse.com/1281626","tags":["report"]},{"url":"https://bugzilla.suse.com/1281631","tags":["report"]},{"url":"https://bugzilla.suse.com/1281635","tags":["report"]},{"url":"https://bugzilla.suse.com/1281639","tags":["report"]},{"url":"https://bugzilla.suse.com/1281640","tags":["report"]},{"url":"https://bugzilla.suse.com/1281650","tags":["report"]},{"url":"https://bugzilla.suse.com/1281672","tags":["report"]},{"url":"https://bugzilla.suse.com/1281676","tags":["report"]},{"url":"https://bugzilla.suse.com/1281677","tags":["report"]},{"url":"https://bugzilla.suse.com/1281688","tags":["report"]},{"url":"https://bugzilla.suse.com/1281691","tags":["report"]},{"url":"https://bugzilla.suse.com/1281696","tags":["report"]},{"url":"https://bugzilla.suse.com/1281701","tags":["report"]},{"url":"https://bugzilla.suse.com/1281702","tags":["report"]},{"url":"https://bugzilla.suse.com/1281705","tags":["report"]},{"url":"https://bugzilla.suse.com/1281706","tags":["report"]},{"url":"https://bugzilla.suse.com/1281707","tags":["report"]},{"url":"https://bugzilla.suse.com/1281708","tags":["report"]},{"url":"https://bugzilla.suse.com/1281715","tags":["report"]},{"url":"https://bugzilla.suse.com/1281723","tags":["report"]},{"url":"https://bugzilla.suse.com/1281724","tags":["report"]},{"url":"https://bugzilla.suse.com/1281735","tags":["report"]},{"url":"https://bugzilla.suse.com/1281736","tags":["report"]},{"url":"https://bugzilla.suse.com/1281753","tags":["report"]},{"url":"https://bugzilla.suse.com/1281776","tags":["report"]},{"url":"https://bugzilla.suse.com/1281779","tags":["report"]},{"url":"https://bugzilla.suse.com/1281781","tags":["report"]},{"url":"https://bugzilla.suse.com/1281783","tags":["report"]},{"url":"https://bugzilla.suse.com/1281784","tags":["report"]},{"url":"https://bugzilla.suse.com/1281785","tags":["report"]},{"url":"https://bugzilla.suse.com/1281796","tags":["report"]},{"url":"https://bugzilla.suse.com/1281799","tags":["report"]},{"url":"https://bugzilla.suse.com/1281801","tags":["report"]},{"url":"https://bugzilla.suse.com/1281804","tags":["report"]},{"url":"https://bugzilla.suse.com/1281813","tags":["report"]},{"url":"https://bugzilla.suse.com/1281824","tags":["report"]},{"url":"https://bugzilla.suse.com/1281828","tags":["report"]},{"url":"https://bugzilla.suse.com/1281850","tags":["report"]},{"url":"https://bugzilla.suse.com/1281851","tags":["report"]},{"url":"https://bugzilla.suse.com/1281853","tags":["report"]},{"url":"https://bugzilla.suse.com/1281858","tags":["report"]},{"url":"https://bugzilla.suse.com/1281868","tags":["report"]},{"url":"https://bugzilla.suse.com/1281870","tags":["report"]},{"url":"https://bugzilla.suse.com/1281877","tags":["report"]},{"url":"https://bugzilla.suse.com/1281886","tags":["report"]},{"url":"https://bugzilla.suse.com/1281887","tags":["report"]},{"url":"https://bugzilla.suse.com/1281890","tags":["report"]},{"url":"https://bugzilla.suse.com/1281891","tags":["report"]},{"url":"https://bugzilla.suse.com/1281895","tags":["report"]},{"url":"https://bugzilla.suse.com/1281897","tags":["report"]},{"url":"https://bugzilla.suse.com/1281900","tags":["report"]},{"url":"https://bugzilla.suse.com/1281903","tags":["report"]},{"url":"https://bugzilla.suse.com/1281916","tags":["report"]},{"url":"https://bugzilla.suse.com/1281930","tags":["report"]},{"url":"https://bugzilla.suse.com/1281932","tags":["report"]},{"url":"https://bugzilla.suse.com/1281968","tags":["report"]},{"url":"https://bugzilla.suse.com/1281969","tags":["report"]},{"url":"https://bugzilla.suse.com/1281985","tags":["report"]},{"url":"https://bugzilla.suse.com/1281987","tags":["report"]},{"url":"https://bugzilla.suse.com/1281996","tags":["report"]},{"url":"https://bugzilla.suse.com/1282001","tags":["report"]},{"url":"https://bugzilla.suse.com/1282002","tags":["report"]},{"url":"https://bugzilla.suse.com/1282008","tags":["report"]},{"url":"https://bugzilla.suse.com/1282018","tags":["report"]},{"url":"https://bugzilla.suse.com/1282019","tags":["report"]},{"url":"https://bugzilla.suse.com/1282021","tags":["report"]},{"url":"https://bugzilla.suse.com/1282025","tags":["report"]},{"url":"https://bugzilla.suse.com/1282026","tags":["report"]},{"url":"https://bugzilla.suse.com/1282027","tags":["report"]},{"url":"https://bugzilla.suse.com/1282031","tags":["report"]},{"url":"https://bugzilla.suse.com/1282032","tags":["report"]},{"url":"https://bugzilla.suse.com/1282033","tags":["report"]},{"url":"https://bugzilla.suse.com/1282044","tags":["report"]},{"url":"https://bugzilla.suse.com/1282045","tags":["report"]},{"url":"https://bugzilla.suse.com/1282063","tags":["report"]},{"url":"https://bugzilla.suse.com/1282065","tags":["report"]},{"url":"https://bugzilla.suse.com/1282068","tags":["report"]},{"url":"https://bugzilla.suse.com/1282080","tags":["report"]},{"url":"https://bugzilla.suse.com/1282081","tags":["report"]},{"url":"https://bugzilla.suse.com/1282082","tags":["report"]},{"url":"https://bugzilla.suse.com/1282083","tags":["report"]},{"url":"https://bugzilla.suse.com/1282095","tags":["report"]},{"url":"https://bugzilla.suse.com/1282114","tags":["report"]},{"url":"https://bugzilla.suse.com/1282116","tags":["report"]},{"url":"https://bugzilla.suse.com/1282117","tags":["report"]},{"url":"https://bugzilla.suse.com/1282122","tags":["report"]},{"url":"https://bugzilla.suse.com/1282128","tags":["report"]},{"url":"https://bugzilla.suse.com/1282133","tags":["report"]},{"url":"https://bugzilla.suse.com/1282134","tags":["report"]},{"url":"https://bugzilla.suse.com/1282145","tags":["report"]},{"url":"https://bugzilla.suse.com/1282146","tags":["report"]},{"url":"https://bugzilla.suse.com/1282149","tags":["report"]},{"url":"https://bugzilla.suse.com/1282151","tags":["report"]},{"url":"https://bugzilla.suse.com/1282154","tags":["report"]},{"url":"https://bugzilla.suse.com/1282156","tags":["report"]},{"url":"https://bugzilla.suse.com/1282158","tags":["report"]},{"url":"https://bugzilla.suse.com/1282167","tags":["report"]},{"url":"https://bugzilla.suse.com/1282174","tags":["report"]},{"url":"https://bugzilla.suse.com/1282178","tags":["report"]},{"url":"https://bugzilla.suse.com/1282189","tags":["report"]},{"url":"https://bugzilla.suse.com/1282192","tags":["report"]},{"url":"https://bugzilla.suse.com/1282196","tags":["report"]},{"url":"https://bugzilla.suse.com/1282262","tags":["report"]},{"url":"https://bugzilla.suse.com/1282276","tags":["report"]},{"url":"https://bugzilla.suse.com/1282289","tags":["report"]},{"url":"https://bugzilla.suse.com/1282296","tags":["report"]},{"url":"https://bugzilla.suse.com/1282298","tags":["report"]},{"url":"https://bugzilla.suse.com/1282302","tags":["report"]},{"url":"https://bugzilla.suse.com/1282304","tags":["report"]},{"url":"https://bugzilla.suse.com/1282325","tags":["report"]},{"url":"https://bugzilla.suse.com/1282327","tags":["report"]},{"url":"https://bugzilla.suse.com/1282328","tags":["report"]},{"url":"https://bugzilla.suse.com/1282677","tags":["report"]},{"url":"https://bugzilla.suse.com/1282684","tags":["report"]},{"url":"https://bugzilla.suse.com/1282686","tags":["report"]},{"url":"https://bugzilla.suse.com/1282690","tags":["report"]},{"url":"https://bugzilla.suse.com/1282691","tags":["report"]},{"url":"https://bugzilla.suse.com/1282695","tags":["report"]},{"url":"https://bugzilla.suse.com/1282697","tags":["report"]},{"url":"https://bugzilla.suse.com/1282729","tags":["report"]},{"url":"https://bugzilla.suse.com/1282737","tags":["report"]},{"url":"https://bugzilla.suse.com/1282744","tags":["report"]},{"url":"https://bugzilla.suse.com/1282753","tags":["report"]},{"url":"https://bugzilla.suse.com/1282754","tags":["report"]},{"url":"https://bugzilla.suse.com/1282759","tags":["report"]},{"url":"https://bugzilla.suse.com/1282763","tags":["report"]},{"url":"https://bugzilla.suse.com/1282764","tags":["report"]},{"url":"https://bugzilla.suse.com/1282769","tags":["report"]},{"url":"https://bugzilla.suse.com/1282772","tags":["report"]},{"url":"https://bugzilla.suse.com/1282773","tags":["report"]},{"url":"https://bugzilla.suse.com/1282775","tags":["report"]},{"url":"https://bugzilla.suse.com/1282776","tags":["report"]},{"url":"https://bugzilla.suse.com/1282778","tags":["report"]},{"url":"https://bugzilla.suse.com/1282805","tags":["report"]},{"url":"https://bugzilla.suse.com/1282814","tags":["report"]},{"url":"https://bugzilla.suse.com/1282867","tags":["report"]},{"url":"https://bugzilla.suse.com/1282870","tags":["report"]},{"url":"https://bugzilla.suse.com/1282879","tags":["report"]},{"url":"https://bugzilla.suse.com/1282885","tags":["report"]},{"url":"https://bugzilla.suse.com/1282887","tags":["report"]},{"url":"https://bugzilla.suse.com/1282889","tags":["report"]},{"url":"https://bugzilla.suse.com/1282890","tags":["report"]},{"url":"https://bugzilla.suse.com/1282893","tags":["report"]},{"url":"https://bugzilla.suse.com/1282898","tags":["report"]},{"url":"https://bugzilla.suse.com/1282911","tags":["report"]},{"url":"https://bugzilla.suse.com/1282914","tags":["report"]},{"url":"https://bugzilla.suse.com/1282915","tags":["report"]},{"url":"https://bugzilla.suse.com/1282920","tags":["report"]},{"url":"https://bugzilla.suse.com/1282924","tags":["report"]},{"url":"https://bugzilla.suse.com/1282925","tags":["report"]},{"url":"https://bugzilla.suse.com/1282926","tags":["report"]},{"url":"https://bugzilla.suse.com/1282927","tags":["report"]},{"url":"https://bugzilla.suse.com/1282935","tags":["report"]},{"url":"https://bugzilla.suse.com/1282955","tags":["report"]},{"url":"https://bugzilla.suse.com/1282957","tags":["report"]},{"url":"https://bugzilla.suse.com/1282962","tags":["report"]},{"url":"https://bugzilla.suse.com/1282963","tags":["report"]},{"url":"https://bugzilla.suse.com/1282974","tags":["report"]},{"url":"https://bugzilla.suse.com/1282984","tags":["report"]},{"url":"https://bugzilla.suse.com/1283004","tags":["report"]},{"url":"https://bugzilla.suse.com/1283016","tags":["report"]},{"url":"https://bugzilla.suse.com/1283017","tags":["report"]},{"url":"https://bugzilla.suse.com/1283018","tags":["report"]},{"url":"https://bugzilla.suse.com/1283036","tags":["report"]},{"url":"https://bugzilla.suse.com/1283039","tags":["report"]},{"url":"https://bugzilla.suse.com/1283045","tags":["report"]},{"url":"https://bugzilla.suse.com/1283047","tags":["report"]},{"url":"https://bugzilla.suse.com/1283051","tags":["report"]},{"url":"https://bugzilla.suse.com/1283058","tags":["report"]},{"url":"https://bugzilla.suse.com/1283076","tags":["report"]},{"url":"https://bugzilla.suse.com/1283077","tags":["report"]},{"url":"https://bugzilla.suse.com/1283078","tags":["report"]},{"url":"https://bugzilla.suse.com/1283081","tags":["report"]},{"url":"https://bugzilla.suse.com/1283087","tags":["report"]},{"url":"https://bugzilla.suse.com/1283113","tags":["report"]},{"url":"https://bugzilla.suse.com/1283114","tags":["report"]},{"url":"https://bugzilla.suse.com/1283122","tags":["report"]},{"url":"https://bugzilla.suse.com/1283132","tags":["report"]},{"url":"https://bugzilla.suse.com/1283134","tags":["report"]},{"url":"https://bugzilla.suse.com/1283136","tags":["report"]},{"url":"https://bugzilla.suse.com/1283145","tags":["report"]},{"url":"https://bugzilla.suse.com/1283155","tags":["report"]},{"url":"https://bugzilla.suse.com/1283157","tags":["report"]},{"url":"https://bugzilla.suse.com/1283159","tags":["report"]},{"url":"https://bugzilla.suse.com/1283164","tags":["report"]},{"url":"https://bugzilla.suse.com/1283175","tags":["report"]},{"url":"https://bugzilla.suse.com/1283177","tags":["report"]},{"url":"https://bugzilla.suse.com/1283196","tags":["report"]},{"url":"https://bugzilla.suse.com/1283197","tags":["report"]},{"url":"https://bugzilla.suse.com/1283202","tags":["report"]},{"url":"https://bugzilla.suse.com/1283206","tags":["report"]},{"url":"https://bugzilla.suse.com/1283208","tags":["report"]},{"url":"https://bugzilla.suse.com/1283209","tags":["report"]},{"url":"https://bugzilla.suse.com/1283211","tags":["report"]},{"url":"https://bugzilla.suse.com/1283214","tags":["report"]},{"url":"https://bugzilla.suse.com/1283215","tags":["report"]},{"url":"https://bugzilla.suse.com/1283220","tags":["report"]},{"url":"https://bugzilla.suse.com/1283223","tags":["report"]},{"url":"https://bugzilla.suse.com/1283224","tags":["report"]},{"url":"https://bugzilla.suse.com/1283225","tags":["report"]},{"url":"https://bugzilla.suse.com/1283226","tags":["report"]},{"url":"https://bugzilla.suse.com/1283229","tags":["report"]},{"url":"https://bugzilla.suse.com/1283231","tags":["report"]},{"url":"https://bugzilla.suse.com/1283271","tags":["report"]},{"url":"https://bugzilla.suse.com/1283276","tags":["report"]},{"url":"https://bugzilla.suse.com/1283278","tags":["report"]},{"url":"https://bugzilla.suse.com/1283287","tags":["report"]},{"url":"https://bugzilla.suse.com/1283288","tags":["report"]},{"url":"https://bugzilla.suse.com/1283292","tags":["report"]},{"url":"https://bugzilla.suse.com/1283333","tags":["report"]},{"url":"https://bugzilla.suse.com/1283334","tags":["report"]},{"url":"https://bugzilla.suse.com/1283335","tags":["report"]},{"url":"https://bugzilla.suse.com/1283337","tags":["report"]},{"url":"https://bugzilla.suse.com/1283339","tags":["report"]},{"url":"https://bugzilla.suse.com/1283343","tags":["report"]},{"url":"https://bugzilla.suse.com/1283349","tags":["report"]},{"url":"https://bugzilla.suse.com/1283356","tags":["report"]},{"url":"https://bugzilla.suse.com/1283360","tags":["report"]},{"url":"https://bugzilla.suse.com/1283364","tags":["report"]},{"url":"https://bugzilla.suse.com/1283416","tags":["report"]},{"url":"https://bugzilla.suse.com/1283418","tags":["report"]},{"url":"https://bugzilla.suse.com/1283429","tags":["report"]},{"url":"https://bugzilla.suse.com/1283445","tags":["report"]},{"url":"https://bugzilla.suse.com/1283453","tags":["report"]},{"url":"https://bugzilla.suse.com/1283464","tags":["report"]},{"url":"https://bugzilla.suse.com/1283469","tags":["report"]},{"url":"https://bugzilla.suse.com/1283474","tags":["report"]},{"url":"https://bugzilla.suse.com/1283481","tags":["report"]},{"url":"https://bugzilla.suse.com/1283483","tags":["report"]},{"url":"https://bugzilla.suse.com/1283485","tags":["report"]},{"url":"https://bugzilla.suse.com/1283486","tags":["report"]},{"url":"https://bugzilla.suse.com/1283502","tags":["report"]},{"url":"https://bugzilla.suse.com/1283511","tags":["report"]},{"url":"https://bugzilla.suse.com/1283585","tags":["report"]},{"url":"https://bugzilla.suse.com/1283662","tags":["report"]},{"url":"https://bugzilla.suse.com/1283668","tags":["report"]},{"url":"https://bugzilla.suse.com/1283741","tags":["report"]},{"url":"https://bugzilla.suse.com/1283746","tags":["report"]},{"url":"https://bugzilla.suse.com/1283752","tags":["report"]},{"url":"https://bugzilla.suse.com/1283754","tags":["report"]},{"url":"https://bugzilla.suse.com/1283782","tags":["report"]},{"url":"https://bugzilla.suse.com/1283793","tags":["report"]},{"url":"https://bugzilla.suse.com/1283810","tags":["report"]},{"url":"https://bugzilla.suse.com/1283812","tags":["report"]},{"url":"https://bugzilla.suse.com/1283821","tags":["report"]},{"url":"https://bugzilla.suse.com/1283830","tags":["report"]},{"url":"https://bugzilla.suse.com/1283833","tags":["report"]},{"url":"https://bugzilla.suse.com/1283834","tags":["report"]},{"url":"https://bugzilla.suse.com/1283837","tags":["report"]},{"url":"https://bugzilla.suse.com/1283838","tags":["report"]},{"url":"https://bugzilla.suse.com/1283842","tags":["report"]},{"url":"https://bugzilla.suse.com/1283844","tags":["report"]},{"url":"https://bugzilla.suse.com/1283845","tags":["report"]},{"url":"https://bugzilla.suse.com/1283846","tags":["report"]},{"url":"https://bugzilla.suse.com/1283850","tags":["report"]},{"url":"https://bugzilla.suse.com/1283853","tags":["report"]},{"url":"https://bugzilla.suse.com/1283855","tags":["report"]},{"url":"https://bugzilla.suse.com/1283856","tags":["report"]},{"url":"https://bugzilla.suse.com/1283858","tags":["report"]},{"url":"https://bugzilla.suse.com/1283859","tags":["report"]},{"url":"https://bugzilla.suse.com/1283862","tags":["report"]},{"url":"https://bugzilla.suse.com/1283863","tags":["report"]},{"url":"https://bugzilla.suse.com/1283869","tags":["report"]},{"url":"https://bugzilla.suse.com/1283871","tags":["report"]},{"url":"https://bugzilla.suse.com/1283873","tags":["report"]},{"url":"https://bugzilla.suse.com/1283877","tags":["report"]},{"url":"https://bugzilla.suse.com/1283878","tags":["report"]},{"url":"https://bugzilla.suse.com/1283884","tags":["report"]},{"url":"https://bugzilla.suse.com/1283886","tags":["report"]},{"url":"https://bugzilla.suse.com/1283903","tags":["report"]},{"url":"https://bugzilla.suse.com/1283916","tags":["report"]},{"url":"https://bugzilla.suse.com/1283920","tags":["report"]},{"url":"https://bugzilla.suse.com/1283921","tags":["report"]},{"url":"https://bugzilla.suse.com/1283928","tags":["report"]},{"url":"https://bugzilla.suse.com/1283933","tags":["report"]},{"url":"https://bugzilla.suse.com/1283941","tags":["report"]},{"url":"https://bugzilla.suse.com/1283958","tags":["report"]},{"url":"https://bugzilla.suse.com/1283960","tags":["report"]},{"url":"https://bugzilla.suse.com/1283967","tags":["report"]},{"url":"https://bugzilla.suse.com/1284024","tags":["report"]},{"url":"https://bugzilla.suse.com/1284031","tags":["report"]},{"url":"https://bugzilla.suse.com/1284064","tags":["report"]},{"url":"https://bugzilla.suse.com/1284150","tags":["report"]},{"url":"https://bugzilla.suse.com/1284243","tags":["report"]},{"url":"https://bugzilla.suse.com/1284292","tags":["report"]},{"url":"https://bugzilla.suse.com/1284293","tags":["report"]},{"url":"https://bugzilla.suse.com/1284296","tags":["report"]},{"url":"https://bugzilla.suse.com/1284298","tags":["report"]},{"url":"https://bugzilla.suse.com/1284302","tags":["report"]},{"url":"https://bugzilla.suse.com/1284304","tags":["report"]},{"url":"https://bugzilla.suse.com/1284305","tags":["report"]},{"url":"https://bugzilla.suse.com/1284310","tags":["report"]},{"url":"https://bugzilla.suse.com/1284312","tags":["report"]},{"url":"https://bugzilla.suse.com/1284313","tags":["report"]},{"url":"https://bugzilla.suse.com/1284346","tags":["report"]},{"url":"https://bugzilla.suse.com/1284349","tags":["report"]},{"url":"https://bugzilla.suse.com/1284350","tags":["report"]},{"url":"https://bugzilla.suse.com/1284358","tags":["report"]},{"url":"https://bugzilla.suse.com/1284360","tags":["report"]},{"url":"https://bugzilla.suse.com/1284363","tags":["report"]},{"url":"https://bugzilla.suse.com/1284419","tags":["report"]},{"url":"https://bugzilla.suse.com/1284422","tags":["report"]},{"url":"https://bugzilla.suse.com/1284446","tags":["report"]},{"url":"https://bugzilla.suse.com/1284455","tags":["report"]},{"url":"https://bugzilla.suse.com/1284477","tags":["report"]},{"url":"https://bugzilla.suse.com/1284483","tags":["report"]},{"url":"https://bugzilla.suse.com/1284484","tags":["report"]},{"url":"https://bugzilla.suse.com/1284485","tags":["report"]},{"url":"https://bugzilla.suse.com/1284498","tags":["report"]},{"url":"https://bugzilla.suse.com/1284503","tags":["report"]},{"url":"https://bugzilla.suse.com/1284504","tags":["report"]},{"url":"https://bugzilla.suse.com/1284505","tags":["report"]},{"url":"https://bugzilla.suse.com/1284509","tags":["report"]},{"url":"https://bugzilla.suse.com/1284512","tags":["report"]},{"url":"https://bugzilla.suse.com/1284513","tags":["report"]},{"url":"https://bugzilla.suse.com/1284514","tags":["report"]},{"url":"https://bugzilla.suse.com/1284515","tags":["report"]},{"url":"https://bugzilla.suse.com/1284517","tags":["report"]},{"url":"https://bugzilla.suse.com/1284537","tags":["report"]},{"url":"https://bugzilla.suse.com/1284540","tags":["report"]},{"url":"https://bugzilla.suse.com/1284541","tags":["report"]},{"url":"https://bugzilla.suse.com/1284542","tags":["report"]},{"url":"https://bugzilla.suse.com/1284543","tags":["report"]},{"url":"https://bugzilla.suse.com/1284544","tags":["report"]},{"url":"https://bugzilla.suse.com/1284545","tags":["report"]},{"url":"https://bugzilla.suse.com/1284553","tags":["report"]},{"url":"https://bugzilla.suse.com/1284554","tags":["report"]},{"url":"https://bugzilla.suse.com/1284555","tags":["report"]},{"url":"https://bugzilla.suse.com/1284557","tags":["report"]},{"url":"https://bugzilla.suse.com/1284563","tags":["report"]},{"url":"https://bugzilla.suse.com/1284568","tags":["report"]},{"url":"https://bugzilla.suse.com/1284577","tags":["report"]},{"url":"https://bugzilla.suse.com/1284578","tags":["report"]},{"url":"https://bugzilla.suse.com/1284579","tags":["report"]},{"url":"https://bugzilla.suse.com/1284584","tags":["report"]},{"url":"https://bugzilla.suse.com/1284595","tags":["report"]},{"url":"https://bugzilla.suse.com/1284601","tags":["report"]},{"url":"https://bugzilla.suse.com/1284602","tags":["report"]},{"url":"https://bugzilla.suse.com/1284605","tags":["report"]},{"url":"https://bugzilla.suse.com/1284609","tags":["report"]},{"url":"https://bugzilla.suse.com/1284615","tags":["report"]},{"url":"https://bugzilla.suse.com/1284616","tags":["report"]},{"url":"https://bugzilla.suse.com/1284620","tags":["report"]},{"url":"https://bugzilla.suse.com/1284621","tags":["report"]},{"url":"https://bugzilla.suse.com/1284623","tags":["report"]},{"url":"https://bugzilla.suse.com/1284626","tags":["report"]},{"url":"https://bugzilla.suse.com/1284630","tags":["report"]},{"url":"https://bugzilla.suse.com/1284631","tags":["report"]},{"url":"https://bugzilla.suse.com/1284635","tags":["report"]},{"url":"https://bugzilla.suse.com/1284636","tags":["report"]},{"url":"https://bugzilla.suse.com/1284637","tags":["report"]},{"url":"https://bugzilla.suse.com/1284638","tags":["report"]},{"url":"https://bugzilla.suse.com/1284640","tags":["report"]},{"url":"https://bugzilla.suse.com/1284641","tags":["report"]},{"url":"https://bugzilla.suse.com/1284643","tags":["report"]},{"url":"https://bugzilla.suse.com/1284644","tags":["report"]},{"url":"https://bugzilla.suse.com/1284652","tags":["report"]},{"url":"https://bugzilla.suse.com/1284704","tags":["report"]},{"url":"https://bugzilla.suse.com/1284706","tags":["report"]},{"url":"https://bugzilla.suse.com/1284707","tags":["report"]},{"url":"https://bugzilla.suse.com/1284709","tags":["report"]},{"url":"https://bugzilla.suse.com/1284721","tags":["report"]},{"url":"https://bugzilla.suse.com/1284723","tags":["report"]},{"url":"https://bugzilla.suse.com/1284740","tags":["report"]},{"url":"https://bugzilla.suse.com/1285553","tags":["report"]},{"url":"https://bugzilla.suse.com/1285556","tags":["report"]},{"url":"https://bugzilla.suse.com/1285560","tags":["report"]},{"url":"https://bugzilla.suse.com/1285561","tags":["report"]},{"url":"https://bugzilla.suse.com/1285562","tags":["report"]},{"url":"https://bugzilla.suse.com/1285564","tags":["report"]},{"url":"https://bugzilla.suse.com/1285569","tags":["report"]},{"url":"https://bugzilla.suse.com/1285587","tags":["report"]},{"url":"https://bugzilla.suse.com/1285624","tags":["report"]},{"url":"https://bugzilla.suse.com/1285648","tags":["report"]},{"url":"https://bugzilla.suse.com/1285668","tags":["report"]},{"url":"https://bugzilla.suse.com/1285685","tags":["report"]},{"url":"https://bugzilla.suse.com/1285914","tags":["report"]},{"url":"https://bugzilla.suse.com/1285957","tags":["report"]},{"url":"https://bugzilla.suse.com/1285971","tags":["report"]},{"url":"https://bugzilla.suse.com/1285976","tags":["report"]},{"url":"https://bugzilla.suse.com/1285978","tags":["report"]},{"url":"https://bugzilla.suse.com/1285979","tags":["report"]},{"url":"https://bugzilla.suse.com/1285985","tags":["report"]},{"url":"https://bugzilla.suse.com/1285988","tags":["report"]},{"url":"https://bugzilla.suse.com/1285998","tags":["report"]},{"url":"https://bugzilla.suse.com/1286009","tags":["report"]},{"url":"https://bugzilla.suse.com/1286012","tags":["report"]},{"url":"https://bugzilla.suse.com/1286013","tags":["report"]},{"url":"https://bugzilla.suse.com/1286019","tags":["report"]},{"url":"https://bugzilla.suse.com/1286036","tags":["report"]},{"url":"https://bugzilla.suse.com/1286037","tags":["report"]},{"url":"https://bugzilla.suse.com/1286112","tags":["report"]},{"url":"https://bugzilla.suse.com/1286114","tags":["report"]},{"url":"https://bugzilla.suse.com/1286119","tags":["report"]},{"url":"https://bugzilla.suse.com/1286121","tags":["report"]},{"url":"https://bugzilla.suse.com/1286123","tags":["report"]},{"url":"https://bugzilla.suse.com/1286158","tags":["report"]},{"url":"https://bugzilla.suse.com/1286160","tags":["report"]},{"url":"https://bugzilla.suse.com/1286161","tags":["report"]},{"url":"https://bugzilla.suse.com/1286171","tags":["report"]},{"url":"https://bugzilla.suse.com/1286190","tags":["report"]},{"url":"https://bugzilla.suse.com/1286204","tags":["report"]},{"url":"https://bugzilla.suse.com/1286205","tags":["report"]},{"url":"https://bugzilla.suse.com/1286207","tags":["report"]},{"url":"https://bugzilla.suse.com/1286215","tags":["report"]},{"url":"https://bugzilla.suse.com/1286217","tags":["report"]},{"url":"https://bugzilla.suse.com/1286224","tags":["report"]},{"url":"https://bugzilla.suse.com/1286233","tags":["report"]},{"url":"https://bugzilla.suse.com/1286234","tags":["report"]},{"url":"https://bugzilla.suse.com/1286237","tags":["report"]},{"url":"https://bugzilla.suse.com/1286240","tags":["report"]},{"url":"https://bugzilla.suse.com/1286257","tags":["report"]},{"url":"https://bugzilla.suse.com/1286259","tags":["report"]},{"url":"https://bugzilla.suse.com/1286267","tags":["report"]},{"url":"https://bugzilla.suse.com/1286342","tags":["report"]},{"url":"https://bugzilla.suse.com/1286346","tags":["report"]},{"url":"https://bugzilla.suse.com/1286390","tags":["report"]},{"url":"https://bugzilla.suse.com/1286391","tags":["report"]},{"url":"https://bugzilla.suse.com/1286394","tags":["report"]},{"url":"https://bugzilla.suse.com/1286417","tags":["report"]},{"url":"https://bugzilla.suse.com/1286421","tags":["report"]},{"url":"https://bugzilla.suse.com/1286431","tags":["report"]},{"url":"https://bugzilla.suse.com/1286432","tags":["report"]},{"url":"https://bugzilla.suse.com/1286443","tags":["report"]},{"url":"https://bugzilla.suse.com/1286444","tags":["report"]},{"url":"https://bugzilla.suse.com/1286453","tags":["report"]},{"url":"https://bugzilla.suse.com/1286455","tags":["report"]},{"url":"https://bugzilla.suse.com/1286457","tags":["report"]},{"url":"https://bugzilla.suse.com/1286469","tags":["report"]},{"url":"https://bugzilla.suse.com/1286514","tags":["report"]},{"url":"https://bugzilla.suse.com/1286529","tags":["report"]},{"url":"https://bugzilla.suse.com/1286625","tags":["report"]},{"url":"https://bugzilla.suse.com/1286654","tags":["report"]},{"url":"https://bugzilla.suse.com/1286669","tags":["report"]},{"url":"https://bugzilla.suse.com/1286671","tags":["report"]},{"url":"https://bugzilla.suse.com/1286672","tags":["report"]},{"url":"https://bugzilla.suse.com/1286689","tags":["report"]},{"url":"https://bugzilla.suse.com/1286692","tags":["report"]},{"url":"https://bugzilla.suse.com/1286704","tags":["report"]},{"url":"https://bugzilla.suse.com/1286707","tags":["report"]},{"url":"https://bugzilla.suse.com/1286713","tags":["report"]},{"url":"https://bugzilla.suse.com/1286720","tags":["report"]},{"url":"https://bugzilla.suse.com/1286735","tags":["report"]},{"url":"https://bugzilla.suse.com/1286741","tags":["report"]},{"url":"https://bugzilla.suse.com/1286742","tags":["report"]},{"url":"https://bugzilla.suse.com/1286756","tags":["report"]},{"url":"https://bugzilla.suse.com/1286757","tags":["report"]},{"url":"https://bugzilla.suse.com/1286772","tags":["report"]},{"url":"https://bugzilla.suse.com/1286775","tags":["report"]},{"url":"https://bugzilla.suse.com/1286778","tags":["report"]},{"url":"https://bugzilla.suse.com/1286782","tags":["report"]},{"url":"https://bugzilla.suse.com/1286785","tags":["report"]},{"url":"https://bugzilla.suse.com/1286787","tags":["report"]},{"url":"https://bugzilla.suse.com/1286819","tags":["report"]},{"url":"https://bugzilla.suse.com/1286820","tags":["report"]},{"url":"https://bugzilla.suse.com/1286821","tags":["report"]},{"url":"https://bugzilla.suse.com/1286822","tags":["report"]},{"url":"https://bugzilla.suse.com/1286823","tags":["report"]},{"url":"https://bugzilla.suse.com/1286824","tags":["report"]},{"url":"https://bugzilla.suse.com/1286841","tags":["report"]},{"url":"https://bugzilla.suse.com/1286843","tags":["report"]},{"url":"https://bugzilla.suse.com/1286850","tags":["report"]},{"url":"https://bugzilla.suse.com/1286856","tags":["report"]},{"url":"https://bugzilla.suse.com/1286857","tags":["report"]},{"url":"https://bugzilla.suse.com/1286859","tags":["report"]},{"url":"https://bugzilla.suse.com/1286860","tags":["report"]},{"url":"https://bugzilla.suse.com/1286862","tags":["report"]},{"url":"https://bugzilla.suse.com/1286863","tags":["report"]},{"url":"https://bugzilla.suse.com/1286864","tags":["report"]},{"url":"https://bugzilla.suse.com/1286865","tags":["report"]},{"url":"https://bugzilla.suse.com/1286867","tags":["report"]},{"url":"https://bugzilla.suse.com/1286872","tags":["report"]},{"url":"https://bugzilla.suse.com/1286874","tags":["report"]},{"url":"https://bugzilla.suse.com/1286877","tags":["report"]},{"url":"https://bugzilla.suse.com/1286890","tags":["report"]},{"url":"https://bugzilla.suse.com/1286913","tags":["report"]},{"url":"https://bugzilla.suse.com/1286918","tags":["report"]},{"url":"https://bugzilla.suse.com/1286919","tags":["report"]},{"url":"https://bugzilla.suse.com/1287173","tags":["report"]},{"url":"https://bugzilla.suse.com/1287191","tags":["report"]},{"url":"https://bugzilla.suse.com/1287256","tags":["report"]},{"url":"https://bugzilla.suse.com/1287268","tags":["report"]},{"url":"https://bugzilla.suse.com/1287342","tags":["report"]},{"url":"https://bugzilla.suse.com/1287346","tags":["report"]},{"url":"https://bugzilla.suse.com/1287347","tags":["report"]},{"url":"https://bugzilla.suse.com/1287351","tags":["report"]},{"url":"https://bugzilla.suse.com/1287364","tags":["report"]},{"url":"https://bugzilla.suse.com/1287592","tags":["report"]},{"url":"https://bugzilla.suse.com/1287594","tags":["report"]},{"url":"https://bugzilla.suse.com/1287597","tags":["report"]},{"url":"https://bugzilla.suse.com/1287648","tags":["report"]},{"url":"https://bugzilla.suse.com/1287649","tags":["report"]},{"url":"https://bugzilla.suse.com/1287655","tags":["report"]},{"url":"https://bugzilla.suse.com/1287658","tags":["report"]},{"url":"https://bugzilla.suse.com/1287674","tags":["report"]},{"url":"https://bugzilla.suse.com/1287680","tags":["report"]},{"url":"https://bugzilla.suse.com/1287682","tags":["report"]},{"url":"https://bugzilla.suse.com/1287714","tags":["report"]},{"url":"https://bugzilla.suse.com/1287719","tags":["report"]},{"url":"https://bugzilla.suse.com/1287720","tags":["report"]},{"url":"https://bugzilla.suse.com/1287737","tags":["report"]},{"url":"https://bugzilla.suse.com/1287749","tags":["report"]},{"url":"https://bugzilla.suse.com/1287757","tags":["report"]},{"url":"https://bugzilla.suse.com/1287765","tags":["report"]},{"url":"https://bugzilla.suse.com/1287773","tags":["report"]},{"url":"https://bugzilla.suse.com/1287774","tags":["report"]},{"url":"https://bugzilla.suse.com/1287966","tags":["report"]},{"url":"https://bugzilla.suse.com/1287984","tags":["report"]},{"url":"https://bugzilla.suse.com/1287985","tags":["report"]},{"url":"https://bugzilla.suse.com/1287995","tags":["report"]},{"url":"https://bugzilla.suse.com/1288001","tags":["report"]},{"url":"https://bugzilla.suse.com/1288002","tags":["report"]},{"url":"https://bugzilla.suse.com/1288005","tags":["report"]},{"url":"https://bugzilla.suse.com/1288007","tags":["report"]},{"url":"https://bugzilla.suse.com/1288014","tags":["report"]},{"url":"https://bugzilla.suse.com/1288061","tags":["report"]},{"url":"https://bugzilla.suse.com/1288088","tags":["report"]},{"url":"https://bugzilla.suse.com/1288125","tags":["report"]},{"url":"https://bugzilla.suse.com/1288127","tags":["report"]},{"url":"https://bugzilla.suse.com/1288246","tags":["report"]},{"url":"https://bugzilla.suse.com/1288248","tags":["report"]},{"url":"https://bugzilla.suse.com/1288521","tags":["report"]},{"url":"https://bugzilla.suse.com/1288522","tags":["report"]},{"url":"https://bugzilla.suse.com/1288527","tags":["report"]},{"url":"https://bugzilla.suse.com/1288584","tags":["report"]},{"url":"https://bugzilla.suse.com/1288592","tags":["report"]},{"url":"https://bugzilla.suse.com/1288627","tags":["report"]},{"url":"https://bugzilla.suse.com/1288629","tags":["report"]},{"url":"https://bugzilla.suse.com/1288668","tags":["report"]},{"url":"https://bugzilla.suse.com/1288694","tags":["report"]},{"url":"https://bugzilla.suse.com/1288752","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2024-49974","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-50241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2024-53073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-71073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-100071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-100078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-100079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31708","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-31709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-43350","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-45944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46135","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46139","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-53179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-63809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64324","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64413","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64525","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64534","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68388","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68467","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68478","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72029","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72047","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72059","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72075","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72076","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72077","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72079","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72105","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72133","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72140","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72142","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72149","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72152","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72182","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72233","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72240","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72241","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72267","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72268","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72272","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72273","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72275","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72302","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72304","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72318","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72391","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72396","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72400","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72405","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72441","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72479","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72480","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72486","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72489","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74265","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74276","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74278","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74280","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74294","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74320","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74341","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74380","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74381","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74402","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74417","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74424","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74458","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74498","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74505","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74519","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74547","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74549","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74552","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74613","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74620","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74624","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74641","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74651","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74655","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74715","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74720","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74746","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74753","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80573","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80618","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80652","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80702","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80704","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80707","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80709","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80752","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80762","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80767","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80794","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80812","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80826","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80827","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80829","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80831","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80832","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80902","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80911","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80914","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80918","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80931","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80941","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80966","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80967","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80972","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80973","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80978","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80988","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80989","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80990","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89438","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89440","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89443","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89463","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89464","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89465","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89466","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89469","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89470","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89473","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89474","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89524","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89553","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89560","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89562","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89595","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89598","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89621","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89622","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89626","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89627","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89628","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89655","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89724","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89751","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89774","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89786","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89787","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89800","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89801","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89821","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89824","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89843","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89844","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89845","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89846","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89849","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89850","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89852","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89853","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89854","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89855","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89856","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89857","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89858","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89859","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89860","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89861","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89864","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89865","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89870","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89872","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89877","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89878","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89879","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89880","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89881","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89883","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89887","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89888","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89894","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89895","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89927","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89932","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89937","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89938","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89939","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89951","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89952","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89953","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89979","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89980","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89982","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89999","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90000","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90017","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90018","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90019","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90020","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90021","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90030","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90032","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90033","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90042","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90045","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90057","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90081","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90082","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90087","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90093","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90103","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90128","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90138","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90148","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90230","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90245","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90251","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90253","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90254","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90352","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90354","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90357","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90366","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90370","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90372","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90373","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90378","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90382","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90385","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90394","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90395","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90398","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90399","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90403","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92476","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92496","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92498","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92504","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92506","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92521","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-92522","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93040","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93046","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93048","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93052","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93053","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93056","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93062","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93063","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93065","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93067","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93084","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93114","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93115","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93118","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93130","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93141","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93156","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93161","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93162","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93165","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93168","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93177","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93178","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93179","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93183","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93184","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93234","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93242","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93250","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93262","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93271","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93274","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93279","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93281","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93287","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93788","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93789","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93790","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93791","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93792","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93793","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93795","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93797","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93798","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93799","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93802","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93805","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93808","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93814","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93828","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97408","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97418","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97420","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97425","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97427","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97429","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97444","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97445","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97446","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97448","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97449","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97450","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97453","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97454","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97475","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97483","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97484","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97495","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97497","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97507","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97510","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97517","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97518","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97528","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97530","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97532","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97535","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97536","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97537","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97540","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97541","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97554","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97556","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97561","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97562","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97596","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97599","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97603","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97613","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97900","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97907","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97908","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97909","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97930","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97948","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97954","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97955","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97963","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97964","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97965","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97969","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97977","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97991","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97993","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98023","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98025","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98031","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98041","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98044","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98055","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98068","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98069","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98070","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98071","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98072","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98074","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98078","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98092","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98108","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98111","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98116","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98121","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98124","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98126","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98127","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98154","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98155","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98158","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98159","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98160","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98167","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98170","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98171","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98175","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98185","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98186","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98187","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98188","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98189","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98236","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98237","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98238","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98247","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98249","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98261","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98263","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98264","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98282","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98283","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98292","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98293","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98295","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98306","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98307","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98308","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98309","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98311","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98312","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98314","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98316","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98319","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98325","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98326","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98328","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98331","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98332","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98334","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98336","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98337","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98339","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98340","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98342","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98343","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98345","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98348","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98349","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98351","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98363","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98368","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98374","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98404","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98406","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98407","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98409","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98410","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98416","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98421","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98422","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98426","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98432","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98455","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98457","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98461","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98471","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98499","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98501","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98508","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98509","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98511","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98514","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98515","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98516","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98519","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98521","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98527","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98529","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98597","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98600","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98602","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98608","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98609","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98612","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98623","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98694","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98696","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98697","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98698","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98699","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98700","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98701","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98703","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98705","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98706","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98710","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98711","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98717","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98718","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98721","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98742","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98744","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98748","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98757","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98758","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98760","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98761","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98763","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98764","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98765","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98766","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98768","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98769","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98771","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98772","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98773","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98779","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98780","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98781","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98782","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98783","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98784","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98809","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98830","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98835","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98836","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98837","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98838","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98848","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98863","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98871","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98884","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98889","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98892","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98893","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98896","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98910","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98912","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98915","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98933","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98935","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98936","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98940","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98956","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98970","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98971","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99006","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99007","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99008","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99010","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99022","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99034","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99035","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99038","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99039","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99049","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99090","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99091","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99095","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99131","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99150","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20265091-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1267882","tags":["report"]},{"url":"https://bugzilla.suse.com/1269182","tags":["report"]},{"url":"https://bugzilla.suse.com/1274257","tags":["report"]},{"url":"https://bugzilla.suse.com/1275521","tags":["report"]},{"url":"https://bugzilla.suse.com/1275955","tags":["report"]},{"url":"https://bugzilla.suse.com/1276245","tags":["report"]},{"url":"https://bugzilla.suse.com/1276275","tags":["report"]},{"url":"https://bugzilla.suse.com/1276440","tags":["report"]},{"url":"https://bugzilla.suse.com/1276443","tags":["report"]},{"url":"https://bugzilla.suse.com/1276774","tags":["report"]},{"url":"https://bugzilla.suse.com/1277079","tags":["report"]},{"url":"https://bugzilla.suse.com/1277084","tags":["report"]},{"url":"https://bugzilla.suse.com/1277130","tags":["report"]},{"url":"https://bugzilla.suse.com/1277135","tags":["report"]},{"url":"https://bugzilla.suse.com/1277142","tags":["report"]},{"url":"https://bugzilla.suse.com/1277157","tags":["report"]},{"url":"https://bugzilla.suse.com/1277168","tags":["report"]},{"url":"https://bugzilla.suse.com/1277182","tags":["report"]},{"url":"https://bugzilla.suse.com/1277200","tags":["report"]},{"url":"https://bugzilla.suse.com/1277333","tags":["report"]},{"url":"https://bugzilla.suse.com/1277451","tags":["report"]},{"url":"https://bugzilla.suse.com/1277675","tags":["report"]},{"url":"https://bugzilla.suse.com/1277732","tags":["report"]},{"url":"https://bugzilla.suse.com/1277785","tags":["report"]},{"url":"https://bugzilla.suse.com/1277819","tags":["report"]},{"url":"https://bugzilla.suse.com/1278074","tags":["report"]},{"url":"https://bugzilla.suse.com/1278081","tags":["report"]},{"url":"https://bugzilla.suse.com/1278117","tags":["report"]},{"url":"https://bugzilla.suse.com/1278172","tags":["report"]},{"url":"https://bugzilla.suse.com/1278198","tags":["report"]},{"url":"https://bugzilla.suse.com/1278213","tags":["report"]},{"url":"https://bugzilla.suse.com/1278217","tags":["report"]},{"url":"https://bugzilla.suse.com/1278350","tags":["report"]},{"url":"https://bugzilla.suse.com/1278379","tags":["report"]},{"url":"https://bugzilla.suse.com/1278405","tags":["report"]},{"url":"https://bugzilla.suse.com/1279420","tags":["report"]},{"url":"https://bugzilla.suse.com/1279460","tags":["report"]},{"url":"https://bugzilla.suse.com/1279700","tags":["report"]},{"url":"https://bugzilla.suse.com/1279823","tags":["report"]},{"url":"https://bugzilla.suse.com/1280312","tags":["report"]},{"url":"https://bugzilla.suse.com/1280330","tags":["report"]},{"url":"https://bugzilla.suse.com/1280331","tags":["report"]},{"url":"https://bugzilla.suse.com/1280332","tags":["report"]},{"url":"https://bugzilla.suse.com/1280346","tags":["report"]},{"url":"https://bugzilla.suse.com/1280988","tags":["report"]},{"url":"https://bugzilla.suse.com/1281006","tags":["report"]},{"url":"https://bugzilla.suse.com/1281080","tags":["report"]},{"url":"https://bugzilla.suse.com/1281145","tags":["report"]},{"url":"https://bugzilla.suse.com/1281256","tags":["report"]},{"url":"https://bugzilla.suse.com/1281274","tags":["report"]},{"url":"https://bugzilla.suse.com/1281342","tags":["report"]},{"url":"https://bugzilla.suse.com/1281528","tags":["report"]},{"url":"https://bugzilla.suse.com/1281532","tags":["report"]},{"url":"https://bugzilla.suse.com/1281536","tags":["report"]},{"url":"https://bugzilla.suse.com/1281552","tags":["report"]},{"url":"https://bugzilla.suse.com/1281555","tags":["report"]},{"url":"https://bugzilla.suse.com/1281588","tags":["report"]},{"url":"https://bugzilla.suse.com/1281883","tags":["report"]},{"url":"https://bugzilla.suse.com/1282165","tags":["report"]},{"url":"https://bugzilla.suse.com/1282169","tags":["report"]},{"url":"https://bugzilla.suse.com/1282735","tags":["report"]},{"url":"https://bugzilla.suse.com/1282741","tags":["report"]},{"url":"https://bugzilla.suse.com/1282886","tags":["report"]},{"url":"https://bugzilla.suse.com/1282958","tags":["report"]},{"url":"https://bugzilla.suse.com/1282971","tags":["report"]},{"url":"https://bugzilla.suse.com/1282993","tags":["report"]},{"url":"https://bugzilla.suse.com/1283038","tags":["report"]},{"url":"https://bugzilla.suse.com/1283173","tags":["report"]},{"url":"https://bugzilla.suse.com/1283228","tags":["report"]},{"url":"https://bugzilla.suse.com/1283233","tags":["report"]},{"url":"https://bugzilla.suse.com/1283504","tags":["report"]},{"url":"https://bugzilla.suse.com/1283508","tags":["report"]},{"url":"https://bugzilla.suse.com/1283513","tags":["report"]},{"url":"https://bugzilla.suse.com/1283737","tags":["report"]},{"url":"https://bugzilla.suse.com/1283780","tags":["report"]},{"url":"https://bugzilla.suse.com/1283781","tags":["report"]},{"url":"https://bugzilla.suse.com/1283785","tags":["report"]},{"url":"https://bugzilla.suse.com/1283887","tags":["report"]},{"url":"https://bugzilla.suse.com/1284303","tags":["report"]},{"url":"https://bugzilla.suse.com/1284306","tags":["report"]},{"url":"https://bugzilla.suse.com/1284561","tags":["report"]},{"url":"https://bugzilla.suse.com/1284600","tags":["report"]},{"url":"https://bugzilla.suse.com/1284632","tags":["report"]},{"url":"https://bugzilla.suse.com/1284642","tags":["report"]},{"url":"https://bugzilla.suse.com/1285594","tags":["report"]},{"url":"https://bugzilla.suse.com/1285645","tags":["report"]},{"url":"https://bugzilla.suse.com/1285647","tags":["report"]},{"url":"https://bugzilla.suse.com/1286001","tags":["report"]},{"url":"https://bugzilla.suse.com/1286133","tags":["report"]},{"url":"https://bugzilla.suse.com/1286186","tags":["report"]},{"url":"https://bugzilla.suse.com/1286208","tags":["report"]},{"url":"https://bugzilla.suse.com/1286458","tags":["report"]},{"url":"https://bugzilla.suse.com/1286665","tags":["report"]},{"url":"https://bugzilla.suse.com/1286667","tags":["report"]},{"url":"https://bugzilla.suse.com/1286670","tags":["report"]},{"url":"https://bugzilla.suse.com/1286673","tags":["report"]},{"url":"https://bugzilla.suse.com/1286674","tags":["report"]},{"url":"https://bugzilla.suse.com/1286694","tags":["report"]},{"url":"https://bugzilla.suse.com/1286708","tags":["report"]},{"url":"https://bugzilla.suse.com/1286744","tags":["report"]},{"url":"https://bugzilla.suse.com/1286826","tags":["report"]},{"url":"https://bugzilla.suse.com/1286870","tags":["report"]},{"url":"https://bugzilla.suse.com/1287647","tags":["report"]},{"url":"https://bugzilla.suse.com/1287981","tags":["report"]},{"url":"https://bugzilla.suse.com/1288126","tags":["report"]},{"url":"https://bugzilla.suse.com/1288226","tags":["report"]},{"url":"https://bugzilla.suse.com/1288406","tags":["report"]},{"url":"https://bugzilla.suse.com/1288513","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2023-7356","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-52968","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64430","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-68460","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72064","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72073","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72089","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72258","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72259","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72290","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72360","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72361","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72362","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72386","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72387","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74303","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74353","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74393","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74442","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74447","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74451","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74452","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74472","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-74514","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80542","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80749","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80815","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80862","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80891","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80903","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81011","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-81014","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89439","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89803","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89807","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89819","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89825","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89874","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89886","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89944","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89983","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90015","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90060","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90119","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90136","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90137","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90344","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93804","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97428","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97494","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97593","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97605","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97917","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-97976","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98054","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98107","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98109","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98110","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98291","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98327","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98329","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98335","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98346","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98392","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98411","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98412","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98456","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98459","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98462","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98512","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98517","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98522","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98743","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-98949","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99004","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99012","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99013","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-99094","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-20265121-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1245695","tags":["report"]},{"url":"https://bugzilla.suse.com/1248669","tags":["report"]},{"url":"https://bugzilla.suse.com/1252918","tags":["report"]},{"url":"https://bugzilla.suse.com/1255703","tags":["report"]},{"url":"https://bugzilla.suse.com/1266860","tags":["report"]},{"url":"https://bugzilla.suse.com/1273029","tags":["report"]},{"url":"https://bugzilla.suse.com/1273250","tags":["report"]},{"url":"https://bugzilla.suse.com/1273327","tags":["report"]},{"url":"https://bugzilla.suse.com/1273334","tags":["report"]},{"url":"https://bugzilla.suse.com/1273338","tags":["report"]},{"url":"https://bugzilla.suse.com/1273341","tags":["report"]},{"url":"https://bugzilla.suse.com/1274286","tags":["report"]},{"url":"https://bugzilla.suse.com/1275542","tags":["report"]},{"url":"https://bugzilla.suse.com/1277179","tags":["report"]},{"url":"https://bugzilla.suse.com/1277260","tags":["report"]},{"url":"https://bugzilla.suse.com/1277750","tags":["report"]},{"url":"https://bugzilla.suse.com/1280469","tags":["report"]},{"url":"https://bugzilla.suse.com/1280496","tags":["report"]},{"url":"https://bugzilla.suse.com/1280950","tags":["report"]},{"url":"https://bugzilla.suse.com/1281042","tags":["report"]},{"url":"https://bugzilla.suse.com/1281046","tags":["report"]},{"url":"https://bugzilla.suse.com/1281175","tags":["report"]},{"url":"https://bugzilla.suse.com/1281580","tags":["report"]},{"url":"https://bugzilla.suse.com/1281792","tags":["report"]},{"url":"https://bugzilla.suse.com/1281993","tags":["report"]},{"url":"https://bugzilla.suse.com/1282810","tags":["report"]},{"url":"https://bugzilla.suse.com/1282869","tags":["report"]},{"url":"https://bugzilla.suse.com/1282932","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38117","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-38632","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-40100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2025-68741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-46195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64257","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64379","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64513","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64539","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64546","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64549","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-64604","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72085","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72086","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-72310","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-80579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89606","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89607","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89631","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89636","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89638","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-89851","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90125","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-90434","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93269","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93785","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-93787","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2026-23059","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-23059","tags":["report"]},{"url":"https://git.kernel.org/linus/19bc5f2a6962dfaa0e32d0e0bc2271993d85d414","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-8278-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8289-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8296-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8296-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8289-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8278-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8393-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8440-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8499-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8570-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8594-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8604-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8605-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8570-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-8669-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2024-50004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-58097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-37926","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-38591","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40082","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68358","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68365","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68725","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68749","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68803","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68823","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71188","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71192","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71224","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22977","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22979","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22980","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22990","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22991","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22992","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22994","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22996","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22997","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22999","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23001","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23003","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23006","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23010","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23019","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23020","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23021","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23025","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23026","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23030","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23031","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23032","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23035","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23047","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23049","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23050","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23053","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23054","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23056","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23057","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23058","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23061","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23062","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23063","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23064","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23065","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23068","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23069","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23073","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23075","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23076","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23080","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23085","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23087","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23088","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23089","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23090","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23091","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23093","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23094","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23095","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23096","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23097","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23098","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23099","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23101","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23102","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23103","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23105","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23107","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23108","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23110","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23116","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23120","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23121","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23126","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23129","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23142","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23144","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23146","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23151","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23160","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23166","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23172","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23178","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23179","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23191","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23193","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23204","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23213","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23216","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23260","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23351","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23394","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31419","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31431","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31504","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31533","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43033","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43078","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31676","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43284","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43494","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43500","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43503","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45998","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46000","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46028","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47326","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47327","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47329","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47330","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47332","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47333","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47334","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47335","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47336","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-47337","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-36347","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2024-57795","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-40164","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-68206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-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-68291","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-68369","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-68821","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-71123","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-71144","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-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-43362","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46323","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-40005","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71274","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71286","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71292","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71294","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71305","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23220","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23229","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23234","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23235","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23237","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23272","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23392","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23428","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23450","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23455","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31411","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31418","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31436","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31448","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31478","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31607","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31637","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31649","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31657","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31659","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31668","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31669","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31682","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31685","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31687","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31693","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43011","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43037","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43038","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43071","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43117","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43123","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43124","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43128","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43132","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43133","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43134","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43136","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43139","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43140","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43141","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43145","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43148","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43149","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43150","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43153","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43156","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43159","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43163","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43167","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43168","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43169","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43170","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43173","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43175","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43180","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43182","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43183","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43184","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43186","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43189","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43190","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43194","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43196","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43199","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43200","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43202","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43203","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43205","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43206","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43207","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43209","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43211","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43214","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43215","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43218","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43221","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43222","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43223","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43226","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43227","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43230","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43231","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43232","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43233","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43236","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43238","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43239","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43241","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43248","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43256","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43257","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43258","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43262","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43264","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43268","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43269","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43271","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43273","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43275","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43278","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43279","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43283","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43287","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43288","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43291","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43295","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43296","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43297","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43300","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43302","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43304","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43312","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43313","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43314","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43315","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43318","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43319","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43320","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43341","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43378","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43383","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43384","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43406","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43493","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45847","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45848","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45849","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45851","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45852","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45856","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45857","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45859","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45860","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45861","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45862","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45864","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45865","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45866","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45867","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45868","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45869","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45870","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45871","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45872","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45873","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45875","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45877","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45878","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45879","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45880","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45881","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45882","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45883","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45884","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45885","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45886","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45890","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45891","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45893","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45895","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45902","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45904","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45905","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45910","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45912","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45913","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45914","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45915","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45916","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45917","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45919","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45921","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45923","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45928","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45935","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45936","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45938","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45941","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45946","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45947","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45948","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45954","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45957","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45960","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45962","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45964","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45965","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45968","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45969","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45970","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45973","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45974","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45976","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45978","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45982","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45983","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45984","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45988","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46043","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46119","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46135","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46195","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46243","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46244","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46246","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46247","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46249","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46250","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46251","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46253","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46254","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46255","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46259","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46261","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46265","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46266","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46267","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46270","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46289","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46328","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71187","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2025-71201","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22981","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22985","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22986","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22987","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-22993","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23002","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23004","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23007","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23008","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23009","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23012","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23013","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23014","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23015","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23017","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23022","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23023","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23024","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23036","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23042","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23044","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23045","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23046","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23051","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23052","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23055","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23066","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23067","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23070","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23072","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23077","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23079","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23081","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23092","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23104","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23106","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23109","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23114","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23115","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23118","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23122","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23130","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23138","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23143","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23147","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23152","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23154","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23157","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23158","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23161","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23162","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23165","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23171","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31444","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46290","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46317","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53277","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-23427","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31635","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31718","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43083","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43125","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43185","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43197","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43376","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43402","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-45898","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46039","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46084","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46316","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46325","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64018","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-64034","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31405","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31414","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31501","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31589","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31633","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31636","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-31705","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43198","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43379","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43465","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-43499","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46113","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46137","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46242","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-46331","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52924","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-52989","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53086","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53131","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53176","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53212","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53225","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53228","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2026-53359","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-23059","title":"scsi: qla2xxx: Sanitize payload size to prevent member overflow","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Sanitize payload size to prevent member overflow\n\nIn qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size\nreported by firmware is used to calculate the copy length into\nitem-\u003eiocb. However, the iocb member is defined as a fixed-size 64-byte\narray within struct purex_item.\n\nIf the reported frame_size exceeds 64 bytes, subsequent memcpy calls will\noverflow the iocb member boundary. While extra memory might be allocated,\nthis cross-member write is unsafe and triggers warnings under\nCONFIG_FORTIFY_SOURCE.\n\nFix this by capping total_bytes to the size of the iocb member (64 bytes)\nbefore allocation and copying. This ensures all copies remain within the\nbounds of the destination structure member.","status":"published","published":"2026-02-04T16:07:42.15Z","modified":"2026-05-11T21:59:12.428Z","updated_at":"2026-11-02T13:42:15.603999Z"}],"euvd":[{"id":"EUVD-2026-5485","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Sanitize payload size to prevent member overflow\n\nIn qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size\nreported by firmware is used to calculate the copy length into\nitem-\u003eiocb. However, the iocb member is defined as a fixed-size 64-byte\narray within struct purex_item.\n\nIf the reported frame_size exceeds 64 bytes, subsequent memcpy calls will\noverflow the iocb member boundary. While extra memory might be allocated,\nthis cross-member write is unsafe and triggers warnings under\nCONFIG_FORTIFY_SOURCE.\n\nFix this by capping total_bytes to the size of the iocb member (64 bytes)\nbefore allocation and copying. This ensures all copies remain within the\nbounds of the destination structure member.","status":"published","published":"2026-02-04T16:07:42Z","modified":"2026-05-11T21:59:12Z","updated_at":"2026-11-02T19:04:45.494343Z"}],"ghsa":[{"id":"GHSA-6mm8-fcwp-3g49","title":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Sanitize...","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Sanitize payload size to prevent member overflow\n\nIn qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size\nreported by firmware is used to calculate the copy length into\nitem-\u003eiocb. However, the iocb member is defined as a fixed-size 64-byte\narray within struct purex_item.\n\nIf the reported frame_size exceeds 64 bytes, subsequent memcpy calls will\noverflow the iocb member boundary. While extra memory might be allocated,\nthis cross-member write is unsafe and triggers warnings under\nCONFIG_FORTIFY_SOURCE.\n\nFix this by capping total_bytes to the size of the iocb member (64 bytes)\nbefore allocation and copying. This ensures all copies remain within the\nbounds of the destination structure member.","status":"published","published":"2026-02-04T18:30:43Z","modified":"2026-02-04T18:30:53Z","updated_at":"2026-11-02T15:06:02.555847Z"}],"nvd":[{"id":"CVE-2026-23059","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Sanitize payload size to prevent member overflow\n\nIn qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size\nreported by firmware is used to calculate the copy length into\nitem-\u003eiocb. However, the iocb member is defined as a fixed-size 64-byte\narray within struct purex_item.\n\nIf the reported frame_size exceeds 64 bytes, subsequent memcpy calls will\noverflow the iocb member boundary. While extra memory might be allocated,\nthis cross-member write is unsafe and triggers warnings under\nCONFIG_FORTIFY_SOURCE.\n\nFix this by capping total_bytes to the size of the iocb member (64 bytes)\nbefore allocation and copying. This ensures all copies remain within the\nbounds of the destination structure member.","status":"published","published":"2026-02-04T17:16:16.583Z","modified":"2026-06-17T10:20:47.323Z","updated_at":"2026-11-02T14:12:05.149641Z"}],"osv":[{"id":"OESA-2026-1566","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp: Deal with race between UDP socket address change and rehash\n\nIf a UDP socket changes its local address while it\u0026apos;s receiving\ndatagrams, as a result of connect(), there is a period during which\na lookup operation might fail to find it, after the address is changed\nbut before the secondary hash (port and address) and the four-tuple\nhash (local and remote ports and addresses) are updated.\n\nSecondary hash chains were introduced by commit 30fff9231fad (\u0026quot;udp:\nbind() optimisation\u0026quot;) and, as a result, a rehash operation became\nneeded to make a bound socket reachable again after a connect().\n\nThis operation was introduced by commit 719f835853a9 (\u0026quot;udp: add\nrehash on connect()\u0026quot;) which isn\u0026apos;t however a complete fix: the\nsocket will be found once the rehashing completes, but not while\nit\u0026apos;s pending.\n\nThis is noticeable with a socat(1) server in UDP4-LISTEN mode, and a\nclient sending datagrams to it. After the server receives the first\ndatagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to\nthe address of the sender, in order to set up a directed flow.\n\nNow, if the client, running on a different CPU thread, happens to\nsend a (subsequent) datagram while the server\u0026apos;s socket changes its\naddress, but is not rehashed yet, this will result in a failed\nlookup and a port unreachable error delivered to the client, as\napparent from the following reproducer:\n\n  LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))\n  dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in\n\n  while :; do\n  \ttaskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.1 || sleep 1\n  \ttaskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null\n  \twait\n  done\n\nwhere the client will eventually get ECONNREFUSED on a write()\n(typically the second or third one of a given iteration):\n\n  2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused\n\nThis issue was first observed as a seldom failure in Podman\u0026apos;s tests\nchecking UDP functionality while using pasta(1) to connect the\ncontainer\u0026apos;s network namespace, which leads us to a reproducer with\nthe lookup error resulting in an ICMP packet on a tap device:\n\n  LOCAL_ADDR=\u0026quot;$(ip -j -4 addr show|jq -rM \u0026apos;.[] | .addr_info[0] | select(.scope == \u0026quot;global\u0026quot;).local\u0026apos;)\u0026quot;\n\n  while :; do\n  \t./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.2 || sleep 1\n  \tsocat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null\n  \twait\n  \tcmp tmp.in tmp.out\n  done\n\nOnce this fails:\n\n  tmp.in tmp.out differ: char 8193, line 29\n\nwe can finally have a look at what\u0026apos;s going on:\n\n  $ tshark -r pasta.pcap\n      1   0.000000           :: ? ff02::16     ICMPv6 110 Multicast Listener Report Message v2\n      2   0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      3   0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      4   0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      5   0.168827 c6:47:05:8d:dc:04 ? Broadcast    ARP 42 Who has 88.198.0.161? Tell 88.198.0.164\n      6   0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55\n      7   0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      8   0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable)\n      9   0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     10   0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     11   0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096\n     12   0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0\n\nOn the third datagram received, the network namespace of the container\ninitiates an ARP lookup to deliver the ICMP message.\n\nIn another variant of this reproducer, starting the client with:\n\n  strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru\n---truncated---(CVE-2024-57974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()\n\nIf track_pfn_copy() fails, we already added the dst VMA to the maple\ntree. As fork() fails, we\u0026apos;ll cleanup the maple tree, and stumble over\nthe dst VMA for which we neither performed any reservation nor copied\nany page tables.\n\nConsequently untrack_pfn() will see VM_PAT and try obtaining the\nPAT information from the page table -- which fails because the page\ntable was not copied.\n\nThe easiest fix would be to simply clear the VM_PAT flag of the dst VMA\nif track_pfn_copy() fails. However, the whole thing is about \u0026quot;simply\u0026quot;\nclearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy()\nand performed a reservation, but copying the page tables fails, we\u0026apos;ll\nsimply clear the VM_PAT flag, not properly undoing the reservation ...\nwhich is also wrong.\n\nSo let\u0026apos;s fix it properly: set the VM_PAT flag only if the reservation\nsucceeded (leaving it clear initially), and undo the reservation if\nanything goes wrong while copying the page tables: clearing the VM_PAT\nflag after undoing the reservation.\n\nNote that any copied page table entries will get zapped when the VMA will\nget removed later, after copy_page_range() succeeded; as VM_PAT is not set\nthen, we won\u0026apos;t try cleaning VM_PAT up once more and untrack_pfn() will be\nhappy. Note that leaving these page tables in place without a reservation\nis not a problem, as we are aborting fork(); this process will never run.\n\nA reproducer can trigger this usually at the first try:\n\n  https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c\n\n  WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110\n  Modules linked in: ...\n  CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\n  RIP: 0010:get_pat_info+0xf6/0x110\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ...\n   untrack_pfn+0x52/0x110\n   unmap_single_vma+0xa6/0xe0\n   unmap_vmas+0x105/0x1f0\n   exit_mmap+0xf6/0x460\n   __mmput+0x4b/0x120\n   copy_process+0x1bf6/0x2aa0\n   kernel_clone+0xab/0x440\n   __do_sys_clone+0x66/0x90\n   do_syscall_64+0x95/0x180\n\nLikely this case was missed in:\n\n  d155df53f310 (\u0026quot;x86/mm/pat: clear VM_PAT if copy_p4d_range failed\u0026quot;)\n\n... and instead of undoing the reservation we simply cleared the VM_PAT flag.\n\nKeep the documentation of these functions in include/linux/pgtable.h,\none place is more than sufficient -- we should clean that up for the other\nfunctions like track_pfn_remap/untrack_pfn separately.(CVE-2025-22090)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: make fallback action and fallback decision atomic\n\nSyzkaller reported the following splat:\n\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary)\n  Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline]\n  RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00\n  RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246\n  RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45\n  RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001\n  RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n  R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000\n  FS:  00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432\n   tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975\n   tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166\n   tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925\n   tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363\n   ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205\n   ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254\n   dst_input include/net/dst.h:469 [inline]\n   ip_rcv_finish net/ipv4/ip_input.c:447 [inline]\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567\n   __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975\n   __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088\n   process_backlog+0x301/0x1360 net/core/dev.c:6440\n   __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453\n   napi_poll net/core/dev.c:7517 [inline]\n   net_rx_action+0xb44/0x1010 net/core/dev.c:7644\n   handle_softirqs+0x1d0/0x770 kernel/softirq.c:579\n   do_softirq+0x3f/0x90 kernel/softirq.c:480\n   \u0026lt;/IRQ\u0026gt;\n   \u0026lt;TASK\u0026gt;\n   __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407\n   local_bh_enable include/linux/bottom_half.h:33 [inline]\n   inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524\n   mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985\n   mptcp_check_listen_stop net/mptcp/mib.h:118 [inline]\n   __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000\n   mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066\n   inet_release+0xed/0x200 net/ipv4/af_inet.c:435\n   inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487\n   __sock_release+0xb3/0x270 net/socket.c:649\n   sock_close+0x1c/0x30 net/socket.c:1439\n   __fput+0x402/0xb70 fs/file_table.c:465\n   task_work_run+0x150/0x240 kernel/task_work.c:227\n   resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n   exit_to_user_mode_loop+0xd4\n---truncated---(CVE-2025-38491)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic\n\nThe decompress_io_ctx may be released asynchronously after\nI/O completion. If this file is deleted immediately after read,\nand the kworker of processing post_read_wq has not been executed yet\ndue to high workloads, It is possible that the inode(f2fs_inode_info)\nis evicted and freed before it is used f2fs_free_dic.\n\n    The UAF case as below:\n    Thread A                                      Thread B\n    - f2fs_decompress_end_io\n     - f2fs_put_dic\n      - queue_work\n        add free_dic work to post_read_wq\n                                                   - do_unlink\n                                                    - iput\n                                                     - evict\n                                                      - call_rcu\n    This file is deleted after read.\n\n    Thread C                                 kworker to process post_read_wq\n    - rcu_do_batch\n     - f2fs_free_inode\n      - kmem_cache_free\n     inode is freed by rcu\n                                             - process_scheduled_works\n                                              - f2fs_late_free_dic\n                                               - f2fs_free_dic\n                                                - f2fs_release_decomp_mem\n                                      read (dic-\u0026gt;inode)-\u0026gt;i_compress_algorithm\n\nThis patch store compress_algorithm and sbi in dic to avoid inode UAF.\n\nIn addition, the previous solution is deprecated in [1] may cause system hang.\n[1] https://lore.kernel.org/all/(CVE-2025-38627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n[ceph] parse_longname(): strrchr() expects NUL-terminated string\n\n... and parse_longname() is not guaranteed that.  That\u0026apos;s the reason\nwhy it uses kmemdup_nul() to build the argument for kstrtou64();\nthe problem is, kstrtou64() is not the only thing that need it.\n\nJust get a NUL-terminated copy of the entire thing and be done\nwith that...(CVE-2025-38660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: remove refcounting in expectation dumpers\n\nSame pattern as previous patch: do not keep the expectation object\nalive via refcount, only store a cookie value and then use that\nas the skip hint for dump resumption.\n\nAFAICS this has the same issue as the one resolved in the conntrack\ndumper, when we do\n  if (!refcount_inc_not_zero(\u0026amp;exp-\u0026gt;use))\n\nto increment the refcount, there is a chance that exp == last, which\ncauses a double-increment of the refcount and subsequent memory leak.(CVE-2025-39764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: avoid accessing metadata when pointer is invalid in object_err()\n\nobject_err() reports details of an object for further debugging, such as\nthe freelist pointer, redzone, etc. However, if the pointer is invalid,\nattempting to access object metadata can lead to a crash since it does\nnot point to a valid object.\n\nOne known path to the crash is when alloc_consistency_checks()\ndetermines the pointer to the allocated object is invalid because of a\nfreelist corruption, and calls object_err() to report it. The debug code\nshould report and handle the corruption gracefully and not crash in the\nprocess.\n\nIn case the pointer is NULL or check_valid_pointer() returns false for\nthe pointer, only print the pointer value and skip accessing metadata.(CVE-2025-39902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix Rx page leak on multi-buffer frames\n\nThe ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each\nbuffer in the current frame. This function was introduced as part of\nhandling multi-buffer XDP support in the ice driver.\n\nIt works by iterating over the buffers from first_desc up to 1 plus the\ntotal number of fragments in the frame, cached from before the XDP program\nwas executed.\n\nIf the hardware posts a descriptor with a size of 0, the logic used in\nice_put_rx_mbuf() breaks. Such descriptors get skipped and don\u0026apos;t get added\nas fragments in ice_add_xdp_frag. Since the buffer isn\u0026apos;t counted as a\nfragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don\u0026apos;t\ncall ice_put_rx_buf().\n\nBecause we don\u0026apos;t call ice_put_rx_buf(), we don\u0026apos;t attempt to re-use the\npage or free it. This leaves a stale page in the ring, as we don\u0026apos;t\nincrement next_to_alloc.\n\nThe ice_reuse_rx_page() assumes that the next_to_alloc has been incremented\nproperly, and that it always points to a buffer with a NULL page. Since\nthis function doesn\u0026apos;t check, it will happily recycle a page over the top\nof the next_to_alloc buffer, losing track of the old page.\n\nNote that this leak only occurs for multi-buffer frames. The\nice_put_rx_mbuf() function always handles at least one buffer, so a\nsingle-buffer frame will always get handled correctly. It is not clear\nprecisely why the hardware hands us descriptors with a size of 0 sometimes,\nbut it happens somewhat regularly with \u0026quot;jumbo frames\u0026quot; used by 9K MTU.\n\nTo fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on\nall buffers between first_desc and next_to_clean. Borrow the logic of a\nsimilar function in i40e used for this same purpose. Use the same logic\nalso in ice_get_pgcnts().\n\nInstead of iterating over just the number of fragments, use a loop which\niterates until the current index reaches to the next_to_clean element just\npast the current frame. Unlike i40e, the ice_put_rx_mbuf() function does\ncall ice_put_rx_buf() on the last buffer of the frame indicating the end of\npacket.\n\nFor non-linear (multi-buffer) frames, we need to take care when adjusting\nthe pagecnt_bias. An XDP program might release fragments from the tail of\nthe frame, in which case that fragment page is already released. Only\nupdate the pagecnt_bias for the first descriptor and fragments still\nremaining post-XDP program. Take care to only access the shared info for\nfragmented buffers, as this avoids a significant cache miss.\n\nThe xdp_xmit value only needs to be updated if an XDP program is run, and\nonly once per packet. Drop the xdp_xmit pointer argument from\nice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function\ndirectly. This avoids needing to pass the argument and avoids an extra\nbit-wise OR for each buffer in the frame.\n\nMove the increment of the ntc local variable to ensure its updated *before*\nall calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic\nrequires the index of the element just after the current frame.\n\nNow that we use an index pointer in the ring to identify the packet, we no\nlonger need to track or cache the number of fragments in the rx_ring.(CVE-2025-39948)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: Set fb_display[i]-\u0026gt;mode to NULL when the mode is released\n\nRecently, we discovered the following issue through syzkaller:\n\nBUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0\nRead of size 4 at addr ff11000001b3c69c by task syz.xxx\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xab/0xe0\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb9/0x280\n kasan_report+0xb8/0xf0\n fb_mode_is_equal+0x285/0x2f0\n fbcon_mode_deleted+0x129/0x180\n fb_set_var+0xe7f/0x11d0\n do_fb_ioctl+0x6a0/0x750\n fb_ioctl+0xe0/0x140\n __x64_sys_ioctl+0x193/0x210\n do_syscall_64+0x5f/0x9c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nBased on experimentation and analysis, during framebuffer unregistration,\nonly the memory of fb_info-\u0026gt;modelist is freed, without setting the\ncorresponding fb_display[i]-\u0026gt;mode to NULL for the freed modes. This leads\nto UAF issues during subsequent accesses. Here\u0026apos;s an example of reproduction\nsteps:\n1. With /dev/fb0 already registered in the system, load a kernel module\n   to register a new device /dev/fb1;\n2. Set fb1\u0026apos;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);\n3. Switch console from fb to VGA (to allow normal rmmod of the ko);\n4. Unload the kernel module, at this point fb1\u0026apos;s modelist is freed, leaving\n   a wild pointer in fb_display[];\n5. Trigger the bug via system calls through fb0 attempting to delete a mode\n   from fb0.\n\nAdd a check in do_unregister_framebuffer(): if the mode to be freed exists\nin fb_display[], set the corresponding mode pointer to NULL.(CVE-2025-40323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb\n\nThe Mesa issue referenced below pointed out a possible deadlock:\n\n[ 1231.611031]  Possible interrupt unsafe locking scenario:\n\n[ 1231.611033]        CPU0                    CPU1\n[ 1231.611034]        ----                    ----\n[ 1231.611035]   lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611038]                                local_irq_disable();\n[ 1231.611039]                                lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611041]                                lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611044]   \u0026lt;Interrupt\u0026gt;\n[ 1231.611045]     lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611047]\n                *** DEADLOCK ***\n\nIn this example, CPU0 would be any function accessing job-\u0026gt;dependencies\nthrough the xa_* functions that don\u0026apos;t disable interrupts (eg:\ndrm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()).\n\nCPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling\ncallback so in an interrupt context. It will deadlock when trying to\ngrab the xa_lock which is already held by CPU0.\n\nReplacing all xa_* usage by their xa_*_irq counterparts would fix\nthis issue, but Christian pointed out another issue: dma_fence_signal\ntakes fence.lock and so does dma_fence_add_callback.\n\n  dma_fence_signal() // locks f1.lock\n  -\u0026gt; drm_sched_entity_kill_jobs_cb()\n  -\u0026gt; foreach dependencies\n     -\u0026gt; dma_fence_add_callback() // locks f2.lock\n\nThis will deadlock if f1 and f2 share the same spinlock.\n\nTo fix both issues, the code iterating on dependencies and re-arming them\nis moved out to drm_sched_entity_kill_jobs_work().\n\n[phasta: commit message nits](CVE-2025-40329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n    Internal error: Oops: 000000009600004f [#1] SMP\n    CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n    Hardware name: LS1028A RDB Board (DT)\n    pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n    pc : xfrm_input+0xde8/0x1318\n    lr : xfrm_input+0x61c/0x1318\n    sp : ffff800080003b20\n    Call trace:\n     xfrm_input+0xde8/0x1318\n     xfrm6_rcv+0x38/0x44\n     xfrm6_esp_rcv+0x48/0xa8\n     ip6_protocol_deliver_rcu+0x94/0x4b0\n     ip6_input_finish+0x44/0x70\n     ip6_input+0x44/0xc0\n     ipv6_rcv+0x6c/0x114\n     __netif_receive_skb_one_core+0x5c/0x8c\n     __netif_receive_skb+0x18/0x60\n     process_backlog+0x78/0x17c\n     __napi_poll+0x38/0x180\n     net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imon: make send_packet() more robust\n\nsyzbot is reporting that imon has three problems which result in\nhung tasks due to forever holding device lock [1].\n\nFirst problem is that when usb_rx_callback_intf0() once got -EPROTO error\nafter ictx-\u0026gt;dev_present_intf0 became true, usb_rx_callback_intf0()\nresubmits urb after printk(), and resubmitted urb causes\nusb_rx_callback_intf0() to again get -EPROTO error. This results in\nprintk() flooding (RCU stalls).\n\nAlan Stern commented [2] that\n\n  In theory it\u0026apos;s okay to resubmit _if_ the driver has a robust\n  error-recovery scheme (such as giving up after some fixed limit on the\n  number of errors or after some fixed time has elapsed, perhaps with a\n  time delay to prevent a flood of errors).  Most drivers don\u0026apos;t bother to\n  do this; they simply give up right away.  This makes them more\n  vulnerable to short-term noise interference during USB transfers, but in\n  reality such interference is quite rare.  There\u0026apos;s nothing really wrong\n  with giving up right away.\n\nbut imon has a poor error-recovery scheme which just retries forever;\nthis behavior should be fixed.\n\nSince I\u0026apos;m not sure whether it is safe for imon users to give up upon any\nerror code, this patch takes care of only union of error codes chosen from\nmodules in drivers/media/rc/ directory which handle -EPROTO error (i.e.\nir_toy, mceusb and igorplugusb).\n\nSecond problem is that when usb_rx_callback_intf0() once got -EPROTO error\nbefore ictx-\u0026gt;dev_present_intf0 becomes true, usb_rx_callback_intf0() always\nresubmits urb due to commit 8791d63af0cf (\u0026quot;[media] imon: don\u0026apos;t wedge\nhardware after early callbacks\u0026quot;). Move the ictx-\u0026gt;dev_present_intf0 test\nintroduced by commit 6f6b90c9231a (\u0026quot;[media] imon: don\u0026apos;t parse scancodes\nuntil intf configured\u0026quot;) to immediately before imon_incoming_packet(), or\nthe first problem explained above happens without printk() flooding (i.e.\nhung task).\n\nThird problem is that when usb_rx_callback_intf0() is not called for some\nreason (e.g. flaky hardware; the reproducer for this problem sometimes\nprevents usb_rx_callback_intf0() from being called),\nwait_for_completion_interruptible() in send_packet() never returns (i.e.\nhung task). As a workaround for such situation, change send_packet() to\nwait for completion with timeout of 10 seconds.(CVE-2025-68194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: arm: scmi: Fix genpd leak on provider registration failure\n\nIf of_genpd_add_provider_onecell() fails during probe, the previously\ncreated generic power domains are not removed, leading to a memory leak\nand potential kernel crash later in genpd_debug_add().\n\nAdd proper error handling to unwind the initialized domains before\nreturning from probe to ensure all resources are correctly released on\nfailure.\n\nExample crash trace observed without this fix:\n\n  | Unable to handle kernel paging request at virtual address fffffffffffffc70\n  | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT\n  | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform\n  | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  | pc : genpd_debug_add+0x2c/0x160\n  | lr : genpd_debug_init+0x74/0x98\n  | Call trace:\n  |  genpd_debug_add+0x2c/0x160 (P)\n  |  genpd_debug_init+0x74/0x98\n  |  do_one_initcall+0xd0/0x2d8\n  |  do_initcall_level+0xa0/0x140\n  |  do_initcalls+0x60/0xa8\n  |  do_basic_setup+0x28/0x40\n  |  kernel_init_freeable+0xe8/0x170\n  |  kernel_init+0x2c/0x140\n  |  ret_from_fork+0x10/0x20(CVE-2025-68204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0026apos;s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs.(CVE-2025-68209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksm: use range-walk function to jump over holes in scan_get_next_rmap_item\n\nCurrently, scan_get_next_rmap_item() walks every page address in a VMA to\nlocate mergeable pages.  This becomes highly inefficient when scanning\nlarge virtual memory areas that contain mostly unmapped regions, causing\nksmd to use large amount of cpu without deduplicating much pages.\n\nThis patch replaces the per-address lookup with a range walk using\nwalk_page_range().  The range walker allows KSM to skip over entire\nunmapped holes in a VMA, avoiding unnecessary lookups.  This problem was\npreviously discussed in [1].\n\nConsider the following test program which creates a 32 TiB mapping in the\nvirtual address space but only populates a single page:\n\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\n\n/* 32 TiB */\nconst size_t size = 32ul * 1024 * 1024 * 1024 * 1024;\n\nint main() {\n        char *area = mmap(NULL, size, PROT_READ | PROT_WRITE,\n                          MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);\n\n        if (area == MAP_FAILED) {\n                perror(\u0026quot;mmap() failed\\n\u0026quot;);\n                return -1;\n        }\n\n        /* Populate a single page such that we get an anon_vma. */\n        *area = 0;\n\n        /* Enable KSM. */\n        madvise(area, size, MADV_MERGEABLE);\n        pause();\n        return 0;\n}\n\n$ ./ksm-sparse  \u0026amp;\n$ echo 1 \u0026gt; /sys/kernel/mm/ksm/run \n\nWithout this patch ksmd uses 100% of the cpu for a long time (more then 1\nhour in my test machine) scanning all the 32 TiB virtual address space\nthat contain only one mapped page.  This makes ksmd essentially deadlocked\nnot able to deduplicate anything of value.  With this patch ksmd walks\nonly the one mapped page and skips the rest of the 32 TiB virtual address\nspace, making the scan fast using little cpu.(CVE-2025-68211)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempool: fix poisoning order\u0026gt;0 pages with HIGHMEM\n\nThe kernel test has reported:\n\n  BUG: unable to handle page fault for address: fffba000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  *pde = 03171067 *pte = 00000000\n  Oops: Oops: 0002 [#1]\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G                T   6.18.0-rc2-00031-gec7f31b2a2d3 #1 NONE  a1d066dfe789f54bc7645c7989957d2bdee593ca\n  Tainted: [T]=RANDSTRUCT\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  EIP: memset (arch/x86/include/asm/string_32.h:168 arch/x86/lib/memcpy_32.c:17)\n  Code: a5 8b 4d f4 83 e1 03 74 02 f3 a4 83 c4 04 5e 5f 5d 2e e9 73 41 01 00 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c6 89 d0 89 f7 \u0026lt;f3\u0026gt; aa 89 f0 5e 5f 5d 2e e9 53 41 01 00 cc cc cc 55 89 e5 53 57 56\n  EAX: 0000006b EBX: 00000015 ECX: 001fefff EDX: 0000006b\n  ESI: fffb9000 EDI: fffba000 EBP: c611fbf0 ESP: c611fbe8\n  DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010287\n  CR0: 80050033 CR2: fffba000 CR3: 0316e000 CR4: 00040690\n  Call Trace:\n   poison_element (mm/mempool.c:83 mm/mempool.c:102)\n   mempool_init_node (mm/mempool.c:142 mm/mempool.c:226)\n   mempool_init_noprof (mm/mempool.c:250 (discriminator 1))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   bio_integrity_initfn (block/bio-integrity.c:483 (discriminator 8))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   do_one_initcall (init/main.c:1283)\n\nChristoph found out this is due to the poisoning code not dealing\nproperly with CONFIG_HIGHMEM because only the first page is mapped but\nthen the whole potentially high-order page is accessed.\n\nWe could give up on HIGHMEM here, but it\u0026apos;s straightforward to fix this\nwith a loop that\u0026apos;s mapping, poisoning or checking and unmapping\nindividual pages.(CVE-2025-68231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtdchar: fix integer overflow in read/write ioctls\n\nThe \u0026quot;req.start\u0026quot; and \u0026quot;req.len\u0026quot; variables are u64 values that come from the\nuser at the start of the function.  We mask away the high 32 bits of\n\u0026quot;req.len\u0026quot; so that\u0026apos;s capped at U32_MAX but the \u0026quot;req.start\u0026quot; variable can go\nup to U64_MAX which means that the addition can still integer overflow.\n\nUse check_add_overflow() to fix this bug.(CVE-2025-68237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n  BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n  Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u0026gt;work\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\u0026quot;usb: gadget: core: flush gadget workqueue after\ndevice removal\u0026quot;) attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget\u0026apos;s memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a \u0026apos;teardown\u0026apos;\nflag and a \u0026apos;state_lock\u0026apos; spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.(CVE-2025-68282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: fix NULL pointer deference when splitting folio\n\nCommit c010d47f107f (\u0026quot;mm: thp: split huge page to any lower order pages\u0026quot;)\nintroduced an early check on the folio\u0026apos;s order via mapping-\u0026gt;flags before\nproceeding with the split work.\n\nThis check introduced a bug: for shmem folios in the swap cache and\ntruncated folios, the mapping pointer can be NULL.  Accessing\nmapping-\u0026gt;flags in this state leads directly to a NULL pointer dereference.\n\nThis commit fixes the issue by moving the check for mapping != NULL before\nany attempt to access mapping-\u0026gt;flags.(CVE-2025-68293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU/AMD: Add RDSEED fix for Zen5\n\nThere\u0026apos;s an issue with RDSEED\u0026apos;s 16-bit and 32-bit register output\nvariants on Zen5 which return a random value of 0 \u0026quot;at a rate inconsistent\nwith randomness while incorrectly signaling success (CF=1)\u0026quot;. Search the\nweb for AMD-SB-7055 for more detail.\n\nAdd a fix glue which checks microcode revisions.\n\n  [ bp: Add microcode revisions checking, rewrite. ](CVE-2025-68313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninet: frags: flush pending skbs in fqdir_pre_exit()\n\nWe have been seeing occasional deadlocks on pernet_ops_rwsem since\nSeptember in NIPA. The stuck task was usually modprobe (often loading\na driver like ipvlan), trying to take the lock as a Writer.\nlockdep does not track readers for rwsems so the read wasn\u0026apos;t obvious\nfrom the reports.\n\nOn closer inspection the Reader holding the lock was conntrack looping\nforever in nf_conntrack_cleanup_net_list(). Based on past experience\nwith occasional NIPA crashes I looked thru the tests which run before\nthe crash and noticed that the crash follows ip_defrag.sh. An immediate\nred flag. Scouring thru (de)fragmentation queues reveals skbs sitting\naround, holding conntrack references.\n\nThe problem is that since conntrack depends on nf_defrag_ipv6,\nnf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its\nnetns exit hooks run _after_ conntrack\u0026apos;s netns exit hook.\n\nFlush all fragment queue SKBs during fqdir_pre_exit() to release\nconntrack references before conntrack cleanup runs. Also flush\nthe queues in timer expiry handlers when they discover fqdir-\u0026gt;dead\nis set, in case packet sneaks in while we\u0026apos;re running the pre_exit\nflush.\n\nThe commit under Fixes is not exactly the culprit, but I think\npreviously the timer firing would eventually unblock the spinning\nconntrack.(CVE-2025-68768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix middle attribute validation in push_nsh() action\n\nThe push_nsh() action structure looks like this:\n\n OVS_ACTION_ATTR_PUSH_NSH(OVS_KEY_ATTR_NSH(OVS_NSH_KEY_ATTR_BASE,...))\n\nThe outermost OVS_ACTION_ATTR_PUSH_NSH attribute is OK\u0026apos;ed by the\nnla_for_each_nested() inside __ovs_nla_copy_actions().  The innermost\nOVS_NSH_KEY_ATTR_BASE/MD1/MD2 are OK\u0026apos;ed by the nla_for_each_nested()\ninside nsh_key_put_from_nlattr().  But nothing checks if the attribute\nin the middle is OK.  We don\u0026apos;t even check that this attribute is the\nOVS_KEY_ATTR_NSH.  We just do a double unwrap with a pair of nla_data()\ncalls - first time directly while calling validate_push_nsh() and the\nsecond time as part of the nla_for_each_nested() macro, which isn\u0026apos;t\nsafe, potentially causing invalid memory access if the size of this\nattribute is incorrect.  The failure may not be noticed during\nvalidation due to larger netlink buffer, but cause trouble later during\naction execution where the buffer is allocated exactly to the size:\n\n BUG: KASAN: slab-out-of-bounds in nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n Read of size 184 at addr ffff88816459a634 by task a.out/22624\n\n CPU: 8 UID: 0 PID: 22624 6.18.0-rc7+ #115 PREEMPT(voluntary)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x51/0x70\n  print_address_description.constprop.0+0x2c/0x390\n  kasan_report+0xdd/0x110\n  kasan_check_range+0x35/0x1b0\n  __asan_memcpy+0x20/0x60\n  nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n  push_nsh+0x82/0x120 [openvswitch]\n  do_execute_actions+0x1405/0x2840 [openvswitch]\n  ovs_execute_actions+0xd5/0x3b0 [openvswitch]\n  ovs_packet_cmd_execute+0x949/0xdb0 [openvswitch]\n  genl_family_rcv_msg_doit+0x1d6/0x2b0\n  genl_family_rcv_msg+0x336/0x580\n  genl_rcv_msg+0x9f/0x130\n  netlink_rcv_skb+0x11f/0x370\n  genl_rcv+0x24/0x40\n  netlink_unicast+0x73e/0xaa0\n  netlink_sendmsg+0x744/0xbf0\n  __sys_sendto+0x3d6/0x450\n  do_syscall_64+0x79/0x2c0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  \u0026lt;/TASK\u0026gt;\n\nLet\u0026apos;s add some checks that the attribute is properly sized and it\u0026apos;s\nthe only one attribute inside the action.  Technically, there is no\nreal reason for OVS_KEY_ATTR_NSH to be there, as we know that we\u0026apos;re\npushing an NSH header already, it just creates extra nesting, but\nthat\u0026apos;s how uAPI works today.  So, keeping as it is.(CVE-2025-68785)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: alps - fix use-after-free bugs caused by dev3_register_work\n\nThe dev3_register_work delayed work item is initialized within\nalps_reconnect() and scheduled upon receipt of the first bare\nPS/2 packet from an external PS/2 device connected to the ALPS\ntouchpad. During device detachment, the original implementation\ncalls flush_workqueue() in psmouse_disconnect() to ensure\ncompletion of dev3_register_work. However, the flush_workqueue()\nin psmouse_disconnect() only blocks and waits for work items that\nwere already queued to the workqueue prior to its invocation. Any\nwork items submitted after flush_workqueue() is called are not\nincluded in the set of tasks that the flush operation awaits.\nThis means that after flush_workqueue() has finished executing,\nthe dev3_register_work could still be scheduled. Although the\npsmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(),\nthe scheduling of dev3_register_work remains unaffected.\n\nThe race condition can occur as follows:\n\nCPU 0 (cleanup path)     | CPU 1 (delayed work)\npsmouse_disconnect()     |\n  psmouse_set_state()    |\n  flush_workqueue()      | alps_report_bare_ps2_packet()\n  alps_disconnect()      |   psmouse_queue_work()\n    kfree(priv); // FREE | alps_register_bare_ps2_mouse()\n                         |   priv = container_of(work...); // USE\n                         |   priv-\u0026gt;dev3 // USE\n\nAdd disable_delayed_work_sync() in alps_disconnect() to ensure\nthat dev3_register_work is properly canceled and prevented from\nexecuting after the alps_data structure has been deallocated.\n\nThis bug is identified by static analysis.(CVE-2025-68822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential deadlock\n\nAs Jiaming Zhang and syzbot reported, there is potential deadlock in\nf2fs as below:\n\nChain exists of:\n  \u0026amp;sbi-\u0026gt;cp_rwsem --\u0026gt; fs_reclaim --\u0026gt; sb_internal#2\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  rlock(sb_internal#2);\n                               lock(fs_reclaim);\n                               lock(sb_internal#2);\n  rlock(\u0026amp;sbi-\u0026gt;cp_rwsem);\n\n *** DEADLOCK ***\n\n3 locks held by kswapd0/73:\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197\n #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890\n\nstack backtrace:\nCPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043\n check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175\n check_prev_add kernel/locking/lockdep.c:3165 [inline]\n check_prevs_add kernel/locking/lockdep.c:3284 [inline]\n validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908\n __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237\n lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868\n down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537\n f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]\n f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]\n f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791\n f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867\n f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925\n f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897\n evict+0x504/0x9c0 fs/inode.c:810\n f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853\n evict+0x504/0x9c0 fs/inode.c:810\n dispose_list fs/inode.c:852 [inline]\n prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000\n super_cache_scan+0x39b/0x4b0 fs/super.c:224\n do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437\n shrink_slab_memcg mm/shrinker.c:550 [inline]\n shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628\n shrink_one+0x28a/0x7c0 mm/vmscan.c:4955\n shrink_many mm/vmscan.c:5016 [inline]\n lru_gen_shrink_node mm/vmscan.c:5094 [inline]\n shrink_node+0x315d/0x3780 mm/vmscan.c:6081\n kswapd_shrink_node mm/vmscan.c:6941 [inline]\n balance_pgdat mm/vmscan.c:7124 [inline]\n kswapd+0x147c/0x2800 mm/vmscan.c:7389\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is deadlock among four locks as below:\n\nkswapd\n- fs_reclaim\t\t\t\t--- Lock A\n - shrink_one\n  - evict\n   - f2fs_evict_inode\n    - sb_start_intwrite\t\t\t--- Lock B\n\n- iput\n - evict\n  - f2fs_evict_inode\n   - sb_start_intwrite\t\t\t--- Lock B\n   - f2fs_truncate\n    - f2fs_truncate_blocks\n     - f2fs_do_truncate_blocks\n      - f2fs_lock_op\t\t\t--- Lock C\n\nioctl\n- f2fs_ioc_commit_atomic_write\n - f2fs_lock_op\t\t\t\t--- Lock C\n  - __f2fs_commit_atomic_write\n   - __replace_atomic_write_block\n    - f2fs_get_dnode_of_data\n     - __get_node_folio\n      - f2fs_check_nid_range\n       - f2fs_handle_error\n        - f2fs_record_errors\n         - f2fs_down_write\t\t--- Lock D\n\nopen\n- do_open\n - do_truncate\n  - security_inode_need_killpriv\n   - f2fs_getxattr\n    - lookup_all_xattrs\n     - f2fs_handle_error\n      - f2fs_record_errors\n       - f2fs_down_write\t\t--- Lock D\n        - f2fs_commit_super\n         - read_mapping_folio\n          - filemap_alloc_folio_noprof\n           - prepare_alloc_pages\n            - fs_reclaim_acquire\t--- Lock A\n\nIn order to a\n---truncated---(CVE-2025-71065)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: Avoid NULL pointer deref for evicted BOs\n\nIt is possible for a BO to exist that is not currently associated with a\nresource, e.g. because it has been evicted.\n\nWhen devcoredump tries to read the contents of all BOs for dumping, we need\nto expect this as well -- in this case, ENODATA is recorded instead of the\nbuffer contents.(CVE-2025-71083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n   GID entry ref leak for dev syz1 index 2 ref=573\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS:  00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n        -\u0026gt; team_port_disable()\n        -\u0026gt; team_queue_override_port_del()\n        -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n        -\u0026gt; team_queue_override_port_prio_changed()\n        -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n        -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly\n\nThe netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a\nLS_NLA_TYPE_DGID attribute, it is invalid if it does not.\n\nUse the nl parsing logic properly and call nla_parse_deprecated() to fill\nthe nlattrs array and then directly index that array to get the data for\nthe DGID. Just fail if it is NULL.\n\nRemove the for loop searching for the nla, and squash the validation and\nparsing into one function.\n\nFixes an uninitialized read from the stack triggered by userspace if it\ndoes not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE\nquery.\n\n    BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline]\n    BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     hex_byte_pack include/linux/hex.h:13 [inline]\n     ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509\n     ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633\n     pointer+0xc09/0x1bd0 lib/vsprintf.c:2542\n     vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930\n     vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279\n     vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426\n     vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465\n     vprintk+0x36/0x50 kernel/printk/printk_safe.c:82\n     _printk+0x17e/0x1b0 kernel/printk/printk.c:2475\n     ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline]\n     ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141\n     rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline]\n     rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n     rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259\n     netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n     netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346\n     netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896\n     sock_sendmsg_nosec net/socket.c:714 [inline]\n     __sock_sendmsg+0x333/0x3d0 net/socket.c:729\n     ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617\n     ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671\n     __sys_sendmsg+0x1aa/0x300 net/socket.c:2703\n     __compat_sys_sendmsg net/compat.c:346 [inline]\n     __do_compat_sys_sendmsg net/compat.c:353 [inline]\n     __se_compat_sys_sendmsg net/compat.c:350 [inline]\n     __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350\n     ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371\n     do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n     __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306\n     do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331\n     do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3(CVE-2025-71096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: Fix reference count leak when using error routes with nexthop objects\n\nWhen a nexthop object is deleted, it is marked as dead and then\nfib_table_flush() is called to flush all the routes that are using the\ndead nexthop.\n\nThe current logic in fib_table_flush() is to only flush error routes\n(e.g., blackhole) when it is called as part of network namespace\ndismantle (i.e., with flush_all=true). Therefore, error routes are not\nflushed when their nexthop object is deleted:\n\n # ip link add name dummy1 up type dummy\n # ip nexthop add id 1 dev dummy1\n # ip route add 198.51.100.1/32 nhid 1\n # ip route add blackhole 198.51.100.2/32 nhid 1\n # ip nexthop del id 1\n # ip route show\n blackhole 198.51.100.2 nhid 1 dev dummy1\n\nAs such, they keep holding a reference on the nexthop object which in\nturn holds a reference on the nexthop device, resulting in a reference\ncount leak:\n\n # ip link del dev dummy1\n [   70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2\n\nFix by flushing error routes when their nexthop is marked as dead.\n\nIPv6 does not suffer from this problem.(CVE-2025-71097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Avoid walking the Namespace if start_node is NULL\n\nAlthough commit 0c9992315e73 (\u0026quot;ACPICA: Avoid walking the ACPI Namespace\nif it is not there\u0026quot;) fixed the situation when both start_node and\nacpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed\non Honor Magicbook 14 Pro [1].\n\nThat happens due to the access to the member of parent_node in\nacpi_ns_get_next_node().  The NULL pointer dereference will always\nhappen, no matter whether or not the start_node is equal to\nACPI_ROOT_OBJECT, so move the check of start_node being NULL\nout of the if block.\n\nUnfortunately, all the attempts to contact Honor have failed, they\nrefused to provide any technical support for Linux.\n\nThe bad DSDT table\u0026apos;s dump could be found on GitHub [2].\n\nDMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025\n\n[ rjw: Subject adjustment, changelog edits ](CVE-2025-71118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Sign extend kfunc call arguments\n\nThe kfunc calls are native calls so they should follow LoongArch calling\nconventions. Sign extend its arguments properly to avoid kernel panic.\nThis is done by adding a new emit_abi_ext() helper. The emit_abi_ext()\nhelper performs extension in place meaning a value already store in the\ntarget register (Note: this is different from the existing sign_extend()\nhelper and thus we can\u0026apos;t reuse it).(CVE-2025-71129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tilcdc: Fix removal actions in case of failed probe\n\nThe drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers\nshould only be called when the device has been successfully registered.\nCurrently, these functions are called unconditionally in tilcdc_fini(),\nwhich causes warnings during probe deferral scenarios.\n\n[    7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68\n...\n[    8.005820]  drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108\n[    8.005858]  drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8\n[    8.005885]  drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144\n[    8.005911]  drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc]\n[    8.005957]  tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]\n\nFix this by rewriting the failed probe cleanup path using the standard\ngoto error handling pattern, which ensures that cleanup functions are\nonly called on successfully initialized resources. Additionally, remove\nthe now-unnecessary is_registered flag.(CVE-2025-71141)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: stm32: dmamux: fix device leak on route allocation\n\nMake sure to drop the reference taken when looking up the DMA mux\nplatform device during route allocation.\n\nNote that holding a reference to a device does not prevent its driver\ndata from going away so there is no point in keeping the reference.(CVE-2025-71186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()\n\nWhen ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().(CVE-2025-71220)\n\nIn the Linux kernel, a race condition vulnerability exists in the mmp_pdma driver. The vulnerability occurs in the mmp_pdma_residue() function which lacks proper locking mechanisms, potentially leading to use-after-free issues when accessing descriptor lists and descriptor contents.\n\nThe race condition occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors. This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan \u0026gt; 1).\n\nThe fix involves protecting the chain_running list iteration and descriptor access with the chan-\u0026gt;desc_lock spinlock.(CVE-2025-71221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: fix refcount leak in smb2_open()\n\nWhen ksmbd_vfs_getattr() fails, the reference count of ksmbd_file\nmust be released.(CVE-2025-71223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u0026gt;r1bio_pool) and conf-\u0026gt;raid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u0026gt;raid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too.(CVE-2025-71225)\n\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Free sp in error path to fix system crash  System crash seen during load/unload test in a loop,  [61110.449331] qla2xxx [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494](CVE-2025-71232)\n\nIn the Linux kernel, there is a race condition vulnerability in the SCSI qla2xxx driver. System crash was observed during load/unload loop testing. The root cause was a memory free operation occurring in interrupt context. When device discovery/fabric scan was in progress and module unload was issued setting the UNLOADING flag, work queue items could not be allocated and mapped memory had to be freed in interrupt context, leading to system crash.(CVE-2025-71235)\n\nA NULL pointer dereference vulnerability exists in the SCSI qla2xxx driver subsystem of the Linux kernel. When the system attempts to free associated memory in the qla_fab_async_scan function, it fails to validate whether the sp pointer is NULL, leading to kernel NULL pointer dereference and system crashes. This vulnerability can be exploited by attackers to cause denial of service.(CVE-2025-71236)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sock: fix hardened usercopy panic in sock_recv_errqueue\n\nskbuff_fclone_cache was created without defining a usercopy region,\n[1] unlike skbuff_head_cache which properly whitelists the cb[] field.\n[2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is\nenabled and the kernel attempts to copy sk_buff.cb data to userspace\nvia sock_recv_errqueue() -\u0026gt; put_cmsg().\n\nThe crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()\n   (from skbuff_fclone_cache) [1]\n2. The skb is cloned via skb_clone() using the pre-allocated fclone\n[3] 3. The cloned skb is queued to sk_error_queue for timestamp\nreporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)\n5. sock_recv_errqueue() calls put_cmsg() to copy serr-\u0026gt;ee from skb-\u0026gt;cb\n[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no\n   usercopy whitelist [5]\n\nWhen cloned skbs allocated from skbuff_fclone_cache are used in the\nsocket error queue, accessing the sock_exterr_skb structure in skb-\u0026gt;cb\nvia put_cmsg() triggers a usercopy hardening violation:\n\n[    5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object \u0026apos;skbuff_fclone_cache\u0026apos; (offset 296, size 16)!\n[    5.382796] kernel BUG at mm/usercopy.c:102!\n[    5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n[    5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7\n[    5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[    5.384903] RIP: 0010:usercopy_abort+0x6c/0x80\n[    5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff \u0026lt;0f\u0026gt; 0b 490\n[    5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246\n[    5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74\n[    5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0\n[    5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74\n[    5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001\n[    5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00\n[    5.384903] FS:  0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000\n[    5.384903] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0\n[    5.384903] PKRU: 55555554\n[    5.384903] Call Trace:\n[    5.384903]  \u0026lt;TASK\u0026gt;\n[    5.384903]  __check_heap_object+0x9a/0xd0\n[    5.384903]  __check_object_size+0x46c/0x690\n[    5.384903]  put_cmsg+0x129/0x5e0\n[    5.384903]  sock_recv_errqueue+0x22f/0x380\n[    5.384903]  tls_sw_recvmsg+0x7ed/0x1960\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? schedule+0x6d/0x270\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? mutex_unlock+0x81/0xd0\n[    5.384903]  ? __pfx_mutex_unlock+0x10/0x10\n[    5.384903]  ? __pfx_tls_sw_recvmsg+0x10/0x10\n[    5.384903]  ? _raw_spin_lock_irqsave+0x8f/0xf0\n[    5.384903]  ? _raw_read_unlock_irqrestore+0x20/0x40\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n\nThe crash offset 296 corresponds to skb2-\u0026gt;cb within skbuff_fclones:\n  - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -\n  offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 =\n  272 + 24 (inside sock_exterr_skb.ee)\n\nThis patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.\n\n[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885\n[2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104\n[3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566\n[4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491\n[5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719(CVE-2026-22977)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix memory leak in skb_segment_list for GRO packets\n\nWhen skb_segment_list() is called during packet forwarding, it handles\npackets that were aggregated by the GRO engine.\n\nHistorically, the segmentation logic in skb_segment_list assumes that\nindividual segments are split from a parent SKB and may need to carry\ntheir own socket memory accounting. Accordingly, the code transfers\ntruesize from the parent to the newly created segments.\n\nPrior to commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;), this\ntruesize subtraction in skb_segment_list() was valid because fragments\nstill carry a reference to the original socket.\n\nHowever, commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;) changed\nthis behavior by ensuring that fraglist entries are explicitly\norphaned (skb-\u0026gt;sk = NULL) to prevent illegal orphaning later in the\nstack. This change meant that the entire socket memory charge remained\nwith the head SKB, but the corresponding accounting logic in\nskb_segment_list() was never updated.\n\nAs a result, the current code unconditionally adds each fragment\u0026apos;s\ntruesize to delta_truesize and subtracts it from the parent SKB. Since\nthe fragments are no longer charged to the socket, this subtraction\nresults in an effective under-count of memory when the head is freed.\nThis causes sk_wmem_alloc to remain non-zero, preventing socket\ndestruction and leading to a persistent memory leak.\n\nThe leak can be observed via KMEMLEAK when tearing down the networking\nenvironment:\n\nunreferenced object 0xffff8881e6eb9100 (size 2048):\n  comm \u0026quot;ping\u0026quot;, pid 6720, jiffies 4295492526\n  backtrace:\n    kmem_cache_alloc_noprof+0x5c6/0x800\n    sk_prot_alloc+0x5b/0x220\n    sk_alloc+0x35/0xa00\n    inet6_create.part.0+0x303/0x10d0\n    __sock_create+0x248/0x640\n    __sys_socket+0x11b/0x1d0\n\nSince skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST\npackets constructed by GRO, the truesize adjustment is removed.\n\nThe call to skb_release_head_state() must be preserved. As documented in\ncommit cf673ed0e057 (\u0026quot;net: fix fraglist segmentation reference count\nleak\u0026quot;), it is still required to correctly drop references to SKB\nextensions that may be overwritten during __copy_skb_header().(CVE-2026-22979)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in handle_auth_done()\n\nPerform an explicit bounds check on payload_len to avoid a possible\nout-of-bounds access in the callout.\n\n[ idryomov: changelog ](CVE-2026-22984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make free_choose_arg_map() resilient to partial allocation\n\nfree_choose_arg_map() may dereference a NULL pointer if its caller fails\nafter a partial allocation.\n\nFor example, in decode_choose_args(), if allocation of arg_map-\u0026gt;args\nfails, execution jumps to the fail label and free_choose_arg_map() is\ncalled. Since arg_map-\u0026gt;size is updated to a non-zero value before memory\nallocation, free_choose_arg_map() will iterate over arg_map-\u0026gt;args and\ndereference a NULL pointer.\n\nTo prevent this potential NULL pointer dereference and make\nfree_choose_arg_map() more resilient, add checks for pointers before\niterating.(CVE-2026-22991)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: do not free existing class in qfq_change_class()\n\nFixes qfq_change_class() error case.\n\ncl-\u0026gt;qdisc and cl should only be freed if a new class and qdisc\nwere allocated, or we risk various UAF.(CVE-2026-22999)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n\nBlamed commit did not take care of VLAN encapsulations\nas spotted by syzbot [1].\n\nUse skb_vlan_inet_prepare() instead of pskb_inet_may_pull().\n\n[1]\n BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n  INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n  IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729\n  __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860\n  ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903\n gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1\n  ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311\n  __netif_receive_skb_one_core net/core/dev.c:6139 [inline]\n  __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252\n  netif_receive_skb_internal net/core/dev.c:6338 [inline]\n  netif_receive_skb+0x57/0x630 net/core/dev.c:6397\n  tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485\n  tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n  slab_post_alloc_hook mm/slub.c:4960 [inline]\n  slab_alloc_node mm/slub.c:5263 [inline]\n  kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315\n  kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586\n  __alloc_skb+0x805/0x1040 net/core/skbuff.c:690\n  alloc_skb include/linux/skbuff.h:1383 [inline]\n  alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712\n  sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995\n  tun_alloc_skb drivers/net/tun.c:1461 [inline]\n  tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025(CVE-2026-23003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix use-after-free in inet6_addr_del().\n\nsyzbot reported use-after-free of inet6_ifaddr in\ninet6_addr_del(). [0]\n\nThe cited commit accidentally moved ipv6_del_addr() for\nmngtmpaddr before reading its ifp-\u0026gt;flags for temporary\naddresses in inet6_addr_del().\n\nLet\u0026apos;s move ipv6_del_addr() down to fix the UAF.\n\n[0]:\nBUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\nRead of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593\n\nCPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\n addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181\n inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f164cf8f749\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749\nRDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003\nRBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 9593:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n poison_kmalloc_redzone mm/kasan/common.c:397 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414\n kmalloc_noprof include/linux/slab.h:957 [inline]\n kzalloc_noprof include/linux/slab.h:1094 [inline]\n ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120\n inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050\n addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160\n inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 6099:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584\n poison_slab_object mm/kasan/common.c:252 [inline]\n __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284\n kasan_slab_free include/linux/kasan.h:234 [inline]\n slab_free_hook mm/slub.c:2540 [inline]\n slab_free_freelist_hook mm/slub.c:2569 [inline]\n slab_free_bulk mm/slub.c:6696 [inline]\n kmem_cache_free_bulk mm/slub.c:7383 [inline]\n kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362\n kfree_bulk include/linux/slab.h:830 [inline]\n kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523\n kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline]\n kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801\n process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257\n process_scheduled_works kernel/workqu\n---truncated---(CVE-2026-23010)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_under_panic net/core/skbuff.c:223 [inline]\n  skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n  ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n  dev_hard_header include/linux/netdevice.h:3436 [inline]\n  neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n  NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n  ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n  NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n  mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n  mld_send_cr net/ipv6/mcast.c:2154 [inline]\n  mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n  worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n  kthread+0x711/0x8a0 kernel/kthread.c:463\n  ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: fix memory leak in update_eth_regs_async()\n\nWhen asynchronously writing to the device registers and if usb_submit_urb()\nfail, the code fail to release allocated to this point resources.(CVE-2026-23021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n  lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT  8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  __dump_stack (lib/dump_stack.c:95)\n  dump_stack_lvl (lib/dump_stack.c:123)\n  dump_stack (lib/dump_stack.c:130)\n  spin_dump (kernel/locking/spinlock_debug.c:71)\n  do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n  _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n  __free_frozen_pages (mm/page_alloc.c:2973)\n  ___free_pages (mm/page_alloc.c:5295)\n  __free_pages (mm/page_alloc.c:5334)\n  tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n  ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n  ? rcu_core (kernel/rcu/tree.c:?)\n  rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n  rcu_core_si (kernel/rcu/tree.c:2879)\n  handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n  __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n  irq_exit_rcu (kernel/softirq.c:741)\n  sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n  free_pcppages_bulk (mm/page_alloc.c:1494)\n  drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n  __drain_all_pages (mm/page_alloc.c:2731)\n  drain_all_pages (mm/page_alloc.c:2747)\n  kcompactd (mm/compaction.c:3115)\n  kthread (kernel/kthread.c:465)\n  ? __cfi_kcompactd (mm/compaction.c:3166)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork (arch/x86/kernel/process.c:164)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n  \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock.  The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback.  However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op.  Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;).  The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized.  Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix kmemleak by releasing references to fault configfs items\n\nWhen CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk\ndriver sets up fault injection support by creating the timeout_inject,\nrequeue_inject, and init_hctx_fault_inject configfs items as children\nof the top-level nullbX configfs group.\n\nHowever, when the nullbX device is removed, the references taken to\nthese fault-config configfs items are not released. As a result,\nkmemleak reports a memory leak, for example:\n\nunreferenced object 0xc00000021ff25c40 (size 32):\n  comm \u0026quot;mkdir\u0026quot;, pid 10665, jiffies 4322121578\n  hex dump (first 32 bytes):\n    69 6e 69 74 5f 68 63 74 78 5f 66 61 75 6c 74 5f  init_hctx_fault_\n    69 6e 6a 65 63 74 00 88 00 00 00 00 00 00 00 00  inject..........\n  backtrace (crc 1a018c86):\n    __kmalloc_node_track_caller_noprof+0x494/0xbd8\n    kvasprintf+0x74/0xf4\n    config_item_set_name+0xf0/0x104\n    config_group_init_type_name+0x48/0xfc\n    fault_config_init+0x48/0xf0\n    0xc0080000180559e4\n    configfs_mkdir+0x304/0x814\n    vfs_mkdir+0x49c/0x604\n    do_mkdirat+0x314/0x3d0\n    sys_mkdir+0xa0/0xd8\n    system_call_exception+0x1b0/0x4f0\n    system_call_vectored_common+0x15c/0x2ec\n\nFix this by explicitly releasing the references to the fault-config\nconfigfs items when dropping the reference to the top-level nullbX\nconfigfs group.(CVE-2026-23032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u0026gt;paused, not just clear it\n\nCurrently calc_target() clears t-\u0026gt;paused if the request shouldn\u0026apos;t be\npaused anymore, but doesn\u0026apos;t ever set t-\u0026gt;paused even though it\u0026apos;s able to\ndetermine when the request should be paused.  Setting t-\u0026gt;paused is left\nto __submit_request() which is fine for regular requests but doesn\u0026apos;t\nwork for linger requests -- since __submit_request() doesn\u0026apos;t operate\non linger requests, there is nowhere for lreq-\u0026gt;t.paused to be set.\nOne consequence of this is that watches don\u0026apos;t get reestablished on\npaused -\u0026gt; unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u0026gt;watch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt\u0026apos;s waiting for lreq-\u0026gt;reg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u0026gt;watch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \u0026quot;rbd unmap\u0026quot; would inevitably\nhang in D state on an attempt to grab the mutex.(CVE-2026-23047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix a deadlock when returning a delegation during open()\n\nBen Coddington reports seeing a hang in the following stack trace:\n  0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415\n  1 [ffffd0b50e177548] schedule at ffffffff9ca05717\n  2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1\n  3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb\n  4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5\n  5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]\n  6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]\n  7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]\n  8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]\n  9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]\n 10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]\n 11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]\n 12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]\n 13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]\n 14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]\n 15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]\n 16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]\n 17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea\n 18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e\n 19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935\n\nThe issue is that the delegreturn is being asked to wait for a layout\nreturn that cannot complete because a state recovery was initiated. The\nstate recovery cannot complete until the open() finishes processing the\ndelegations it was given.\n\nThe solution is to propagate the existing flags that indicate a\nnon-blocking call to the function pnfs_roc(), so that it knows not to\nwait in this situation.(CVE-2026-23050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nA buffer overflow vulnerability exists in the QLogic Fibre Channel driver (qla2xxx) of the Linux kernel. In the functions `qla27xx_copy_fpin_pkt()` and `qla27xx_copy_multiple_pkt()`, the code uses the firmware-reported `frame_size` to calculate the copy length into `item-\u0026gt;iocb`. However, the `iocb` member is defined as a fixed-size 64-byte array within `struct purex_item`. If the reported `frame_size` exceeds 64 bytes, subsequent `memcpy` calls will overflow the boundary of the `iocb` member. This cross-member write is unsafe and can lead to memory corruption, potentially exploitable to compromise the confidentiality, integrity, and availability of the kernel.(CVE-2026-23059)\n\nA NULL pointer dereference vulnerability exists in the be2net network driver within the Linux kernel, specifically in the be_cmd_get_mac_from_list() function. According to the function\u0026apos;s contract, when the parameter pmac_id_valid is set to false, the driver may request a PMAC_ID from the network card\u0026apos;s firmware and store it at the provided address pmac_id. However, there is a location within the driver where both conditions pmac_id_valid == false and pmac_id == NULL are passed simultaneously. This results in an attempt to dereference a NULL pointer, potentially leading to a kernel crash or system instability.(CVE-2026-23084)\n\nA memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the \u0026apos;itt\u0026apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit \u0026apos;unsigned long\u0026apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix isolate sysfs check condition\n\nuacce supports the device isolation feature. If the driver\nimplements the isolate_err_threshold_read and\nisolate_err_threshold_write callback functions, uacce will create\nsysfs files now. Users can read and configure the isolation policy\nthrough sysfs. Currently, sysfs files are created as long as either\nisolate_err_threshold_read or isolate_err_threshold_write callback\nfunctions are present.\n\nHowever, accessing a non-existent callback function may cause the\nsystem to crash. Therefore, intercept the creation of sysfs if\nneither read nor write exists; create sysfs if either is supported,\nbut intercept unsupported operations at the call site.(CVE-2026-23094)\n\nA deadlock vulnerability exists in the Linux kernel due to incorrect lock acquisition ordering. This vulnerability affects the migration functionality for hugetlb (huge page) file folios. The specific scenario is: when two kernel tasks (Tasks) attempt to acquire the `folio_lock` and `i_mmap_rwsem` locks in opposite orders, a circular wait is formed, leading to a system deadlock. For example, Task A holds `folio_lock` and then tries to acquire the `i_mmap_rwsem` read lock, while Task B holds the `i_mmap_rwsem` write lock and then tries to acquire `folio_lock`. This lock ordering violates the rules defined in mm/rmap.c. This vulnerability can render parts of the affected system unavailable, impacting system availability.(CVE-2026-23097)\n\nIn the Linux kernel SCSI core layer, there is a fragile ordering logic between marking commands as completed or failed, designed to ensure the error handler only wakes when the last running command completes or times out. This logic contains race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. Specifically, there are two issues: 1. A memory ordering issue within the `scsi_dec_host_busy()` function. The write operation that clears the `SCMD_STATE_INFLIGHT` flag may be reordered with read counting operations in `scsi_host_busy()`. This can cause other CPUs to see inconsistent busy counts, preventing the correct triggering of the error handler wake-up. 2. A general ordering issue with the `scsi_eh_inc_host_failed()` function. It counts busy commands before incrementing the `host_failed` count, which can race with the processing of a final command in `scsi_dec_host_busy()`, resulting in neither side waking the error handler task.(CVE-2026-23110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec\n\nnvmet_tcp_build_pdu_iovec() could walk past cmd-\u0026gt;req.sg when a PDU\nlength or offset exceeds sg_cnt and then use bogus sg-\u0026gt;length/offset\nvalues, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining\nentries, and sg-\u0026gt;length/offset before building the bvec.(CVE-2026-23112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove\n\nOn APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and\nih2 interrupt ring buffers are not initialized. This is by design, as\nthese secondary IH rings are only available on discrete GPUs. See\nvega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when\nAMD_IS_APU is set.\n\nHowever, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to\nget the timestamp of the last interrupt entry. When retry faults are\nenabled on APUs (noretry=0), this function is called from the SVM page\nfault recovery path, resulting in a NULL pointer dereference when\namdgpu_ih_decode_iv_ts_helper() attempts to access ih-\u0026gt;ring[].\n\nThe crash manifests as:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000004\n  RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]\n  Call Trace:\n   amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]\n   svm_range_restore_pages+0xae5/0x11c0 [amdgpu]\n   amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu]\n   gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]\n   amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu]\n   amdgpu_ih_process+0x84/0x100 [amdgpu]\n\nThis issue was exposed by commit 1446226d32a4 (\u0026quot;drm/amdgpu: Remove GC HW\nIP 9.3.0 from noretry=1\u0026quot;) which changed the default for Renoir APU from\nnoretry=1 to noretry=0, enabling retry fault handling and thus\nexercising the buggy code path.\n\nFix this by adding a check for ih1.ring_size before attempting to use\nit. Also restore the soft_ih support from commit dd299441654f (\u0026quot;drm/amdgpu:\nRework retry fault removal\u0026quot;).  This is needed if the hardware doesn\u0026apos;t\nsupport secondary HW IH rings.\n\nv2: additional updates (Alex)\n\n(cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)(CVE-2026-23163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()\n\nWhen the socket is closed while in TCP_LISTEN a callback is run to\nflush all outstanding packets, which in turns calls\nnvmet_tcp_listen_data_ready() with the sk_callback_lock held.\nSo we need to check if we are in TCP_LISTEN before attempting\nto get the sk_callback_lock() to avoid a deadlock.(CVE-2026-23179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: amd: fix memory leak in acp3x pdm dma ops(CVE-2026-23190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()\n\nIn iscsit_dec_session_usage_count(), the function calls complete() while\nholding the sess-\u0026gt;session_usage_lock. Similar to the connection usage count\nlogic, the waiter signaled by complete() (e.g., in the session release\npath) may wake up and free the iscsit_session structure immediately.\n\nThis creates a race condition where the current thread may attempt to\nexecute spin_unlock_bh() on a session structure that has already been\ndeallocated, resulting in a KASAN slab-use-after-free.\n\nTo resolve this, release the session_usage_lock before calling complete()\nto ensure all dereferences of the sess pointer are finished before the\nwaiter is allowed to proceed with deallocation.(CVE-2026-23193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: fix memory leak in smb2_open_file()\n\nReproducer:\n\n  1. server: directories are exported read-only\n  2. client: mount -t cifs //${server_ip}/export /mnt\n  3. client: dd if=/dev/zero of=/mnt/file bs=512 count=1000 oflag=direct\n  4. client: umount /mnt\n  5. client: sleep 1\n  6. client: modprobe -r cifs\n\nThe error message is as follows:\n\n  =============================================================================\n  BUG cifs_small_rq (Not tainted): Objects remaining on __kmem_cache_shutdown()\n  -----------------------------------------------------------------------------\n\n  Object 0x00000000d47521be @offset=14336\n  ...\n  WARNING: mm/slub.c:1251 at __kmem_cache_shutdown+0x34e/0x440, CPU#0: modprobe/1577\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   kmem_cache_destroy+0x94/0x190\n   cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n   cleanup_module+0x4e/0x540 [cifs]\n   __se_sys_delete_module+0x278/0x400\n   __x64_sys_delete_module+0x5f/0x70\n   x64_sys_call+0x2299/0x2ff0\n   do_syscall_64+0x89/0x350\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ...\n  kmem_cache_destroy cifs_small_rq: Slab cache still has objects when called from cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n  WARNING: mm/slab_common.c:532 at kmem_cache_destroy+0x16b/0x190, CPU#0: modprobe/1577(CVE-2026-23205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)\n\nIn the Linux kernel, the ksmbd component contains an infinite loop vulnerability. The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() sets work-\u0026gt;next_smb2_rcv_hdr_off to zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header\u0026apos;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with \u0026quot;bad smb2 signature\u0026quot; messages and high CPU usage.(CVE-2026-23220)\n\nIn the Linux kernel, the following vulnerability has been resolved:  smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()  On kthread_run() failure in ksmbd_tcp_new_connection(), the transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter.  Replace free_transport() with ksmbd_tcp_disconnect().  The Linux kernel CVE team has assigned CVE-2026-23228 to this issue.(CVE-2026-23228)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:37.727225213Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1567","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp: Deal with race between UDP socket address change and rehash\n\nIf a UDP socket changes its local address while it\u0026apos;s receiving\ndatagrams, as a result of connect(), there is a period during which\na lookup operation might fail to find it, after the address is changed\nbut before the secondary hash (port and address) and the four-tuple\nhash (local and remote ports and addresses) are updated.\n\nSecondary hash chains were introduced by commit 30fff9231fad (\u0026quot;udp:\nbind() optimisation\u0026quot;) and, as a result, a rehash operation became\nneeded to make a bound socket reachable again after a connect().\n\nThis operation was introduced by commit 719f835853a9 (\u0026quot;udp: add\nrehash on connect()\u0026quot;) which isn\u0026apos;t however a complete fix: the\nsocket will be found once the rehashing completes, but not while\nit\u0026apos;s pending.\n\nThis is noticeable with a socat(1) server in UDP4-LISTEN mode, and a\nclient sending datagrams to it. After the server receives the first\ndatagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to\nthe address of the sender, in order to set up a directed flow.\n\nNow, if the client, running on a different CPU thread, happens to\nsend a (subsequent) datagram while the server\u0026apos;s socket changes its\naddress, but is not rehashed yet, this will result in a failed\nlookup and a port unreachable error delivered to the client, as\napparent from the following reproducer:\n\n  LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))\n  dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in\n\n  while :; do\n  \ttaskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.1 || sleep 1\n  \ttaskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null\n  \twait\n  done\n\nwhere the client will eventually get ECONNREFUSED on a write()\n(typically the second or third one of a given iteration):\n\n  2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused\n\nThis issue was first observed as a seldom failure in Podman\u0026apos;s tests\nchecking UDP functionality while using pasta(1) to connect the\ncontainer\u0026apos;s network namespace, which leads us to a reproducer with\nthe lookup error resulting in an ICMP packet on a tap device:\n\n  LOCAL_ADDR=\u0026quot;$(ip -j -4 addr show|jq -rM \u0026apos;.[] | .addr_info[0] | select(.scope == \u0026quot;global\u0026quot;).local\u0026apos;)\u0026quot;\n\n  while :; do\n  \t./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.2 || sleep 1\n  \tsocat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null\n  \twait\n  \tcmp tmp.in tmp.out\n  done\n\nOnce this fails:\n\n  tmp.in tmp.out differ: char 8193, line 29\n\nwe can finally have a look at what\u0026apos;s going on:\n\n  $ tshark -r pasta.pcap\n      1   0.000000           :: ? ff02::16     ICMPv6 110 Multicast Listener Report Message v2\n      2   0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      3   0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      4   0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      5   0.168827 c6:47:05:8d:dc:04 ? Broadcast    ARP 42 Who has 88.198.0.161? Tell 88.198.0.164\n      6   0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55\n      7   0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      8   0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable)\n      9   0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     10   0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     11   0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096\n     12   0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0\n\nOn the third datagram received, the network namespace of the container\ninitiates an ARP lookup to deliver the ICMP message.\n\nIn another variant of this reproducer, starting the client with:\n\n  strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru\n---truncated---(CVE-2024-57974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()\n\nIf track_pfn_copy() fails, we already added the dst VMA to the maple\ntree. As fork() fails, we\u0026apos;ll cleanup the maple tree, and stumble over\nthe dst VMA for which we neither performed any reservation nor copied\nany page tables.\n\nConsequently untrack_pfn() will see VM_PAT and try obtaining the\nPAT information from the page table -- which fails because the page\ntable was not copied.\n\nThe easiest fix would be to simply clear the VM_PAT flag of the dst VMA\nif track_pfn_copy() fails. However, the whole thing is about \u0026quot;simply\u0026quot;\nclearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy()\nand performed a reservation, but copying the page tables fails, we\u0026apos;ll\nsimply clear the VM_PAT flag, not properly undoing the reservation ...\nwhich is also wrong.\n\nSo let\u0026apos;s fix it properly: set the VM_PAT flag only if the reservation\nsucceeded (leaving it clear initially), and undo the reservation if\nanything goes wrong while copying the page tables: clearing the VM_PAT\nflag after undoing the reservation.\n\nNote that any copied page table entries will get zapped when the VMA will\nget removed later, after copy_page_range() succeeded; as VM_PAT is not set\nthen, we won\u0026apos;t try cleaning VM_PAT up once more and untrack_pfn() will be\nhappy. Note that leaving these page tables in place without a reservation\nis not a problem, as we are aborting fork(); this process will never run.\n\nA reproducer can trigger this usually at the first try:\n\n  https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c\n\n  WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110\n  Modules linked in: ...\n  CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\n  RIP: 0010:get_pat_info+0xf6/0x110\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ...\n   untrack_pfn+0x52/0x110\n   unmap_single_vma+0xa6/0xe0\n   unmap_vmas+0x105/0x1f0\n   exit_mmap+0xf6/0x460\n   __mmput+0x4b/0x120\n   copy_process+0x1bf6/0x2aa0\n   kernel_clone+0xab/0x440\n   __do_sys_clone+0x66/0x90\n   do_syscall_64+0x95/0x180\n\nLikely this case was missed in:\n\n  d155df53f310 (\u0026quot;x86/mm/pat: clear VM_PAT if copy_p4d_range failed\u0026quot;)\n\n... and instead of undoing the reservation we simply cleared the VM_PAT flag.\n\nKeep the documentation of these functions in include/linux/pgtable.h,\none place is more than sufficient -- we should clean that up for the other\nfunctions like track_pfn_remap/untrack_pfn separately.(CVE-2025-22090)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: make fallback action and fallback decision atomic\n\nSyzkaller reported the following splat:\n\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary)\n  Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline]\n  RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00\n  RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246\n  RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45\n  RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001\n  RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n  R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000\n  FS:  00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432\n   tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975\n   tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166\n   tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925\n   tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363\n   ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205\n   ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254\n   dst_input include/net/dst.h:469 [inline]\n   ip_rcv_finish net/ipv4/ip_input.c:447 [inline]\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567\n   __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975\n   __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088\n   process_backlog+0x301/0x1360 net/core/dev.c:6440\n   __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453\n   napi_poll net/core/dev.c:7517 [inline]\n   net_rx_action+0xb44/0x1010 net/core/dev.c:7644\n   handle_softirqs+0x1d0/0x770 kernel/softirq.c:579\n   do_softirq+0x3f/0x90 kernel/softirq.c:480\n   \u0026lt;/IRQ\u0026gt;\n   \u0026lt;TASK\u0026gt;\n   __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407\n   local_bh_enable include/linux/bottom_half.h:33 [inline]\n   inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524\n   mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985\n   mptcp_check_listen_stop net/mptcp/mib.h:118 [inline]\n   __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000\n   mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066\n   inet_release+0xed/0x200 net/ipv4/af_inet.c:435\n   inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487\n   __sock_release+0xb3/0x270 net/socket.c:649\n   sock_close+0x1c/0x30 net/socket.c:1439\n   __fput+0x402/0xb70 fs/file_table.c:465\n   task_work_run+0x150/0x240 kernel/task_work.c:227\n   resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n   exit_to_user_mode_loop+0xd4\n---truncated---(CVE-2025-38491)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic\n\nThe decompress_io_ctx may be released asynchronously after\nI/O completion. If this file is deleted immediately after read,\nand the kworker of processing post_read_wq has not been executed yet\ndue to high workloads, It is possible that the inode(f2fs_inode_info)\nis evicted and freed before it is used f2fs_free_dic.\n\n    The UAF case as below:\n    Thread A                                      Thread B\n    - f2fs_decompress_end_io\n     - f2fs_put_dic\n      - queue_work\n        add free_dic work to post_read_wq\n                                                   - do_unlink\n                                                    - iput\n                                                     - evict\n                                                      - call_rcu\n    This file is deleted after read.\n\n    Thread C                                 kworker to process post_read_wq\n    - rcu_do_batch\n     - f2fs_free_inode\n      - kmem_cache_free\n     inode is freed by rcu\n                                             - process_scheduled_works\n                                              - f2fs_late_free_dic\n                                               - f2fs_free_dic\n                                                - f2fs_release_decomp_mem\n                                      read (dic-\u0026gt;inode)-\u0026gt;i_compress_algorithm\n\nThis patch store compress_algorithm and sbi in dic to avoid inode UAF.\n\nIn addition, the previous solution is deprecated in [1] may cause system hang.\n[1] https://lore.kernel.org/all/(CVE-2025-38627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n[ceph] parse_longname(): strrchr() expects NUL-terminated string\n\n... and parse_longname() is not guaranteed that.  That\u0026apos;s the reason\nwhy it uses kmemdup_nul() to build the argument for kstrtou64();\nthe problem is, kstrtou64() is not the only thing that need it.\n\nJust get a NUL-terminated copy of the entire thing and be done\nwith that...(CVE-2025-38660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: remove refcounting in expectation dumpers\n\nSame pattern as previous patch: do not keep the expectation object\nalive via refcount, only store a cookie value and then use that\nas the skip hint for dump resumption.\n\nAFAICS this has the same issue as the one resolved in the conntrack\ndumper, when we do\n  if (!refcount_inc_not_zero(\u0026amp;exp-\u0026gt;use))\n\nto increment the refcount, there is a chance that exp == last, which\ncauses a double-increment of the refcount and subsequent memory leak.(CVE-2025-39764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: avoid accessing metadata when pointer is invalid in object_err()\n\nobject_err() reports details of an object for further debugging, such as\nthe freelist pointer, redzone, etc. However, if the pointer is invalid,\nattempting to access object metadata can lead to a crash since it does\nnot point to a valid object.\n\nOne known path to the crash is when alloc_consistency_checks()\ndetermines the pointer to the allocated object is invalid because of a\nfreelist corruption, and calls object_err() to report it. The debug code\nshould report and handle the corruption gracefully and not crash in the\nprocess.\n\nIn case the pointer is NULL or check_valid_pointer() returns false for\nthe pointer, only print the pointer value and skip accessing metadata.(CVE-2025-39902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix Rx page leak on multi-buffer frames\n\nThe ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each\nbuffer in the current frame. This function was introduced as part of\nhandling multi-buffer XDP support in the ice driver.\n\nIt works by iterating over the buffers from first_desc up to 1 plus the\ntotal number of fragments in the frame, cached from before the XDP program\nwas executed.\n\nIf the hardware posts a descriptor with a size of 0, the logic used in\nice_put_rx_mbuf() breaks. Such descriptors get skipped and don\u0026apos;t get added\nas fragments in ice_add_xdp_frag. Since the buffer isn\u0026apos;t counted as a\nfragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don\u0026apos;t\ncall ice_put_rx_buf().\n\nBecause we don\u0026apos;t call ice_put_rx_buf(), we don\u0026apos;t attempt to re-use the\npage or free it. This leaves a stale page in the ring, as we don\u0026apos;t\nincrement next_to_alloc.\n\nThe ice_reuse_rx_page() assumes that the next_to_alloc has been incremented\nproperly, and that it always points to a buffer with a NULL page. Since\nthis function doesn\u0026apos;t check, it will happily recycle a page over the top\nof the next_to_alloc buffer, losing track of the old page.\n\nNote that this leak only occurs for multi-buffer frames. The\nice_put_rx_mbuf() function always handles at least one buffer, so a\nsingle-buffer frame will always get handled correctly. It is not clear\nprecisely why the hardware hands us descriptors with a size of 0 sometimes,\nbut it happens somewhat regularly with \u0026quot;jumbo frames\u0026quot; used by 9K MTU.\n\nTo fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on\nall buffers between first_desc and next_to_clean. Borrow the logic of a\nsimilar function in i40e used for this same purpose. Use the same logic\nalso in ice_get_pgcnts().\n\nInstead of iterating over just the number of fragments, use a loop which\niterates until the current index reaches to the next_to_clean element just\npast the current frame. Unlike i40e, the ice_put_rx_mbuf() function does\ncall ice_put_rx_buf() on the last buffer of the frame indicating the end of\npacket.\n\nFor non-linear (multi-buffer) frames, we need to take care when adjusting\nthe pagecnt_bias. An XDP program might release fragments from the tail of\nthe frame, in which case that fragment page is already released. Only\nupdate the pagecnt_bias for the first descriptor and fragments still\nremaining post-XDP program. Take care to only access the shared info for\nfragmented buffers, as this avoids a significant cache miss.\n\nThe xdp_xmit value only needs to be updated if an XDP program is run, and\nonly once per packet. Drop the xdp_xmit pointer argument from\nice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function\ndirectly. This avoids needing to pass the argument and avoids an extra\nbit-wise OR for each buffer in the frame.\n\nMove the increment of the ntc local variable to ensure its updated *before*\nall calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic\nrequires the index of the element just after the current frame.\n\nNow that we use an index pointer in the ring to identify the packet, we no\nlonger need to track or cache the number of fragments in the rx_ring.(CVE-2025-39948)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: Set fb_display[i]-\u0026gt;mode to NULL when the mode is released\n\nRecently, we discovered the following issue through syzkaller:\n\nBUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0\nRead of size 4 at addr ff11000001b3c69c by task syz.xxx\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xab/0xe0\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb9/0x280\n kasan_report+0xb8/0xf0\n fb_mode_is_equal+0x285/0x2f0\n fbcon_mode_deleted+0x129/0x180\n fb_set_var+0xe7f/0x11d0\n do_fb_ioctl+0x6a0/0x750\n fb_ioctl+0xe0/0x140\n __x64_sys_ioctl+0x193/0x210\n do_syscall_64+0x5f/0x9c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nBased on experimentation and analysis, during framebuffer unregistration,\nonly the memory of fb_info-\u0026gt;modelist is freed, without setting the\ncorresponding fb_display[i]-\u0026gt;mode to NULL for the freed modes. This leads\nto UAF issues during subsequent accesses. Here\u0026apos;s an example of reproduction\nsteps:\n1. With /dev/fb0 already registered in the system, load a kernel module\n   to register a new device /dev/fb1;\n2. Set fb1\u0026apos;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);\n3. Switch console from fb to VGA (to allow normal rmmod of the ko);\n4. Unload the kernel module, at this point fb1\u0026apos;s modelist is freed, leaving\n   a wild pointer in fb_display[];\n5. Trigger the bug via system calls through fb0 attempting to delete a mode\n   from fb0.\n\nAdd a check in do_unregister_framebuffer(): if the mode to be freed exists\nin fb_display[], set the corresponding mode pointer to NULL.(CVE-2025-40323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb\n\nThe Mesa issue referenced below pointed out a possible deadlock:\n\n[ 1231.611031]  Possible interrupt unsafe locking scenario:\n\n[ 1231.611033]        CPU0                    CPU1\n[ 1231.611034]        ----                    ----\n[ 1231.611035]   lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611038]                                local_irq_disable();\n[ 1231.611039]                                lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611041]                                lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611044]   \u0026lt;Interrupt\u0026gt;\n[ 1231.611045]     lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611047]\n                *** DEADLOCK ***\n\nIn this example, CPU0 would be any function accessing job-\u0026gt;dependencies\nthrough the xa_* functions that don\u0026apos;t disable interrupts (eg:\ndrm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()).\n\nCPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling\ncallback so in an interrupt context. It will deadlock when trying to\ngrab the xa_lock which is already held by CPU0.\n\nReplacing all xa_* usage by their xa_*_irq counterparts would fix\nthis issue, but Christian pointed out another issue: dma_fence_signal\ntakes fence.lock and so does dma_fence_add_callback.\n\n  dma_fence_signal() // locks f1.lock\n  -\u0026gt; drm_sched_entity_kill_jobs_cb()\n  -\u0026gt; foreach dependencies\n     -\u0026gt; dma_fence_add_callback() // locks f2.lock\n\nThis will deadlock if f1 and f2 share the same spinlock.\n\nTo fix both issues, the code iterating on dependencies and re-arming them\nis moved out to drm_sched_entity_kill_jobs_work().\n\n[phasta: commit message nits](CVE-2025-40329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n    Internal error: Oops: 000000009600004f [#1] SMP\n    CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n    Hardware name: LS1028A RDB Board (DT)\n    pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n    pc : xfrm_input+0xde8/0x1318\n    lr : xfrm_input+0x61c/0x1318\n    sp : ffff800080003b20\n    Call trace:\n     xfrm_input+0xde8/0x1318\n     xfrm6_rcv+0x38/0x44\n     xfrm6_esp_rcv+0x48/0xa8\n     ip6_protocol_deliver_rcu+0x94/0x4b0\n     ip6_input_finish+0x44/0x70\n     ip6_input+0x44/0xc0\n     ipv6_rcv+0x6c/0x114\n     __netif_receive_skb_one_core+0x5c/0x8c\n     __netif_receive_skb+0x18/0x60\n     process_backlog+0x78/0x17c\n     __napi_poll+0x38/0x180\n     net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imon: make send_packet() more robust\n\nsyzbot is reporting that imon has three problems which result in\nhung tasks due to forever holding device lock [1].\n\nFirst problem is that when usb_rx_callback_intf0() once got -EPROTO error\nafter ictx-\u0026gt;dev_present_intf0 became true, usb_rx_callback_intf0()\nresubmits urb after printk(), and resubmitted urb causes\nusb_rx_callback_intf0() to again get -EPROTO error. This results in\nprintk() flooding (RCU stalls).\n\nAlan Stern commented [2] that\n\n  In theory it\u0026apos;s okay to resubmit _if_ the driver has a robust\n  error-recovery scheme (such as giving up after some fixed limit on the\n  number of errors or after some fixed time has elapsed, perhaps with a\n  time delay to prevent a flood of errors).  Most drivers don\u0026apos;t bother to\n  do this; they simply give up right away.  This makes them more\n  vulnerable to short-term noise interference during USB transfers, but in\n  reality such interference is quite rare.  There\u0026apos;s nothing really wrong\n  with giving up right away.\n\nbut imon has a poor error-recovery scheme which just retries forever;\nthis behavior should be fixed.\n\nSince I\u0026apos;m not sure whether it is safe for imon users to give up upon any\nerror code, this patch takes care of only union of error codes chosen from\nmodules in drivers/media/rc/ directory which handle -EPROTO error (i.e.\nir_toy, mceusb and igorplugusb).\n\nSecond problem is that when usb_rx_callback_intf0() once got -EPROTO error\nbefore ictx-\u0026gt;dev_present_intf0 becomes true, usb_rx_callback_intf0() always\nresubmits urb due to commit 8791d63af0cf (\u0026quot;[media] imon: don\u0026apos;t wedge\nhardware after early callbacks\u0026quot;). Move the ictx-\u0026gt;dev_present_intf0 test\nintroduced by commit 6f6b90c9231a (\u0026quot;[media] imon: don\u0026apos;t parse scancodes\nuntil intf configured\u0026quot;) to immediately before imon_incoming_packet(), or\nthe first problem explained above happens without printk() flooding (i.e.\nhung task).\n\nThird problem is that when usb_rx_callback_intf0() is not called for some\nreason (e.g. flaky hardware; the reproducer for this problem sometimes\nprevents usb_rx_callback_intf0() from being called),\nwait_for_completion_interruptible() in send_packet() never returns (i.e.\nhung task). As a workaround for such situation, change send_packet() to\nwait for completion with timeout of 10 seconds.(CVE-2025-68194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: arm: scmi: Fix genpd leak on provider registration failure\n\nIf of_genpd_add_provider_onecell() fails during probe, the previously\ncreated generic power domains are not removed, leading to a memory leak\nand potential kernel crash later in genpd_debug_add().\n\nAdd proper error handling to unwind the initialized domains before\nreturning from probe to ensure all resources are correctly released on\nfailure.\n\nExample crash trace observed without this fix:\n\n  | Unable to handle kernel paging request at virtual address fffffffffffffc70\n  | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT\n  | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform\n  | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  | pc : genpd_debug_add+0x2c/0x160\n  | lr : genpd_debug_init+0x74/0x98\n  | Call trace:\n  |  genpd_debug_add+0x2c/0x160 (P)\n  |  genpd_debug_init+0x74/0x98\n  |  do_one_initcall+0xd0/0x2d8\n  |  do_initcall_level+0xa0/0x140\n  |  do_initcalls+0x60/0xa8\n  |  do_basic_setup+0x28/0x40\n  |  kernel_init_freeable+0xe8/0x170\n  |  kernel_init+0x2c/0x140\n  |  ret_from_fork+0x10/0x20(CVE-2025-68204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0026apos;s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs.(CVE-2025-68209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksm: use range-walk function to jump over holes in scan_get_next_rmap_item\n\nCurrently, scan_get_next_rmap_item() walks every page address in a VMA to\nlocate mergeable pages.  This becomes highly inefficient when scanning\nlarge virtual memory areas that contain mostly unmapped regions, causing\nksmd to use large amount of cpu without deduplicating much pages.\n\nThis patch replaces the per-address lookup with a range walk using\nwalk_page_range().  The range walker allows KSM to skip over entire\nunmapped holes in a VMA, avoiding unnecessary lookups.  This problem was\npreviously discussed in [1].\n\nConsider the following test program which creates a 32 TiB mapping in the\nvirtual address space but only populates a single page:\n\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\n\n/* 32 TiB */\nconst size_t size = 32ul * 1024 * 1024 * 1024 * 1024;\n\nint main() {\n        char *area = mmap(NULL, size, PROT_READ | PROT_WRITE,\n                          MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);\n\n        if (area == MAP_FAILED) {\n                perror(\u0026quot;mmap() failed\\n\u0026quot;);\n                return -1;\n        }\n\n        /* Populate a single page such that we get an anon_vma. */\n        *area = 0;\n\n        /* Enable KSM. */\n        madvise(area, size, MADV_MERGEABLE);\n        pause();\n        return 0;\n}\n\n$ ./ksm-sparse  \u0026amp;\n$ echo 1 \u0026gt; /sys/kernel/mm/ksm/run \n\nWithout this patch ksmd uses 100% of the cpu for a long time (more then 1\nhour in my test machine) scanning all the 32 TiB virtual address space\nthat contain only one mapped page.  This makes ksmd essentially deadlocked\nnot able to deduplicate anything of value.  With this patch ksmd walks\nonly the one mapped page and skips the rest of the 32 TiB virtual address\nspace, making the scan fast using little cpu.(CVE-2025-68211)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempool: fix poisoning order\u0026gt;0 pages with HIGHMEM\n\nThe kernel test has reported:\n\n  BUG: unable to handle page fault for address: fffba000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  *pde = 03171067 *pte = 00000000\n  Oops: Oops: 0002 [#1]\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G                T   6.18.0-rc2-00031-gec7f31b2a2d3 #1 NONE  a1d066dfe789f54bc7645c7989957d2bdee593ca\n  Tainted: [T]=RANDSTRUCT\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  EIP: memset (arch/x86/include/asm/string_32.h:168 arch/x86/lib/memcpy_32.c:17)\n  Code: a5 8b 4d f4 83 e1 03 74 02 f3 a4 83 c4 04 5e 5f 5d 2e e9 73 41 01 00 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c6 89 d0 89 f7 \u0026lt;f3\u0026gt; aa 89 f0 5e 5f 5d 2e e9 53 41 01 00 cc cc cc 55 89 e5 53 57 56\n  EAX: 0000006b EBX: 00000015 ECX: 001fefff EDX: 0000006b\n  ESI: fffb9000 EDI: fffba000 EBP: c611fbf0 ESP: c611fbe8\n  DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010287\n  CR0: 80050033 CR2: fffba000 CR3: 0316e000 CR4: 00040690\n  Call Trace:\n   poison_element (mm/mempool.c:83 mm/mempool.c:102)\n   mempool_init_node (mm/mempool.c:142 mm/mempool.c:226)\n   mempool_init_noprof (mm/mempool.c:250 (discriminator 1))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   bio_integrity_initfn (block/bio-integrity.c:483 (discriminator 8))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   do_one_initcall (init/main.c:1283)\n\nChristoph found out this is due to the poisoning code not dealing\nproperly with CONFIG_HIGHMEM because only the first page is mapped but\nthen the whole potentially high-order page is accessed.\n\nWe could give up on HIGHMEM here, but it\u0026apos;s straightforward to fix this\nwith a loop that\u0026apos;s mapping, poisoning or checking and unmapping\nindividual pages.(CVE-2025-68231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtdchar: fix integer overflow in read/write ioctls\n\nThe \u0026quot;req.start\u0026quot; and \u0026quot;req.len\u0026quot; variables are u64 values that come from the\nuser at the start of the function.  We mask away the high 32 bits of\n\u0026quot;req.len\u0026quot; so that\u0026apos;s capped at U32_MAX but the \u0026quot;req.start\u0026quot; variable can go\nup to U64_MAX which means that the addition can still integer overflow.\n\nUse check_add_overflow() to fix this bug.(CVE-2025-68237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n  BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n  Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u0026gt;work\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\u0026quot;usb: gadget: core: flush gadget workqueue after\ndevice removal\u0026quot;) attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget\u0026apos;s memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a \u0026apos;teardown\u0026apos;\nflag and a \u0026apos;state_lock\u0026apos; spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.(CVE-2025-68282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: fix NULL pointer deference when splitting folio\n\nCommit c010d47f107f (\u0026quot;mm: thp: split huge page to any lower order pages\u0026quot;)\nintroduced an early check on the folio\u0026apos;s order via mapping-\u0026gt;flags before\nproceeding with the split work.\n\nThis check introduced a bug: for shmem folios in the swap cache and\ntruncated folios, the mapping pointer can be NULL.  Accessing\nmapping-\u0026gt;flags in this state leads directly to a NULL pointer dereference.\n\nThis commit fixes the issue by moving the check for mapping != NULL before\nany attempt to access mapping-\u0026gt;flags.(CVE-2025-68293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU/AMD: Add RDSEED fix for Zen5\n\nThere\u0026apos;s an issue with RDSEED\u0026apos;s 16-bit and 32-bit register output\nvariants on Zen5 which return a random value of 0 \u0026quot;at a rate inconsistent\nwith randomness while incorrectly signaling success (CF=1)\u0026quot;. Search the\nweb for AMD-SB-7055 for more detail.\n\nAdd a fix glue which checks microcode revisions.\n\n  [ bp: Add microcode revisions checking, rewrite. ](CVE-2025-68313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninet: frags: flush pending skbs in fqdir_pre_exit()\n\nWe have been seeing occasional deadlocks on pernet_ops_rwsem since\nSeptember in NIPA. The stuck task was usually modprobe (often loading\na driver like ipvlan), trying to take the lock as a Writer.\nlockdep does not track readers for rwsems so the read wasn\u0026apos;t obvious\nfrom the reports.\n\nOn closer inspection the Reader holding the lock was conntrack looping\nforever in nf_conntrack_cleanup_net_list(). Based on past experience\nwith occasional NIPA crashes I looked thru the tests which run before\nthe crash and noticed that the crash follows ip_defrag.sh. An immediate\nred flag. Scouring thru (de)fragmentation queues reveals skbs sitting\naround, holding conntrack references.\n\nThe problem is that since conntrack depends on nf_defrag_ipv6,\nnf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its\nnetns exit hooks run _after_ conntrack\u0026apos;s netns exit hook.\n\nFlush all fragment queue SKBs during fqdir_pre_exit() to release\nconntrack references before conntrack cleanup runs. Also flush\nthe queues in timer expiry handlers when they discover fqdir-\u0026gt;dead\nis set, in case packet sneaks in while we\u0026apos;re running the pre_exit\nflush.\n\nThe commit under Fixes is not exactly the culprit, but I think\npreviously the timer firing would eventually unblock the spinning\nconntrack.(CVE-2025-68768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix middle attribute validation in push_nsh() action\n\nThe push_nsh() action structure looks like this:\n\n OVS_ACTION_ATTR_PUSH_NSH(OVS_KEY_ATTR_NSH(OVS_NSH_KEY_ATTR_BASE,...))\n\nThe outermost OVS_ACTION_ATTR_PUSH_NSH attribute is OK\u0026apos;ed by the\nnla_for_each_nested() inside __ovs_nla_copy_actions().  The innermost\nOVS_NSH_KEY_ATTR_BASE/MD1/MD2 are OK\u0026apos;ed by the nla_for_each_nested()\ninside nsh_key_put_from_nlattr().  But nothing checks if the attribute\nin the middle is OK.  We don\u0026apos;t even check that this attribute is the\nOVS_KEY_ATTR_NSH.  We just do a double unwrap with a pair of nla_data()\ncalls - first time directly while calling validate_push_nsh() and the\nsecond time as part of the nla_for_each_nested() macro, which isn\u0026apos;t\nsafe, potentially causing invalid memory access if the size of this\nattribute is incorrect.  The failure may not be noticed during\nvalidation due to larger netlink buffer, but cause trouble later during\naction execution where the buffer is allocated exactly to the size:\n\n BUG: KASAN: slab-out-of-bounds in nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n Read of size 184 at addr ffff88816459a634 by task a.out/22624\n\n CPU: 8 UID: 0 PID: 22624 6.18.0-rc7+ #115 PREEMPT(voluntary)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x51/0x70\n  print_address_description.constprop.0+0x2c/0x390\n  kasan_report+0xdd/0x110\n  kasan_check_range+0x35/0x1b0\n  __asan_memcpy+0x20/0x60\n  nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n  push_nsh+0x82/0x120 [openvswitch]\n  do_execute_actions+0x1405/0x2840 [openvswitch]\n  ovs_execute_actions+0xd5/0x3b0 [openvswitch]\n  ovs_packet_cmd_execute+0x949/0xdb0 [openvswitch]\n  genl_family_rcv_msg_doit+0x1d6/0x2b0\n  genl_family_rcv_msg+0x336/0x580\n  genl_rcv_msg+0x9f/0x130\n  netlink_rcv_skb+0x11f/0x370\n  genl_rcv+0x24/0x40\n  netlink_unicast+0x73e/0xaa0\n  netlink_sendmsg+0x744/0xbf0\n  __sys_sendto+0x3d6/0x450\n  do_syscall_64+0x79/0x2c0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  \u0026lt;/TASK\u0026gt;\n\nLet\u0026apos;s add some checks that the attribute is properly sized and it\u0026apos;s\nthe only one attribute inside the action.  Technically, there is no\nreal reason for OVS_KEY_ATTR_NSH to be there, as we know that we\u0026apos;re\npushing an NSH header already, it just creates extra nesting, but\nthat\u0026apos;s how uAPI works today.  So, keeping as it is.(CVE-2025-68785)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: alps - fix use-after-free bugs caused by dev3_register_work\n\nThe dev3_register_work delayed work item is initialized within\nalps_reconnect() and scheduled upon receipt of the first bare\nPS/2 packet from an external PS/2 device connected to the ALPS\ntouchpad. During device detachment, the original implementation\ncalls flush_workqueue() in psmouse_disconnect() to ensure\ncompletion of dev3_register_work. However, the flush_workqueue()\nin psmouse_disconnect() only blocks and waits for work items that\nwere already queued to the workqueue prior to its invocation. Any\nwork items submitted after flush_workqueue() is called are not\nincluded in the set of tasks that the flush operation awaits.\nThis means that after flush_workqueue() has finished executing,\nthe dev3_register_work could still be scheduled. Although the\npsmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(),\nthe scheduling of dev3_register_work remains unaffected.\n\nThe race condition can occur as follows:\n\nCPU 0 (cleanup path)     | CPU 1 (delayed work)\npsmouse_disconnect()     |\n  psmouse_set_state()    |\n  flush_workqueue()      | alps_report_bare_ps2_packet()\n  alps_disconnect()      |   psmouse_queue_work()\n    kfree(priv); // FREE | alps_register_bare_ps2_mouse()\n                         |   priv = container_of(work...); // USE\n                         |   priv-\u0026gt;dev3 // USE\n\nAdd disable_delayed_work_sync() in alps_disconnect() to ensure\nthat dev3_register_work is properly canceled and prevented from\nexecuting after the alps_data structure has been deallocated.\n\nThis bug is identified by static analysis.(CVE-2025-68822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential deadlock\n\nAs Jiaming Zhang and syzbot reported, there is potential deadlock in\nf2fs as below:\n\nChain exists of:\n  \u0026amp;sbi-\u0026gt;cp_rwsem --\u0026gt; fs_reclaim --\u0026gt; sb_internal#2\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  rlock(sb_internal#2);\n                               lock(fs_reclaim);\n                               lock(sb_internal#2);\n  rlock(\u0026amp;sbi-\u0026gt;cp_rwsem);\n\n *** DEADLOCK ***\n\n3 locks held by kswapd0/73:\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197\n #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890\n\nstack backtrace:\nCPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043\n check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175\n check_prev_add kernel/locking/lockdep.c:3165 [inline]\n check_prevs_add kernel/locking/lockdep.c:3284 [inline]\n validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908\n __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237\n lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868\n down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537\n f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]\n f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]\n f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791\n f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867\n f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925\n f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897\n evict+0x504/0x9c0 fs/inode.c:810\n f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853\n evict+0x504/0x9c0 fs/inode.c:810\n dispose_list fs/inode.c:852 [inline]\n prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000\n super_cache_scan+0x39b/0x4b0 fs/super.c:224\n do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437\n shrink_slab_memcg mm/shrinker.c:550 [inline]\n shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628\n shrink_one+0x28a/0x7c0 mm/vmscan.c:4955\n shrink_many mm/vmscan.c:5016 [inline]\n lru_gen_shrink_node mm/vmscan.c:5094 [inline]\n shrink_node+0x315d/0x3780 mm/vmscan.c:6081\n kswapd_shrink_node mm/vmscan.c:6941 [inline]\n balance_pgdat mm/vmscan.c:7124 [inline]\n kswapd+0x147c/0x2800 mm/vmscan.c:7389\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is deadlock among four locks as below:\n\nkswapd\n- fs_reclaim\t\t\t\t--- Lock A\n - shrink_one\n  - evict\n   - f2fs_evict_inode\n    - sb_start_intwrite\t\t\t--- Lock B\n\n- iput\n - evict\n  - f2fs_evict_inode\n   - sb_start_intwrite\t\t\t--- Lock B\n   - f2fs_truncate\n    - f2fs_truncate_blocks\n     - f2fs_do_truncate_blocks\n      - f2fs_lock_op\t\t\t--- Lock C\n\nioctl\n- f2fs_ioc_commit_atomic_write\n - f2fs_lock_op\t\t\t\t--- Lock C\n  - __f2fs_commit_atomic_write\n   - __replace_atomic_write_block\n    - f2fs_get_dnode_of_data\n     - __get_node_folio\n      - f2fs_check_nid_range\n       - f2fs_handle_error\n        - f2fs_record_errors\n         - f2fs_down_write\t\t--- Lock D\n\nopen\n- do_open\n - do_truncate\n  - security_inode_need_killpriv\n   - f2fs_getxattr\n    - lookup_all_xattrs\n     - f2fs_handle_error\n      - f2fs_record_errors\n       - f2fs_down_write\t\t--- Lock D\n        - f2fs_commit_super\n         - read_mapping_folio\n          - filemap_alloc_folio_noprof\n           - prepare_alloc_pages\n            - fs_reclaim_acquire\t--- Lock A\n\nIn order to a\n---truncated---(CVE-2025-71065)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: Avoid NULL pointer deref for evicted BOs\n\nIt is possible for a BO to exist that is not currently associated with a\nresource, e.g. because it has been evicted.\n\nWhen devcoredump tries to read the contents of all BOs for dumping, we need\nto expect this as well -- in this case, ENODATA is recorded instead of the\nbuffer contents.(CVE-2025-71083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n   GID entry ref leak for dev syz1 index 2 ref=573\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS:  00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n        -\u0026gt; team_port_disable()\n        -\u0026gt; team_queue_override_port_del()\n        -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n        -\u0026gt; team_queue_override_port_prio_changed()\n        -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n        -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly\n\nThe netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a\nLS_NLA_TYPE_DGID attribute, it is invalid if it does not.\n\nUse the nl parsing logic properly and call nla_parse_deprecated() to fill\nthe nlattrs array and then directly index that array to get the data for\nthe DGID. Just fail if it is NULL.\n\nRemove the for loop searching for the nla, and squash the validation and\nparsing into one function.\n\nFixes an uninitialized read from the stack triggered by userspace if it\ndoes not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE\nquery.\n\n    BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline]\n    BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     hex_byte_pack include/linux/hex.h:13 [inline]\n     ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509\n     ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633\n     pointer+0xc09/0x1bd0 lib/vsprintf.c:2542\n     vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930\n     vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279\n     vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426\n     vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465\n     vprintk+0x36/0x50 kernel/printk/printk_safe.c:82\n     _printk+0x17e/0x1b0 kernel/printk/printk.c:2475\n     ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline]\n     ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141\n     rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline]\n     rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n     rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259\n     netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n     netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346\n     netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896\n     sock_sendmsg_nosec net/socket.c:714 [inline]\n     __sock_sendmsg+0x333/0x3d0 net/socket.c:729\n     ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617\n     ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671\n     __sys_sendmsg+0x1aa/0x300 net/socket.c:2703\n     __compat_sys_sendmsg net/compat.c:346 [inline]\n     __do_compat_sys_sendmsg net/compat.c:353 [inline]\n     __se_compat_sys_sendmsg net/compat.c:350 [inline]\n     __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350\n     ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371\n     do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n     __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306\n     do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331\n     do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3(CVE-2025-71096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: Fix reference count leak when using error routes with nexthop objects\n\nWhen a nexthop object is deleted, it is marked as dead and then\nfib_table_flush() is called to flush all the routes that are using the\ndead nexthop.\n\nThe current logic in fib_table_flush() is to only flush error routes\n(e.g., blackhole) when it is called as part of network namespace\ndismantle (i.e., with flush_all=true). Therefore, error routes are not\nflushed when their nexthop object is deleted:\n\n # ip link add name dummy1 up type dummy\n # ip nexthop add id 1 dev dummy1\n # ip route add 198.51.100.1/32 nhid 1\n # ip route add blackhole 198.51.100.2/32 nhid 1\n # ip nexthop del id 1\n # ip route show\n blackhole 198.51.100.2 nhid 1 dev dummy1\n\nAs such, they keep holding a reference on the nexthop object which in\nturn holds a reference on the nexthop device, resulting in a reference\ncount leak:\n\n # ip link del dev dummy1\n [   70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2\n\nFix by flushing error routes when their nexthop is marked as dead.\n\nIPv6 does not suffer from this problem.(CVE-2025-71097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Avoid walking the Namespace if start_node is NULL\n\nAlthough commit 0c9992315e73 (\u0026quot;ACPICA: Avoid walking the ACPI Namespace\nif it is not there\u0026quot;) fixed the situation when both start_node and\nacpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed\non Honor Magicbook 14 Pro [1].\n\nThat happens due to the access to the member of parent_node in\nacpi_ns_get_next_node().  The NULL pointer dereference will always\nhappen, no matter whether or not the start_node is equal to\nACPI_ROOT_OBJECT, so move the check of start_node being NULL\nout of the if block.\n\nUnfortunately, all the attempts to contact Honor have failed, they\nrefused to provide any technical support for Linux.\n\nThe bad DSDT table\u0026apos;s dump could be found on GitHub [2].\n\nDMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025\n\n[ rjw: Subject adjustment, changelog edits ](CVE-2025-71118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Sign extend kfunc call arguments\n\nThe kfunc calls are native calls so they should follow LoongArch calling\nconventions. Sign extend its arguments properly to avoid kernel panic.\nThis is done by adding a new emit_abi_ext() helper. The emit_abi_ext()\nhelper performs extension in place meaning a value already store in the\ntarget register (Note: this is different from the existing sign_extend()\nhelper and thus we can\u0026apos;t reuse it).(CVE-2025-71129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tilcdc: Fix removal actions in case of failed probe\n\nThe drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers\nshould only be called when the device has been successfully registered.\nCurrently, these functions are called unconditionally in tilcdc_fini(),\nwhich causes warnings during probe deferral scenarios.\n\n[    7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68\n...\n[    8.005820]  drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108\n[    8.005858]  drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8\n[    8.005885]  drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144\n[    8.005911]  drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc]\n[    8.005957]  tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]\n\nFix this by rewriting the failed probe cleanup path using the standard\ngoto error handling pattern, which ensures that cleanup functions are\nonly called on successfully initialized resources. Additionally, remove\nthe now-unnecessary is_registered flag.(CVE-2025-71141)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: stm32: dmamux: fix device leak on route allocation\n\nMake sure to drop the reference taken when looking up the DMA mux\nplatform device during route allocation.\n\nNote that holding a reference to a device does not prevent its driver\ndata from going away so there is no point in keeping the reference.(CVE-2025-71186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()\n\nWhen ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().(CVE-2025-71220)\n\nIn the Linux kernel, a race condition vulnerability exists in the mmp_pdma driver. The vulnerability occurs in the mmp_pdma_residue() function which lacks proper locking mechanisms, potentially leading to use-after-free issues when accessing descriptor lists and descriptor contents.\n\nThe race condition occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors. This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan \u0026gt; 1).\n\nThe fix involves protecting the chain_running list iteration and descriptor access with the chan-\u0026gt;desc_lock spinlock.(CVE-2025-71221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: fix refcount leak in smb2_open()\n\nWhen ksmbd_vfs_getattr() fails, the reference count of ksmbd_file\nmust be released.(CVE-2025-71223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u0026gt;r1bio_pool) and conf-\u0026gt;raid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u0026gt;raid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too.(CVE-2025-71225)\n\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Free sp in error path to fix system crash  System crash seen during load/unload test in a loop,  [61110.449331] qla2xxx [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494](CVE-2025-71232)\n\nIn the Linux kernel, there is a race condition vulnerability in the SCSI qla2xxx driver. System crash was observed during load/unload loop testing. The root cause was a memory free operation occurring in interrupt context. When device discovery/fabric scan was in progress and module unload was issued setting the UNLOADING flag, work queue items could not be allocated and mapped memory had to be freed in interrupt context, leading to system crash.(CVE-2025-71235)\n\nA NULL pointer dereference vulnerability exists in the SCSI qla2xxx driver subsystem of the Linux kernel. When the system attempts to free associated memory in the qla_fab_async_scan function, it fails to validate whether the sp pointer is NULL, leading to kernel NULL pointer dereference and system crashes. This vulnerability can be exploited by attackers to cause denial of service.(CVE-2025-71236)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sock: fix hardened usercopy panic in sock_recv_errqueue\n\nskbuff_fclone_cache was created without defining a usercopy region,\n[1] unlike skbuff_head_cache which properly whitelists the cb[] field.\n[2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is\nenabled and the kernel attempts to copy sk_buff.cb data to userspace\nvia sock_recv_errqueue() -\u0026gt; put_cmsg().\n\nThe crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()\n   (from skbuff_fclone_cache) [1]\n2. The skb is cloned via skb_clone() using the pre-allocated fclone\n[3] 3. The cloned skb is queued to sk_error_queue for timestamp\nreporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)\n5. sock_recv_errqueue() calls put_cmsg() to copy serr-\u0026gt;ee from skb-\u0026gt;cb\n[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no\n   usercopy whitelist [5]\n\nWhen cloned skbs allocated from skbuff_fclone_cache are used in the\nsocket error queue, accessing the sock_exterr_skb structure in skb-\u0026gt;cb\nvia put_cmsg() triggers a usercopy hardening violation:\n\n[    5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object \u0026apos;skbuff_fclone_cache\u0026apos; (offset 296, size 16)!\n[    5.382796] kernel BUG at mm/usercopy.c:102!\n[    5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n[    5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7\n[    5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[    5.384903] RIP: 0010:usercopy_abort+0x6c/0x80\n[    5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff \u0026lt;0f\u0026gt; 0b 490\n[    5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246\n[    5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74\n[    5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0\n[    5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74\n[    5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001\n[    5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00\n[    5.384903] FS:  0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000\n[    5.384903] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0\n[    5.384903] PKRU: 55555554\n[    5.384903] Call Trace:\n[    5.384903]  \u0026lt;TASK\u0026gt;\n[    5.384903]  __check_heap_object+0x9a/0xd0\n[    5.384903]  __check_object_size+0x46c/0x690\n[    5.384903]  put_cmsg+0x129/0x5e0\n[    5.384903]  sock_recv_errqueue+0x22f/0x380\n[    5.384903]  tls_sw_recvmsg+0x7ed/0x1960\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? schedule+0x6d/0x270\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? mutex_unlock+0x81/0xd0\n[    5.384903]  ? __pfx_mutex_unlock+0x10/0x10\n[    5.384903]  ? __pfx_tls_sw_recvmsg+0x10/0x10\n[    5.384903]  ? _raw_spin_lock_irqsave+0x8f/0xf0\n[    5.384903]  ? _raw_read_unlock_irqrestore+0x20/0x40\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n\nThe crash offset 296 corresponds to skb2-\u0026gt;cb within skbuff_fclones:\n  - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -\n  offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 =\n  272 + 24 (inside sock_exterr_skb.ee)\n\nThis patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.\n\n[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885\n[2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104\n[3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566\n[4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491\n[5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719(CVE-2026-22977)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix memory leak in skb_segment_list for GRO packets\n\nWhen skb_segment_list() is called during packet forwarding, it handles\npackets that were aggregated by the GRO engine.\n\nHistorically, the segmentation logic in skb_segment_list assumes that\nindividual segments are split from a parent SKB and may need to carry\ntheir own socket memory accounting. Accordingly, the code transfers\ntruesize from the parent to the newly created segments.\n\nPrior to commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;), this\ntruesize subtraction in skb_segment_list() was valid because fragments\nstill carry a reference to the original socket.\n\nHowever, commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;) changed\nthis behavior by ensuring that fraglist entries are explicitly\norphaned (skb-\u0026gt;sk = NULL) to prevent illegal orphaning later in the\nstack. This change meant that the entire socket memory charge remained\nwith the head SKB, but the corresponding accounting logic in\nskb_segment_list() was never updated.\n\nAs a result, the current code unconditionally adds each fragment\u0026apos;s\ntruesize to delta_truesize and subtracts it from the parent SKB. Since\nthe fragments are no longer charged to the socket, this subtraction\nresults in an effective under-count of memory when the head is freed.\nThis causes sk_wmem_alloc to remain non-zero, preventing socket\ndestruction and leading to a persistent memory leak.\n\nThe leak can be observed via KMEMLEAK when tearing down the networking\nenvironment:\n\nunreferenced object 0xffff8881e6eb9100 (size 2048):\n  comm \u0026quot;ping\u0026quot;, pid 6720, jiffies 4295492526\n  backtrace:\n    kmem_cache_alloc_noprof+0x5c6/0x800\n    sk_prot_alloc+0x5b/0x220\n    sk_alloc+0x35/0xa00\n    inet6_create.part.0+0x303/0x10d0\n    __sock_create+0x248/0x640\n    __sys_socket+0x11b/0x1d0\n\nSince skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST\npackets constructed by GRO, the truesize adjustment is removed.\n\nThe call to skb_release_head_state() must be preserved. As documented in\ncommit cf673ed0e057 (\u0026quot;net: fix fraglist segmentation reference count\nleak\u0026quot;), it is still required to correctly drop references to SKB\nextensions that may be overwritten during __copy_skb_header().(CVE-2026-22979)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in handle_auth_done()\n\nPerform an explicit bounds check on payload_len to avoid a possible\nout-of-bounds access in the callout.\n\n[ idryomov: changelog ](CVE-2026-22984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make free_choose_arg_map() resilient to partial allocation\n\nfree_choose_arg_map() may dereference a NULL pointer if its caller fails\nafter a partial allocation.\n\nFor example, in decode_choose_args(), if allocation of arg_map-\u0026gt;args\nfails, execution jumps to the fail label and free_choose_arg_map() is\ncalled. Since arg_map-\u0026gt;size is updated to a non-zero value before memory\nallocation, free_choose_arg_map() will iterate over arg_map-\u0026gt;args and\ndereference a NULL pointer.\n\nTo prevent this potential NULL pointer dereference and make\nfree_choose_arg_map() more resilient, add checks for pointers before\niterating.(CVE-2026-22991)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: do not free existing class in qfq_change_class()\n\nFixes qfq_change_class() error case.\n\ncl-\u0026gt;qdisc and cl should only be freed if a new class and qdisc\nwere allocated, or we risk various UAF.(CVE-2026-22999)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n\nBlamed commit did not take care of VLAN encapsulations\nas spotted by syzbot [1].\n\nUse skb_vlan_inet_prepare() instead of pskb_inet_may_pull().\n\n[1]\n BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n  INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n  IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729\n  __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860\n  ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903\n gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1\n  ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311\n  __netif_receive_skb_one_core net/core/dev.c:6139 [inline]\n  __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252\n  netif_receive_skb_internal net/core/dev.c:6338 [inline]\n  netif_receive_skb+0x57/0x630 net/core/dev.c:6397\n  tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485\n  tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n  slab_post_alloc_hook mm/slub.c:4960 [inline]\n  slab_alloc_node mm/slub.c:5263 [inline]\n  kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315\n  kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586\n  __alloc_skb+0x805/0x1040 net/core/skbuff.c:690\n  alloc_skb include/linux/skbuff.h:1383 [inline]\n  alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712\n  sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995\n  tun_alloc_skb drivers/net/tun.c:1461 [inline]\n  tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025(CVE-2026-23003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix use-after-free in inet6_addr_del().\n\nsyzbot reported use-after-free of inet6_ifaddr in\ninet6_addr_del(). [0]\n\nThe cited commit accidentally moved ipv6_del_addr() for\nmngtmpaddr before reading its ifp-\u0026gt;flags for temporary\naddresses in inet6_addr_del().\n\nLet\u0026apos;s move ipv6_del_addr() down to fix the UAF.\n\n[0]:\nBUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\nRead of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593\n\nCPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\n addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181\n inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f164cf8f749\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749\nRDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003\nRBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 9593:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n poison_kmalloc_redzone mm/kasan/common.c:397 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414\n kmalloc_noprof include/linux/slab.h:957 [inline]\n kzalloc_noprof include/linux/slab.h:1094 [inline]\n ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120\n inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050\n addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160\n inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 6099:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584\n poison_slab_object mm/kasan/common.c:252 [inline]\n __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284\n kasan_slab_free include/linux/kasan.h:234 [inline]\n slab_free_hook mm/slub.c:2540 [inline]\n slab_free_freelist_hook mm/slub.c:2569 [inline]\n slab_free_bulk mm/slub.c:6696 [inline]\n kmem_cache_free_bulk mm/slub.c:7383 [inline]\n kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362\n kfree_bulk include/linux/slab.h:830 [inline]\n kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523\n kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline]\n kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801\n process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257\n process_scheduled_works kernel/workqu\n---truncated---(CVE-2026-23010)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_under_panic net/core/skbuff.c:223 [inline]\n  skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n  ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n  dev_hard_header include/linux/netdevice.h:3436 [inline]\n  neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n  NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n  ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n  NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n  mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n  mld_send_cr net/ipv6/mcast.c:2154 [inline]\n  mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n  worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n  kthread+0x711/0x8a0 kernel/kthread.c:463\n  ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: fix memory leak in update_eth_regs_async()\n\nWhen asynchronously writing to the device registers and if usb_submit_urb()\nfail, the code fail to release allocated to this point resources.(CVE-2026-23021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n  lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT  8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  __dump_stack (lib/dump_stack.c:95)\n  dump_stack_lvl (lib/dump_stack.c:123)\n  dump_stack (lib/dump_stack.c:130)\n  spin_dump (kernel/locking/spinlock_debug.c:71)\n  do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n  _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n  __free_frozen_pages (mm/page_alloc.c:2973)\n  ___free_pages (mm/page_alloc.c:5295)\n  __free_pages (mm/page_alloc.c:5334)\n  tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n  ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n  ? rcu_core (kernel/rcu/tree.c:?)\n  rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n  rcu_core_si (kernel/rcu/tree.c:2879)\n  handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n  __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n  irq_exit_rcu (kernel/softirq.c:741)\n  sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n  free_pcppages_bulk (mm/page_alloc.c:1494)\n  drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n  __drain_all_pages (mm/page_alloc.c:2731)\n  drain_all_pages (mm/page_alloc.c:2747)\n  kcompactd (mm/compaction.c:3115)\n  kthread (kernel/kthread.c:465)\n  ? __cfi_kcompactd (mm/compaction.c:3166)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork (arch/x86/kernel/process.c:164)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n  \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock.  The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback.  However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op.  Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;).  The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized.  Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix kmemleak by releasing references to fault configfs items\n\nWhen CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk\ndriver sets up fault injection support by creating the timeout_inject,\nrequeue_inject, and init_hctx_fault_inject configfs items as children\nof the top-level nullbX configfs group.\n\nHowever, when the nullbX device is removed, the references taken to\nthese fault-config configfs items are not released. As a result,\nkmemleak reports a memory leak, for example:\n\nunreferenced object 0xc00000021ff25c40 (size 32):\n  comm \u0026quot;mkdir\u0026quot;, pid 10665, jiffies 4322121578\n  hex dump (first 32 bytes):\n    69 6e 69 74 5f 68 63 74 78 5f 66 61 75 6c 74 5f  init_hctx_fault_\n    69 6e 6a 65 63 74 00 88 00 00 00 00 00 00 00 00  inject..........\n  backtrace (crc 1a018c86):\n    __kmalloc_node_track_caller_noprof+0x494/0xbd8\n    kvasprintf+0x74/0xf4\n    config_item_set_name+0xf0/0x104\n    config_group_init_type_name+0x48/0xfc\n    fault_config_init+0x48/0xf0\n    0xc0080000180559e4\n    configfs_mkdir+0x304/0x814\n    vfs_mkdir+0x49c/0x604\n    do_mkdirat+0x314/0x3d0\n    sys_mkdir+0xa0/0xd8\n    system_call_exception+0x1b0/0x4f0\n    system_call_vectored_common+0x15c/0x2ec\n\nFix this by explicitly releasing the references to the fault-config\nconfigfs items when dropping the reference to the top-level nullbX\nconfigfs group.(CVE-2026-23032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u0026gt;paused, not just clear it\n\nCurrently calc_target() clears t-\u0026gt;paused if the request shouldn\u0026apos;t be\npaused anymore, but doesn\u0026apos;t ever set t-\u0026gt;paused even though it\u0026apos;s able to\ndetermine when the request should be paused.  Setting t-\u0026gt;paused is left\nto __submit_request() which is fine for regular requests but doesn\u0026apos;t\nwork for linger requests -- since __submit_request() doesn\u0026apos;t operate\non linger requests, there is nowhere for lreq-\u0026gt;t.paused to be set.\nOne consequence of this is that watches don\u0026apos;t get reestablished on\npaused -\u0026gt; unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u0026gt;watch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt\u0026apos;s waiting for lreq-\u0026gt;reg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u0026gt;watch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \u0026quot;rbd unmap\u0026quot; would inevitably\nhang in D state on an attempt to grab the mutex.(CVE-2026-23047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix a deadlock when returning a delegation during open()\n\nBen Coddington reports seeing a hang in the following stack trace:\n  0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415\n  1 [ffffd0b50e177548] schedule at ffffffff9ca05717\n  2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1\n  3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb\n  4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5\n  5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]\n  6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]\n  7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]\n  8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]\n  9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]\n 10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]\n 11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]\n 12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]\n 13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]\n 14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]\n 15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]\n 16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]\n 17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea\n 18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e\n 19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935\n\nThe issue is that the delegreturn is being asked to wait for a layout\nreturn that cannot complete because a state recovery was initiated. The\nstate recovery cannot complete until the open() finishes processing the\ndelegations it was given.\n\nThe solution is to propagate the existing flags that indicate a\nnon-blocking call to the function pnfs_roc(), so that it knows not to\nwait in this situation.(CVE-2026-23050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nA buffer overflow vulnerability exists in the QLogic Fibre Channel driver (qla2xxx) of the Linux kernel. In the functions `qla27xx_copy_fpin_pkt()` and `qla27xx_copy_multiple_pkt()`, the code uses the firmware-reported `frame_size` to calculate the copy length into `item-\u0026gt;iocb`. However, the `iocb` member is defined as a fixed-size 64-byte array within `struct purex_item`. If the reported `frame_size` exceeds 64 bytes, subsequent `memcpy` calls will overflow the boundary of the `iocb` member. This cross-member write is unsafe and can lead to memory corruption, potentially exploitable to compromise the confidentiality, integrity, and availability of the kernel.(CVE-2026-23059)\n\nA NULL pointer dereference vulnerability exists in the be2net network driver within the Linux kernel, specifically in the be_cmd_get_mac_from_list() function. According to the function\u0026apos;s contract, when the parameter pmac_id_valid is set to false, the driver may request a PMAC_ID from the network card\u0026apos;s firmware and store it at the provided address pmac_id. However, there is a location within the driver where both conditions pmac_id_valid == false and pmac_id == NULL are passed simultaneously. This results in an attempt to dereference a NULL pointer, potentially leading to a kernel crash or system instability.(CVE-2026-23084)\n\nA memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the \u0026apos;itt\u0026apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit \u0026apos;unsigned long\u0026apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix isolate sysfs check condition\n\nuacce supports the device isolation feature. If the driver\nimplements the isolate_err_threshold_read and\nisolate_err_threshold_write callback functions, uacce will create\nsysfs files now. Users can read and configure the isolation policy\nthrough sysfs. Currently, sysfs files are created as long as either\nisolate_err_threshold_read or isolate_err_threshold_write callback\nfunctions are present.\n\nHowever, accessing a non-existent callback function may cause the\nsystem to crash. Therefore, intercept the creation of sysfs if\nneither read nor write exists; create sysfs if either is supported,\nbut intercept unsupported operations at the call site.(CVE-2026-23094)\n\nA deadlock vulnerability exists in the Linux kernel due to incorrect lock acquisition ordering. This vulnerability affects the migration functionality for hugetlb (huge page) file folios. The specific scenario is: when two kernel tasks (Tasks) attempt to acquire the `folio_lock` and `i_mmap_rwsem` locks in opposite orders, a circular wait is formed, leading to a system deadlock. For example, Task A holds `folio_lock` and then tries to acquire the `i_mmap_rwsem` read lock, while Task B holds the `i_mmap_rwsem` write lock and then tries to acquire `folio_lock`. This lock ordering violates the rules defined in mm/rmap.c. This vulnerability can render parts of the affected system unavailable, impacting system availability.(CVE-2026-23097)\n\nIn the Linux kernel SCSI core layer, there is a fragile ordering logic between marking commands as completed or failed, designed to ensure the error handler only wakes when the last running command completes or times out. This logic contains race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. Specifically, there are two issues: 1. A memory ordering issue within the `scsi_dec_host_busy()` function. The write operation that clears the `SCMD_STATE_INFLIGHT` flag may be reordered with read counting operations in `scsi_host_busy()`. This can cause other CPUs to see inconsistent busy counts, preventing the correct triggering of the error handler wake-up. 2. A general ordering issue with the `scsi_eh_inc_host_failed()` function. It counts busy commands before incrementing the `host_failed` count, which can race with the processing of a final command in `scsi_dec_host_busy()`, resulting in neither side waking the error handler task.(CVE-2026-23110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec\n\nnvmet_tcp_build_pdu_iovec() could walk past cmd-\u0026gt;req.sg when a PDU\nlength or offset exceeds sg_cnt and then use bogus sg-\u0026gt;length/offset\nvalues, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining\nentries, and sg-\u0026gt;length/offset before building the bvec.(CVE-2026-23112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove\n\nOn APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and\nih2 interrupt ring buffers are not initialized. This is by design, as\nthese secondary IH rings are only available on discrete GPUs. See\nvega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when\nAMD_IS_APU is set.\n\nHowever, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to\nget the timestamp of the last interrupt entry. When retry faults are\nenabled on APUs (noretry=0), this function is called from the SVM page\nfault recovery path, resulting in a NULL pointer dereference when\namdgpu_ih_decode_iv_ts_helper() attempts to access ih-\u0026gt;ring[].\n\nThe crash manifests as:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000004\n  RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]\n  Call Trace:\n   amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]\n   svm_range_restore_pages+0xae5/0x11c0 [amdgpu]\n   amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu]\n   gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]\n   amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu]\n   amdgpu_ih_process+0x84/0x100 [amdgpu]\n\nThis issue was exposed by commit 1446226d32a4 (\u0026quot;drm/amdgpu: Remove GC HW\nIP 9.3.0 from noretry=1\u0026quot;) which changed the default for Renoir APU from\nnoretry=1 to noretry=0, enabling retry fault handling and thus\nexercising the buggy code path.\n\nFix this by adding a check for ih1.ring_size before attempting to use\nit. Also restore the soft_ih support from commit dd299441654f (\u0026quot;drm/amdgpu:\nRework retry fault removal\u0026quot;).  This is needed if the hardware doesn\u0026apos;t\nsupport secondary HW IH rings.\n\nv2: additional updates (Alex)\n\n(cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)(CVE-2026-23163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()\n\nWhen the socket is closed while in TCP_LISTEN a callback is run to\nflush all outstanding packets, which in turns calls\nnvmet_tcp_listen_data_ready() with the sk_callback_lock held.\nSo we need to check if we are in TCP_LISTEN before attempting\nto get the sk_callback_lock() to avoid a deadlock.(CVE-2026-23179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: amd: fix memory leak in acp3x pdm dma ops(CVE-2026-23190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()\n\nIn iscsit_dec_session_usage_count(), the function calls complete() while\nholding the sess-\u0026gt;session_usage_lock. Similar to the connection usage count\nlogic, the waiter signaled by complete() (e.g., in the session release\npath) may wake up and free the iscsit_session structure immediately.\n\nThis creates a race condition where the current thread may attempt to\nexecute spin_unlock_bh() on a session structure that has already been\ndeallocated, resulting in a KASAN slab-use-after-free.\n\nTo resolve this, release the session_usage_lock before calling complete()\nto ensure all dereferences of the sess pointer are finished before the\nwaiter is allowed to proceed with deallocation.(CVE-2026-23193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: fix memory leak in smb2_open_file()\n\nReproducer:\n\n  1. server: directories are exported read-only\n  2. client: mount -t cifs //${server_ip}/export /mnt\n  3. client: dd if=/dev/zero of=/mnt/file bs=512 count=1000 oflag=direct\n  4. client: umount /mnt\n  5. client: sleep 1\n  6. client: modprobe -r cifs\n\nThe error message is as follows:\n\n  =============================================================================\n  BUG cifs_small_rq (Not tainted): Objects remaining on __kmem_cache_shutdown()\n  -----------------------------------------------------------------------------\n\n  Object 0x00000000d47521be @offset=14336\n  ...\n  WARNING: mm/slub.c:1251 at __kmem_cache_shutdown+0x34e/0x440, CPU#0: modprobe/1577\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   kmem_cache_destroy+0x94/0x190\n   cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n   cleanup_module+0x4e/0x540 [cifs]\n   __se_sys_delete_module+0x278/0x400\n   __x64_sys_delete_module+0x5f/0x70\n   x64_sys_call+0x2299/0x2ff0\n   do_syscall_64+0x89/0x350\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ...\n  kmem_cache_destroy cifs_small_rq: Slab cache still has objects when called from cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n  WARNING: mm/slab_common.c:532 at kmem_cache_destroy+0x16b/0x190, CPU#0: modprobe/1577(CVE-2026-23205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)\n\nIn the Linux kernel, the ksmbd component contains an infinite loop vulnerability. The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() sets work-\u0026gt;next_smb2_rcv_hdr_off to zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header\u0026apos;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with \u0026quot;bad smb2 signature\u0026quot; messages and high CPU usage.(CVE-2026-23220)\n\nIn the Linux kernel, the following vulnerability has been resolved:  smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()  On kthread_run() failure in ksmbd_tcp_new_connection(), the transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter.  Replace free_transport() with ksmbd_tcp_disconnect().  The Linux kernel CVE team has assigned CVE-2026-23228 to this issue.(CVE-2026-23228)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:37.776858405Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"OESA-2026-1570","title":"kernel security update","description":"The Linux Kernel, the operating system core itself.\r\n\r\nSecurity Fix(es):\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nudp: Deal with race between UDP socket address change and rehash\n\nIf a UDP socket changes its local address while it\u0026apos;s receiving\ndatagrams, as a result of connect(), there is a period during which\na lookup operation might fail to find it, after the address is changed\nbut before the secondary hash (port and address) and the four-tuple\nhash (local and remote ports and addresses) are updated.\n\nSecondary hash chains were introduced by commit 30fff9231fad (\u0026quot;udp:\nbind() optimisation\u0026quot;) and, as a result, a rehash operation became\nneeded to make a bound socket reachable again after a connect().\n\nThis operation was introduced by commit 719f835853a9 (\u0026quot;udp: add\nrehash on connect()\u0026quot;) which isn\u0026apos;t however a complete fix: the\nsocket will be found once the rehashing completes, but not while\nit\u0026apos;s pending.\n\nThis is noticeable with a socat(1) server in UDP4-LISTEN mode, and a\nclient sending datagrams to it. After the server receives the first\ndatagram (cf. _xioopen_ipdgram_listen()), it issues a connect() to\nthe address of the sender, in order to set up a directed flow.\n\nNow, if the client, running on a different CPU thread, happens to\nsend a (subsequent) datagram while the server\u0026apos;s socket changes its\naddress, but is not rehashed yet, this will result in a failed\nlookup and a port unreachable error delivered to the client, as\napparent from the following reproducer:\n\n  LEN=$(($(cat /proc/sys/net/core/wmem_default) / 4))\n  dd if=/dev/urandom bs=1 count=${LEN} of=tmp.in\n\n  while :; do\n  \ttaskset -c 1 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.1 || sleep 1\n  \ttaskset -c 2 socat OPEN:tmp.in UDP4:localhost:1337,shut-null\n  \twait\n  done\n\nwhere the client will eventually get ECONNREFUSED on a write()\n(typically the second or third one of a given iteration):\n\n  2024/11/13 21:28:23 socat[46901] E write(6, 0x556db2e3c000, 8192): Connection refused\n\nThis issue was first observed as a seldom failure in Podman\u0026apos;s tests\nchecking UDP functionality while using pasta(1) to connect the\ncontainer\u0026apos;s network namespace, which leads us to a reproducer with\nthe lookup error resulting in an ICMP packet on a tap device:\n\n  LOCAL_ADDR=\u0026quot;$(ip -j -4 addr show|jq -rM \u0026apos;.[] | .addr_info[0] | select(.scope == \u0026quot;global\u0026quot;).local\u0026apos;)\u0026quot;\n\n  while :; do\n  \t./pasta --config-net -p pasta.pcap -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,trunc \u0026amp;\n  \tsleep 0.2 || sleep 1\n  \tsocat OPEN:tmp.in UDP4:${LOCAL_ADDR}:1337,shut-null\n  \twait\n  \tcmp tmp.in tmp.out\n  done\n\nOnce this fails:\n\n  tmp.in tmp.out differ: char 8193, line 29\n\nwe can finally have a look at what\u0026apos;s going on:\n\n  $ tshark -r pasta.pcap\n      1   0.000000           :: ? ff02::16     ICMPv6 110 Multicast Listener Report Message v2\n      2   0.168690 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      3   0.168767 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      4   0.168806 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      5   0.168827 c6:47:05:8d:dc:04 ? Broadcast    ARP 42 Who has 88.198.0.161? Tell 88.198.0.164\n      6   0.168851 9a:55:9a:55:9a:55 ? c6:47:05:8d:dc:04 ARP 42 88.198.0.161 is at 9a:55:9a:55:9a:55\n      7   0.168875 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n      8   0.168896 88.198.0.164 ? 88.198.0.161 ICMP 590 Destination unreachable (Port unreachable)\n      9   0.168926 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     10   0.168959 88.198.0.161 ? 88.198.0.164 UDP 8234 60260 ? 1337 Len=8192\n     11   0.168989 88.198.0.161 ? 88.198.0.164 UDP 4138 60260 ? 1337 Len=4096\n     12   0.169010 88.198.0.161 ? 88.198.0.164 UDP 42 60260 ? 1337 Len=0\n\nOn the third datagram received, the network namespace of the container\ninitiates an ARP lookup to deliver the ICMP message.\n\nIn another variant of this reproducer, starting the client with:\n\n  strace -f pasta --config-net -u 1337 socat UDP4-LISTEN:1337,null-eof OPEN:tmp.out,create,tru\n---truncated---(CVE-2024-57974)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/mm/pat: Fix VM_PAT handling when fork() fails in copy_page_range()\n\nIf track_pfn_copy() fails, we already added the dst VMA to the maple\ntree. As fork() fails, we\u0026apos;ll cleanup the maple tree, and stumble over\nthe dst VMA for which we neither performed any reservation nor copied\nany page tables.\n\nConsequently untrack_pfn() will see VM_PAT and try obtaining the\nPAT information from the page table -- which fails because the page\ntable was not copied.\n\nThe easiest fix would be to simply clear the VM_PAT flag of the dst VMA\nif track_pfn_copy() fails. However, the whole thing is about \u0026quot;simply\u0026quot;\nclearing the VM_PAT flag is shaky as well: if we passed track_pfn_copy()\nand performed a reservation, but copying the page tables fails, we\u0026apos;ll\nsimply clear the VM_PAT flag, not properly undoing the reservation ...\nwhich is also wrong.\n\nSo let\u0026apos;s fix it properly: set the VM_PAT flag only if the reservation\nsucceeded (leaving it clear initially), and undo the reservation if\nanything goes wrong while copying the page tables: clearing the VM_PAT\nflag after undoing the reservation.\n\nNote that any copied page table entries will get zapped when the VMA will\nget removed later, after copy_page_range() succeeded; as VM_PAT is not set\nthen, we won\u0026apos;t try cleaning VM_PAT up once more and untrack_pfn() will be\nhappy. Note that leaving these page tables in place without a reservation\nis not a problem, as we are aborting fork(); this process will never run.\n\nA reproducer can trigger this usually at the first try:\n\n  https://gitlab.com/davidhildenbrand/scratchspace/-/raw/main/reproducers/pat_fork.c\n\n  WARNING: CPU: 26 PID: 11650 at arch/x86/mm/pat/memtype.c:983 get_pat_info+0xf6/0x110\n  Modules linked in: ...\n  CPU: 26 UID: 0 PID: 11650 Comm: repro3 Not tainted 6.12.0-rc5+ #92\n  Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-2.fc40 04/01/2014\n  RIP: 0010:get_pat_info+0xf6/0x110\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   ...\n   untrack_pfn+0x52/0x110\n   unmap_single_vma+0xa6/0xe0\n   unmap_vmas+0x105/0x1f0\n   exit_mmap+0xf6/0x460\n   __mmput+0x4b/0x120\n   copy_process+0x1bf6/0x2aa0\n   kernel_clone+0xab/0x440\n   __do_sys_clone+0x66/0x90\n   do_syscall_64+0x95/0x180\n\nLikely this case was missed in:\n\n  d155df53f310 (\u0026quot;x86/mm/pat: clear VM_PAT if copy_p4d_range failed\u0026quot;)\n\n... and instead of undoing the reservation we simply cleared the VM_PAT flag.\n\nKeep the documentation of these functions in include/linux/pgtable.h,\none place is more than sufficient -- we should clean that up for the other\nfunctions like track_pfn_remap/untrack_pfn separately.(CVE-2025-22090)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmptcp: make fallback action and fallback decision atomic\n\nSyzkaller reported the following splat:\n\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 __mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 check_fully_established net/mptcp/options.c:982 [inline]\n  WARNING: CPU: 1 PID: 7704 at net/mptcp/protocol.h:1223 mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Modules linked in:\n  CPU: 1 UID: 0 PID: 7704 Comm: syz.3.1419 Not tainted 6.16.0-rc3-gbd5ce2324dba #20 PREEMPT(voluntary)\n  Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  RIP: 0010:__mptcp_do_fallback net/mptcp/protocol.h:1223 [inline]\n  RIP: 0010:mptcp_do_fallback net/mptcp/protocol.h:1244 [inline]\n  RIP: 0010:check_fully_established net/mptcp/options.c:982 [inline]\n  RIP: 0010:mptcp_incoming_options+0x21a8/0x2510 net/mptcp/options.c:1153\n  Code: 24 18 e8 bb 2a 00 fd e9 1b df ff ff e8 b1 21 0f 00 e8 ec 5f c4 fc 44 0f b7 ac 24 b0 00 00 00 e9 54 f1 ff ff e8 d9 5f c4 fc 90 \u0026lt;0f\u0026gt; 0b 90 e9 b8 f4 ff ff e8 8b 2a 00 fd e9 8d e6 ff ff e8 81 2a 00\n  RSP: 0018:ffff8880a3f08448 EFLAGS: 00010246\n  RAX: 0000000000000000 RBX: ffff8880180a8000 RCX: ffffffff84afcf45\n  RDX: ffff888090223700 RSI: ffffffff84afdaa7 RDI: 0000000000000001\n  RBP: ffff888017955780 R08: 0000000000000001 R09: 0000000000000000\n  R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000\n  R13: ffff8880180a8910 R14: ffff8880a3e9d058 R15: 0000000000000000\n  FS:  00005555791b8500(0000) GS:ffff88811c495000(0000) knlGS:0000000000000000\n  CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n  CR2: 000000110c2800b7 CR3: 0000000058e44000 CR4: 0000000000350ef0\n  Call Trace:\n   \u0026lt;IRQ\u0026gt;\n   tcp_reset+0x26f/0x2b0 net/ipv4/tcp_input.c:4432\n   tcp_validate_incoming+0x1057/0x1b60 net/ipv4/tcp_input.c:5975\n   tcp_rcv_established+0x5b5/0x21f0 net/ipv4/tcp_input.c:6166\n   tcp_v4_do_rcv+0x5dc/0xa70 net/ipv4/tcp_ipv4.c:1925\n   tcp_v4_rcv+0x3473/0x44a0 net/ipv4/tcp_ipv4.c:2363\n   ip_protocol_deliver_rcu+0xba/0x480 net/ipv4/ip_input.c:205\n   ip_local_deliver_finish+0x2f1/0x500 net/ipv4/ip_input.c:233\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_local_deliver+0x1be/0x560 net/ipv4/ip_input.c:254\n   dst_input include/net/dst.h:469 [inline]\n   ip_rcv_finish net/ipv4/ip_input.c:447 [inline]\n   NF_HOOK include/linux/netfilter.h:317 [inline]\n   NF_HOOK include/linux/netfilter.h:311 [inline]\n   ip_rcv+0x514/0x810 net/ipv4/ip_input.c:567\n   __netif_receive_skb_one_core+0x197/0x1e0 net/core/dev.c:5975\n   __netif_receive_skb+0x1f/0x120 net/core/dev.c:6088\n   process_backlog+0x301/0x1360 net/core/dev.c:6440\n   __napi_poll.constprop.0+0xba/0x550 net/core/dev.c:7453\n   napi_poll net/core/dev.c:7517 [inline]\n   net_rx_action+0xb44/0x1010 net/core/dev.c:7644\n   handle_softirqs+0x1d0/0x770 kernel/softirq.c:579\n   do_softirq+0x3f/0x90 kernel/softirq.c:480\n   \u0026lt;/IRQ\u0026gt;\n   \u0026lt;TASK\u0026gt;\n   __local_bh_enable_ip+0xed/0x110 kernel/softirq.c:407\n   local_bh_enable include/linux/bottom_half.h:33 [inline]\n   inet_csk_listen_stop+0x2c5/0x1070 net/ipv4/inet_connection_sock.c:1524\n   mptcp_check_listen_stop.part.0+0x1cc/0x220 net/mptcp/protocol.c:2985\n   mptcp_check_listen_stop net/mptcp/mib.h:118 [inline]\n   __mptcp_close+0x9b9/0xbd0 net/mptcp/protocol.c:3000\n   mptcp_close+0x2f/0x140 net/mptcp/protocol.c:3066\n   inet_release+0xed/0x200 net/ipv4/af_inet.c:435\n   inet6_release+0x4f/0x70 net/ipv6/af_inet6.c:487\n   __sock_release+0xb3/0x270 net/socket.c:649\n   sock_close+0x1c/0x30 net/socket.c:1439\n   __fput+0x402/0xb70 fs/file_table.c:465\n   task_work_run+0x150/0x240 kernel/task_work.c:227\n   resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]\n   exit_to_user_mode_loop+0xd4\n---truncated---(CVE-2025-38491)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: compress: fix UAF of f2fs_inode_info in f2fs_free_dic\n\nThe decompress_io_ctx may be released asynchronously after\nI/O completion. If this file is deleted immediately after read,\nand the kworker of processing post_read_wq has not been executed yet\ndue to high workloads, It is possible that the inode(f2fs_inode_info)\nis evicted and freed before it is used f2fs_free_dic.\n\n    The UAF case as below:\n    Thread A                                      Thread B\n    - f2fs_decompress_end_io\n     - f2fs_put_dic\n      - queue_work\n        add free_dic work to post_read_wq\n                                                   - do_unlink\n                                                    - iput\n                                                     - evict\n                                                      - call_rcu\n    This file is deleted after read.\n\n    Thread C                                 kworker to process post_read_wq\n    - rcu_do_batch\n     - f2fs_free_inode\n      - kmem_cache_free\n     inode is freed by rcu\n                                             - process_scheduled_works\n                                              - f2fs_late_free_dic\n                                               - f2fs_free_dic\n                                                - f2fs_release_decomp_mem\n                                      read (dic-\u0026gt;inode)-\u0026gt;i_compress_algorithm\n\nThis patch store compress_algorithm and sbi in dic to avoid inode UAF.\n\nIn addition, the previous solution is deprecated in [1] may cause system hang.\n[1] https://lore.kernel.org/all/(CVE-2025-38627)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\n[ceph] parse_longname(): strrchr() expects NUL-terminated string\n\n... and parse_longname() is not guaranteed that.  That\u0026apos;s the reason\nwhy it uses kmemdup_nul() to build the argument for kstrtou64();\nthe problem is, kstrtou64() is not the only thing that need it.\n\nJust get a NUL-terminated copy of the entire thing and be done\nwith that...(CVE-2025-38660)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: ctnetlink: remove refcounting in expectation dumpers\n\nSame pattern as previous patch: do not keep the expectation object\nalive via refcount, only store a cookie value and then use that\nas the skip hint for dump resumption.\n\nAFAICS this has the same issue as the one resolved in the conntrack\ndumper, when we do\n  if (!refcount_inc_not_zero(\u0026amp;exp-\u0026gt;use))\n\nto increment the refcount, there is a chance that exp == last, which\ncauses a double-increment of the refcount and subsequent memory leak.(CVE-2025-39764)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/slub: avoid accessing metadata when pointer is invalid in object_err()\n\nobject_err() reports details of an object for further debugging, such as\nthe freelist pointer, redzone, etc. However, if the pointer is invalid,\nattempting to access object metadata can lead to a crash since it does\nnot point to a valid object.\n\nOne known path to the crash is when alloc_consistency_checks()\ndetermines the pointer to the allocated object is invalid because of a\nfreelist corruption, and calls object_err() to report it. The debug code\nshould report and handle the corruption gracefully and not crash in the\nprocess.\n\nIn case the pointer is NULL or check_valid_pointer() returns false for\nthe pointer, only print the pointer value and skip accessing metadata.(CVE-2025-39902)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nice: fix Rx page leak on multi-buffer frames\n\nThe ice_put_rx_mbuf() function handles calling ice_put_rx_buf() for each\nbuffer in the current frame. This function was introduced as part of\nhandling multi-buffer XDP support in the ice driver.\n\nIt works by iterating over the buffers from first_desc up to 1 plus the\ntotal number of fragments in the frame, cached from before the XDP program\nwas executed.\n\nIf the hardware posts a descriptor with a size of 0, the logic used in\nice_put_rx_mbuf() breaks. Such descriptors get skipped and don\u0026apos;t get added\nas fragments in ice_add_xdp_frag. Since the buffer isn\u0026apos;t counted as a\nfragment, we do not iterate over it in ice_put_rx_mbuf(), and thus we don\u0026apos;t\ncall ice_put_rx_buf().\n\nBecause we don\u0026apos;t call ice_put_rx_buf(), we don\u0026apos;t attempt to re-use the\npage or free it. This leaves a stale page in the ring, as we don\u0026apos;t\nincrement next_to_alloc.\n\nThe ice_reuse_rx_page() assumes that the next_to_alloc has been incremented\nproperly, and that it always points to a buffer with a NULL page. Since\nthis function doesn\u0026apos;t check, it will happily recycle a page over the top\nof the next_to_alloc buffer, losing track of the old page.\n\nNote that this leak only occurs for multi-buffer frames. The\nice_put_rx_mbuf() function always handles at least one buffer, so a\nsingle-buffer frame will always get handled correctly. It is not clear\nprecisely why the hardware hands us descriptors with a size of 0 sometimes,\nbut it happens somewhat regularly with \u0026quot;jumbo frames\u0026quot; used by 9K MTU.\n\nTo fix ice_put_rx_mbuf(), we need to make sure to call ice_put_rx_buf() on\nall buffers between first_desc and next_to_clean. Borrow the logic of a\nsimilar function in i40e used for this same purpose. Use the same logic\nalso in ice_get_pgcnts().\n\nInstead of iterating over just the number of fragments, use a loop which\niterates until the current index reaches to the next_to_clean element just\npast the current frame. Unlike i40e, the ice_put_rx_mbuf() function does\ncall ice_put_rx_buf() on the last buffer of the frame indicating the end of\npacket.\n\nFor non-linear (multi-buffer) frames, we need to take care when adjusting\nthe pagecnt_bias. An XDP program might release fragments from the tail of\nthe frame, in which case that fragment page is already released. Only\nupdate the pagecnt_bias for the first descriptor and fragments still\nremaining post-XDP program. Take care to only access the shared info for\nfragmented buffers, as this avoids a significant cache miss.\n\nThe xdp_xmit value only needs to be updated if an XDP program is run, and\nonly once per packet. Drop the xdp_xmit pointer argument from\nice_put_rx_mbuf(). Instead, set xdp_xmit in the ice_clean_rx_irq() function\ndirectly. This avoids needing to pass the argument and avoids an extra\nbit-wise OR for each buffer in the frame.\n\nMove the increment of the ntc local variable to ensure its updated *before*\nall calls to ice_get_pgcnts() or ice_put_rx_mbuf(), as the loop logic\nrequires the index of the element just after the current frame.\n\nNow that we use an index pointer in the ring to identify the packet, we no\nlonger need to track or cache the number of fragments in the rx_ring.(CVE-2025-39948)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nfbcon: Set fb_display[i]-\u0026gt;mode to NULL when the mode is released\n\nRecently, we discovered the following issue through syzkaller:\n\nBUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0\nRead of size 4 at addr ff11000001b3c69c by task syz.xxx\n...\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0xab/0xe0\n print_address_description.constprop.0+0x2c/0x390\n print_report+0xb9/0x280\n kasan_report+0xb8/0xf0\n fb_mode_is_equal+0x285/0x2f0\n fbcon_mode_deleted+0x129/0x180\n fb_set_var+0xe7f/0x11d0\n do_fb_ioctl+0x6a0/0x750\n fb_ioctl+0xe0/0x140\n __x64_sys_ioctl+0x193/0x210\n do_syscall_64+0x5f/0x9c0\n entry_SYSCALL_64_after_hwframe+0x76/0x7e\n\nBased on experimentation and analysis, during framebuffer unregistration,\nonly the memory of fb_info-\u0026gt;modelist is freed, without setting the\ncorresponding fb_display[i]-\u0026gt;mode to NULL for the freed modes. This leads\nto UAF issues during subsequent accesses. Here\u0026apos;s an example of reproduction\nsteps:\n1. With /dev/fb0 already registered in the system, load a kernel module\n   to register a new device /dev/fb1;\n2. Set fb1\u0026apos;s mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP);\n3. Switch console from fb to VGA (to allow normal rmmod of the ko);\n4. Unload the kernel module, at this point fb1\u0026apos;s modelist is freed, leaving\n   a wild pointer in fb_display[];\n5. Trigger the bug via system calls through fb0 attempting to delete a mode\n   from fb0.\n\nAdd a check in do_unregister_framebuffer(): if the mode to be freed exists\nin fb_display[], set the corresponding mode pointer to NULL.(CVE-2025-40323)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/sched: Fix deadlock in drm_sched_entity_kill_jobs_cb\n\nThe Mesa issue referenced below pointed out a possible deadlock:\n\n[ 1231.611031]  Possible interrupt unsafe locking scenario:\n\n[ 1231.611033]        CPU0                    CPU1\n[ 1231.611034]        ----                    ----\n[ 1231.611035]   lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611038]                                local_irq_disable();\n[ 1231.611039]                                lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611041]                                lock(\u0026amp;xa-\u0026gt;xa_lock#17);\n[ 1231.611044]   \u0026lt;Interrupt\u0026gt;\n[ 1231.611045]     lock(\u0026amp;fence-\u0026gt;lock);\n[ 1231.611047]\n                *** DEADLOCK ***\n\nIn this example, CPU0 would be any function accessing job-\u0026gt;dependencies\nthrough the xa_* functions that don\u0026apos;t disable interrupts (eg:\ndrm_sched_job_add_dependency(), drm_sched_entity_kill_jobs_cb()).\n\nCPU1 is executing drm_sched_entity_kill_jobs_cb() as a fence signalling\ncallback so in an interrupt context. It will deadlock when trying to\ngrab the xa_lock which is already held by CPU0.\n\nReplacing all xa_* usage by their xa_*_irq counterparts would fix\nthis issue, but Christian pointed out another issue: dma_fence_signal\ntakes fence.lock and so does dma_fence_add_callback.\n\n  dma_fence_signal() // locks f1.lock\n  -\u0026gt; drm_sched_entity_kill_jobs_cb()\n  -\u0026gt; foreach dependencies\n     -\u0026gt; dma_fence_add_callback() // locks f2.lock\n\nThis will deadlock if f1 and f2 share the same spinlock.\n\nTo fix both issues, the code iterating on dependencies and re-arming them\nis moved out to drm_sched_entity_kill_jobs_work().\n\n[phasta: commit message nits](CVE-2025-40329)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: qmi_wwan: initialize MAC header offset in qmimux_rx_fixup\n\nRaw IP packets have no MAC header, leaving skb-\u0026gt;mac_header uninitialized.\nThis can trigger kernel panics on ARM64 when xfrm or other subsystems\naccess the offset due to strict alignment checks.\n\nInitialize the MAC header to prevent such crashes.\n\nThis can trigger kernel panics on ARM when running IPsec over the\nqmimux0 interface.\n\nExample trace:\n\n    Internal error: Oops: 000000009600004f [#1] SMP\n    CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Not tainted 6.12.34-gbe78e49cb433 #1\n    Hardware name: LS1028A RDB Board (DT)\n    pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n    pc : xfrm_input+0xde8/0x1318\n    lr : xfrm_input+0x61c/0x1318\n    sp : ffff800080003b20\n    Call trace:\n     xfrm_input+0xde8/0x1318\n     xfrm6_rcv+0x38/0x44\n     xfrm6_esp_rcv+0x48/0xa8\n     ip6_protocol_deliver_rcu+0x94/0x4b0\n     ip6_input_finish+0x44/0x70\n     ip6_input+0x44/0xc0\n     ipv6_rcv+0x6c/0x114\n     __netif_receive_skb_one_core+0x5c/0x8c\n     __netif_receive_skb+0x18/0x60\n     process_backlog+0x78/0x17c\n     __napi_poll+0x38/0x180\n     net_rx_action+0x168/0x2f0(CVE-2025-68192)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: imon: make send_packet() more robust\n\nsyzbot is reporting that imon has three problems which result in\nhung tasks due to forever holding device lock [1].\n\nFirst problem is that when usb_rx_callback_intf0() once got -EPROTO error\nafter ictx-\u0026gt;dev_present_intf0 became true, usb_rx_callback_intf0()\nresubmits urb after printk(), and resubmitted urb causes\nusb_rx_callback_intf0() to again get -EPROTO error. This results in\nprintk() flooding (RCU stalls).\n\nAlan Stern commented [2] that\n\n  In theory it\u0026apos;s okay to resubmit _if_ the driver has a robust\n  error-recovery scheme (such as giving up after some fixed limit on the\n  number of errors or after some fixed time has elapsed, perhaps with a\n  time delay to prevent a flood of errors).  Most drivers don\u0026apos;t bother to\n  do this; they simply give up right away.  This makes them more\n  vulnerable to short-term noise interference during USB transfers, but in\n  reality such interference is quite rare.  There\u0026apos;s nothing really wrong\n  with giving up right away.\n\nbut imon has a poor error-recovery scheme which just retries forever;\nthis behavior should be fixed.\n\nSince I\u0026apos;m not sure whether it is safe for imon users to give up upon any\nerror code, this patch takes care of only union of error codes chosen from\nmodules in drivers/media/rc/ directory which handle -EPROTO error (i.e.\nir_toy, mceusb and igorplugusb).\n\nSecond problem is that when usb_rx_callback_intf0() once got -EPROTO error\nbefore ictx-\u0026gt;dev_present_intf0 becomes true, usb_rx_callback_intf0() always\nresubmits urb due to commit 8791d63af0cf (\u0026quot;[media] imon: don\u0026apos;t wedge\nhardware after early callbacks\u0026quot;). Move the ictx-\u0026gt;dev_present_intf0 test\nintroduced by commit 6f6b90c9231a (\u0026quot;[media] imon: don\u0026apos;t parse scancodes\nuntil intf configured\u0026quot;) to immediately before imon_incoming_packet(), or\nthe first problem explained above happens without printk() flooding (i.e.\nhung task).\n\nThird problem is that when usb_rx_callback_intf0() is not called for some\nreason (e.g. flaky hardware; the reproducer for this problem sometimes\nprevents usb_rx_callback_intf0() from being called),\nwait_for_completion_interruptible() in send_packet() never returns (i.e.\nhung task). As a workaround for such situation, change send_packet() to\nwait for completion with timeout of 10 seconds.(CVE-2025-68194)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npmdomain: arm: scmi: Fix genpd leak on provider registration failure\n\nIf of_genpd_add_provider_onecell() fails during probe, the previously\ncreated generic power domains are not removed, leading to a memory leak\nand potential kernel crash later in genpd_debug_add().\n\nAdd proper error handling to unwind the initialized domains before\nreturning from probe to ensure all resources are correctly released on\nfailure.\n\nExample crash trace observed without this fix:\n\n  | Unable to handle kernel paging request at virtual address fffffffffffffc70\n  | CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.18.0-rc1 #405 PREEMPT\n  | Hardware name: ARM LTD ARM Juno Development Platform/ARM Juno Development Platform\n  | pstate: 00000005 (nzcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)\n  | pc : genpd_debug_add+0x2c/0x160\n  | lr : genpd_debug_init+0x74/0x98\n  | Call trace:\n  |  genpd_debug_add+0x2c/0x160 (P)\n  |  genpd_debug_init+0x74/0x98\n  |  do_one_initcall+0xd0/0x2d8\n  |  do_initcall_level+0xa0/0x140\n  |  do_initcalls+0x60/0xa8\n  |  do_basic_setup+0x28/0x40\n  |  kernel_init_freeable+0xe8/0x170\n  |  kernel_init+0x2c/0x140\n  |  ret_from_fork+0x10/0x20(CVE-2025-68204)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmlx5: Fix default values in create CQ\n\nCurrently, CQs without a completion function are assigned the\nmlx5_add_cq_to_tasklet function by default. This is problematic since\nonly user CQs created through the mlx5_ib driver are intended to use\nthis function.\n\nAdditionally, all CQs that will use doorbells instead of polling for\ncompletions must call mlx5_cq_arm. However, the default CQ creation flow\nleaves a valid value in the CQ\u0026apos;s arm_db field, allowing FW to send\ninterrupts to polling-only CQs in certain corner cases.\n\nThese two factors would allow a polling-only kernel CQ to be triggered\nby an EQ interrupt and call a completion function intended only for user\nCQs, causing a null pointer exception.\n\nSome areas in the driver have prevented this issue with one-off fixes\nbut did not address the root cause.\n\nThis patch fixes the described issue by adding defaults to the create CQ\nflow. It adds a default dummy completion function to protect against\nnull pointer exceptions, and it sets an invalid command sequence number\nby default in kernel CQs to prevent the FW from sending an interrupt to\nthe CQ until it is armed. User CQs are responsible for their own\ninitialization values.\n\nCallers of mlx5_core_create_cq are responsible for changing the\ncompletion function and arming the CQ per their needs.(CVE-2025-68209)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nksm: use range-walk function to jump over holes in scan_get_next_rmap_item\n\nCurrently, scan_get_next_rmap_item() walks every page address in a VMA to\nlocate mergeable pages.  This becomes highly inefficient when scanning\nlarge virtual memory areas that contain mostly unmapped regions, causing\nksmd to use large amount of cpu without deduplicating much pages.\n\nThis patch replaces the per-address lookup with a range walk using\nwalk_page_range().  The range walker allows KSM to skip over entire\nunmapped holes in a VMA, avoiding unnecessary lookups.  This problem was\npreviously discussed in [1].\n\nConsider the following test program which creates a 32 TiB mapping in the\nvirtual address space but only populates a single page:\n\n#include \u0026lt;unistd.h\u0026gt;\n#include \u0026lt;stdio.h\u0026gt;\n#include \u0026lt;sys/mman.h\u0026gt;\n\n/* 32 TiB */\nconst size_t size = 32ul * 1024 * 1024 * 1024 * 1024;\n\nint main() {\n        char *area = mmap(NULL, size, PROT_READ | PROT_WRITE,\n                          MAP_NORESERVE | MAP_PRIVATE | MAP_ANON, -1, 0);\n\n        if (area == MAP_FAILED) {\n                perror(\u0026quot;mmap() failed\\n\u0026quot;);\n                return -1;\n        }\n\n        /* Populate a single page such that we get an anon_vma. */\n        *area = 0;\n\n        /* Enable KSM. */\n        madvise(area, size, MADV_MERGEABLE);\n        pause();\n        return 0;\n}\n\n$ ./ksm-sparse  \u0026amp;\n$ echo 1 \u0026gt; /sys/kernel/mm/ksm/run \n\nWithout this patch ksmd uses 100% of the cpu for a long time (more then 1\nhour in my test machine) scanning all the 32 TiB virtual address space\nthat contain only one mapped page.  This makes ksmd essentially deadlocked\nnot able to deduplicate anything of value.  With this patch ksmd walks\nonly the one mapped page and skips the rest of the 32 TiB virtual address\nspace, making the scan fast using little cpu.(CVE-2025-68211)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/mempool: fix poisoning order\u0026gt;0 pages with HIGHMEM\n\nThe kernel test has reported:\n\n  BUG: unable to handle page fault for address: fffba000\n  #PF: supervisor write access in kernel mode\n  #PF: error_code(0x0002) - not-present page\n  *pde = 03171067 *pte = 00000000\n  Oops: Oops: 0002 [#1]\n  CPU: 0 UID: 0 PID: 1 Comm: swapper/0 Tainted: G                T   6.18.0-rc2-00031-gec7f31b2a2d3 #1 NONE  a1d066dfe789f54bc7645c7989957d2bdee593ca\n  Tainted: [T]=RANDSTRUCT\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014\n  EIP: memset (arch/x86/include/asm/string_32.h:168 arch/x86/lib/memcpy_32.c:17)\n  Code: a5 8b 4d f4 83 e1 03 74 02 f3 a4 83 c4 04 5e 5f 5d 2e e9 73 41 01 00 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 89 c6 89 d0 89 f7 \u0026lt;f3\u0026gt; aa 89 f0 5e 5f 5d 2e e9 53 41 01 00 cc cc cc 55 89 e5 53 57 56\n  EAX: 0000006b EBX: 00000015 ECX: 001fefff EDX: 0000006b\n  ESI: fffb9000 EDI: fffba000 EBP: c611fbf0 ESP: c611fbe8\n  DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068 EFLAGS: 00010287\n  CR0: 80050033 CR2: fffba000 CR3: 0316e000 CR4: 00040690\n  Call Trace:\n   poison_element (mm/mempool.c:83 mm/mempool.c:102)\n   mempool_init_node (mm/mempool.c:142 mm/mempool.c:226)\n   mempool_init_noprof (mm/mempool.c:250 (discriminator 1))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   bio_integrity_initfn (block/bio-integrity.c:483 (discriminator 8))\n   ? mempool_alloc_pages (mm/mempool.c:640)\n   do_one_initcall (init/main.c:1283)\n\nChristoph found out this is due to the poisoning code not dealing\nproperly with CONFIG_HIGHMEM because only the first page is mapped but\nthen the whole potentially high-order page is accessed.\n\nWe could give up on HIGHMEM here, but it\u0026apos;s straightforward to fix this\nwith a loop that\u0026apos;s mapping, poisoning or checking and unmapping\nindividual pages.(CVE-2025-68231)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmtdchar: fix integer overflow in read/write ioctls\n\nThe \u0026quot;req.start\u0026quot; and \u0026quot;req.len\u0026quot; variables are u64 values that come from the\nuser at the start of the function.  We mask away the high 32 bits of\n\u0026quot;req.len\u0026quot; so that\u0026apos;s capped at U32_MAX but the \u0026quot;req.start\u0026quot; variable can go\nup to U64_MAX which means that the addition can still integer overflow.\n\nUse check_add_overflow() to fix this bug.(CVE-2025-68237)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nusb: gadget: udc: fix use-after-free in usb_gadget_state_work\n\nA race condition during gadget teardown can lead to a use-after-free\nin usb_gadget_state_work(), as reported by KASAN:\n\n  BUG: KASAN: invalid-access in sysfs_notify+0x2c/0xd0\n  Workqueue: events usb_gadget_state_work\n\nThe fundamental race occurs because a concurrent event (e.g., an\ninterrupt) can call usb_gadget_set_state() and schedule gadget-\u0026gt;work\nat any time during the cleanup process in usb_del_gadget().\n\nCommit 399a45e5237c (\u0026quot;usb: gadget: core: flush gadget workqueue after\ndevice removal\u0026quot;) attempted to fix this by moving flush_work() to after\ndevice_del(). However, this does not fully solve the race, as a new\nwork item can still be scheduled *after* flush_work() completes but\nbefore the gadget\u0026apos;s memory is freed, leading to the same use-after-free.\n\nThis patch fixes the race condition robustly by introducing a \u0026apos;teardown\u0026apos;\nflag and a \u0026apos;state_lock\u0026apos; spinlock to the usb_gadget struct. The flag is\nset during cleanup in usb_del_gadget() *before* calling flush_work() to\nprevent any new work from being scheduled once cleanup has commenced.\nThe scheduling site, usb_gadget_set_state(), now checks this flag under\nthe lock before queueing the work, thus safely closing the race window.(CVE-2025-68282)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/huge_memory: fix NULL pointer deference when splitting folio\n\nCommit c010d47f107f (\u0026quot;mm: thp: split huge page to any lower order pages\u0026quot;)\nintroduced an early check on the folio\u0026apos;s order via mapping-\u0026gt;flags before\nproceeding with the split work.\n\nThis check introduced a bug: for shmem folios in the swap cache and\ntruncated folios, the mapping pointer can be NULL.  Accessing\nmapping-\u0026gt;flags in this state leads directly to a NULL pointer dereference.\n\nThis commit fixes the issue by moving the check for mapping != NULL before\nany attempt to access mapping-\u0026gt;flags.(CVE-2025-68293)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nx86/CPU/AMD: Add RDSEED fix for Zen5\n\nThere\u0026apos;s an issue with RDSEED\u0026apos;s 16-bit and 32-bit register output\nvariants on Zen5 which return a random value of 0 \u0026quot;at a rate inconsistent\nwith randomness while incorrectly signaling success (CF=1)\u0026quot;. Search the\nweb for AMD-SB-7055 for more detail.\n\nAdd a fix glue which checks microcode revisions.\n\n  [ bp: Add microcode revisions checking, rewrite. ](CVE-2025-68313)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ninet: frags: flush pending skbs in fqdir_pre_exit()\n\nWe have been seeing occasional deadlocks on pernet_ops_rwsem since\nSeptember in NIPA. The stuck task was usually modprobe (often loading\na driver like ipvlan), trying to take the lock as a Writer.\nlockdep does not track readers for rwsems so the read wasn\u0026apos;t obvious\nfrom the reports.\n\nOn closer inspection the Reader holding the lock was conntrack looping\nforever in nf_conntrack_cleanup_net_list(). Based on past experience\nwith occasional NIPA crashes I looked thru the tests which run before\nthe crash and noticed that the crash follows ip_defrag.sh. An immediate\nred flag. Scouring thru (de)fragmentation queues reveals skbs sitting\naround, holding conntrack references.\n\nThe problem is that since conntrack depends on nf_defrag_ipv6,\nnf_defrag_ipv6 will load first. Since nf_defrag_ipv6 loads first its\nnetns exit hooks run _after_ conntrack\u0026apos;s netns exit hook.\n\nFlush all fragment queue SKBs during fqdir_pre_exit() to release\nconntrack references before conntrack cleanup runs. Also flush\nthe queues in timer expiry handlers when they discover fqdir-\u0026gt;dead\nis set, in case packet sneaks in while we\u0026apos;re running the pre_exit\nflush.\n\nThe commit under Fixes is not exactly the culprit, but I think\npreviously the timer firing would eventually unblock the spinning\nconntrack.(CVE-2025-68768)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: openvswitch: fix middle attribute validation in push_nsh() action\n\nThe push_nsh() action structure looks like this:\n\n OVS_ACTION_ATTR_PUSH_NSH(OVS_KEY_ATTR_NSH(OVS_NSH_KEY_ATTR_BASE,...))\n\nThe outermost OVS_ACTION_ATTR_PUSH_NSH attribute is OK\u0026apos;ed by the\nnla_for_each_nested() inside __ovs_nla_copy_actions().  The innermost\nOVS_NSH_KEY_ATTR_BASE/MD1/MD2 are OK\u0026apos;ed by the nla_for_each_nested()\ninside nsh_key_put_from_nlattr().  But nothing checks if the attribute\nin the middle is OK.  We don\u0026apos;t even check that this attribute is the\nOVS_KEY_ATTR_NSH.  We just do a double unwrap with a pair of nla_data()\ncalls - first time directly while calling validate_push_nsh() and the\nsecond time as part of the nla_for_each_nested() macro, which isn\u0026apos;t\nsafe, potentially causing invalid memory access if the size of this\nattribute is incorrect.  The failure may not be noticed during\nvalidation due to larger netlink buffer, but cause trouble later during\naction execution where the buffer is allocated exactly to the size:\n\n BUG: KASAN: slab-out-of-bounds in nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n Read of size 184 at addr ffff88816459a634 by task a.out/22624\n\n CPU: 8 UID: 0 PID: 22624 6.18.0-rc7+ #115 PREEMPT(voluntary)\n Call Trace:\n  \u0026lt;TASK\u0026gt;\n  dump_stack_lvl+0x51/0x70\n  print_address_description.constprop.0+0x2c/0x390\n  kasan_report+0xdd/0x110\n  kasan_check_range+0x35/0x1b0\n  __asan_memcpy+0x20/0x60\n  nsh_hdr_from_nlattr+0x1dd/0x6a0 [openvswitch]\n  push_nsh+0x82/0x120 [openvswitch]\n  do_execute_actions+0x1405/0x2840 [openvswitch]\n  ovs_execute_actions+0xd5/0x3b0 [openvswitch]\n  ovs_packet_cmd_execute+0x949/0xdb0 [openvswitch]\n  genl_family_rcv_msg_doit+0x1d6/0x2b0\n  genl_family_rcv_msg+0x336/0x580\n  genl_rcv_msg+0x9f/0x130\n  netlink_rcv_skb+0x11f/0x370\n  genl_rcv+0x24/0x40\n  netlink_unicast+0x73e/0xaa0\n  netlink_sendmsg+0x744/0xbf0\n  __sys_sendto+0x3d6/0x450\n  do_syscall_64+0x79/0x2c0\n  entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  \u0026lt;/TASK\u0026gt;\n\nLet\u0026apos;s add some checks that the attribute is properly sized and it\u0026apos;s\nthe only one attribute inside the action.  Technically, there is no\nreal reason for OVS_KEY_ATTR_NSH to be there, as we know that we\u0026apos;re\npushing an NSH header already, it just creates extra nesting, but\nthat\u0026apos;s how uAPI works today.  So, keeping as it is.(CVE-2025-68785)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmedia: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()\n\nrlen value is a user-controlled value, but dtv5100_i2c_msg() does not\ncheck the size of the rlen value. Therefore, if it is set to a value\nlarger than sizeof(st-\u0026gt;data), an out-of-bounds vuln occurs for st-\u0026gt;data.\n\nTherefore, we need to add proper range checking to prevent this vuln.(CVE-2025-68819)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nInput: alps - fix use-after-free bugs caused by dev3_register_work\n\nThe dev3_register_work delayed work item is initialized within\nalps_reconnect() and scheduled upon receipt of the first bare\nPS/2 packet from an external PS/2 device connected to the ALPS\ntouchpad. During device detachment, the original implementation\ncalls flush_workqueue() in psmouse_disconnect() to ensure\ncompletion of dev3_register_work. However, the flush_workqueue()\nin psmouse_disconnect() only blocks and waits for work items that\nwere already queued to the workqueue prior to its invocation. Any\nwork items submitted after flush_workqueue() is called are not\nincluded in the set of tasks that the flush operation awaits.\nThis means that after flush_workqueue() has finished executing,\nthe dev3_register_work could still be scheduled. Although the\npsmouse state is set to PSMOUSE_CMD_MODE in psmouse_disconnect(),\nthe scheduling of dev3_register_work remains unaffected.\n\nThe race condition can occur as follows:\n\nCPU 0 (cleanup path)     | CPU 1 (delayed work)\npsmouse_disconnect()     |\n  psmouse_set_state()    |\n  flush_workqueue()      | alps_report_bare_ps2_packet()\n  alps_disconnect()      |   psmouse_queue_work()\n    kfree(priv); // FREE | alps_register_bare_ps2_mouse()\n                         |   priv = container_of(work...); // USE\n                         |   priv-\u0026gt;dev3 // USE\n\nAdd disable_delayed_work_sync() in alps_disconnect() to ensure\nthat dev3_register_work is properly canceled and prevented from\nexecuting after the alps_data structure has been deallocated.\n\nThis bug is identified by static analysis.(CVE-2025-68822)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to avoid potential deadlock\n\nAs Jiaming Zhang and syzbot reported, there is potential deadlock in\nf2fs as below:\n\nChain exists of:\n  \u0026amp;sbi-\u0026gt;cp_rwsem --\u0026gt; fs_reclaim --\u0026gt; sb_internal#2\n\n Possible unsafe locking scenario:\n\n       CPU0                    CPU1\n       ----                    ----\n  rlock(sb_internal#2);\n                               lock(fs_reclaim);\n                               lock(sb_internal#2);\n  rlock(\u0026amp;sbi-\u0026gt;cp_rwsem);\n\n *** DEADLOCK ***\n\n3 locks held by kswapd0/73:\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: balance_pgdat mm/vmscan.c:7015 [inline]\n #0: ffffffff8e247a40 (fs_reclaim){+.+.}-{0:0}, at: kswapd+0x951/0x2800 mm/vmscan.c:7389\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_trylock_shared fs/super.c:562 [inline]\n #1: ffff8880118400e0 (\u0026amp;type-\u0026gt;s_umount_key#50){.+.+}-{4:4}, at: super_cache_scan+0x91/0x4b0 fs/super.c:197\n #2: ffff888011840610 (sb_internal#2){.+.+}-{0:0}, at: f2fs_evict_inode+0x8d9/0x1b60 fs/f2fs/inode.c:890\n\nstack backtrace:\nCPU: 0 UID: 0 PID: 73 Comm: kswapd0 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nCall Trace:\n \u0026lt;TASK\u0026gt;\n dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120\n print_circular_bug+0x2ee/0x310 kernel/locking/lockdep.c:2043\n check_noncircular+0x134/0x160 kernel/locking/lockdep.c:2175\n check_prev_add kernel/locking/lockdep.c:3165 [inline]\n check_prevs_add kernel/locking/lockdep.c:3284 [inline]\n validate_chain+0xb9b/0x2140 kernel/locking/lockdep.c:3908\n __lock_acquire+0xab9/0xd20 kernel/locking/lockdep.c:5237\n lock_acquire+0x120/0x360 kernel/locking/lockdep.c:5868\n down_read+0x46/0x2e0 kernel/locking/rwsem.c:1537\n f2fs_down_read fs/f2fs/f2fs.h:2278 [inline]\n f2fs_lock_op fs/f2fs/f2fs.h:2357 [inline]\n f2fs_do_truncate_blocks+0x21c/0x10c0 fs/f2fs/file.c:791\n f2fs_truncate_blocks+0x10a/0x300 fs/f2fs/file.c:867\n f2fs_truncate+0x489/0x7c0 fs/f2fs/file.c:925\n f2fs_evict_inode+0x9f2/0x1b60 fs/f2fs/inode.c:897\n evict+0x504/0x9c0 fs/inode.c:810\n f2fs_evict_inode+0x1dc/0x1b60 fs/f2fs/inode.c:853\n evict+0x504/0x9c0 fs/inode.c:810\n dispose_list fs/inode.c:852 [inline]\n prune_icache_sb+0x21b/0x2c0 fs/inode.c:1000\n super_cache_scan+0x39b/0x4b0 fs/super.c:224\n do_shrink_slab+0x6ef/0x1110 mm/shrinker.c:437\n shrink_slab_memcg mm/shrinker.c:550 [inline]\n shrink_slab+0x7ef/0x10d0 mm/shrinker.c:628\n shrink_one+0x28a/0x7c0 mm/vmscan.c:4955\n shrink_many mm/vmscan.c:5016 [inline]\n lru_gen_shrink_node mm/vmscan.c:5094 [inline]\n shrink_node+0x315d/0x3780 mm/vmscan.c:6081\n kswapd_shrink_node mm/vmscan.c:6941 [inline]\n balance_pgdat mm/vmscan.c:7124 [inline]\n kswapd+0x147c/0x2800 mm/vmscan.c:7389\n kthread+0x70e/0x8a0 kernel/kthread.c:463\n ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158\n ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245\n \u0026lt;/TASK\u0026gt;\n\nThe root cause is deadlock among four locks as below:\n\nkswapd\n- fs_reclaim\t\t\t\t--- Lock A\n - shrink_one\n  - evict\n   - f2fs_evict_inode\n    - sb_start_intwrite\t\t\t--- Lock B\n\n- iput\n - evict\n  - f2fs_evict_inode\n   - sb_start_intwrite\t\t\t--- Lock B\n   - f2fs_truncate\n    - f2fs_truncate_blocks\n     - f2fs_do_truncate_blocks\n      - f2fs_lock_op\t\t\t--- Lock C\n\nioctl\n- f2fs_ioc_commit_atomic_write\n - f2fs_lock_op\t\t\t\t--- Lock C\n  - __f2fs_commit_atomic_write\n   - __replace_atomic_write_block\n    - f2fs_get_dnode_of_data\n     - __get_node_folio\n      - f2fs_check_nid_range\n       - f2fs_handle_error\n        - f2fs_record_errors\n         - f2fs_down_write\t\t--- Lock D\n\nopen\n- do_open\n - do_truncate\n  - security_inode_need_killpriv\n   - f2fs_getxattr\n    - lookup_all_xattrs\n     - f2fs_handle_error\n      - f2fs_record_errors\n       - f2fs_down_write\t\t--- Lock D\n        - f2fs_commit_super\n         - read_mapping_folio\n          - filemap_alloc_folio_noprof\n           - prepare_alloc_pages\n            - fs_reclaim_acquire\t--- Lock A\n\nIn order to a\n---truncated---(CVE-2025-71065)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsvcrdma: bound check rq_pages index in inline path\n\nsvc_rdma_copy_inline_range indexed rqstp-\u0026gt;rq_pages[rc_curpage] without\nverifying rc_curpage stays within the allocated page array. Add guards\nbefore the first use and after advancing to a new page.(CVE-2025-71068)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/ttm: Avoid NULL pointer deref for evicted BOs\n\nIt is possible for a BO to exist that is not currently associated with a\nresource, e.g. because it has been evicted.\n\nWhen devcoredump tries to read the contents of all BOs for dumping, we need\nto expect this as well -- in this case, ENODATA is recorded instead of the\nbuffer contents.(CVE-2025-71083)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/cm: Fix leaking the multicast GID table reference\n\nIf the CM ID is destroyed while the CM event for multicast creating is\nstill queued the cancel_work_sync() will prevent the work from running\nwhich also prevents destroying the ah_attr. This leaks a refcount and\ntriggers a WARN:\n\n   GID entry ref leak for dev syz1 index 2 ref=573\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 release_gid_table drivers/infiniband/core/cache.c:806 [inline]\n   WARNING: CPU: 1 PID: 655 at drivers/infiniband/core/cache.c:809 gid_table_release_one+0x284/0x3cc drivers/infiniband/core/cache.c:886\n\nDestroy the ah_attr after canceling the work, it is safe to call this\ntwice.(CVE-2025-71084)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nteam: fix check for port enabled in team_queue_override_port_prio_changed()\n\nThere has been a syzkaller bug reported recently with the following\ntrace:\n\nlist_del corruption, ffff888058bea080-\u0026gt;prev is LIST_POISON2 (dead000000000122)\n------------[ cut here ]------------\nkernel BUG at lib/list_debug.c:59!\nOops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\nCPU: 3 UID: 0 PID: 21246 Comm: syz.0.2928 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1 04/01/2014\nRIP: 0010:__list_del_entry_valid_or_report+0x13e/0x200 lib/list_debug.c:59\nCode: 48 c7 c7 e0 71 f0 8b e8 30 08 ef fc 90 0f 0b 48 89 ef e8 a5 02 55 fd 48 89 ea 48 89 de 48 c7 c7 40 72 f0 8b e8 13 08 ef fc 90 \u0026lt;0f\u0026gt; 0b 48 89 ef e8 88 02 55 fd 48 89 ea 48 b8 00 00 00 00 00 fc ff\nRSP: 0018:ffffc9000d49f370 EFLAGS: 00010286\nRAX: 000000000000004e RBX: ffff888058bea080 RCX: ffffc9002817d000\nRDX: 0000000000000000 RSI: ffffffff819becc6 RDI: 0000000000000005\nRBP: dead000000000122 R08: 0000000000000005 R09: 0000000000000000\nR10: 0000000080000000 R11: 0000000000000001 R12: ffff888039e9c230\nR13: ffff888058bea088 R14: ffff888058bea080 R15: ffff888055461480\nFS:  00007fbbcfe6f6c0(0000) GS:ffff8880d6d0a000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 000000110c3afcb0 CR3: 00000000382c7000 CR4: 0000000000352ef0\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __list_del_entry_valid include/linux/list.h:132 [inline]\n __list_del_entry include/linux/list.h:223 [inline]\n list_del_rcu include/linux/rculist.h:178 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:826 [inline]\n __team_queue_override_port_del drivers/net/team/team_core.c:821 [inline]\n team_queue_override_port_prio_changed drivers/net/team/team_core.c:883 [inline]\n team_priority_option_set+0x171/0x2f0 drivers/net/team/team_core.c:1534\n team_option_set drivers/net/team/team_core.c:376 [inline]\n team_nl_options_set_doit+0x8ae/0xe60 drivers/net/team/team_core.c:2653\n genl_family_rcv_msg_doit+0x209/0x2f0 net/netlink/genetlink.c:1115\n genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]\n genl_rcv_msg+0x55c/0x800 net/netlink/genetlink.c:1210\n netlink_rcv_skb+0x158/0x420 net/netlink/af_netlink.c:2552\n genl_rcv+0x28/0x40 net/netlink/genetlink.c:1219\n netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n netlink_unicast+0x5aa/0x870 net/netlink/af_netlink.c:1346\n netlink_sendmsg+0x8c8/0xdd0 net/netlink/af_netlink.c:1896\n sock_sendmsg_nosec net/socket.c:727 [inline]\n __sock_sendmsg net/socket.c:742 [inline]\n ____sys_sendmsg+0xa98/0xc70 net/socket.c:2630\n ___sys_sendmsg+0x134/0x1d0 net/socket.c:2684\n __sys_sendmsg+0x16d/0x220 net/socket.c:2716\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xfa0 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nThe problem is in this flow:\n1) Port is enabled, queue_id != 0, in qom_list\n2) Port gets disabled\n        -\u0026gt; team_port_disable()\n        -\u0026gt; team_queue_override_port_del()\n        -\u0026gt; del (removed from list)\n3) Port is disabled, queue_id != 0, not in any list\n4) Priority changes\n        -\u0026gt; team_queue_override_port_prio_changed()\n        -\u0026gt; checks: port disabled \u0026amp;\u0026amp; queue_id != 0\n        -\u0026gt; calls del - hits the BUG as it is removed already\n\nTo fix this, change the check in team_queue_override_port_prio_changed()\nso it returns early if port is not enabled.(CVE-2025-71091)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/core: Check for the presence of LS_NLA_TYPE_DGID correctly\n\nThe netlink response for RDMA_NL_LS_OP_IP_RESOLVE should always have a\nLS_NLA_TYPE_DGID attribute, it is invalid if it does not.\n\nUse the nl parsing logic properly and call nla_parse_deprecated() to fill\nthe nlattrs array and then directly index that array to get the data for\nthe DGID. Just fail if it is NULL.\n\nRemove the for loop searching for the nla, and squash the validation and\nparsing into one function.\n\nFixes an uninitialized read from the stack triggered by userspace if it\ndoes not provide the DGID to a kernel initiated RDMA_NL_LS_OP_IP_RESOLVE\nquery.\n\n    BUG: KMSAN: uninit-value in hex_byte_pack include/linux/hex.h:13 [inline]\n    BUG: KMSAN: uninit-value in ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     hex_byte_pack include/linux/hex.h:13 [inline]\n     ip6_string+0xef4/0x13a0 lib/vsprintf.c:1490\n     ip6_addr_string+0x18a/0x3e0 lib/vsprintf.c:1509\n     ip_addr_string+0x245/0xee0 lib/vsprintf.c:1633\n     pointer+0xc09/0x1bd0 lib/vsprintf.c:2542\n     vsnprintf+0xf8a/0x1bd0 lib/vsprintf.c:2930\n     vprintk_store+0x3ae/0x1530 kernel/printk/printk.c:2279\n     vprintk_emit+0x307/0xcd0 kernel/printk/printk.c:2426\n     vprintk_default+0x3f/0x50 kernel/printk/printk.c:2465\n     vprintk+0x36/0x50 kernel/printk/printk_safe.c:82\n     _printk+0x17e/0x1b0 kernel/printk/printk.c:2475\n     ib_nl_process_good_ip_rsep drivers/infiniband/core/addr.c:128 [inline]\n     ib_nl_handle_ip_res_resp+0x963/0x9d0 drivers/infiniband/core/addr.c:141\n     rdma_nl_rcv_msg drivers/infiniband/core/netlink.c:-1 [inline]\n     rdma_nl_rcv_skb drivers/infiniband/core/netlink.c:239 [inline]\n     rdma_nl_rcv+0xefa/0x11c0 drivers/infiniband/core/netlink.c:259\n     netlink_unicast_kernel net/netlink/af_netlink.c:1320 [inline]\n     netlink_unicast+0xf04/0x12b0 net/netlink/af_netlink.c:1346\n     netlink_sendmsg+0x10b3/0x1250 net/netlink/af_netlink.c:1896\n     sock_sendmsg_nosec net/socket.c:714 [inline]\n     __sock_sendmsg+0x333/0x3d0 net/socket.c:729\n     ____sys_sendmsg+0x7e0/0xd80 net/socket.c:2617\n     ___sys_sendmsg+0x271/0x3b0 net/socket.c:2671\n     __sys_sendmsg+0x1aa/0x300 net/socket.c:2703\n     __compat_sys_sendmsg net/compat.c:346 [inline]\n     __do_compat_sys_sendmsg net/compat.c:353 [inline]\n     __se_compat_sys_sendmsg net/compat.c:350 [inline]\n     __ia32_compat_sys_sendmsg+0xa4/0x100 net/compat.c:350\n     ia32_sys_call+0x3f6c/0x4310 arch/x86/include/generated/asm/syscalls_32.h:371\n     do_syscall_32_irqs_on arch/x86/entry/syscall_32.c:83 [inline]\n     __do_fast_syscall_32+0xb0/0x150 arch/x86/entry/syscall_32.c:306\n     do_fast_syscall_32+0x38/0x80 arch/x86/entry/syscall_32.c:331\n     do_SYSENTER_32+0x1f/0x30 arch/x86/entry/syscall_32.c:3(CVE-2025-71096)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: Fix reference count leak when using error routes with nexthop objects\n\nWhen a nexthop object is deleted, it is marked as dead and then\nfib_table_flush() is called to flush all the routes that are using the\ndead nexthop.\n\nThe current logic in fib_table_flush() is to only flush error routes\n(e.g., blackhole) when it is called as part of network namespace\ndismantle (i.e., with flush_all=true). Therefore, error routes are not\nflushed when their nexthop object is deleted:\n\n # ip link add name dummy1 up type dummy\n # ip nexthop add id 1 dev dummy1\n # ip route add 198.51.100.1/32 nhid 1\n # ip route add blackhole 198.51.100.2/32 nhid 1\n # ip nexthop del id 1\n # ip route show\n blackhole 198.51.100.2 nhid 1 dev dummy1\n\nAs such, they keep holding a reference on the nexthop object which in\nturn holds a reference on the nexthop device, resulting in a reference\ncount leak:\n\n # ip link del dev dummy1\n [   70.516258] unregister_netdevice: waiting for dummy1 to become free. Usage count = 2\n\nFix by flushing error routes when their nexthop is marked as dead.\n\nIPv6 does not suffer from this problem.(CVE-2025-71097)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nACPICA: Avoid walking the Namespace if start_node is NULL\n\nAlthough commit 0c9992315e73 (\u0026quot;ACPICA: Avoid walking the ACPI Namespace\nif it is not there\u0026quot;) fixed the situation when both start_node and\nacpi_gbl_root_node are NULL, the Linux kernel mainline now still crashed\non Honor Magicbook 14 Pro [1].\n\nThat happens due to the access to the member of parent_node in\nacpi_ns_get_next_node().  The NULL pointer dereference will always\nhappen, no matter whether or not the start_node is equal to\nACPI_ROOT_OBJECT, so move the check of start_node being NULL\nout of the if block.\n\nUnfortunately, all the attempts to contact Honor have failed, they\nrefused to provide any technical support for Linux.\n\nThe bad DSDT table\u0026apos;s dump could be found on GitHub [2].\n\nDMI: HONOR FMB-P/FMB-P-PCB, BIOS 1.13 05/08/2025\n\n[ rjw: Subject adjustment, changelog edits ](CVE-2025-71118)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nSUNRPC: svcauth_gss: avoid NULL deref on zero length gss_token in gss_read_proxy_verf\n\nA zero length gss_token results in pages == 0 and in_token-\u0026gt;pages[0]\nis NULL. The code unconditionally evaluates\npage_address(in_token-\u0026gt;pages[0]) for the initial memcpy, which can\ndereference NULL even when the copy length is 0. Guard the first\nmemcpy so it only runs when length \u0026gt; 0.(CVE-2025-71120)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nLoongArch: BPF: Sign extend kfunc call arguments\n\nThe kfunc calls are native calls so they should follow LoongArch calling\nconventions. Sign extend its arguments properly to avoid kernel panic.\nThis is done by adding a new emit_abi_ext() helper. The emit_abi_ext()\nhelper performs extension in place meaning a value already store in the\ntarget register (Note: this is different from the existing sign_extend()\nhelper and thus we can\u0026apos;t reuse it).(CVE-2025-71129)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/tilcdc: Fix removal actions in case of failed probe\n\nThe drm_kms_helper_poll_fini() and drm_atomic_helper_shutdown() helpers\nshould only be called when the device has been successfully registered.\nCurrently, these functions are called unconditionally in tilcdc_fini(),\nwhich causes warnings during probe deferral scenarios.\n\n[    7.972317] WARNING: CPU: 0 PID: 23 at drivers/gpu/drm/drm_atomic_state_helper.c:175 drm_atomic_helper_crtc_duplicate_state+0x60/0x68\n...\n[    8.005820]  drm_atomic_helper_crtc_duplicate_state from drm_atomic_get_crtc_state+0x68/0x108\n[    8.005858]  drm_atomic_get_crtc_state from drm_atomic_helper_disable_all+0x90/0x1c8\n[    8.005885]  drm_atomic_helper_disable_all from drm_atomic_helper_shutdown+0x90/0x144\n[    8.005911]  drm_atomic_helper_shutdown from tilcdc_fini+0x68/0xf8 [tilcdc]\n[    8.005957]  tilcdc_fini [tilcdc] from tilcdc_pdev_probe+0xb0/0x6d4 [tilcdc]\n\nFix this by rewriting the failed probe cleanup path using the standard\ngoto error handling pattern, which ensures that cleanup functions are\nonly called on successfully initialized resources. Additionally, remove\nthe now-unnecessary is_registered flag.(CVE-2025-71141)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndmaengine: stm32: dmamux: fix device leak on route allocation\n\nMake sure to drop the reference taken when looking up the DMA mux\nplatform device during route allocation.\n\nNote that holding a reference to a device does not prevent its driver\ndata from going away so there is no point in keeping the reference.(CVE-2025-71186)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: call ksmbd_session_rpc_close() on error path in create_smb2_pipe()\n\nWhen ksmbd_iov_pin_rsp() fails, we should call ksmbd_session_rpc_close().(CVE-2025-71220)\n\nIn the Linux kernel, a race condition vulnerability exists in the mmp_pdma driver. The vulnerability occurs in the mmp_pdma_residue() function which lacks proper locking mechanisms, potentially leading to use-after-free issues when accessing descriptor lists and descriptor contents.\n\nThe race condition occurs when multiple threads call tx_status() while the tasklet on another CPU is freeing completed descriptors. This issue can be reproduced when running dmatest on the same channel with multiple threads (threads_per_chan \u0026gt; 1).\n\nThe fix involves protecting the chain_running list iteration and descriptor access with the chan-\u0026gt;desc_lock spinlock.(CVE-2025-71221)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/server: fix refcount leak in smb2_open()\n\nWhen ksmbd_vfs_getattr() fails, the reference count of ksmbd_file\nmust be released.(CVE-2025-71223)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmd: suspend array while updating raid_disks via sysfs\n\nIn raid1_reshape(), freeze_array() is called before modifying the r1bio\nmemory pool (conf-\u0026gt;r1bio_pool) and conf-\u0026gt;raid_disks, and\nunfreeze_array() is called after the update is completed.\n\nHowever, freeze_array() only waits until nr_sync_pending and\n(nr_pending - nr_queued) of all buckets reaches zero. When an I/O error\noccurs, nr_queued is increased and the corresponding r1bio is queued to\neither retry_list or bio_end_io_list. As a result, freeze_array() may\nunblock before these r1bios are released.\n\nThis can lead to a situation where conf-\u0026gt;raid_disks and the mempool have\nalready been updated while queued r1bios, allocated with the old\nraid_disks value, are later released. Consequently, free_r1bio() may\naccess memory out of bounds in put_all_bios() and release r1bios of the\nwrong size to the new mempool, potentially causing issues with the\nmempool as well.\n\nSince only normal I/O might increase nr_queued while an I/O error occurs,\nsuspending the array avoids this issue.\n\nNote: Updating raid_disks via ioctl SET_ARRAY_INFO already suspends\nthe array. Therefore, we suspend the array when updating raid_disks\nvia sysfs to avoid this issue too.(CVE-2025-71225)\n\nIn the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Free sp in error path to fix system crash  System crash seen during load/unload test in a loop,  [61110.449331] qla2xxx [0000:27:00.0]-0042:0: Disabled MSI-X. [61110.467494](CVE-2025-71232)\n\nIn the Linux kernel, there is a race condition vulnerability in the SCSI qla2xxx driver. System crash was observed during load/unload loop testing. The root cause was a memory free operation occurring in interrupt context. When device discovery/fabric scan was in progress and module unload was issued setting the UNLOADING flag, work queue items could not be allocated and mapped memory had to be freed in interrupt context, leading to system crash.(CVE-2025-71235)\n\nA NULL pointer dereference vulnerability exists in the SCSI qla2xxx driver subsystem of the Linux kernel. When the system attempts to free associated memory in the qla_fab_async_scan function, it fails to validate whether the sp pointer is NULL, leading to kernel NULL pointer dereference and system crashes. This vulnerability can be exploited by attackers to cause denial of service.(CVE-2025-71236)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: sock: fix hardened usercopy panic in sock_recv_errqueue\n\nskbuff_fclone_cache was created without defining a usercopy region,\n[1] unlike skbuff_head_cache which properly whitelists the cb[] field.\n[2] This causes a usercopy BUG() when CONFIG_HARDENED_USERCOPY is\nenabled and the kernel attempts to copy sk_buff.cb data to userspace\nvia sock_recv_errqueue() -\u0026gt; put_cmsg().\n\nThe crash occurs when: 1. TCP allocates an skb using alloc_skb_fclone()\n   (from skbuff_fclone_cache) [1]\n2. The skb is cloned via skb_clone() using the pre-allocated fclone\n[3] 3. The cloned skb is queued to sk_error_queue for timestamp\nreporting 4. Userspace reads the error queue via recvmsg(MSG_ERRQUEUE)\n5. sock_recv_errqueue() calls put_cmsg() to copy serr-\u0026gt;ee from skb-\u0026gt;cb\n[4] 6. __check_heap_object() fails because skbuff_fclone_cache has no\n   usercopy whitelist [5]\n\nWhen cloned skbs allocated from skbuff_fclone_cache are used in the\nsocket error queue, accessing the sock_exterr_skb structure in skb-\u0026gt;cb\nvia put_cmsg() triggers a usercopy hardening violation:\n\n[    5.379589] usercopy: Kernel memory exposure attempt detected from SLUB object \u0026apos;skbuff_fclone_cache\u0026apos; (offset 296, size 16)!\n[    5.382796] kernel BUG at mm/usercopy.c:102!\n[    5.383923] Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI\n[    5.384903] CPU: 1 UID: 0 PID: 138 Comm: poc_put_cmsg Not tainted 6.12.57 #7\n[    5.384903] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014\n[    5.384903] RIP: 0010:usercopy_abort+0x6c/0x80\n[    5.384903] Code: 1a 86 51 48 c7 c2 40 15 1a 86 41 52 48 c7 c7 c0 15 1a 86 48 0f 45 d6 48 c7 c6 80 15 1a 86 48 89 c1 49 0f 45 f3 e8 84 27 88 ff \u0026lt;0f\u0026gt; 0b 490\n[    5.384903] RSP: 0018:ffffc900006f77a8 EFLAGS: 00010246\n[    5.384903] RAX: 000000000000006f RBX: ffff88800f0ad2a8 RCX: 1ffffffff0f72e74\n[    5.384903] RDX: 0000000000000000 RSI: 0000000000000004 RDI: ffffffff87b973a0\n[    5.384903] RBP: 0000000000000010 R08: 0000000000000000 R09: fffffbfff0f72e74\n[    5.384903] R10: 0000000000000003 R11: 79706f6372657375 R12: 0000000000000001\n[    5.384903] R13: ffff88800f0ad2b8 R14: ffffea00003c2b40 R15: ffffea00003c2b00\n[    5.384903] FS:  0000000011bc4380(0000) GS:ffff8880bf100000(0000) knlGS:0000000000000000\n[    5.384903] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[    5.384903] CR2: 000056aa3b8e5fe4 CR3: 000000000ea26004 CR4: 0000000000770ef0\n[    5.384903] PKRU: 55555554\n[    5.384903] Call Trace:\n[    5.384903]  \u0026lt;TASK\u0026gt;\n[    5.384903]  __check_heap_object+0x9a/0xd0\n[    5.384903]  __check_object_size+0x46c/0x690\n[    5.384903]  put_cmsg+0x129/0x5e0\n[    5.384903]  sock_recv_errqueue+0x22f/0x380\n[    5.384903]  tls_sw_recvmsg+0x7ed/0x1960\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? schedule+0x6d/0x270\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n[    5.384903]  ? mutex_unlock+0x81/0xd0\n[    5.384903]  ? __pfx_mutex_unlock+0x10/0x10\n[    5.384903]  ? __pfx_tls_sw_recvmsg+0x10/0x10\n[    5.384903]  ? _raw_spin_lock_irqsave+0x8f/0xf0\n[    5.384903]  ? _raw_read_unlock_irqrestore+0x20/0x40\n[    5.384903]  ? srso_alias_return_thunk+0x5/0xfbef5\n\nThe crash offset 296 corresponds to skb2-\u0026gt;cb within skbuff_fclones:\n  - sizeof(struct sk_buff) = 232 - offsetof(struct sk_buff, cb) = 40 -\n  offset of skb2.cb in fclones = 232 + 40 = 272 - crash offset 296 =\n  272 + 24 (inside sock_exterr_skb.ee)\n\nThis patch uses a local stack variable as a bounce buffer to avoid the hardened usercopy check failure.\n\n[1] https://elixir.bootlin.com/linux/v6.12.62/source/net/ipv4/tcp.c#L885\n[2] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5104\n[3] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5566\n[4] https://elixir.bootlin.com/linux/v6.12.62/source/net/core/skbuff.c#L5491\n[5] https://elixir.bootlin.com/linux/v6.12.62/source/mm/slub.c#L5719(CVE-2026-22977)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: fix memory leak in skb_segment_list for GRO packets\n\nWhen skb_segment_list() is called during packet forwarding, it handles\npackets that were aggregated by the GRO engine.\n\nHistorically, the segmentation logic in skb_segment_list assumes that\nindividual segments are split from a parent SKB and may need to carry\ntheir own socket memory accounting. Accordingly, the code transfers\ntruesize from the parent to the newly created segments.\n\nPrior to commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;), this\ntruesize subtraction in skb_segment_list() was valid because fragments\nstill carry a reference to the original socket.\n\nHowever, commit ed4cccef64c1 (\u0026quot;gro: fix ownership transfer\u0026quot;) changed\nthis behavior by ensuring that fraglist entries are explicitly\norphaned (skb-\u0026gt;sk = NULL) to prevent illegal orphaning later in the\nstack. This change meant that the entire socket memory charge remained\nwith the head SKB, but the corresponding accounting logic in\nskb_segment_list() was never updated.\n\nAs a result, the current code unconditionally adds each fragment\u0026apos;s\ntruesize to delta_truesize and subtracts it from the parent SKB. Since\nthe fragments are no longer charged to the socket, this subtraction\nresults in an effective under-count of memory when the head is freed.\nThis causes sk_wmem_alloc to remain non-zero, preventing socket\ndestruction and leading to a persistent memory leak.\n\nThe leak can be observed via KMEMLEAK when tearing down the networking\nenvironment:\n\nunreferenced object 0xffff8881e6eb9100 (size 2048):\n  comm \u0026quot;ping\u0026quot;, pid 6720, jiffies 4295492526\n  backtrace:\n    kmem_cache_alloc_noprof+0x5c6/0x800\n    sk_prot_alloc+0x5b/0x220\n    sk_alloc+0x35/0xa00\n    inet6_create.part.0+0x303/0x10d0\n    __sock_create+0x248/0x640\n    __sys_socket+0x11b/0x1d0\n\nSince skb_segment_list() is exclusively used for SKB_GSO_FRAGLIST\npackets constructed by GRO, the truesize adjustment is removed.\n\nThe call to skb_release_head_state() must be preserved. As documented in\ncommit cf673ed0e057 (\u0026quot;net: fix fraglist segmentation reference count\nleak\u0026quot;), it is still required to correctly drop references to SKB\nextensions that may be overwritten during __copy_skb_header().(CVE-2026-22979)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: prevent potential out-of-bounds reads in handle_auth_done()\n\nPerform an explicit bounds check on payload_len to avoid a possible\nout-of-bounds access in the callout.\n\n[ idryomov: changelog ](CVE-2026-22984)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make free_choose_arg_map() resilient to partial allocation\n\nfree_choose_arg_map() may dereference a NULL pointer if its caller fails\nafter a partial allocation.\n\nFor example, in decode_choose_args(), if allocation of arg_map-\u0026gt;args\nfails, execution jumps to the fail label and free_choose_arg_map() is\ncalled. Since arg_map-\u0026gt;size is updated to a non-zero value before memory\nallocation, free_choose_arg_map() will iterate over arg_map-\u0026gt;args and\ndereference a NULL pointer.\n\nTo prevent this potential NULL pointer dereference and make\nfree_choose_arg_map() more resilient, add checks for pointers before\niterating.(CVE-2026-22991)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet/sched: sch_qfq: do not free existing class in qfq_change_class()\n\nFixes qfq_change_class() error case.\n\ncl-\u0026gt;qdisc and cl should only be freed if a new class and qdisc\nwere allocated, or we risk various UAF.(CVE-2026-22999)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nip6_tunnel: use skb_vlan_inet_prepare() in __ip6_tnl_rcv()\n\nBlamed commit did not take care of VLAN encapsulations\nas spotted by syzbot [1].\n\nUse skb_vlan_inet_prepare() instead of pskb_inet_may_pull().\n\n[1]\n BUG: KMSAN: uninit-value in __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n BUG: KMSAN: uninit-value in INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n BUG: KMSAN: uninit-value in IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  __INET_ECN_decapsulate include/net/inet_ecn.h:253 [inline]\n  INET_ECN_decapsulate include/net/inet_ecn.h:275 [inline]\n  IP6_ECN_decapsulate+0x7a8/0x1fa0 include/net/inet_ecn.h:321\n  ip6ip6_dscp_ecn_decapsulate+0x16f/0x1b0 net/ipv6/ip6_tunnel.c:729\n  __ip6_tnl_rcv+0xed9/0x1b50 net/ipv6/ip6_tunnel.c:860\n  ip6_tnl_rcv+0xc3/0x100 net/ipv6/ip6_tunnel.c:903\n gre_rcv+0x1529/0x1b90 net/ipv6/ip6_gre.c:-1\n  ip6_protocol_deliver_rcu+0x1c89/0x2c60 net/ipv6/ip6_input.c:438\n  ip6_input_finish+0x1f4/0x4a0 net/ipv6/ip6_input.c:489\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ip6_input+0x9c/0x330 net/ipv6/ip6_input.c:500\n  ip6_mc_input+0x7ca/0xc10 net/ipv6/ip6_input.c:590\n  dst_input include/net/dst.h:474 [inline]\n  ip6_rcv_finish+0x958/0x990 net/ipv6/ip6_input.c:79\n  NF_HOOK include/linux/netfilter.h:318 [inline]\n  ipv6_rcv+0xf1/0x3c0 net/ipv6/ip6_input.c:311\n  __netif_receive_skb_one_core net/core/dev.c:6139 [inline]\n  __netif_receive_skb+0x1df/0xac0 net/core/dev.c:6252\n  netif_receive_skb_internal net/core/dev.c:6338 [inline]\n  netif_receive_skb+0x57/0x630 net/core/dev.c:6397\n  tun_rx_batched+0x1df/0x980 drivers/net/tun.c:1485\n  tun_get_user+0x5c0e/0x6c60 drivers/net/tun.c:1953\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nUninit was created at:\n  slab_post_alloc_hook mm/slub.c:4960 [inline]\n  slab_alloc_node mm/slub.c:5263 [inline]\n  kmem_cache_alloc_node_noprof+0x9e7/0x17a0 mm/slub.c:5315\n  kmalloc_reserve+0x13c/0x4b0 net/core/skbuff.c:586\n  __alloc_skb+0x805/0x1040 net/core/skbuff.c:690\n  alloc_skb include/linux/skbuff.h:1383 [inline]\n  alloc_skb_with_frags+0xc5/0xa60 net/core/skbuff.c:6712\n  sock_alloc_send_pskb+0xacc/0xc60 net/core/sock.c:2995\n  tun_alloc_skb drivers/net/tun.c:1461 [inline]\n  tun_get_user+0x1142/0x6c60 drivers/net/tun.c:1794\n  tun_chr_write_iter+0x3e9/0x5c0 drivers/net/tun.c:1999\n  new_sync_write fs/read_write.c:593 [inline]\n  vfs_write+0xbe2/0x15d0 fs/read_write.c:686\n  ksys_write fs/read_write.c:738 [inline]\n  __do_sys_write fs/read_write.c:749 [inline]\n  __se_sys_write fs/read_write.c:746 [inline]\n  __x64_sys_write+0x1fb/0x4d0 fs/read_write.c:746\n  x64_sys_call+0x30ab/0x3e70 arch/x86/include/generated/asm/syscalls_64.h:2\n  do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n  do_syscall_64+0xd3/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nCPU: 0 UID: 0 PID: 6465 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(none)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025(CVE-2026-23003)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv6: Fix use-after-free in inet6_addr_del().\n\nsyzbot reported use-after-free of inet6_ifaddr in\ninet6_addr_del(). [0]\n\nThe cited commit accidentally moved ipv6_del_addr() for\nmngtmpaddr before reading its ifp-\u0026gt;flags for temporary\naddresses in inet6_addr_del().\n\nLet\u0026apos;s move ipv6_del_addr() down to fix the UAF.\n\n[0]:\nBUG: KASAN: slab-use-after-free in inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\nRead of size 4 at addr ffff88807b89c86c by task syz.3.1618/9593\n\nCPU: 0 UID: 0 PID: 9593 Comm: syz.3.1618 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nCall Trace:\n \u0026lt;TASK\u0026gt;\n __dump_stack lib/dump_stack.c:94 [inline]\n dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120\n print_address_description mm/kasan/report.c:378 [inline]\n print_report+0xcd/0x630 mm/kasan/report.c:482\n kasan_report+0xe0/0x110 mm/kasan/report.c:595\n inet6_addr_del.constprop.0+0x67a/0x6b0 net/ipv6/addrconf.c:3117\n addrconf_del_ifaddr+0x11e/0x190 net/ipv6/addrconf.c:3181\n inet6_ioctl+0x1e5/0x2b0 net/ipv6/af_inet6.c:582\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\nRIP: 0033:0x7f164cf8f749\nCode: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 \u0026lt;48\u0026gt; 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48\nRSP: 002b:00007f164de64038 EFLAGS: 00000246 ORIG_RAX: 0000000000000010\nRAX: ffffffffffffffda RBX: 00007f164d1e5fa0 RCX: 00007f164cf8f749\nRDX: 0000200000000000 RSI: 0000000000008936 RDI: 0000000000000003\nRBP: 00007f164d013f91 R08: 0000000000000000 R09: 0000000000000000\nR10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000\nR13: 00007f164d1e6038 R14: 00007f164d1e5fa0 R15: 00007ffde15c8288\n \u0026lt;/TASK\u0026gt;\n\nAllocated by task 9593:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n poison_kmalloc_redzone mm/kasan/common.c:397 [inline]\n __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:414\n kmalloc_noprof include/linux/slab.h:957 [inline]\n kzalloc_noprof include/linux/slab.h:1094 [inline]\n ipv6_add_addr+0x4e3/0x2010 net/ipv6/addrconf.c:1120\n inet6_addr_add+0x256/0x9b0 net/ipv6/addrconf.c:3050\n addrconf_add_ifaddr+0x1fc/0x450 net/ipv6/addrconf.c:3160\n inet6_ioctl+0x103/0x2b0 net/ipv6/af_inet6.c:580\n sock_do_ioctl+0x118/0x280 net/socket.c:1254\n sock_ioctl+0x227/0x6b0 net/socket.c:1375\n vfs_ioctl fs/ioctl.c:51 [inline]\n __do_sys_ioctl fs/ioctl.c:597 [inline]\n __se_sys_ioctl fs/ioctl.c:583 [inline]\n __x64_sys_ioctl+0x18e/0x210 fs/ioctl.c:583\n do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]\n do_syscall_64+0xcd/0xf80 arch/x86/entry/syscall_64.c:94\n entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nFreed by task 6099:\n kasan_save_stack+0x33/0x60 mm/kasan/common.c:56\n kasan_save_track+0x14/0x30 mm/kasan/common.c:77\n kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:584\n poison_slab_object mm/kasan/common.c:252 [inline]\n __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284\n kasan_slab_free include/linux/kasan.h:234 [inline]\n slab_free_hook mm/slub.c:2540 [inline]\n slab_free_freelist_hook mm/slub.c:2569 [inline]\n slab_free_bulk mm/slub.c:6696 [inline]\n kmem_cache_free_bulk mm/slub.c:7383 [inline]\n kmem_cache_free_bulk+0x2bf/0x680 mm/slub.c:7362\n kfree_bulk include/linux/slab.h:830 [inline]\n kvfree_rcu_bulk+0x1b7/0x1e0 mm/slab_common.c:1523\n kvfree_rcu_drain_ready mm/slab_common.c:1728 [inline]\n kfree_rcu_monitor+0x1d0/0x2f0 mm/slab_common.c:1801\n process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257\n process_scheduled_works kernel/workqu\n---truncated---(CVE-2026-23010)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nipv4: ip_gre: make ipgre_header() robust\n\nAnalog to commit db5b4e39c4e6 (\u0026quot;ip6_gre: make ip6gre_header() robust\u0026quot;)\n\nOver the years, syzbot found many ways to crash the kernel\nin ipgre_header() [1].\n\nThis involves team or bonding drivers ability to dynamically\nchange their dev-\u0026gt;needed_headroom and/or dev-\u0026gt;hard_header_len\n\nIn this particular crash mld_newpack() allocated an skb\nwith a too small reserve/headroom, and by the time mld_sendpack()\nwas called, syzbot managed to attach an ipgre device.\n\n[1]\nskbuff: skb_under_panic: text:ffffffff89ea3cb7 len:2030915468 put:2030915372 head:ffff888058b43000 data:ffff887fdfa6e194 tail:0x120 end:0x6c0 dev:team0\n kernel BUG at net/core/skbuff.c:213 !\nOops: invalid opcode: 0000 [#1] SMP KASAN PTI\nCPU: 1 UID: 0 PID: 1322 Comm: kworker/1:9 Not tainted syzkaller #0 PREEMPT(full)\nHardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025\nWorkqueue: mld mld_ifc_work\n RIP: 0010:skb_panic+0x157/0x160 net/core/skbuff.c:213\nCall Trace:\n \u0026lt;TASK\u0026gt;\n  skb_under_panic net/core/skbuff.c:223 [inline]\n  skb_push+0xc3/0xe0 net/core/skbuff.c:2641\n  ipgre_header+0x67/0x290 net/ipv4/ip_gre.c:897\n  dev_hard_header include/linux/netdevice.h:3436 [inline]\n  neigh_connected_output+0x286/0x460 net/core/neighbour.c:1618\n  NF_HOOK_COND include/linux/netfilter.h:307 [inline]\n  ip6_output+0x340/0x550 net/ipv6/ip6_output.c:247\n  NF_HOOK+0x9e/0x380 include/linux/netfilter.h:318\n  mld_sendpack+0x8d4/0xe60 net/ipv6/mcast.c:1855\n  mld_send_cr net/ipv6/mcast.c:2154 [inline]\n  mld_ifc_work+0x83e/0xd60 net/ipv6/mcast.c:2693\n  process_one_work kernel/workqueue.c:3257 [inline]\n  process_scheduled_works+0xad1/0x1770 kernel/workqueue.c:3340\n  worker_thread+0x8a0/0xda0 kernel/workqueue.c:3421\n  kthread+0x711/0x8a0 kernel/kthread.c:463\n  ret_from_fork+0x510/0xa50 arch/x86/kernel/process.c:158\n  ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246(CVE-2026-23011)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: usb: pegasus: fix memory leak in update_eth_regs_async()\n\nWhen asynchronously writing to the device registers and if usb_submit_urb()\nfail, the code fail to release allocated to this point resources.(CVE-2026-23021)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nmm/page_alloc: prevent pcp corruption with SMP=n\n\nThe kernel test robot has reported:\n\n BUG: spinlock trylock failure on UP on CPU#0, kcompactd0/28\n  lock: 0xffff888807e35ef0, .magic: dead4ead, .owner: kcompactd0/28, .owner_cpu: 0\n CPU: 0 UID: 0 PID: 28 Comm: kcompactd0 Not tainted 6.18.0-rc5-00127-ga06157804399 #1 PREEMPT  8cc09ef94dcec767faa911515ce9e609c45db470\n Call Trace:\n  \u0026lt;IRQ\u0026gt;\n  __dump_stack (lib/dump_stack.c:95)\n  dump_stack_lvl (lib/dump_stack.c:123)\n  dump_stack (lib/dump_stack.c:130)\n  spin_dump (kernel/locking/spinlock_debug.c:71)\n  do_raw_spin_trylock (kernel/locking/spinlock_debug.c:?)\n  _raw_spin_trylock (include/linux/spinlock_api_smp.h:89 kernel/locking/spinlock.c:138)\n  __free_frozen_pages (mm/page_alloc.c:2973)\n  ___free_pages (mm/page_alloc.c:5295)\n  __free_pages (mm/page_alloc.c:5334)\n  tlb_remove_table_rcu (include/linux/mm.h:? include/linux/mm.h:3122 include/asm-generic/tlb.h:220 mm/mmu_gather.c:227 mm/mmu_gather.c:290)\n  ? __cfi_tlb_remove_table_rcu (mm/mmu_gather.c:289)\n  ? rcu_core (kernel/rcu/tree.c:?)\n  rcu_core (include/linux/rcupdate.h:341 kernel/rcu/tree.c:2607 kernel/rcu/tree.c:2861)\n  rcu_core_si (kernel/rcu/tree.c:2879)\n  handle_softirqs (arch/x86/include/asm/jump_label.h:36 include/trace/events/irq.h:142 kernel/softirq.c:623)\n  __irq_exit_rcu (arch/x86/include/asm/jump_label.h:36 kernel/softirq.c:725)\n  irq_exit_rcu (kernel/softirq.c:741)\n  sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1052)\n  \u0026lt;/IRQ\u0026gt;\n  \u0026lt;TASK\u0026gt;\n RIP: 0010:_raw_spin_unlock_irqrestore (arch/x86/include/asm/preempt.h:95 include/linux/spinlock_api_smp.h:152 kernel/locking/spinlock.c:194)\n  free_pcppages_bulk (mm/page_alloc.c:1494)\n  drain_pages_zone (include/linux/spinlock.h:391 mm/page_alloc.c:2632)\n  __drain_all_pages (mm/page_alloc.c:2731)\n  drain_all_pages (mm/page_alloc.c:2747)\n  kcompactd (mm/compaction.c:3115)\n  kthread (kernel/kthread.c:465)\n  ? __cfi_kcompactd (mm/compaction.c:3166)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork (arch/x86/kernel/process.c:164)\n  ? __cfi_kthread (kernel/kthread.c:412)\n  ret_from_fork_asm (arch/x86/entry/entry_64.S:255)\n  \u0026lt;/TASK\u0026gt;\n\nMatthew has analyzed the report and identified that in drain_page_zone()\nwe are in a section protected by spin_lock(\u0026amp;pcp-\u0026gt;lock) and then get an\ninterrupt that attempts spin_trylock() on the same lock.  The code is\ndesigned to work this way without disabling IRQs and occasionally fail the\ntrylock with a fallback.  However, the SMP=n spinlock implementation\nassumes spin_trylock() will always succeed, and thus it\u0026apos;s normally a\nno-op.  Here the enabled lock debugging catches the problem, but otherwise\nit could cause a corruption of the pcp structure.\n\nThe problem has been introduced by commit 574907741599 (\u0026quot;mm/page_alloc:\nleave IRQs enabled for per-cpu page allocations\u0026quot;).  The pcp locking scheme\nrecognizes the need for disabling IRQs to prevent nesting spin_trylock()\nsections on SMP=n, but the need to prevent the nesting in spin_lock() has\nnot been recognized.  Fix it by introducing local wrappers that change the\nspin_lock() to spin_lock_iqsave() with SMP=n and use them in all places\nthat do spin_lock(\u0026amp;pcp-\u0026gt;lock).\n\n[(CVE-2026-23025)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnull_blk: fix kmemleak by releasing references to fault configfs items\n\nWhen CONFIG_BLK_DEV_NULL_BLK_FAULT_INJECTION is enabled, the null-blk\ndriver sets up fault injection support by creating the timeout_inject,\nrequeue_inject, and init_hctx_fault_inject configfs items as children\nof the top-level nullbX configfs group.\n\nHowever, when the nullbX device is removed, the references taken to\nthese fault-config configfs items are not released. As a result,\nkmemleak reports a memory leak, for example:\n\nunreferenced object 0xc00000021ff25c40 (size 32):\n  comm \u0026quot;mkdir\u0026quot;, pid 10665, jiffies 4322121578\n  hex dump (first 32 bytes):\n    69 6e 69 74 5f 68 63 74 78 5f 66 61 75 6c 74 5f  init_hctx_fault_\n    69 6e 6a 65 63 74 00 88 00 00 00 00 00 00 00 00  inject..........\n  backtrace (crc 1a018c86):\n    __kmalloc_node_track_caller_noprof+0x494/0xbd8\n    kvasprintf+0x74/0xf4\n    config_item_set_name+0xf0/0x104\n    config_group_init_type_name+0x48/0xfc\n    fault_config_init+0x48/0xf0\n    0xc0080000180559e4\n    configfs_mkdir+0x304/0x814\n    vfs_mkdir+0x49c/0x604\n    do_mkdirat+0x314/0x3d0\n    sys_mkdir+0xa0/0xd8\n    system_call_exception+0x1b0/0x4f0\n    system_call_vectored_common+0x15c/0x2ec\n\nFix this by explicitly releasing the references to the fault-config\nconfigfs items when dropping the reference to the top-level nullbX\nconfigfs group.(CVE-2026-23032)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node()\n\nIn nfs4_ff_alloc_deviceid_node(), if the allocation for ds_versions fails,\nthe function jumps to the out_scratch label without freeing the already\nallocated dsaddrs list, leading to a memory leak.\n\nFix this by jumping to the out_err_drain_dsaddrs label, which properly\nfrees the dsaddrs list before cleaning up other resources.(CVE-2026-23038)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nlibceph: make calc_target() set t-\u0026gt;paused, not just clear it\n\nCurrently calc_target() clears t-\u0026gt;paused if the request shouldn\u0026apos;t be\npaused anymore, but doesn\u0026apos;t ever set t-\u0026gt;paused even though it\u0026apos;s able to\ndetermine when the request should be paused.  Setting t-\u0026gt;paused is left\nto __submit_request() which is fine for regular requests but doesn\u0026apos;t\nwork for linger requests -- since __submit_request() doesn\u0026apos;t operate\non linger requests, there is nowhere for lreq-\u0026gt;t.paused to be set.\nOne consequence of this is that watches don\u0026apos;t get reestablished on\npaused -\u0026gt; unpaused transitions in cases where requests have been paused\nlong enough for the (paused) unwatch request to time out and for the\nsubsequent (re)watch request to enter the paused state.  On top of the\nwatch not getting reestablished, rbd_reregister_watch() gets stuck with\nrbd_dev-\u0026gt;watch_mutex held:\n\n  rbd_register_watch\n    __rbd_register_watch\n      ceph_osdc_watch\n        linger_reg_commit_wait\n\nIt\u0026apos;s waiting for lreq-\u0026gt;reg_commit_wait to be completed, but for that to\nhappen the respective request needs to end up on need_resend_linger list\nand be kicked when requests are unpaused.  There is no chance for that\nif the request in question is never marked paused in the first place.\n\nThe fact that rbd_dev-\u0026gt;watch_mutex remains taken out forever then\nprevents the image from getting unmapped -- \u0026quot;rbd unmap\u0026quot; would inevitably\nhang in D state on an attempt to grab the mutex.(CVE-2026-23047)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\npNFS: Fix a deadlock when returning a delegation during open()\n\nBen Coddington reports seeing a hang in the following stack trace:\n  0 [ffffd0b50e1774e0] __schedule at ffffffff9ca05415\n  1 [ffffd0b50e177548] schedule at ffffffff9ca05717\n  2 [ffffd0b50e177558] bit_wait at ffffffff9ca061e1\n  3 [ffffd0b50e177568] __wait_on_bit at ffffffff9ca05cfb\n  4 [ffffd0b50e1775c8] out_of_line_wait_on_bit at ffffffff9ca05ea5\n  5 [ffffd0b50e177618] pnfs_roc at ffffffffc154207b [nfsv4]\n  6 [ffffd0b50e1776b8] _nfs4_proc_delegreturn at ffffffffc1506586 [nfsv4]\n  7 [ffffd0b50e177788] nfs4_proc_delegreturn at ffffffffc1507480 [nfsv4]\n  8 [ffffd0b50e1777f8] nfs_do_return_delegation at ffffffffc1523e41 [nfsv4]\n  9 [ffffd0b50e177838] nfs_inode_set_delegation at ffffffffc1524a75 [nfsv4]\n 10 [ffffd0b50e177888] nfs4_process_delegation at ffffffffc14f41dd [nfsv4]\n 11 [ffffd0b50e1778a0] _nfs4_opendata_to_nfs4_state at ffffffffc1503edf [nfsv4]\n 12 [ffffd0b50e1778c0] _nfs4_open_and_get_state at ffffffffc1504e56 [nfsv4]\n 13 [ffffd0b50e177978] _nfs4_do_open at ffffffffc15051b8 [nfsv4]\n 14 [ffffd0b50e1779f8] nfs4_do_open at ffffffffc150559c [nfsv4]\n 15 [ffffd0b50e177a80] nfs4_atomic_open at ffffffffc15057fb [nfsv4]\n 16 [ffffd0b50e177ad0] nfs4_file_open at ffffffffc15219be [nfsv4]\n 17 [ffffd0b50e177b78] do_dentry_open at ffffffff9c09e6ea\n 18 [ffffd0b50e177ba8] vfs_open at ffffffff9c0a082e\n 19 [ffffd0b50e177bd0] dentry_open at ffffffff9c0a0935\n\nThe issue is that the delegreturn is being asked to wait for a layout\nreturn that cannot complete because a state recovery was initiated. The\nstate recovery cannot complete until the open() finishes processing the\ndelegations it was given.\n\nThe solution is to propagate the existing flags that indicate a\nnon-blocking call to the function pnfs_roc(), so that it knows not to\nwait in this situation.(CVE-2026-23050)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: hv_netvsc: reject RSS hash key programming without RX indirection table\n\nRSS configuration requires a valid RX indirection table. When the device\nreports a single receive queue, rndis_filter_device_add() does not\nallocate an indirection table, accepting RSS hash key updates in this\nstate leads to a hang.\n\nFix this by gating netvsc_set_rxfh() on ndc-\u0026gt;rx_table_sz and return\n-EOPNOTSUPP when the table is absent. This aligns set_rxfh with the device\ncapabilities and prevents incorrect behavior.(CVE-2026-23054)\n\nA buffer overflow vulnerability exists in the QLogic Fibre Channel driver (qla2xxx) of the Linux kernel. In the functions `qla27xx_copy_fpin_pkt()` and `qla27xx_copy_multiple_pkt()`, the code uses the firmware-reported `frame_size` to calculate the copy length into `item-\u0026gt;iocb`. However, the `iocb` member is defined as a fixed-size 64-byte array within `struct purex_item`. If the reported `frame_size` exceeds 64 bytes, subsequent `memcpy` calls will overflow the boundary of the `iocb` member. This cross-member write is unsafe and can lead to memory corruption, potentially exploitable to compromise the confidentiality, integrity, and availability of the kernel.(CVE-2026-23059)\n\nA NULL pointer dereference vulnerability exists in the be2net network driver within the Linux kernel, specifically in the be_cmd_get_mac_from_list() function. According to the function\u0026apos;s contract, when the parameter pmac_id_valid is set to false, the driver may request a PMAC_ID from the network card\u0026apos;s firmware and store it at the provided address pmac_id. However, there is a location within the driver where both conditions pmac_id_valid == false and pmac_id == NULL are passed simultaneously. This results in an attempt to dereference a NULL pointer, potentially leading to a kernel crash or system instability.(CVE-2026-23084)\n\nA memory address truncation vulnerability exists in the irqchip/gic-v3-its driver of the Linux kernel. On 32-bit ARM machines with CONFIG_ARM_LPAE enabled, when using larger VMSPLIT configurations, lowmem allocations may be backed by physical memory addresses above the 32-bit address limit. The GICv3 driver allocates the \u0026apos;itt\u0026apos; object using GFP_KERNEL. Since all memory below the 4GB physical address limit is in ZONE_DMA in this configuration, kmalloc() defaults to higher addresses in ZONE_NORMAL. However, the driver stores these physical addresses in 32-bit \u0026apos;unsigned long\u0026apos; variables, causing the high addresses to be truncated, which leads to system crashes.(CVE-2026-23085)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nuacce: fix isolate sysfs check condition\n\nuacce supports the device isolation feature. If the driver\nimplements the isolate_err_threshold_read and\nisolate_err_threshold_write callback functions, uacce will create\nsysfs files now. Users can read and configure the isolation policy\nthrough sysfs. Currently, sysfs files are created as long as either\nisolate_err_threshold_read or isolate_err_threshold_write callback\nfunctions are present.\n\nHowever, accessing a non-existent callback function may cause the\nsystem to crash. Therefore, intercept the creation of sysfs if\nneither read nor write exists; create sysfs if either is supported,\nbut intercept unsupported operations at the call site.(CVE-2026-23094)\n\nA deadlock vulnerability exists in the Linux kernel due to incorrect lock acquisition ordering. This vulnerability affects the migration functionality for hugetlb (huge page) file folios. The specific scenario is: when two kernel tasks (Tasks) attempt to acquire the `folio_lock` and `i_mmap_rwsem` locks in opposite orders, a circular wait is formed, leading to a system deadlock. For example, Task A holds `folio_lock` and then tries to acquire the `i_mmap_rwsem` read lock, while Task B holds the `i_mmap_rwsem` write lock and then tries to acquire `folio_lock`. This lock ordering violates the rules defined in mm/rmap.c. This vulnerability can render parts of the affected system unavailable, impacting system availability.(CVE-2026-23097)\n\nIn the Linux kernel SCSI core layer, there is a fragile ordering logic between marking commands as completed or failed, designed to ensure the error handler only wakes when the last running command completes or times out. This logic contains race conditions. These race conditions can cause the SCSI layer to fail to wake the error handler, leaving I/O through the SCSI host stuck as the error state cannot advance. Specifically, there are two issues: 1. A memory ordering issue within the `scsi_dec_host_busy()` function. The write operation that clears the `SCMD_STATE_INFLIGHT` flag may be reordered with read counting operations in `scsi_host_busy()`. This can cause other CPUs to see inconsistent busy counts, preventing the correct triggering of the error handler wake-up. 2. A general ordering issue with the `scsi_eh_inc_host_failed()` function. It counts busy commands before incrementing the `host_failed` count, which can race with the processing of a final command in `scsi_dec_host_busy()`, resulting in neither side waking the error handler task.(CVE-2026-23110)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: add bounds checks in nvmet_tcp_build_pdu_iovec\n\nnvmet_tcp_build_pdu_iovec() could walk past cmd-\u0026gt;req.sg when a PDU\nlength or offset exceeds sg_cnt and then use bogus sg-\u0026gt;length/offset\nvalues, leading to _copy_to_iter() GPF/KASAN. Guard sg_idx, remaining\nentries, and sg-\u0026gt;length/offset before building the bvec.(CVE-2026-23112)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove\n\nOn APUs such as Raven and Renoir (GC 9.1.0, 9.2.2, 9.3.0), the ih1 and\nih2 interrupt ring buffers are not initialized. This is by design, as\nthese secondary IH rings are only available on discrete GPUs. See\nvega10_ih_sw_init() which explicitly skips ih1/ih2 initialization when\nAMD_IS_APU is set.\n\nHowever, amdgpu_gmc_filter_faults_remove() unconditionally uses ih1 to\nget the timestamp of the last interrupt entry. When retry faults are\nenabled on APUs (noretry=0), this function is called from the SVM page\nfault recovery path, resulting in a NULL pointer dereference when\namdgpu_ih_decode_iv_ts_helper() attempts to access ih-\u0026gt;ring[].\n\nThe crash manifests as:\n\n  BUG: kernel NULL pointer dereference, address: 0000000000000004\n  RIP: 0010:amdgpu_ih_decode_iv_ts_helper+0x22/0x40 [amdgpu]\n  Call Trace:\n   amdgpu_gmc_filter_faults_remove+0x60/0x130 [amdgpu]\n   svm_range_restore_pages+0xae5/0x11c0 [amdgpu]\n   amdgpu_vm_handle_fault+0xc8/0x340 [amdgpu]\n   gmc_v9_0_process_interrupt+0x191/0x220 [amdgpu]\n   amdgpu_irq_dispatch+0xed/0x2c0 [amdgpu]\n   amdgpu_ih_process+0x84/0x100 [amdgpu]\n\nThis issue was exposed by commit 1446226d32a4 (\u0026quot;drm/amdgpu: Remove GC HW\nIP 9.3.0 from noretry=1\u0026quot;) which changed the default for Renoir APU from\nnoretry=1 to noretry=0, enabling retry fault handling and thus\nexercising the buggy code path.\n\nFix this by adding a check for ih1.ring_size before attempting to use\nit. Also restore the soft_ih support from commit dd299441654f (\u0026quot;drm/amdgpu:\nRework retry fault removal\u0026quot;).  This is needed if the hardware doesn\u0026apos;t\nsupport secondary HW IH rings.\n\nv2: additional updates (Alex)\n\n(cherry picked from commit 6ce8d536c80aa1f059e82184f0d1994436b1d526)(CVE-2026-23163)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()\n\nWhen the socket is closed while in TCP_LISTEN a callback is run to\nflush all outstanding packets, which in turns calls\nnvmet_tcp_listen_data_ready() with the sk_callback_lock held.\nSo we need to check if we are in TCP_LISTEN before attempting\nto get the sk_callback_lock() to avoid a deadlock.(CVE-2026-23179)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nASoC: amd: fix memory leak in acp3x pdm dma ops(CVE-2026-23190)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_session_usage_count()\n\nIn iscsit_dec_session_usage_count(), the function calls complete() while\nholding the sess-\u0026gt;session_usage_lock. Similar to the connection usage count\nlogic, the waiter signaled by complete() (e.g., in the session release\npath) may wake up and free the iscsit_session structure immediately.\n\nThis creates a race condition where the current thread may attempt to\nexecute spin_unlock_bh() on a session structure that has already been\ndeallocated, resulting in a KASAN slab-use-after-free.\n\nTo resolve this, release the session_usage_lock before calling complete()\nto ensure all dereferences of the sess pointer are finished before the\nwaiter is allowed to proceed with deallocation.(CVE-2026-23193)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nsmb/client: fix memory leak in smb2_open_file()\n\nReproducer:\n\n  1. server: directories are exported read-only\n  2. client: mount -t cifs //${server_ip}/export /mnt\n  3. client: dd if=/dev/zero of=/mnt/file bs=512 count=1000 oflag=direct\n  4. client: umount /mnt\n  5. client: sleep 1\n  6. client: modprobe -r cifs\n\nThe error message is as follows:\n\n  =============================================================================\n  BUG cifs_small_rq (Not tainted): Objects remaining on __kmem_cache_shutdown()\n  -----------------------------------------------------------------------------\n\n  Object 0x00000000d47521be @offset=14336\n  ...\n  WARNING: mm/slub.c:1251 at __kmem_cache_shutdown+0x34e/0x440, CPU#0: modprobe/1577\n  ...\n  Call Trace:\n   \u0026lt;TASK\u0026gt;\n   kmem_cache_destroy+0x94/0x190\n   cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n   cleanup_module+0x4e/0x540 [cifs]\n   __se_sys_delete_module+0x278/0x400\n   __x64_sys_delete_module+0x5f/0x70\n   x64_sys_call+0x2299/0x2ff0\n   do_syscall_64+0x89/0x350\n   entry_SYSCALL_64_after_hwframe+0x76/0x7e\n  ...\n  kmem_cache_destroy cifs_small_rq: Slab cache still has objects when called from cifs_destroy_request_bufs+0x3e/0x50 [cifs]\n  WARNING: mm/slab_common.c:532 at kmem_cache_destroy+0x16b/0x190, CPU#0: modprobe/1577(CVE-2026-23205)\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nscsi: target: iscsi: Fix use-after-free in iscsit_dec_conn_usage_count()\n\nIn iscsit_dec_conn_usage_count(), the function calls complete() while\nholding the conn-\u0026gt;conn_usage_lock. As soon as complete() is invoked, the\nwaiter (such as iscsit_close_connection()) may wake up and proceed to free\nthe iscsit_conn structure.\n\nIf the waiter frees the memory before the current thread reaches\nspin_unlock_bh(), it results in a KASAN slab-use-after-free as the function\nattempts to release a lock within the already-freed connection structure.\n\nFix this by releasing the spinlock before calling complete().(CVE-2026-23216)\n\nIn the Linux kernel, the ksmbd component contains an infinite loop vulnerability. The problem occurs when a signed request fails smb2 signature verification check. In __process_request(), if check_sign_req() returns an error, set_smb2_rsp_status(work, STATUS_ACCESS_DENIED) is called. set_smb2_rsp_status() sets work-\u0026gt;next_smb2_rcv_hdr_off to zero. By resetting next_smb2_rcv_hdr_off to zero, the pointer to the next command in the chain is lost. Consequently, is_chained_smb2_message() continues to point to the same request header instead of advancing. If the header\u0026apos;s NextCommand field is non-zero, the function returns true, causing __handle_ksmbd_work() to repeatedly process the same failed request in an infinite loop. This results in the kernel log being flooded with \u0026quot;bad smb2 signature\u0026quot; messages and high CPU usage.(CVE-2026-23220)\n\nIn the Linux kernel, the following vulnerability has been resolved:  smb: server: fix leak of active_num_conn in ksmbd_tcp_new_connection()  On kthread_run() failure in ksmbd_tcp_new_connection(), the transport is freed via free_transport(), which does not decrement active_num_conn, leaking this counter.  Replace free_transport() with ksmbd_tcp_disconnect().  The Linux kernel CVE team has assigned CVE-2026-23228 to this issue.(CVE-2026-23228)","status":"published","published":"2026-03-15T11:10:34Z","modified":"2026-08-18T01:19:38.135892245Z","cvss":[{"version":"3.1","score":7.8,"vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:52:45.721983Z"},{"id":"ROOT-OS-UBUNTU-2404-CVE-2026-23059","title":"CVE-2026-23059 in linux - Patched by Root","description":"Root has patched CVE-2026-23059 in the linux package for Root:Ubuntu:24.04. Multiple fixed versions available.","status":"published","published":"2026-11-06T15:54:27Z","modified":"2026-11-06T16:17:54.141637309Z","cvss":[{"version":"3.1","score":7,"vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-06T16:59:13.602872Z"},{"id":"UBUNTU-CVE-2026-23059","description":"In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Sanitize payload size to prevent member overflow In qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size reported by firmware is used to calculate the copy length into item-\u003eiocb. However, the iocb member is defined as a fixed-size 64-byte array within struct purex_item. If the reported frame_size exceeds 64 bytes, subsequent memcpy calls will overflow the iocb member boundary. While extra memory might be allocated, this cross-member write is unsafe and triggers warnings under CONFIG_FORTIFY_SOURCE. Fix this by capping total_bytes to the size of the iocb member (64 bytes) before allocation and copying. This ensures all copies remain within the bounds of the destination structure member.","status":"published","published":"2026-02-04T17:16:00Z","modified":"2026-11-11T09:39:25.281055213Z","cvss":[{"version":"4.0","score":7.1,"vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N","level":"high"}],"updated_at":"2026-11-11T10:01:20.456291Z"},{"id":"AZL-77244","title":"CVE-2026-23059 affecting package kernel for versions less than 6.6.126.1-1","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Sanitize payload size to prevent member overflow\n\nIn qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size\nreported by firmware is used to calculate the copy length into\nitem-\u003eiocb. However, the iocb member is defined as a fixed-size 64-byte\narray within struct purex_item.\n\nIf the reported frame_size exceeds 64 bytes, subsequent memcpy calls will\noverflow the iocb member boundary. While extra memory might be allocated,\nthis cross-member write is unsafe and triggers warnings under\nCONFIG_FORTIFY_SOURCE.\n\nFix this by capping total_bytes to the size of the iocb member (64 bytes)\nbefore allocation and copying. This ensures all copies remain within the\nbounds of the destination structure member.","status":"published","published":"2026-02-04T17:16:16Z","modified":"2026-08-28T17:56:26.298313Z","updated_at":"2026-11-02T15:28:09.747541Z"},{"id":"BELL-CVE-2026-23059","status":"published","published":"2026-02-10T06:09:21.436602Z","modified":"2026-06-25T07:18:33.415829369Z","updated_at":"2026-11-02T15:28:23.037038Z"},{"id":"CVE-2026-23059","title":"scsi: qla2xxx: Sanitize payload size to prevent member overflow","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nscsi: qla2xxx: Sanitize payload size to prevent member overflow\n\nIn qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size\nreported by firmware is used to calculate the copy length into\nitem-\u003eiocb. However, the iocb member is defined as a fixed-size 64-byte\narray within struct purex_item.\n\nIf the reported frame_size exceeds 64 bytes, subsequent memcpy calls will\noverflow the iocb member boundary. While extra memory might be allocated,\nthis cross-member write is unsafe and triggers warnings under\nCONFIG_FORTIFY_SOURCE.\n\nFix this by capping total_bytes to the size of the iocb member (64 bytes)\nbefore allocation and copying. This ensures all copies remain within the\nbounds of the destination structure member.","status":"published","published":"2026-02-04T16:07:42.15Z","modified":"2026-11-06T17:27:15.916753079Z","updated_at":"2026-11-06T18:04:08.509527Z"},{"id":"DEBIAN-CVE-2026-23059","description":"In the Linux kernel, the following vulnerability has been resolved:  scsi: qla2xxx: Sanitize payload size to prevent member overflow  In qla27xx_copy_fpin_pkt() and qla27xx_copy_multiple_pkt(), the frame_size reported by firmware is used to calculate the copy length into item-\u003eiocb. However, the iocb member is defined as a fixed-size 64-byte array within struct purex_item.  If the reported frame_size exceeds 64 bytes, subsequent memcpy calls will overflow the iocb member boundary. While extra memory might be allocated, this cross-member write is unsafe and triggers warnings under CONFIG_FORTIFY_SOURCE.  Fix this by capping total_bytes to the size of the iocb member (64 bytes) before allocation and copying. This ensures all copies remain within the bounds of the destination structure member.","status":"published","published":"2026-02-04T17:16:16.583Z","modified":"2026-10-01T02:47:36.121657526Z","updated_at":"2026-11-02T15:45:53.516942Z"},{"id":"DSA-6126-1","title":"linux - security update","status":"published","published":"2026-02-09T00:00:00Z","modified":"2026-03-09T02:09:24.491665Z","updated_at":"2026-11-02T15:46:18.296714Z"},{"id":"MGASA-2026-0097","title":"Updated kernel, kmod-virtualbox \u0026 kmod-xtables-addons packages fix security vulnerabilities","description":"Upstream kernel version 6.6.130 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-04-15T16:42:07Z","modified":"2026-04-15T17:01:41.57748Z","updated_at":"2026-11-02T15:49:43.178336Z"},{"id":"MGASA-2026-0098","title":"Updated kernel-linus packages fix security vulnerabilities","description":"Vanilla upstream kernel version 6.6.130 fixes bugs and vulnerabilities.\nFor information about the vulnerabilities see the links.\n","status":"published","published":"2026-04-15T16:42:07Z","modified":"2026-04-15T17:01:42.526844Z","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":"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":"SUSE-SU-2026:24550-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise Micro 6.0 and Micro 6.1 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-68219: cifs: fix memory leak in smb3_fs_context_parse_param error path (bsc#1255222).\n- CVE-2026-31708: smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path (bsc#1264022).\n- CVE-2026-31709: smb: client: validate the whole DACL before rewriting it in cifsacl (bsc#1264024).\n- CVE-2026-43350: smb: client: require a full NFS mode SID before reading mode bits (bsc#1264985).\n- CVE-2026-46155: smb/client: fix out-of-bounds read in smb2_compound_op() (bsc#1267720).\n- CVE-2026-64324: udf: validate free block extents against the partition length (bsc#1273970).\n- CVE-2026-64370: posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path (bsc#1273805).\n- CVE-2026-64380: smb: client: harden POSIX SID length parsing (bsc#1273557).\n- CVE-2026-64413: netfilter: ebtables: zero chainstack array (bsc#1274082).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-68186: binfmt_misc: set have_execfd only once the interpreter is opened (bsc#1274949).\n- CVE-2026-68447: drm/amdkfd: clamp v9 CRIU control stack checkpoint copy to BO size (bsc#1276280).\n- CVE-2026-72010: cgroup/cpuset: rebind mm mempolicy to effective_mems, not mems_allowed (bsc#1276776).\n- CVE-2026-72110: bpf,fork: wipe -\u003ebpf_storage before bailouts that access it (bsc#1277357).\n- CVE-2026-72111: bpf: Reset register bounds before narrowing retval range in check_mem_access() (bsc#1277389).\n- CVE-2026-72127: netdev-genl: report NAPI thread PID in the caller's pid namespace (bsc#1277542).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72253: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (bsc#1277665).\n- CVE-2026-72318: cifs: validate DFS referral string offsets (bsc#1275939).\n- CVE-2026-72400: seg6: validate SRH length before reading fixed fields (bsc#1278030).\n- CVE-2026-72405: net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync (bsc#1278033).\n- CVE-2026-72416: netfilter: nft_compat: ebtables emulation must reject non-bridge targets (bsc#1278041).\n- CVE-2026-72428: bpf: Fix stack slot index in nospec checks (bsc#1278050).\n- CVE-2026-74368: wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic() (bsc#1277103).\n- CVE-2026-74399: evm: terminate and bound the evm_xattrs read buffer (bsc#1278319).\n- CVE-2026-74565: netfilter: nf_tables: make nft_object rhltable per table (bsc#1275568).\n- CVE-2026-74613: vsock/virtio: avoid refilling the RX queue after teardown (bsc#1277903).\n- CVE-2026-74620: net/sched: act_gact, act_police: range check the fallback control action (bsc#1277044).\n- CVE-2026-74624: netfilter: nf_conntrack: defer invalid log until after unlock (bsc#1277599).\n- CVE-2026-74715: net: netfilter: Make ct zone opts configurable for bpf ct helpers (bsc#1277890).\n- CVE-2026-74720: bpf: Preserve pointer state for commuted arithmetic (bsc#1276574).\n- CVE-2026-74746: netfilter: flowtable: publish GC-visible tuple last (bsc#1278101).\n- CVE-2026-74748: netfilter: ipset: fix refcount race between list:set GC and swap (bsc#1277578).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80602: perf/x86/amd/lbr: Fix kernel address leakage (bsc#1278123).\n- CVE-2026-80637: netfilter: synproxy: fix unaligned memory access in timestamp adjustment (bsc#1278343).\n- CVE-2026-80684: KVM: s390: pci: Fix NULL dereference on AIBV allocation failure (bsc#1277467).\n- CVE-2026-80709: s390/zcrypt: Fix wrong domain value verification with EP11 CPRBs (bsc#1278202).\n- CVE-2026-80717: sctp: validate Adaptation Indication parameter length (bsc#1277836).\n- CVE-2026-80755: selinux: reject a permission value exceeding the class permission count (bsc#1278415).\n- CVE-2026-80757: selinux: reject a class permission count below its inherited common (bsc#1278711).\n- CVE-2026-80808: ext4: stop retrying saturated xattr cache entries (bsc#1279795).\n- CVE-2026-80809: ocfs2: fix missing metadata reservation for large xattrs (bsc#1279606).\n- CVE-2026-80855: fuse: fix invalidate lock leak on open O_TRUNC DAX failure (bsc#1279564).\n- CVE-2026-80879: ocfs2: fix circular locking dependency in ocfs2_dio_end_io_write (bsc#1279494).\n- CVE-2026-80881: ocfs2: fix buffer head management in ocfs2_read_blocks() (bsc#1279496).\n- CVE-2026-80978: ip6_gre: fix hardware header length for NBMA tunnels (bsc#1280253).\n- CVE-2026-80988: NTB: ntb_transport: Fail TX enqueue when the QP link is down (bsc#1280266).\n- CVE-2026-89491: ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin() (bsc#1280472).\n- CVE-2026-89494: ocfs2: validate lengths in dlm_mig_lockres_handler (bsc#1280520).\n- CVE-2026-89495: ocfs2: bound namelen in dlm_migrate_request_handler (bsc#1280569).\n- CVE-2026-89537: SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2 (bsc#1280713).\n- CVE-2026-89554: mptcp: fix uninitialized local_id in syncookie MP_JOIN reconstruction (bsc#1280736).\n- CVE-2026-89559: libnvdimm/labels: Prevent integer overflow in __nd_label_validate() (bsc#1280554).\n- CVE-2026-89560: landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation (bsc#1280806).\n- CVE-2026-89595: fsnotify: Fix stale object mask after concurrent mark updates (bsc#1280834).\n- CVE-2026-89608: ecryptfs: pass packet set buffer size to parser (bsc#1280826).\n- CVE-2026-89637: smb: client: fix UAF and buffer leak in cifs_check_trans2() for malformed secondary T2 (bsc#1280492).\n- CVE-2026-89642: cifs: call pagecache_isize_extended() in cifs_setsize() when extending (bsc#1280970).\n- CVE-2026-89649: ceph: bound xattr value length in __build_xattrs() (bsc#1280434).\n- CVE-2026-89654: ceph: fix UAF in check_new_map() on session freed during unlock (bsc#1280415).\n- CVE-2026-89655: ceph: fix UAF in __kick_flushing_caps() on cf entry freed during unlock (bsc#1280398).\n- CVE-2026-89656: libceph: reject buckets with mismatched CRUSH ids (bsc#1280563).\n- CVE-2026-89657: libceph: validate OSD extent maps before cursor advance (bsc#1280545).\n- CVE-2026-89751: x86/tdx: Fix off-by-one in port I/O handling (bsc#1280822).\n- CVE-2026-89761: apparmor: fix out-of-bounds write when null terminating a label vec (bsc#1280745).\n- CVE-2026-89786: ext4: fix out-of-bounds read in ext4_read_inline_dir() (bsc#1280976).\n- CVE-2026-89787: ext4: check dir entry fits before reading the hash trailer in ext4_search_dir() (bsc#1280977).\n- CVE-2026-90042: ceph: properly decrypt filenames in vmalloc() buffers (bsc#1280948).\n- CVE-2026-90057: slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() (bsc#1281650).\n- CVE-2026-90081: net/rds: use wq_has_sleeper() in rds_cong_map_updated() (bsc#1281490).\n- CVE-2026-90092: Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN (bsc#1281384).\n- CVE-2026-90103: NFSv4.2: fix LAYOUTSTATS send buffer exhaustion (bsc#1281538).\n- CVE-2026-90107: net/smc: free pending qentry in smc_llc_flow_stop() before memset (bsc#1281510).\n- CVE-2026-90114: net: bridge: Reject descending VLAN tunnel ranges (bsc#1281509).\n- CVE-2026-90128: vdpa/mlx5: fix wrong list iterated in add_direct_chain error path (bsc#1281577).\n- CVE-2026-90138: vsock: don't check the listener's sk_err in vsock_accept() (bsc#1281535).\n- CVE-2026-90148: NFSv4: Fix incorrect argument passed to nfs4_delete_lease() in nfs4_add_lease() (bsc#1281551).\n- CVE-2026-90227: nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() (bsc#1281705).\n- CVE-2026-90230: nvme: Add the DHCHAP maximum HD IDs (bsc#1281715).\n- CVE-2026-90393: bpf: Fix potential UAF in bpf_netns_link_update_prog (bsc#1282289).\n- CVE-2026-93054: uio: Fix stale info pointer in failed registration path (bsc#1282276).\n- CVE-2026-93228: svcrdma: Reject Write/Reply chunks with segcount 0 (bsc#1282697).\n- CVE-2026-93231: lockd: fix swapped arguments in nlmsvc_match_ip() (bsc#1282778).\n- CVE-2026-93250: vxlan: mdb: Fix use-after-free in vxlan_mdb_flush() (bsc#1282677).\n- CVE-2026-93262: md/raid5-ppl: fix use-after-free in ppl_do_flush() (bsc#1283004).\n- CVE-2026-93795: blk-cgroup: fix leaks and online flag on radix_tree_insert failure (bsc#1283155).\n- CVE-2026-93798: btrfs: fix reloc root cleanup in merge_reloc_roots() (bsc#1282769).\n- CVE-2026-93817: perf: Fix addr_filter_ranges lifetime (bsc#1283017).\n- CVE-2026-93828: exfat: fix handling of damaged volume in exfat_create_upcase_table() (bsc#1282890).\n- CVE-2026-93830: net: stmmac: xgmac2: disable RBUE in default RX interrupt mask (bsc#1282889).\n- CVE-2026-97554: smb: client: avoid using uninitialized SIDs in cifs_posix_to_fattr() (bsc#1283850).\n- CVE-2026-97556: smb: client: avoid leaking refcount when cifs_sb_tlink() fails (bsc#1283853).\n- CVE-2026-97558: smb: client: fix cifsFileInfo reference leak in deferred close (bsc#1283855).\n- CVE-2026-97559: smb: client: fail DACL rewrite when the new DACL exceeds 64K (bsc#1283856).\n- CVE-2026-97561: smb: client: honor forceuid/forcegid when mapping SIDs to uid/gid (bsc#1283858).\n- CVE-2026-97562: smb: client: pin DFS superblock in iterator callback (bsc#1283862).\n- CVE-2026-97563: smb: client: reject out-of-bounds DataOffset in CIFSSMBRead() (bsc#1283877).\n- CVE-2026-97565: smb: client: reject short READ responses in CIFSSMBRead() (bsc#1283793).\n- CVE-2026-97575: media: v4l2-ctrls: validate AV1 tile counts (bsc#1283337).\n- CVE-2026-97596: ipvs: reject invalid states in connection template sync records (bsc#1283941).\n- CVE-2026-97603: idpf: disable DIM work before freeing q_vectors (bsc#1283782).\n- CVE-2026-97612: net: mpls: clear inner_protocol when the last label is popped (bsc#1283967).\n- CVE-2026-97954: net/rds: fix tcp stream corruption with large pages (bsc#1283113).\n- CVE-2026-97963: net: stmmac: initialize ptp_lock at probe time (bsc#1282984).\n- CVE-2026-97964: ppp_synctty: ensure a writeable skb header (bsc#1282962).\n- CVE-2026-97965: vxlan: initialize _md in vxlan_xmit_one() (bsc#1282963).\n- CVE-2026-97991: vdpa_sim_blk: reject out-of-range sector starts (bsc#1283356).\n- CVE-2026-97993: vhost-vdpa: don't install the eventfd_ctx_fdget() error in config_ctx (bsc#1283339).\n- CVE-2026-98014: net/mlx5: E-Switch, prevent mc_list repopulation during vport disable (bsc#1283668).\n- CVE-2026-98022: net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations (bsc#1283810).\n- CVE-2026-98023: vxlan: reject dynamic fdb entries that reference a nexthop id (bsc#1283960).\n- CVE-2026-98031: nexthop: Initialize extack in remove_nh_grp_entry() (bsc#1283662).\n- CVE-2026-98041: bpf: Don't predict JMP32 pointer vs zero comparisons (bsc#1284064).\n- CVE-2026-98068: net/rds: don't let rds_conn_shutdown() consume a concurrent drop (bsc#1283903).\n- CVE-2026-98069: net/rds: acquire the fastpath locks in rds_conn_shutdown() (bsc#1283863).\n- CVE-2026-98070: net/rds: acquire RDS_IN_XMIT in rds_tcp_reset_callbacks() (bsc#1283916).\n- CVE-2026-98071: net/rds: clear cp_flags bits individually in rds_conn_path_reset() (bsc#1283842).\n- CVE-2026-98072: net/rds: use wq_has_sleeper() in release_in_xmit() (bsc#1283846).\n- CVE-2026-98074: bonding: do not clear curr_active_slave prematurely when releasing all slaves (bsc#1283871).\n- CVE-2026-98078: ipvs: fix reversed sequence option serialization (bsc#1284150).\n- CVE-2026-98095: af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header() (bsc#1283921).\n- CVE-2026-98122: vxlan: mdb: Fix use-after-free in vxlan_mdb_remote_src_del() (bsc#1283886).\n- CVE-2026-98124: smb/client: invalidate fscache for fallocate range operations (bsc#1283821).\n- CVE-2026-98125: smb/client: fix stale page cache in insert/collapse range (bsc#1283812).\n- CVE-2026-98126: smb/client: validate new EOF for zero range (bsc#1283859).\n- CVE-2026-98127: smb/client: validate new EOF for insert range (bsc#1283873).\n- CVE-2026-98154: nvme-rdma: fix -EIO cleanup order in queue_rq (bsc#1283418).\n- CVE-2026-98158: ppp_async: drop the errored frame instead of resetting its headroom (bsc#1283933).\n- CVE-2026-98167: smb: client: fix server-\u003etotal_read for compound encrypted PDUs (bsc#1284422).\n- CVE-2026-98169: smb: client: fix potential OOB read in smb3_enum_snapshots() (bsc#1284298).\n- CVE-2026-98170: smb: client: fix OOB struct field reads in move_smb2_ea_to_cifs() (bsc#1284310).\n- CVE-2026-98175: smb: client: cancel reconnect work in clean_demultiplex_info() (bsc#1284312).\n- CVE-2026-98257: rds: ib: use rds_conn_drop() on protocol version mismatch (bsc#1284346).\n- CVE-2026-98258: posix-cpu-timers: Prevent freeing a timer which is queued on the expiry list (bsc#1284584).\n- CVE-2026-98261: cifs: Fix server use-after-free in cifs_chan_skip_or_disable() (bsc#1284605).\n- CVE-2026-98264: ALSA: virtio: reset device before deleting virtqueues (bsc#1284363).\n- CVE-2026-98282: powerpc/iommu: Fix the overflow validation in iommu_tce_check_ioba (bsc#1284360).\n- CVE-2026-98283: KVM: PPC: Book3S HV: fix use-after-free in kvmhv_emulate_tlbie_all_lpid() (bsc#1284595).\n- CVE-2026-98306: seg6: set IPSKB_L3SLAVE from IP6SKB_L3SLAVE on IPIP decapsulation (bsc#1284505).\n- CVE-2026-98368: esp: downgrade zerocopy managed frags before mutating skb frags (bsc#1284498).\n- CVE-2026-98374: tcp: fix use-after-free of retransmit_skb_hint in tcp_send_synack() (bsc#1284740).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n- CVE-2026-98471: KVM: SEV: Do cache maintenance on the source VM during intra-host migration (bsc#1286240).\n- CVE-2026-98631: xsk: Use a 32-bit compare in xsk_map_gen_lookup (bsc#1286233).\n- CVE-2026-99131: xfs: fix capability check in xfs (bsc#1288668).\n- CVE-2026-100071: net: hsr: free learned nodes on device setup failure (bsc#1282870).\n\nThe following non security issues were fixed:\n\n- accel/qaic: reject BO sizes that overflow page count (git-fixes).\n- ACPI: CPPC: Validate the _CPC package header (git-fixes).\n- ACPI: extlog: Validate elog record length before walking sections (git-fixes).\n- ACPI: PCI: pci_link: clear driver_data before free (git-fixes).\n- ACPI: pfr_update: zero-initialize capability query result (git-fixes).\n- ACPI: PM: Drop parent state update from acpi_device_get_power() (git-fixes).\n- ACPI: tables: handle failed initrd override mappings (git-fixes).\n- ACPI: TAD: Rearrange RT data validation checking (stable-fixes).\n- ACPI: video: Fix backlight unregistration ordering (git-fixes).\n- ACPICA: Fix memory leak in acpi_ds_create_field() (git-fixes).\n- ACPICA: Fix PCC OperationRegion command offsets (git-fixes).\n- ACPICA: Initialize parser_state.aml_end in acpi_install_method() (git-fixes).\n- ALSA: 6fire: take stream_mutex in the Digital Thru control (git-fixes).\n- ALSA: aloop: Keep the timer source alive until card release (git-fixes).\n- ALSA: caiaq: Fix races at MIDI URB and trigger accesses (git-fixes).\n- ALSA: caiaq: Fix the Kore controller key map (git-fixes).\n- ALSA: caiaq: Register card at the final step (git-fixes).\n- ALSA: caiaq: Serialize access to the EP1 command buffer (git-fixes).\n- ALSA: compress: add missing OPEN-state gate to SET_METADATA (git-fixes).\n- ALSA: control: Fix virtual master creation reference in kernel-doc (git-fixes).\n- ALSA: cs46xx: fix unit mismatch in DSP code area bounds check (git-fixes).\n- ALSA: hda/hdmi: clamp num_cvts against cvt_nids in hdmi_read_pin_conn (git-fixes).\n- ALSA: hda/hdmi: clamp sad_count in ELD proc write handler (git-fixes).\n- ALSA: hda: Add NULL check for the driver pointer at unsol event work (git-fixes).\n- ALSA: hda: Avoid non-operational GPU warning at regular device removal (git-fixes).\n- ALSA: hda: Fix potential UAF for gating jack (git-fixes).\n- ALSA: hda: intel: Cancel delayed work at shutdown, too (git-fixes).\n- ALSA: hda: Reject codec reset on ASoC (ext_ops) buses (git-fixes).\n- ALSA: jack: Fix kctl free at error in snd_jack_kctl_new() (git-fixes).\n- ALSA: line6: Clear prev_fbuf on capture buffer release (git-fixes).\n- ALSA: line6: Fix potential OOB write in line6_capture_copy() (git-fixes).\n- ALSA: line6: Reject too small max packet sizes (git-fixes).\n- ALSA: line6: Use kzalloc() for PCM buffer allocation (git-fixes).\n- ALSA: pcm: Fix driver_tstamp value reporting (git-fixes).\n- ALSA: pcm: Protect channel-map reads against runtime detach (git-fixes).\n- ALSA: pcm: Protect the unregister notifier traversal (git-fixes).\n- ALSA: pcm: Remove channel-map controls before freeing substreams (git-fixes).\n- ALSA: pcm: Unlink substreams before releasing them (git-fixes).\n- ALSA: seq: oss: Skip events until fully initialized (git-fixes).\n- ALSA: sh: aica: Fix spu_memset() stride (git-fixes).\n- ALSA: ump: Correct return size of fill_rpn() (git-fixes).\n- ALSA: usb-audio: Use fixed control index for us16x08 mixer elements (git-fixes).\n- ALSA: via82xx: use helper to activate DXS controls (git-fixes).\n- ASoC: adau17x1: return cache sync errors from resume (git-fixes).\n- ASoC: ak4642: return cache sync errors from resume (git-fixes).\n- ASoC: amd: acp: Fix .close() being skipped on rollback (git-fixes).\n- ASoC: amd: ps: Fix acp63_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: ps: Fix acp63_sdw_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: raven: Fix acp3x_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: raven: Fix memory leak in acp3x_dma_close() (git-fixes).\n- ASoC: amd: renoir: Fix acp_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: vangogh: Fix acp5x_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) (stable-fixes).\n- ASoC: amd: yc: Fix acp6x_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: arizona-jack: Fix runtime PM imbalance in arizona_start_hpdet_acc_id() (git-fixes).\n- ASoC: atmel-i2s: fix MCK generator error handling (git-fixes).\n- ASoC: atmel-i2s: use optional API for gclk (git-fixes).\n- ASoC: atmel-i2s: use optional API for muxclk (git-fixes).\n- ASoC: atmel: atmel-pcm-pdc: Fix atmel_pcm_close() being skipped on rollback (git-fixes).\n- ASoC: codecs: da732x: Fix definition of ADC2 EQ Overall Volume control (git-fixes).\n- ASoC: codecs: es*: Modify the registers related to ALC RECOVERY (git-fixes).\n- ASoC: codecs: rt5659: propagate GPIO errors (git-fixes).\n- ASoC: codecs: rt5682s: disable jack detection work on shutdown (git-fixes).\n- ASoC: codecs: sta32x: Fix definition of Ch2 and Ch3 Volume Bypass controls (git-fixes).\n- ASoC: codecs: sta32x: Fix definition of limiter threshold controls (git-fixes).\n- ASoC: codecs: sta350: Fix definition of Ch2 and Ch3 Volume Bypass controls (git-fixes).\n- ASoC: codecs: sta350: Fix definition of limiter threshold controls (git-fixes).\n- ASoC: codecs: tlv320adc3xxx: Fix definition of AGC Target Level control (git-fixes).\n- ASoC: codecs: wcd9335: Fix SLIM interface device leak in wcd9335_slim_status() (git-fixes).\n- ASoC: codecs: wm5100: Fix definition of EQ3 Band 1 Volume control (git-fixes).\n- ASoC: codecs: wm8510: Fix definition of ADC Inversion Switch control (git-fixes).\n- ASoC: codecs: wm8737: Fix definition of zero cross switches (git-fixes).\n- ASoC: codecs: wm8750: Fix definition of ALC Capture NG Type control (git-fixes).\n- ASoC: codecs: wm8955: Fix definition of Treble Cutoff control (git-fixes).\n- ASoC: codecs: wm8983: Fix definition of ADC 128x Oversampling control (git-fixes).\n- ASoC: codecs: wm8985: Fix definition of ADC 128x Oversampling control (git-fixes).\n- ASoC: codecs: wm8990: Fix definition of LOMIX AINLMUX Bypass Volume control (git-fixes).\n- ASoC: codecs: wm8990: Fix definition of right input PGA controls (git-fixes).\n- ASoC: codecs: wm8991: Fix definition of LOMIX AINLMUX Bypass Volume control (git-fixes).\n- ASoC: codecs: wm8991: Fix definition of right input PGA controls (git-fixes).\n- ASoC: codecs: wm8994: Fix definition of WM8958 noise gate hold time controls (git-fixes).\n- ASoC: codecs: wm8994: Fix runtime PM leak in wm8994_mic_detect() (git-fixes).\n- ASoC: codecs: wm_hubs: Fix definition of MIXINR to MIXOUTR volume control (git-fixes).\n- ASoC: codecs: wsa883x: disable runtime PM on unbind (git-fixes).\n- ASoC: codecs: wsa884x: disable runtime PM on unbind (git-fixes).\n- ASoC: cs42l56: Remove the ADC Mute Switch control (git-fixes).\n- ASoC: es8316: return cache sync errors from resume (git-fixes).\n- ASoC: fsl_asrc: check the second front-end DMA channel (git-fixes).\n- ASoC: fsl_asrc: use regmap_write_bits to update clock source registers (git-fixes).\n- ASoC: hdac_hda: Balance the runtime PM disable in codec remove (git-fixes).\n- ASoC: hdac_hda: Keep runtime PM state in sync across codec remove/probe (git-fixes).\n- ASoC: hdac_hda: Restore the codec device type on unbind (git-fixes).\n- ASoC: imx-pcm-rpmsg: Fix imx_rpmsg_pcm_close() being skipped on rollback (git-fixes).\n- ASoC: intel: atom: Fix .shutdown() being skipped on rollback (git-fixes).\n- ASoC: Intel: atom: Fix platform device leak on probe failure (git-fixes).\n- ASoC: Intel: avs: Prevent module info underflow (git-fixes).\n- ASoC: Intel: avs: Unprepare a stream when recovery occurs (git-fixes).\n- ASoC: mediatek: common: Handle constraint return value in FE startup (git-fixes).\n- ASoC: mediatek: mt6797: fix wrong unwind order and error code in enable_clock (git-fixes).\n- ASoC: mediatek: mt8183: Fix APLL enable error handling (git-fixes).\n- ASoC: mediatek: mt8183: Fix clock handling in mux disable path (git-fixes).\n- ASoC: mediatek: mt8183: Fix wrong clock cleanup on clk_set_parent() failure (git-fixes).\n- ASoC: mediatek: mt8186: Fix AFE clock error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix APLL enable error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix APLL mux setting error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix clock handling in mux disable path (git-fixes).\n- ASoC: mediatek: mt8186: Fix MCK error handling (git-fixes).\n- ASoC: mediatek: mt8188: Handle constraint return value in FE startup (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Handle clock enable errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Handle tuner clock enable errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Propagate regmap update errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-pcm: Handle runtime resume errors (git-fixes).\n- ASoC: mediatek: mt8192-mt6359: Fix error handling in MTKAIF calibration (git-fixes).\n- ASoC: mediatek: mt8192: check return values in mt8192_afe_gpio_init() (git-fixes).\n- ASoC: mediatek: mt8192: fix AFE clock error handling (git-fixes).\n- ASoC: mediatek: mt8192: fix APLL mux error handling (git-fixes).\n- ASoC: mediatek: mt8192: fix error handling in APLL enable functions (git-fixes).\n- ASoC: mediatek: mt8192: fix MCK clock error handling (git-fixes).\n- ASoC: mediatek: mt8192: Handle regcache_sync() failure in runtime resume (git-fixes).\n- ASoC: mediatek: mt8192: Propagate errors in TDM DAI DAPM event handlers (git-fixes).\n- ASoC: mediatek: mt8192: Propagate mt8192_afe_gpio_request() errors in ADDA DAI (git-fixes).\n- ASoC: mediatek: mt8192: switch to devm_clk_get_optional() (git-fixes).\n- ASoC: mediatek: mt8195: Check paired MEMIF clock enable in FE trigger (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM MCLK error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM probe error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix FE startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix HDMI TX startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix main clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix paired memif clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix register access clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix runtime resume error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix timing system clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix tuner clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Propagate IRQ lookup errors (git-fixes).\n- ASoC: mt6359-accdet: manage private workqueues with devres (git-fixes).\n- ASoC: nau8540: return cache sync errors from resume (git-fixes).\n- ASoC: ops: Fix return value in snd_soc_limit_volume() (git-fixes).\n- ASoC: qcom: q6apm: clear g_apm on driver removal (git-fixes).\n- ASoC: qcom: qdsp6: q6afe: fix clk vote response type mismatch (git-fixes).\n- ASoC: rockchip: rockchip_i2s: Handle runtime PM resume failures in set_fmt (git-fixes).\n- ASoC: rt711-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt711-sdw: always cancel jack work on remove (git-fixes).\n- ASoC: rt712-sdca-dmic: fix drvdata type in the gain controls (git-fixes).\n- ASoC: rt712-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt722-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt1011: return cache sync errors from resume (git-fixes).\n- ASoC: rt1016: return cache sync errors from resume (git-fixes).\n- ASoC: rt1305: return cache sync errors from resume (git-fixes).\n- ASoC: rt1308: return cache sync errors from resume (git-fixes).\n- ASoC: rt5616: return cache sync errors from resume (git-fixes).\n- ASoC: rt5659: return cache sync errors from resume (git-fixes).\n- ASoC: rt5660: return cache sync errors from resume (git-fixes).\n- ASoC: rt5665: return cache sync errors from resume (git-fixes).\n- ASoC: rt5682-sdw: always cancel jack work on remove (git-fixes).\n- ASoC: soc-ac97: Fix error handling in snd_soc_new_ac97_component() (git-fixes).\n- ASoC: soc-component: Fix return type of snd_soc_pcm_component_pointer() (git-fixes).\n- ASoC: ti: davinci-mcasp: Fix runtime PM imbalance in __davinci_mcasp_set_clkdiv() (git-fixes).\n- ASoC: wcd9335: Fix device reference leak in wcd9335_slim_status() (git-fixes).\n- ASoC: wcd-mbhc-v2: Fix incorrect properties names and typos (git-fixes).\n- ASoC: wm8994: don't lose the AIF clock ratio when staying at 32kHz SYSCLK (git-fixes).\n- ASoC: wm8994: fix MCLK gating for AIF clocks sourced from MCLK2 (git-fixes).\n- ASoC: wm8994: fix MCLK index used for setting MCLK rate (git-fixes).\n- ASoC: wm8994: Fix runtime PM imbalance in wm8994_component_probe() (git-fixes).\n- ASoC: wm8994: follow AIF clock source changes in MCLK gating (git-fixes).\n- ASoC: xilinx: formatter_pcm: Fix read-modify-write of AUD_CTRL in hw_params (git-fixes).\n- asymmetric_keys: reject trust keys without IDs (git-fixes).\n- ata: libata-scsi: abort multi-sector pass-through commands when multi_count is 0 (git-fixes).\n- ata: libata-scsi: Fix ata_scsi_hotplug() reference in kernel-doc (git-fixes).\n- ata: pata_parport: fix parport attach idr_alloc for (git-fixes).\n- ata: pata_parport: Fix use-after-free in new_device_store (git-fixes).\n- ata: sata_fsl: Fix use-after-free of host_priv on probe() failure (git-fixes).\n- backlight: lm3630a: Cancel delayed work before destroying workqueue (git-fixes).\n- backlight: qcom-wled: Fix NULL pointer dereference in wled_remove() (git-fixes).\n- backlight: qcom-wled: Fix unbalanced OVP IRQ enable at probe (git-fixes).\n- backlight: qcom-wled: Fix WLED3 brightness register stride (git-fixes).\n- Bluetooth: 6lowpan: Drain RCU readers on registration failure (git-fixes).\n- Bluetooth: 6lowpan: Pin module for 6lowpan_control debugfs file (git-fixes).\n- Bluetooth: 6LoWPAN: Use RCU-safe device list removal (git-fixes).\n- Bluetooth: Add missing newline to bt_dev_{err,warn}_ratelimited() (git-fixes).\n- Bluetooth: btintel: fix buffer over-read in btintel_hw_error() (git-fixes).\n- Bluetooth: btintel: validate DDC record lengths (git-fixes).\n- Bluetooth: btqcomsmd: Convert to platform remove callback returning void (stable-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table (stable-fixes).\n- Bluetooth: hci_conn: Lock parent access during enhanced SCO setup (git-fixes).\n- Bluetooth: hci_core: free the HCI ID if naming fails (git-fixes).\n- Bluetooth: hci_core: Keep RCU protection through LTK filtering (git-fixes).\n- Bluetooth: hci_debugfs: Pin module for debugfs file operations (git-fixes).\n- Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister (git-fixes).\n- Bluetooth: hci_sync: Fix inquiry cache use-after-free (git-fixes).\n- Bluetooth: hci_sync: fix mesh adv timeout units (git-fixes).\n- Bluetooth: hci_sync: Protect IRK identity reads with RCU (git-fixes).\n- Bluetooth: hci_sync: Serialize devcoredump reset during device open (git-fixes).\n- Bluetooth: hci_vhci: Pin module for debugfs file operations (git-fixes).\n- Bluetooth: ISO: Hold the listener during disconnect notification (git-fixes).\n- Bluetooth: L2CAP: hold chan in l2cap_ecred_conn_rsp() (git-fixes).\n- Bluetooth: L2CAP: hold l2cap_conn::lock in l2cap_connect_cfm() (git-fixes).\n- Bluetooth: L2CAP: Reject invalid TxWindow in configuration requests (git-fixes).\n- Bluetooth: L2CAP: Reject mode changes on connected channels (git-fixes).\n- Bluetooth: L2CAP: Use default TxWindow for zero socket option (git-fixes).\n- Bluetooth: MGMT: Fix leaking instance on Add Extended Advertising Parameters (git-fixes).\n- Bluetooth: MGMT: Fix pending state of instances added without HCI traffic (git-fixes).\n- Bluetooth: MGMT: Reject quality report requests during unregister (git-fixes).\n- Bluetooth: msft: Lock failed probe cleanup against feature readers (git-fixes).\n- Bluetooth: RFCOMM: Fix initial port reference race (git-fixes).\n- Bluetooth: selftest: Pin module for selftest debugfs file operations (git-fixes).\n- bus: arm-cci: Drop cci-control-port node reference in __cci_ace_get_port() (git-fixes).\n- bus: arm-cci: Drop CPU node reference in cci_ace_init_ports() (git-fixes).\n- bus: fsl-mc: register the object drivers after misc_class exists (git-fixes).\n- char: scx200_gpio: check cdev_add() return value (git-fixes).\n- checkpatch: skip CamelCase cache for --no-tree without root (git-fixes).\n- cifs: Pass unbyteswapped eof value into SMB2_set_eof() (git-fixes).\n- comedi: comedi_parport: validate the IRQ supplied by userspace (git-fixes).\n- comedi: dmm32at: validate the IRQ supplied by userspace (git-fixes).\n- comedi: dt2811: fix shift-out-of-bounds in IRQ check (git-fixes).\n- comedi: dt2814: validate the IRQ supplied by userspace (git-fixes).\n- comedi: ni_atmio16d: validate the IRQ supplied by userspace (git-fixes).\n- comedi: pcmmio: validate the IRQ supplied by userspace (git-fixes).\n- comedi: pcmuio: validate the IRQs supplied by userspace (git-fixes).\n- crypto: amlogic - Fix DMA memory leak in cipher error path (git-fixes).\n- crypto: amlogic - Fix IRQ handler return value and fallthrough logic (git-fixes).\n- crypto: asymmetric_keys - fix OOB read in pefile_parse_binary (git-fixes).\n- crypto: atmel - handle authenc requests without plaintext (git-fixes).\n- crypto: atmel-aes - fix AADLENR for standalone GHASH (git-fixes).\n- crypto: atmel-sha - reject initialization without a device (git-fixes).\n- crypto: atmel-tdes - sync output bounce buffer before DMA (git-fixes).\n- crypto: atmel-tdes - zero-initialize device state (git-fixes).\n- crypto: caam - fix double-free in caam_rsa_set_priv_key_form() (git-fixes).\n- crypto: ccp - kill v3 IRQ tasklet during teardown (git-fixes).\n- crypto: ccp - kill v5 IRQ tasklet during teardown (git-fixes).\n- crypto: hisilicon/hpre - fix ECDH destination DMA mapping (git-fixes).\n- crypto: hisilicon/hpre - fix GFP flags for dma_alloc_coherent (git-fixes).\n- crypto: hisilicon/hpre - fix pointer dereference before length check (git-fixes).\n- crypto: hisilicon/hpre - remove dma_free_coherent on NULL req-\u003edst in ECDH (git-fixes).\n- crypto: hisilicon/hpre - return -EOVERFLOW for small ECDH output buffer (git-fixes).\n- crypto: qat - avoid OOB read when stripping RSA leading zeros (git-fixes).\n- crypto: qat - fix active_devs leak on crypto alg registration failure (git-fixes).\n- crypto: qat - fix use of destroyed vf2pf_lock on VF restart (git-fixes).\n- crypto: qat - initialise state_lock on every path in adf_devmgr_add_dev() (git-fixes).\n- crypto: qat - release instance on DH fallback allocation failure (git-fixes).\n- crypto: qat - zero the VF migration state buffer on save (git-fixes).\n- crypto: tcrypt - Avoid reading req-\u003ebase after submission (git-fixes).\n- dmaengine: altera-msgdma: initialize state before requesting IRQ (git-fixes).\n- dmaengine: at_hdmac: Fix use-after-free by proper tasklet cleanup (git-fixes).\n- dmaengine: bestcomm: set bcom_eng to NULL on probe failure (git-fixes).\n- dmaengine: dw-axi-dmac: convert clock handling to clk_bulk API (git-fixes).\n- dmaengine: dw-axi-dmac: Fix AXI burst length encoding (git-fixes).\n- dmaengine: dw-axi-dmac: Fix CH_CFG2 channel priority position (git-fixes).\n- dmaengine: dw-axi-dmac: Fix LLI dump out-of-bounds access (git-fixes).\n- dmaengine: fsl_raid: avoid free_q underflow in free_chan_resources (git-fixes).\n- dmaengine: fsl_raid: don't invoke client callback under desc_lock (git-fixes).\n- dmaengine: fsl_raid: zero CF descriptor pool allocations (git-fixes).\n- dmaengine: img-mdc: Fix runtime PM usage counter leak (git-fixes).\n- dmaengine: ioat: disable relaxed ordering before registering the device (git-fixes).\n- dmaengine: mediatek: hsdma: fix runtime PM leak on init failure (git-fixes).\n- dmaengine: mv_xor: kill tasklet on channel add error path (git-fixes).\n- dmaengine: plx_dma: fix NULL pointer deref in plx_dma_isr() (git-fixes).\n- dmaengine: qcom: bam_dma: Defer IRQ trigger type to device tree (git-fixes).\n- dmaengine: qcom: bam_dma: free interrupt before the clock in error path (git-fixes).\n- dmaengine: sprd: use clk_bulk API to fix clock imbalance (git-fixes).\n- dmaengine: sun6i-dma: Fix use-after-free in error handling paths (git-fixes).\n- dmaengine: xilinx_dma: Fix MCDMA descriptor fields based on DMA direction (git-fixes).\n- Documentation: rs485: Pull uart_get_rs485_mode() from serial_core.c (git-fixes).\n- Documentation: virt: Fix the struct snp_guest_request_ioctl name in sev-guest.rst (git-fixes).\n- driver core: Limit the messages on a refused uevent (git-fixes).\n- drivers/base/node: fix UAF on device_register() failure (git-fixes).\n- drm/amd/display: assign missing trace entry in amdgpu_dm_dc_clocks_state (git-fixes).\n- drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs (stable-fixes).\n- drm/amd/display: Fix swap in median3() for DSC rate control (git-fixes).\n- drm/amd/display: fix vready offset assignment in dcn_optc_lock_unlock_state (git-fixes).\n- drm/amd/display: Force GAMCOR for subsampled surfaces with PQ/Gamma22/HLG (git-fixes).\n- drm/amd/display: remove duplicated prev_p_state_change_support assignment (git-fixes).\n- drm/amd/display: take a runtime PM reference only when a CRTC turns on (git-fixes).\n- drm/amd/display: Use kcalloc() instead of kzalloc() (stable-fixes).\n- drm/amd/display: use right type for amdgpu_dc_performance event entries (git-fixes).\n- drm/amd/pm: bound SCLK FCW range entries to the table size (git-fixes).\n- drm/amdgpu/atombios: drop empty function (stable-fixes).\n- drm/amdgpu/gfx6: fix firmware leak on teardown (stable-fixes).\n- drm/amdgpu/sdma3: Work around POLL_REGMEM / FENCE hang (stable-fixes).\n- drm/amdgpu: Check for multiplication overflow in checkpoint stack (bsc#1276280).\n- drm/amdgpu: make Mac FB workaround generic (stable-fixes).\n- drm/amdgpu: reject ANONONLY userptrs that span multiple VMAs (git-fixes).\n- drm/amdgpu: Remove unused amdgpu_i2c functions (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro14,3 (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro15,1 (stable-fixes).\n- drm/amdgpu: rework i2c init and fini (stable-fixes).\n- drm/amdgpu: serialize vblank counter reads against GPU reset (stable-fixes).\n- drm/amdgpu: Use dbg level for VBIOS check messages (stable-fixes).\n- drm/amdkfd: evict the queues only once for CRIU PROCESS_INFO (git-fixes).\n- drm/amdkfd: Fix checkpoint-restore on multi-xcc (bsc#1276280).\n- drm/amdkfd: fix doorbell allocation race creating duplicate allocations (git-fixes).\n- drm/amdkfd: validate SRAT subtables before parsing (git-fixes).\n- drm/bridge: analogix_dp: Restore mandatory samsung DP DT properties (git-fixes).\n- drm/exynos/fimd: fix register offset type in fimd_trigger() (git-fixes).\n- drm/imx/lcdc: avoid duplicate clk_per enable (git-fixes).\n- drm/komeda: Fix bits parsing of GLB_CORE_ID (git-fixes).\n- drm/mali-dp: Fix runtime PM leak in malidp_crtc_atomic_enable() (git-fixes).\n- drm/msm/a6xx: Fix secondary rail vote in ARC votes (git-fixes).\n- drm/msm/a6xx: fix use-after-free of OPP in a6xx_pm_resume (git-fixes).\n- drm/msm/dp: don't report link training success after a reinit (git-fixes).\n- drm/msm/dpu: disable the slave encoder before the master (git-fixes).\n- drm/msm/hdmi_phy: Cleanup after msm_hdmi_phy_resource_enable() failure (git-fixes).\n- drm/msm/mdp5: drop cursor pipe for msm8x76 (git-fixes).\n- drm/msm: Properly handle msm_ioremap() without name (git-fixes).\n- drm/nouveau/svm: drain fault handler before freeing svmm (git-fixes).\n- drm/nouveau: cancel the DP IRQ work before freeing the connector (git-fixes).\n- drm/nouveau: disable the fence uevent work instead of just cancelling it (git-fixes).\n- drm/nouveau: don't dereference outp before checking it in nouveau_dp_irq (git-fixes).\n- drm/nouveau: reject zero-size notifier object allocation (git-fixes).\n- drm/omap: dsi: avoid sending bta sync all the time in writes (git-fixes).\n- drm/panel: ebbg-ft8719: Set prepare_prev_first (git-fixes).\n- drm/panfrost: Explicitly enable MMU interrupts at device init (git-fixes).\n- drm/panfrost: Prevent division by 0 (git-fixes).\n- drm/tegra: Don't pass an ERR_PTR to drm_syncobj_replace_fence() (git-fixes).\n- drm/tegra: Drop reference on postfence (git-fixes).\n- drm/tegra: Fix syncobj_in wait return value check (git-fixes).\n- drm: of: Fix drm_of_get_data_lanes_count_ep() return value documentation (git-fixes).\n- fbdev: atmel_lcdfb: Prevent FIFO work after removal (git-fixes).\n- fbdev: gxt4500: Release WC setup on probe failure (git-fixes).\n- fbdev: sh_mobile_lcdc: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: smscufx: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: ssd1307fb: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: udlfb: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: udlfb: don't rebuild the mode list while the framebuffer is in use (git-fixes).\n- fbdev: xen-fbfront: check for fb_deferred_io_init() error (git-fixes).\n- firewire: cdev: Fix FW_CDEV_IOC_CREATE_ISO_CONTEXT references in kernel-doc (git-fixes).\n- firmware: cs_dsp: clear dsp-\u003erunning on the cs_dsp_run() error path (git-fixes).\n- firmware: imx: dsp: fix mailbox channel leak on kasprintf failure (git-fixes).\n- fpga: Fix of_fpga_mgr_get() reference in fpga_mgr_lock() docs (git-fixes).\n- gpio: crystalcove: add missing MODULE_ALIAS() (git-fixes).\n- gpio: davinci: Clear interrupt status in every bank on suspend (git-fixes).\n- gpio: mxc: fix both_edges bit operations (git-fixes).\n- gpio: mxc: fix wakeup_pads bit operations (git-fixes).\n- gpio: mxc: use BIT() macro (stable-fixes).\n- gpio: mxc: use lock guards for the generic GPIO chip lock (stable-fixes).\n- gpio: pca953x: Preserve wakeup accounting on parent IRQ failure (git-fixes).\n- HID: alps: unregister DualPoint Stick input device on remove (git-fixes).\n- HID: amd_sfh: Remove unsupported motion-state field from accelerometer report (git-fixes).\n- HID: amd_sfh: Use report type from request node (git-fixes).\n- HID: core: Add reserved item tag for main items (stable-fixes).\n- HID: core: Fix out-of-bounds left shift by 32 in s32ton() (git-fixes).\n- HID: cougar: reject short special-key reports (git-fixes).\n- HID: cp2112: validate response report lengths (git-fixes).\n- HID: elo: reject short touchscreen reports (git-fixes).\n- HID: hid-alps: Use pm_ptr instead of #ifdef CONFIG_PM (stable-fixes).\n- HID: hid-steam: Make client_opened a counter (stable-fixes).\n- HID: logitech-dj: validate unnumbered keyboard reports (git-fixes).\n- HID: mcp2221: clear rxbuf after I2C/SMBus transfer completes (git-fixes).\n- HID: mcp2221: fix OOB write in mcp2221_raw_event() (stable-fixes).\n- HID: mcp2221: validate response report length (git-fixes).\n- HID: picoLCD: check for fb_deferred_io_init() error (git-fixes).\n- HID: pxrc: reject short input reports (git-fixes).\n- HID: rate-limit hid_warn to prevent log flooding (stable-fixes).\n- HID: roccat: isku: reject short button reports (git-fixes).\n- HID: roccat: koneplus: reject short button reports (git-fixes).\n- HID: roccat: konepure: reject short button reports (git-fixes).\n- HID: roccat: kovaplus: reject short button reports (git-fixes).\n- HID: roccat: pyra: reject short button reports (git-fixes).\n- HID: roccat: ryos: reject short special reports (git-fixes).\n- HID: roccat: savu: reject short special reports (git-fixes).\n- HID: wacom: fix wacom_intuos_irq NULL pen_input deref (git-fixes).\n- HID: zydacron: validate key report length (git-fixes).\n- hwmon: (coretemp) Refresh the temperature on the first read (git-fixes).\n- hwmon: (corsair-cpro) Make wait_input_report_lock IRQ safe (git-fixes).\n- hwmon: (lm70) Fix rounding of negative temperatures (git-fixes).\n- hwmon: (lm95245) Fix negative temperature conversion (git-fixes).\n- hwmon: (sht3x) Return the consumed count for heater writes (git-fixes).\n- hwrng: amd - report partial reads in non-blocking mode (git-fixes).\n- hwrng: ba431 - fix reported byte count (git-fixes).\n- hwrng: cctrng - Fix runtime PM usage counter leak (git-fixes).\n- hwrng: core - reject unknown RNG names (git-fixes).\n- hwrng: intel - return -ENOMEM when ioremap() fails (git-fixes).\n- hwrng: intel - return -ENOMEM when kmalloc_obj() fails (git-fixes).\n- hwrng: starfive - propagate clock and reset errors (git-fixes).\n- i2c: acpi: Fix adapter reference leak in i2c_acpi_new_device_by_fwnode() (git-fixes).\n- i2c: at91: release DMA channels when probe defers (git-fixes).\n- i2c: designware: queue only one read command for block reads (git-fixes).\n- i2c: mt7621: fix copying uninitialized kernel stack with reduced page_len (git-fixes).\n- i2c: qcom-cci: Fix HALT_ACK reset request being dropped (git-fixes).\n- i2c: xiic: don't clobber msg-\u003elen to signal block-read completion (git-fixes).\n- i2c: xiic: Relocate xiic_i2c_runtime_suspend and xiic_i2c_runtime_resume to facilitate atomic mode (stable-fixes).\n- iio: accel: adis16201: fix channel order for buffer mode (git-fixes).\n- iio: accel: kionix-kx022a: Fix IPOL macro name (git-fixes).\n- iio: accel: kxcjk-1013: Disable autosuspend on remove (git-fixes).\n- iio: accel: mma9551: disable autosuspend on remove (git-fixes).\n- iio: accel: mma9553: disable autosuspend on remove (git-fixes).\n- iio: adc: aspeed: propagate reset deassert errors (git-fixes).\n- iio: adc: aspeed: Simplify with dev_err_probe (stable-fixes).\n- iio: adc: at91-sama5d2: disable autosuspend on remove (git-fixes).\n- iio: adc: stm32: fix minimum sampling time values (git-fixes).\n- iio: adc: ti-adc128s052: validate SPI match data (git-fixes).\n- iio: core: add accessors 'masklength' (stable-fixes).\n- iio: dac: ad5758: Fix alignment for DMA safety (git-fixes).\n- iio: dac: ad5758: Fix the offset calculation (git-fixes).\n- iio: dac: ad5758: Reject out-of-range raw values (git-fixes).\n- iio: humidity: hts221: report available values via read_avail() (git-fixes).\n- iio: imu: adis16400: Check return value of spi_setup() (git-fixes).\n- iio: light: ltrf216a: Return floating point values (stable-fixes).\n- iio: pressure: dps310: fix CFG_REG bit definitions (git-fixes).\n- iio: temperature: tmp117: fix calibbias cache update on I2C write failure (git-fixes).\n- Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11 (stable-fixes).\n- Input: da7280 - fix input device parent assignment (git-fixes).\n- Input: drv2665 - fix input device parent assignment (git-fixes).\n- Input: drv2667 - fix input device parent assignment (git-fixes).\n- Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410 (stable-fixes).\n- Input: lkkbd - disable pending work before freeing device (stable-fixes).\n- Input: maple_keyb - fix key press detection (git-fixes).\n- Input: maplecontrol - emit EV_SYN report after reporting events (git-fixes).\n- Input: matrix-keymap - reject keycodes above KEY_MAX (git-fixes).\n- Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490 (stable-fixes).\n- Input: tps6507x-ts - fix input device parent assignment (git-fixes).\n- Input: xpad - add support for Corsair Novablade Pro (stable-fixes).\n- kernel-binary.spec.in: Emulate kabi.pl error when suse-kabi-tools is used.\n- kobject: fix out-of-bounds access in kobject_action_type() (git-fixes).\n- kobject: Fix the kobj_set_name reference in kset_register() kernel-doc (git-fixes).\n- KVM: SEV: Do cache maintenance on the source VM *before* clearing SEV state (git-fixes).\n- leds: flash: Prevent using uninitialized variable in flash_fault_show() (git-fixes).\n- leds: lm3692x: Fix regulator/gpio leak and wrong enabled state on last write failure (git-fixes).\n- leds: lp8860: Fix device_node leak in lp8860_probe() (git-fixes).\n- leds: pca9532: Check i2c_smbus_read_byte_data() return value (git-fixes).\n- lib/decompress_bunzip2: fix off-by-one in run-length bounds check (git-fixes).\n- lib: decompress_bunzip2: fix integer overflow in run-length decoding (git-fixes).\n- lib: validate in-memory LZ4 chunk length (git-fixes).\n- mac80211: tx: Use info-\u003eflags in ieee80211_tx_h_select_key() (git-fixes).\n- media: adv748x: Fix endpoint reference leaks on probe failure (git-fixes).\n- media: adv7180: Initialize mutex before ancillary clients (git-fixes).\n- media: adv7604: avoid negative array index in log_status when cp_read fails (git-fixes).\n- media: amphion: fix runtime PM imbalance on probe failure (git-fixes).\n- media: amphion: prevent unbind while video instances are open (git-fixes).\n- media: atmel-isi: release unregistered video device on remove (git-fixes).\n- media: au0828: Fix media device leak in au0828_usb_probe() (git-fixes).\n- media: au0828: fix use-after-free in bulk_timeout timer on disconnect (git-fixes).\n- media: au0828: Free URBs when starting DVB streaming fails (git-fixes).\n- media: cx18: Disable PCI device on probe failure (git-fixes).\n- media: cx88: Disable PCI device on MPEG initialization failure (git-fixes).\n- media: cx231xx-audio: drain wq_trigger before audio fini (git-fixes).\n- media: cx231xx: Fix cleanup path on failure (git-fixes).\n- media: cx23885: Fix use-after-free in cx23885_finidev due to race condition (git-fixes).\n- media: cx23885: unregister DVB bus when SP2 CI setup fails (git-fixes).\n- media: em28xx: fix double free in em28xx_alloc_urbs (git-fixes).\n- media: em28xx: reject audio endpoint with zero packet size (git-fixes).\n- media: exynos4-is: Fix a race between s_stream(0) and the interrupt handler (git-fixes).\n- media: go7007: bound EZ-USB I2C transfers to the usb_buf size (git-fixes).\n- media: go7007: unregister the I2C adapter on USB probe failure (git-fixes).\n- media: gspca: use vb2_video_unregister_device() on disconnect (git-fixes).\n- media: hackrf: fix use-after-free in hackrf_alloc_urbs() error path (git-fixes).\n- media: hantro: Disable multicore support (stable-fixes).\n- media: hantro: disable runtime PM before hardware teardown (git-fixes).\n- media: hantro: Harden MPEG-2 control access against NULL (git-fixes).\n- media: i2c: ar0521: remove duplicate media entity cleanup (git-fixes).\n- media: i2c: ov5648: Fix a data race on state-\u003estreaming (git-fixes).\n- media: i2c: ov8856: fix debug message to report actual CSI-2 lane count (git-fixes).\n- media: i2c: tc358743: add missing color-space strings (git-fixes).\n- media: imon: fix use-after-free in display_close via dev_dbg (git-fixes).\n- media: imx-jpeg: cancel timeout worker when streaming stops (git-fixes).\n- media: imx-jpeg: finish the job on device_run() error paths (git-fixes).\n- media: ir-hix5hd2: Ensure rdev is setup before interrupts are enabled (git-fixes).\n- media: ir_toy: Validate the maximum tx carrier (git-fixes).\n- media: m2m-deinterlace: fix default capture field (git-fixes).\n- media: marvell-cam: fix unmet dependency for VIDEO_MMP_CAMERA (git-fixes).\n- media: marvell: manage the MMP camera clock provider (git-fixes).\n- media: mediatek: jpeg: Avoid context access after job finish (git-fixes).\n- media: mediatek: jpeg: retry HW selection after successful wait (git-fixes).\n- media: mediatek: vpu: free IRQ before destroying watchdog workqueue (git-fixes).\n- media: mediatek: vpu: release reserved memory on remove (git-fixes).\n- media: meson-ir-tx: Ensure clock is disabled on unbind (git-fixes).\n- media: meson-ir-tx: Ensure probe error is propagated (git-fixes).\n- media: meson-ir-tx: Prevent divide by zero in meson_irtx_prepare_pulse() (git-fixes).\n- media: meson: vdec: size capture planes from the aligned canvas (git-fixes).\n- media: microchip-csi2dc: fix async notifier leak on probe error path (git-fixes).\n- media: microchip-isc: disable histogram and flush AWB work on teardown (git-fixes).\n- media: microchip-isc: do not touch WB registers when not streaming (git-fixes).\n- media: microchip-isc: fix PM runtime leak in AWB work handler (git-fixes).\n- media: microchip-isc: synchronize the IRQ before disabling clocks on stop (git-fixes).\n- media: mtk-jpeg: Fix runtime PM leak in mtk_jpegdec_worker() (git-fixes).\n- media: mtk-jpeg: Fix runtime PM leak in mtk_jpegenc_worker() (git-fixes).\n- media: platform: mtk-mdp3: Fix device reference leak in mdp_comp_init() (git-fixes).\n- media: pvrusb2: Fix USB parent device leak in class_dev_create() (git-fixes).\n- media: rc: fintek-cir: process a full RX buffer instead of overflowing it (git-fixes).\n- media: rc: mce_kbd: Fix inconsistent locking of keylock (git-fixes).\n- media: redrat3: Ensure all urbs are suspended (git-fixes).\n- media: redrat3: Ensure we don't read beyond the end of the packet (git-fixes).\n- media: redrat3: fix UAF in probe error path leaving rc device registered (git-fixes).\n- media: require two-byte Cypress type 04 records (git-fixes).\n- media: rtl28xxu: fix SDR platform device leak (git-fixes).\n- media: saa7146: Initialize interrupt lock before requesting IRQ (git-fixes).\n- media: streamzap: Add missing rc_unregister_device() (git-fixes).\n- media: stv090x: bound DiSEqC reply length to msg size (git-fixes).\n- media: stv0900: bound DiSEqC reply length to msg size (git-fixes).\n- media: tw68: balance PCI enable on cleanup (git-fixes).\n- media: tw686x: fix V4L2 device lifetime on probe failure (git-fixes).\n- media: uvcvideo: Fix NULL deref on events for uninitialized controls (git-fixes).\n- media: v4l2-ctrls: do nothing if controls == NULL in cluster functions (git-fixes).\n- media: venus: Drop session events without an instance (git-fixes).\n- media: vicodec: fix NULL deref on oversized frame (git-fixes).\n- media: vicodec: fix out-of-bounds write on under-rounded coded dimensions (git-fixes).\n- media: vicodec: make encoder CAPTURE dimensions read-only (git-fixes).\n- media: vicodec: zero-initialize stateful decoder heap buffers (git-fixes).\n- media: vidtv: fix frontend reference leak on unbind (git-fixes).\n- media: vidtv: fix uaf in vidtv_bridge_on_new_pkts_avail (git-fixes).\n- media: vim2m: keep transaction buffer count stable while streaming (git-fixes).\n- media: vivid: round the height down to the vertical subsampling factor (git-fixes).\n- media: vpif_display: Fix i2c adapter reference leak in vpif_probe() (git-fixes).\n- mfd: ab8500: Fix child device leaks on probe failure (git-fixes).\n- mfd: da9150: Balance IRQ wake on teardown (git-fixes).\n- mfd: intel_quark_i2c_gpio: Manage the fixed-rate clock (git-fixes).\n- mfd: tps65217: Check return value when masking interrupt sources (git-fixes).\n- mfd: tps65217: Fix NULL pointer dereference on IRQ init failure (git-fixes).\n- mfd: wcd934x: Fix NULL pointer dereference on IRQ probe deferral (git-fixes).\n- mfd: wcd934x: set DMA mask on parent to silence \"DMA mask not set\" (git-fixes).\n- misc: enclosure: fix UAF on device_register() failure (git-fixes).\n- mm, vmscan: flush tlb before large folio is freed (bsc#1250656).\n- mm: introduce num_pages_contiguous() (bsc#1284243).\n- mtd: amd76xrom: Fix PCI device reference leak in amd76xrom_init_one() (git-fixes).\n- mtd: block: prevent reclaim I/O during request processing (git-fixes).\n- mtd: Call get_wunit() on the master partition (git-fixes).\n- mtd: cfi_cmdset_0002: cap the write-buffer chunk at 256 bytes on an x8 device (git-fixes).\n- mtd: maps: l440gx: Fix double put of the ISA bridge in init_l440gx() (git-fixes).\n- mtd: maps: l440gx: Fix double put of the PM device in init_l440gx() (git-fixes).\n- mtd: maps: pci: balance PCI enable on cleanup (git-fixes).\n- mtd: parsers: qcom: fix offset/size overflow on large partitions (git-fixes).\n- mtd: rawnand: atmel: Fix MCK clock leak in atmel_nand_controller_init() (git-fixes).\n- mtd: rawnand: pl353: fix clk reference leak in pl35x_nfc_setup_interface() (git-fixes).\n- mtd: rawnand: sunxi: reject ECC maximization on small pages (git-fixes).\n- mtd: spi-nor: sfdp: check the length of the SCCR map (git-fixes).\n- mtd: spi-nor: sfdp: check the length of the xSPI Profile 1.0 table (git-fixes).\n- mtd: spi-nor: Unprepare legacy controllers upon RWW wait interruption (git-fixes).\n- mtd: spinand: Fix spinand_manufacturer_ops kernel-doc (git-fixes).\n- net/rds: tcp: don't force RDS_CONN_RESETTING over a concurrent shutdown (git-fixes).\n- net/rds: use clear_bit_unlock() in release_refill() (git-fixes).\n- net: usb: cdc_mbim: don't enable BHs in tx_fixup under netpoll (git-fixes).\n- net: usb: cdc_ncm: don't enable BHs in tx_fixup under netpoll (git-fixes).\n- net: usb: lan78xx: reject invalid EEPROM write requests (git-fixes).\n- net: usb: pegasus: check rx pkt_len against the received length (git-fixes).\n- net: usb: pegasus: do not advance rx_skb-\u003edata on dropped frames (git-fixes).\n- net: usb: r8153_ecm: reject short register reads (git-fixes).\n- net: usb: sierra_net: reject short firmware attribute reads (git-fixes).\n- net: wwan: iosm: validate msg_head before indexing msg_ring (git-fixes).\n- PCI/AER: Fix memory leak in aer_recover_queue() on kfifo buffer overflow (git-fixes).\n- PCI/P2PDMA: Gate the host bridge whitelist warning on verbose (git-fixes).\n- PCI/sysfs: Handle a malformed _DSM result in acpi_attr_is_visible() (git-fixes).\n- PCI/sysfs: Pass the device name length in UTF-16 code units (git-fixes).\n- PCI/sysfs: Stop reporting _DSM failures as -EPERM (git-fixes).\n- PCI: aardvark: Disable PHY on probe failures (git-fixes).\n- PCI: cadence: Preserve all error codes in cdns_plat_pcie_probe() (git-fixes).\n- PCI: Disable MSI for ULi M1575 EHCI controller (git-fixes).\n- PCI: dra7xx: Fix clock enable leak on probe failure (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Pass PF/VF number when BAR programming (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Serialize virtual PCI bus scan (git-fixes).\n- PCI: Fix out-of-bounds MMIO read in nvme_disable_and_flr() (git-fixes).\n- PCI: qcom: Honor IOMMU provider's #iommu-cells in qcom_pcie_config_sid_1_9_0() (git-fixes).\n- PCI: rockchip-host: Do not attempt 5.0 GT/s retraining (git-fixes).\n- PCI: xgene: Use managed clock for PCIe controller (git-fixes).\n- peci: aspeed: Initialize state before requesting IRQ (git-fixes).\n- phy: cadence: Sierra: Do not modify register when getting parent clock (git-fixes).\n- phy: core: Fix race-condition between _of_phy_get() and try_module_get() (git-fixes).\n- phy: HiSilicon: Fix error handling in hi3670_pcie_allclk_ctrl() (git-fixes).\n- phy: hisilicon: hi3670: Fix OF node and device reference leaks (git-fixes).\n- pinctrl: mediatek: mt7629: fix the 2.4 GHz Wi-Fi pin mode array (git-fixes).\n- pinctrl: sprd: free maps on DT map failure (git-fixes).\n- pinctrl: stm32: Fix fwnode reference leak in stm32_gpiolib_register_bank() (git-fixes).\n- platform/chrome: cros_ec_proto: Fix deferred response (git-fixes).\n- platform/olpc: Reserve space for a string terminator (git-fixes).\n- platform/x86/amd/pmc: Fix RTC reference leak in amd_pmc_verify_czn_rtc() (git-fixes).\n- platform/x86/amd: Stop counting intermediate cycles with metrics table (git-fixes).\n- platform/x86/intel-uncore-freq: Continue restoring limits on resume (git-fixes).\n- platform/x86: asus-wmi: validate custom fan curves on enable (git-fixes).\n- platform/x86: gpd pocket fan: Cancel work before releasing GPIOs (git-fixes).\n- platform/x86: hp-wmi: fix heap OOB read and memory corruption in hp_wmi_perform_query() (git-fixes).\n- platform/x86: ibm_rtl: Fix potential OOB read at signature search (git-fixes).\n- platform/x86: intel_telemetry: initialize default trace verbosity (git-fixes).\n- platform/x86: msi-ec: Report valid charge thresholds when unset (git-fixes).\n- power: supply: ab8500: Preserve battery termination current (git-fixes).\n- power: supply: ab8500_btemp: Fix event temperature reporting (git-fixes).\n- power: supply: ab8500_charger: Decode AB8505 USB status (git-fixes).\n- power: supply: ab8500_charger: Fix AC charger re-enable (git-fixes).\n- power: supply: ab8500_charger: Handle detection errors (git-fixes).\n- power: supply: ab8500_charger: Recover inactive AB8505 charger (git-fixes).\n- power: supply: ab8500_charger: Respect AB8505 register layout (git-fixes).\n- power: supply: ab8500_charger: Retry AB8505 USB detection (git-fixes).\n- power: supply: ab8500_charger: Skip absent AB8505 main charger (git-fixes).\n- power: supply: ab8500_fg: Accept status from supplied power (git-fixes).\n- power: supply: ab8500_fg: Avoid reserved AB8505 CCConf bit (git-fixes).\n- power: supply: ab8500_fg: Finalize current measurements (git-fixes).\n- power: supply: ab8500_fg: Report sub-percent charge changes (git-fixes).\n- power: supply: bq2515x: Propagate charge-enable read errors (git-fixes).\n- power: supply: charger-manager: Convert to platform remove callback returning void (stable-fixes).\n- power: supply: generic-adc-battery: fix status with no supplier (git-fixes).\n- power: supply: generic-adc-battery: Propagate charged GPIO errors (git-fixes).\n- power: supply: gpio-charger: Report discharging without input power (git-fixes).\n- power: supply: lp8788-charger: Convert to platform remove callback returning void (stable-fixes).\n- power: supply: lp8788-charger: fix use-after-free on remove (git-fixes).\n- power: supply: lp8788: Use devm_power_supply_register() helper (stable-fixes).\n- power: supply: mp2629: Use the full batt_impedance_compensation name in the ABI document (git-fixes).\n- power: supply: qcom_battmgr: report full batteries (git-fixes).\n- power: supply: qcom_battmgr: report the USB type from USB_ADAP_TYPE (git-fixes).\n- power: supply: sbs-battery: disable polling before supply teardown (git-fixes).\n- pwm: mtk-disp: Fix period readback (git-fixes).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- regulator: ab8500: Fix AB8505 VANA voltage selectors (git-fixes).\n- regulator: ab8500: Handle AB8505 VINTCORE selector 7 (git-fixes).\n- regulator: ab8500: Propagate mode enable read errors (git-fixes).\n- regulator: ab8500: Test dedicated enable bits only (git-fixes).\n- regulator: ab8500: Treat cut 1.0 VAUX3 as fixed (git-fixes).\n- regulator: core: Fix c_rdev reference leak in regulator_resolve_coupling() (git-fixes).\n- regulator: core: Fix coupled regulators reference leak on removal (git-fixes).\n- regulator: core: Fix rdev reference leak in regulator_resolve_supply() (git-fixes).\n- regulator: mp886x: check get_voltage_sel() return value (git-fixes).\n- regulator: mp886x: fix pontential division by zero (git-fixes).\n- regulator: mp886x: fix vsel_mask (git-fixes).\n- regulator: rt6190: Fix runtime PM imbalance in rt6190_out_enable() (git-fixes).\n- Reinstate \"resource: avoid unnecessary lookups in find_next_iomem_res()\" (bsc#1284243).\n- Revert \"mkspec: Exclude rt flavor from kernel-syms dependencies\" (bsc#1244337).\n- Revert \"rpm/mkspec: Fix missing kernel-syms-rt creation\" (bsc#1244337).\n- Revert \"wifi: mac80211: do not use old MBSSID elements\" (git-fixes).\n- rtc: abx80x: fix error check after i2c_smbus_read in read_alarm() (git-fixes).\n- rtc: abx80x: properly handle shared IRQs (git-fixes).\n- rtc: ac100: Assign .num before accessing .hws (git-fixes).\n- rtc: cmos: Disable ACPI RTC event before handling it (git-fixes).\n- rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak (git-fixes).\n- rtc: ds1685: arm the wake-up alarm at power-off only if an alarm is set (git-fixes).\n- rtc: ds1685: do not sleep in the power-off handler (git-fixes).\n- rtc: ftrtc010: fix integer overflow in time calculation (git-fixes).\n- rtc: mpfs: Fix alarm register word order (git-fixes).\n- rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe() (git-fixes).\n- rtc: s35390a: Add missing newline to dev_err (git-fixes).\n- rtc: s35390a: Fix alarm not disabling (git-fixes).\n- rtc: spear: initialize IRQ state before requesting alarm IRQ (git-fixes).\n- selftests/alsa: Do not take another control's event as our own (git-fixes).\n- serial: 8250_lpss: do not touch uninitialized line in ehl_serial_exit() (git-fixes).\n- serial: core: shut down initialized port on removal (git-fixes).\n- serial: max310x: don't clobber the TX break bit in set_termios (git-fixes).\n- serial: pmac_zilog: push received data to the port that received it (git-fixes).\n- serial: pmac_zilog: report received breaks (git-fixes).\n- slimbus: messaging: fix leaked PM vote on tid allocation failure (git-fixes).\n- smb: client: fix next_buffer UAF and NextCommand bounds in compound PDUs (git-fixes).\n- smb: client: use kzalloc to zero-initialize security descriptor buffer (git-fixes).\n- smb: common: change the data type of num_aces to le16 (git-fixes).\n- soc/tegra: flowctrl: Release OF node reference on error (git-fixes).\n- soc: fsl: cpm1: tsa: Fix clock leak in tsa_of_parse_tdms() (git-fixes).\n- soc: fsl: dpio: Fix cleanup on IRQ registration failure (git-fixes).\n- soc: fsl: dpio: Free the IRQ before releasing the I/O object (git-fixes).\n- soc: qcom: apr: clean up failed service registrations (git-fixes).\n- soc: ti: k3-ringacc: Correct ring API kernel-doc (git-fixes).\n- soc: ti: k3-ringacc: Fix DMA ring initialization kernel-doc (git-fixes).\n- soundwire: intel: initialise quirk_mask before reading it (git-fixes).\n- spi: amd: fix len==0 underflow and FIFO overflow (git-fixes).\n- spi: bcm63xx-hsspi: Disable runtime PM on remove (git-fixes).\n- spi: Fix the return value in spi_new_ancillary_device() kernel-doc (git-fixes).\n- spi: jcore: fix divide-by-zero when speed_hz is zero (git-fixes).\n- spi: mtk-nor: fix runtime PM usage count leak in probe error path (git-fixes).\n- spi: mxic: fix ps_clk leak in runtime resume (git-fixes).\n- spi: npcm-fiu: limit UMA data_size to the 16-byte staging buffer (git-fixes).\n- spi: omap2-mcspi: Remove unbalanced pm_runtime_put_sync() calls (git-fixes).\n- spi: spi-sun4i: sun4i_spi_fill_fifo(): always apply A10 FIFO fill level workaround (git-fixes).\n- spi: spi-sun4i: sun4i_spi_transfer_one(): fix transfers for SUN4I_FIFO_DEPTH (git-fixes).\n- spi: zynq-qspi: fix address buffer corruption and support 4-byte address (git-fixes).\n- staging: iio: adc: ad7816: Fix DMA safety issues in SPI transfers (git-fixes).\n- staging: media: av7110: fix corrupted BER reporting in sp8870 (git-fixes).\n- staging: media: imx: csc-scaler: fix ipu_image_convert_run leak on queue error (git-fixes).\n- staging: rtl8723bs: clean up redundant \u0026 parentheses (stable-fixes).\n- Staging: rtl8723bs: Delete dead code from update_current_network() (stable-fixes).\n- staging: rtl8723bs: fix buffer over-read in rtw_update_protection (git-fixes).\n- staging: rtl8723bs: fix RX buffer OOB write from device-reported length (git-fixes).\n- Staging: rtl8723bs: Remove dead code from _rtw_free_network() (stable-fixes).\n- staging: sm750fb: free cmap on framebuffer release (git-fixes).\n- thermal/drivers/sprd: validate the sensor id from the device tree (git-fixes).\n- thermal: Fix CPU mask truncation in power limit trace event (git-fixes).\n- thermal: intel: int340x: Fix temperature selection around 0 C (git-fixes).\n- thermal: intel: powerclamp: Reject invalid window_size values (git-fixes).\n- thermal: ti-soc-thermal: Fix the return value in ti_bandgap_get_sensor_data() kernel-doc (git-fixes).\n- thunderbolt: Disable CL states for the Anker Prime TB5 dock (stable-fixes).\n- thunderbolt: Do not RPM complete unrelated subtrees on unplug (git-fixes).\n- tools/thermal/tmon: Fix string truncation warning in optarg copy (git-fixes).\n- tpm: fix zero-length read discarding the pending response (git-fixes).\n- tpm: tpm_nsc: fix NULL pointer dereference on init failure (git-fixes).\n- tpm: tpm_nsc: stop using the cleanup callback as dev.release (git-fixes).\n- tty: add break_wait kernel-doc (git-fixes).\n- tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup (stable-fixes).\n- tty: vcc: zero-initialize control packet in vcc_send_ctl() (stable-fixes).\n- usb-storage: alauda: check the return value of alauda_read_map() (git-fixes).\n- usb-storage: alauda: do not do DMA from the stack (git-fixes).\n- usb-storage: alauda: fix out-of-bounds zone index (git-fixes).\n- USB: cdc-acm: fix urb leak on disconnect (git-fixes).\n- usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke() (stable-fixes).\n- usb: dwc3: clear forceRM when issuing EndTransfer (git-fixes).\n- usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition (git-fixes).\n- usb: dwc3: gadget: Reinitiate stream for all host NoStream behavior (stable-fixes).\n- usb: fotg210: validate endpoint index in ep0 handlers (git-fixes).\n- usb: gadget: composite: avoid warning on aborted delayed status (git-fixes).\n- usb: gadget: dummy_hcd: fix SuperSpeed ep0 maxpacket (git-fixes).\n- usb: gadget: dummy_hcd: prevent unbind via sysfs (git-fixes).\n- usb: gadget: f_fs: Fix Use-After-Free in AIO error path (git-fixes).\n- usb: gadget: f_mass_storage: ignore class requests while inactive (git-fixes).\n- usb: gadget: f_midi: Annotate struct f_midi with __counted_by (stable-fixes).\n- usb: gadget: f_midi: initialize work in f_midi_alloc() (git-fixes).\n- USB: gadget: ffs: fix mm lifetime handling (stable-fixes).\n- usb: gadget: functionfs: Factorize wait-for-endpoint code (stable-fixes).\n- USB: gadgetfs: do not WARN about excessively large memory allocations (git-fixes).\n- usb: image: microtek: stop SG processing after transfer errors (git-fixes).\n- usb: musb: da8xx: depopulate OF children on probe failure (git-fixes).\n- usb: musb: da8xx: depopulate OF children on remove (git-fixes).\n- usb: ohci-spear: disable controller wakeup on removal (git-fixes).\n- usb: ohci-spear: Remove unnecessary NULL check before clk_disable_unprepare() (stable-fixes).\n- USB: pci-quirks: Release EHCI device reference (git-fixes).\n- USB: serial: cp210x: add Corsair AX1500i Power Supply (stable-fixes).\n- USB: serial: option: add Compal EXC-T1 support (stable-fixes).\n- USB: serial: option: add Compal EXM-G1x support (stable-fixes).\n- USB: serial: option: add Quectel EG060W (stable-fixes).\n- USB: serial: option: add Quectel RG660QB (stable-fixes).\n- USB: serial: option: add support for SIMCom SIM8260C (stable-fixes).\n- USB: serial: sierra: fix urb leak on write completion (git-fixes).\n- USB: serial: usb_wwan: fix urb leak on disconnect (git-fixes).\n- usb: typec: ucsi_ccg: Add retry mechanism in ccg_read (git-fixes).\n- USB: usbmon: fix null-ptr-deref in mon_bus_remove() when mon_bus_init() fails (git-fixes).\n- usbnet: fix EVENT_RX_PAUSED race in usbnet_skb_return() (git-fixes).\n- usbnet: fix smp_processor_id() use in preemptible context (git-fixes).\n- vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote() (bsc#1284243).\n- vfio/type1: conditional rescheduling while pinning (bsc#1284243).\n- vfio/type1: introduce a new member has_rsvd for struct vfio_dma (bsc#1284243).\n- vfio/type1: optimize vfio_pin_pages_remote() (bsc#1284243).\n- vfio/type1: optimize vfio_unpin_pages_remote() (bsc#1284243).\n- vt: skip screen update for DEC alignment test on backgroup consoles (git-fixes).\n- watchdog: mediatek: Apply the driver's mode to a watchdog left running (git-fixes).\n- wifi: ath6kl: don't take RTNL in del_virtual_intf (git-fixes).\n- wifi: ath9k: delete channel-context timers on deinit (git-fixes).\n- wifi: ath10k: avoid IDR mutation during TX cleanup (git-fixes).\n- wifi: ath11k: avoid IDR mutation during pending mgmt TX cleanup (git-fixes).\n- wifi: ath11k: avoid IDR mutation during vif mgmt TX cleanup (git-fixes).\n- wifi: ath11k: disable interrupts during firmware crash recovery (git-fixes).\n- wifi: ath11k: fix locking problem in ath11k_dp_rx_tid_del_func() (git-fixes).\n- wifi: ath11k: fix NULL dereference in ahb remove when QMI init incomplete (git-fixes).\n- wifi: ath11k: Fix possible memory leak in ath11k_dp_srng_setup() (git-fixes).\n- wifi: ath11k: fix sporadic WLAN initialization failures (git-fixes).\n- wifi: ath11k: fix unbalanced IRQ enable/disable during suspend/resume (git-fixes).\n- wifi: ath11k: modify null check logic in ath11k_ce_rx_post_pipe() (git-fixes).\n- wifi: ath11k: reset ar-\u003enum_stations on hardware start (git-fixes).\n- wifi: ath11k: unregister PM notifier on QMI init failure path (git-fixes).\n- wifi: ath12k: avoid IDR mutation during vif mgmt TX cleanup (git-fixes).\n- wifi: ath12k: fix incorrect TID updation in DP monitor status path (stable-fixes).\n- wifi: ath12k: fix struct hal_rx_phyrx_rssi_legacy_info (stable-fixes).\n- wifi: ath12k: fix the fetching of combined rssi (git-fixes).\n- wifi: ath12k: Free allocated CE IRQs on request_irq() failure (git-fixes).\n- wifi: b43: don't pass unterminated string to sscanf() (git-fixes).\n- wifi: b43: fix use-after-free in b43_bcma_remove() (git-fixes).\n- wifi: b43legacy: debugfs: NUL terminate string in debugfs (git-fixes).\n- wifi: brcmsmac: Adjust txpwrindex value in nphy_ipa_rxcal_gaintbl_2GHz (git-fixes).\n- wifi: carl9170: NUL terminate string in debugfs (git-fixes).\n- wifi: cfg80211: allow zero HE OBSS PD offsets (git-fixes).\n- wifi: cfg80211: preserve hidden-group beacon IE ownership (git-fixes).\n- wifi: cfg80211: reject duplicate wiphy cipher suite entries (stable-fixes).\n- wifi: cfg80211: track SSID regardless of country data (git-fixes).\n- wifi: cw1200: fix TX padding OOB read leaking heap data to device (git-fixes).\n- wifi: iwlegacy: 3945: free EEPROM data on remove (git-fixes).\n- wifi: iwlwifi: dvm: pair transport op-mode enter/leave (stable-fixes).\n- wifi: iwlwifi: mvm: remove mvm prefix from iwl_mvm_tx_resp* (stable-fixes).\n- wifi: iwlwifi: mvm: validate TX_CMD response layout (stable-fixes).\n- wifi: mac80211: account proxy paths against the mesh path limit (git-fixes).\n- wifi: mac80211: Add 802.3 multicast encapsulation offload support (stable-fixes).\n- wifi: mac80211: Add multicast to unicast support for 802.3 path (stable-fixes).\n- wifi: mac80211: Add sta pointer sanity check in ieee80211_8023_xmit() (stable-fixes).\n- wifi: mac80211: clear fragment cache entry 'is_protected' (git-fixes).\n- wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed (stable-fixes).\n- wifi: mac80211: don't reset the TXQ scheduling round number (git-fixes).\n- wifi: mac80211: don't send encap offload frames unencrypted (git-fixes).\n- wifi: mac80211: drain PS delivery work during station teardown (git-fixes).\n- wifi: mac80211: drop encap offload frames with a tainted key (git-fixes).\n- wifi: mac80211: Fix a race when expiring a mesh path (git-fixes).\n- wifi: mac80211: fix encryption tailroom (git-fixes).\n- wifi: mac80211: fix key selection for encap offload frames (git-fixes).\n- wifi: mac80211: fix mesh fast xmit path deletion UAF (git-fixes).\n- wifi: mac80211: fix missing RX bitrate update for mesh forwarding path (stable-fixes).\n- wifi: mac80211: fix swapped fq_overlimit/fq_overmemory in aqm debugfs (git-fixes).\n- wifi: mac80211: Fix the return value in mesh_path_add() kernel-doc (git-fixes).\n- wifi: mac80211: fix unauthorised port check for encap offload (git-fixes).\n- wifi: mac80211: handle empty FILS association request payload (git-fixes).\n- wifi: mac80211: init radiotap iter after length checks (git-fixes).\n- wifi: mac80211: kill wake_txqs_tasklet on unregistration (git-fixes).\n- wifi: mac80211: limit injected HT/VHT MCSes (git-fixes).\n- wifi: mac80211: mesh: use hlist_add_head_rcu() (git-fixes).\n- wifi: mac80211: minstrel_ht: validate fixed rate index (git-fixes).\n- wifi: mac80211: prevent AP VLAN tx from other interfaces (git-fixes).\n- wifi: mac80211: refactor populating mesh related fields in sinfo (stable-fixes).\n- wifi: mac80211: release mesh path quota on failed additions (git-fixes).\n- wifi: mac80211: reserve MME tailroom for protected beacons (git-fixes).\n- wifi: mac80211: set info-\u003eband for 802.3 encap offload frames (git-fixes).\n- wifi: mac80211: use link address as TA for non-MLO 4-addr station on MLD AP (git-fixes).\n- wifi: mt76: feed the station RSSI average from the chain signals (git-fixes).\n- wifi: mt76: fix memory leak in USB TX path (git-fixes).\n- wifi: mt76: Fix of_node reference leak in mt76_get_rate_power_limits() (git-fixes).\n- wifi: mt76: fix unlocked wcid check in mt76_tx_status_skb_add() (git-fixes).\n- wifi: mt76: fix wcid-\u003epktid corruption in mt76_wcid_cleanup() (git-fixes).\n- wifi: mt76: mt76x02: validate RX padding before use (git-fixes).\n- wifi: mt76: mt76x02: validate TX-status rate index before mac80211 handoff (git-fixes).\n- wifi: mt76: mt792x: fix UAF in SDIO TX path when out of memory (git-fixes).\n- wifi: mt76: mt7603: don't drop short frames looped back on PS entry (git-fixes).\n- wifi: mt76: mt7615: cancel reset work during unregister (git-fixes).\n- wifi: mt76: mt7615: do not tear down BSS/STA state for monitor vifs (git-fixes).\n- wifi: mt76: mt7615: read MT7663 temperature from the correct offset (git-fixes).\n- wifi: mt76: mt7615: usb: fix source overread in mt7663u_copy (git-fixes).\n- wifi: mt76: mt7615: validate MCU response lengths (git-fixes).\n- wifi: mt76: mt7915: allocate vif wcid in the same range as stations (stable-fixes).\n- wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy (git-fixes).\n- wifi: mt76: mt7915: check default EEPROM firmware size before copying (git-fixes).\n- wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear (git-fixes).\n- wifi: mt76: mt7915: Fix an error handling path in mt7915_add_interface() (git-fixes).\n- wifi: mt76: mt7915: guard firmware memory dump write on disabled memdump (git-fixes).\n- wifi: mt76: mt7915: set correct background radar capability (stable-fixes).\n- wifi: mt76: mt7915: unregister thermal cooling device on hwmon failure (git-fixes).\n- wifi: mt76: mt7921: check drv_pmctrl return in the PCIe reset path (git-fixes).\n- wifi: mt76: mt7921: fix lock inversion between dev-\u003emutex and iflist_mtx (git-fixes).\n- wifi: mt76: mt7921: fix the lock inversion in suspend and resume (git-fixes).\n- wifi: mt76: mt7925: check drv_pmctrl return in the PCIe reset path (git-fixes).\n- wifi: mt76: mt7925: fix lock inversion between dev-\u003emutex and iflist_mtx (git-fixes).\n- wifi: mt76: mt7925: fix the lock inversion in suspend and resume (git-fixes).\n- wifi: mt76: mt7925: honour mac80211's FIF_FCSFAIL instead of hardcoding drop_err (git-fixes).\n- wifi: mt76: mt7925: restore the reset state when fw_pmctrl fails (git-fixes).\n- wifi: mt76: mt7996: fix PLE free page and AC queue register offsets (git-fixes).\n- wifi: mt76: mt7996: validate firmware event lengths before parsing (git-fixes).\n- wifi: mt76: usb: fix source overread in mt76u_copy (git-fixes).\n- wifi: mwifiex: append hotfix number to firmware version string (git-fixes).\n- wifi: p54: validate firmware record lengths (stable-fixes).\n- wifi: rtw88: debugfs: don't vzalloc(0) when rsvd_page is read unconfigured (git-fixes).\n- wifi: rtw88: debugfs: support multiple adapters debugging (stable-fixes).\n- wifi: rtw88: fix out-of-bounds CAM write when key table is full (git-fixes).\n- wifi: rtw88: sdio: zero the padding added to a TX transfer (git-fixes).\n- wifi: rtw89: 8851b: fix swapped DPK channel/bandwidth backup fields (git-fixes).\n- wifi: rtw89: cap firmware section_num before parsing (git-fixes).\n- wifi: wfx: fix possible device hang during init (git-fixes).\n- wifi: wfx: fix use-after-free of the cooling work on device removal (git-fixes).\n- wifi: wfx: validate MIB read length before copying to caller (git-fixes).\n- wwan: wwan_hwsim: Pin module for debugfs file operations (git-fixes).\n- xhci: dbc: lock the minor IDR on registration failure (git-fixes).\n","status":"published","published":"2026-11-03T19:25:57Z","modified":"2026-11-06T17:23:11.195914364Z","updated_at":"2026-11-06T18:05:03.243497Z"},{"id":"SUSE-SU-2026:5091-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 15 SP7 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-68219: cifs: fix memory leak in smb3_fs_context_parse_param error path (bsc#1255222).\n- CVE-2026-31708: smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path (bsc#1264022).\n- CVE-2026-31709: smb: client: validate the whole DACL before rewriting it in cifsacl (bsc#1264024).\n- CVE-2026-43350: smb: client: require a full NFS mode SID before reading mode bits (bsc#1264985).\n- CVE-2026-46155: smb/client: fix out-of-bounds read in smb2_compound_op() (bsc#1267720).\n- CVE-2026-64370: posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path (bsc#1273805).\n- CVE-2026-64380: smb: client: harden POSIX SID length parsing (bsc#1273557).\n- CVE-2026-64430: NTB: epf: Avoid calling pci_irq_vector() from hardirq context (bsc#1274257).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-68186: binfmt_misc: set have_execfd only once the interpreter is opened (bsc#1274949).\n- CVE-2026-68436: drm/amd/display: use kvzalloc to allocate struct dc (bsc#1276275).\n- CVE-2026-68447: drm/amdkfd: clamp v9 CRIU control stack checkpoint copy to BO size (bsc#1276280).\n- CVE-2026-68460: f2fs: fix potential deadlock in f2fs_balance_fs() (bsc#1276774).\n- CVE-2026-72010: cgroup/cpuset: rebind mm mempolicy to effective_mems, not mems_allowed (bsc#1276776).\n- CVE-2026-72073: mmc: vub300: fix use-after-free on probe failure (bsc#1277157).\n- CVE-2026-72110: bpf,fork: wipe -\u003ebpf_storage before bailouts that access it (bsc#1277357).\n- CVE-2026-72111: bpf: Reset register bounds before narrowing retval range in check_mem_access() (bsc#1277389).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72253: netfilter: nf_conntrack_sip: validate skb_dst() before accessing it (bsc#1277665).\n- CVE-2026-72318: cifs: validate DFS referral string offsets (bsc#1275939).\n- CVE-2026-72405: net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync (bsc#1278033).\n- CVE-2026-72416: netfilter: nft_compat: ebtables emulation must reject non-bridge targets (bsc#1278041).\n- CVE-2026-72428: bpf: Fix stack slot index in nospec checks (bsc#1278050).\n- CVE-2026-74368: wifi: ath12k: fix memory leak in ath12k_wifi7_dp_rx_h_verify_tkip_mic() (bsc#1277103).\n- CVE-2026-74472: ublk: reset kernel-owned dev_info fields in ublk_ctrl_add_dev() (bsc#1277785).\n- CVE-2026-74613: vsock/virtio: avoid refilling the RX queue after teardown (bsc#1277903).\n- CVE-2026-74620: net/sched: act_gact, act_police: range check the fallback control action (bsc#1277044).\n- CVE-2026-74624: netfilter: nf_conntrack: defer invalid log until after unlock (bsc#1277599).\n- CVE-2026-74715: net: netfilter: Make ct zone opts configurable for bpf ct helpers (bsc#1277890).\n- CVE-2026-74746: netfilter: flowtable: publish GC-visible tuple last (bsc#1278101).\n- CVE-2026-74748: netfilter: ipset: fix refcount race between list:set GC and swap (bsc#1277578).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80602: perf/x86/amd/lbr: Fix kernel address leakage (bsc#1278123).\n- CVE-2026-80637: netfilter: synproxy: fix unaligned memory access in timestamp adjustment (bsc#1278343).\n- CVE-2026-80717: sctp: validate Adaptation Indication parameter length (bsc#1277836).\n- CVE-2026-80755: selinux: reject a permission value exceeding the class permission count (bsc#1278415).\n- CVE-2026-80757: selinux: reject a class permission count below its inherited common (bsc#1278711).\n- CVE-2026-80808: ext4: stop retrying saturated xattr cache entries (bsc#1279795).\n- CVE-2026-80809: ocfs2: fix missing metadata reservation for large xattrs (bsc#1279606).\n- CVE-2026-80855: fuse: fix invalidate lock leak on open O_TRUNC DAX failure (bsc#1279564).\n- CVE-2026-80879: ocfs2: fix circular locking dependency in ocfs2_dio_end_io_write (bsc#1279494).\n- CVE-2026-80881: ocfs2: fix buffer head management in ocfs2_read_blocks() (bsc#1279496).\n- CVE-2026-80978: ip6_gre: fix hardware header length for NBMA tunnels (bsc#1280253).\n- CVE-2026-89491: ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin() (bsc#1280472).\n- CVE-2026-89494: ocfs2: validate lengths in dlm_mig_lockres_handler (bsc#1280520).\n- CVE-2026-89495: ocfs2: bound namelen in dlm_migrate_request_handler (bsc#1280569).\n- CVE-2026-89537: SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2 (bsc#1280713).\n- CVE-2026-89560: landlock: Require LANDLOCK_ACCESS_FS_MAKE_REG for whiteout creation (bsc#1280806).\n- CVE-2026-89595: fsnotify: Fix stale object mask after concurrent mark updates (bsc#1280834).\n- CVE-2026-89608: ecryptfs: pass packet set buffer size to parser (bsc#1280826).\n- CVE-2026-89637: smb: client: fix UAF and buffer leak in cifs_check_trans2() for malformed secondary T2 (bsc#1280492).\n- CVE-2026-89649: ceph: bound xattr value length in __build_xattrs() (bsc#1280434).\n- CVE-2026-89654: ceph: fix UAF in check_new_map() on session freed during unlock (bsc#1280415).\n- CVE-2026-89655: ceph: fix UAF in __kick_flushing_caps() on cf entry freed during unlock (bsc#1280398).\n- CVE-2026-89656: libceph: reject buckets with mismatched CRUSH ids (bsc#1280563).\n- CVE-2026-89657: libceph: validate OSD extent maps before cursor advance (bsc#1280545).\n- CVE-2026-89751: x86/tdx: Fix off-by-one in port I/O handling (bsc#1280822).\n- CVE-2026-89761: apparmor: fix out-of-bounds write when null terminating a label vec (bsc#1280745).\n- CVE-2026-89786: ext4: fix out-of-bounds read in ext4_read_inline_dir() (bsc#1280976).\n- CVE-2026-89787: ext4: check dir entry fits before reading the hash trailer in ext4_search_dir() (bsc#1280977).\n- CVE-2026-90042: ceph: properly decrypt filenames in vmalloc() buffers (bsc#1280948).\n- CVE-2026-90092: Bluetooth: L2CAP: reject accept queue add unless BT_LISTEN (bsc#1281384).\n- CVE-2026-90128: vdpa/mlx5: fix wrong list iterated in add_direct_chain error path (bsc#1281577).\n- CVE-2026-90148: NFSv4: Fix incorrect argument passed to nfs4_delete_lease() in nfs4_add_lease() (bsc#1281551).\n- CVE-2026-90227: nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() (bsc#1281705).\n- CVE-2026-90393: bpf: Fix potential UAF in bpf_netns_link_update_prog (bsc#1282289).\n- CVE-2026-93054: uio: Fix stale info pointer in failed registration path (bsc#1282276).\n- CVE-2026-93228: svcrdma: Reject Write/Reply chunks with segcount 0 (bsc#1282697).\n- CVE-2026-93262: md/raid5-ppl: fix use-after-free in ppl_do_flush() (bsc#1283004).\n- CVE-2026-93795: blk-cgroup: fix leaks and online flag on radix_tree_insert failure (bsc#1283155).\n- CVE-2026-93798: btrfs: fix reloc root cleanup in merge_reloc_roots() (bsc#1282769).\n- CVE-2026-93817: perf: Fix addr_filter_ranges lifetime (bsc#1283017).\n- CVE-2026-97575: media: v4l2-ctrls: validate AV1 tile counts (bsc#1283337).\n- CVE-2026-97605: erofs: preserve LZMA decoders on resize failure (bsc#1283173).\n- CVE-2026-97926: ufs: validate cylinder group metadata before caching it (bsc#1283887).\n- CVE-2026-98041: bpf: Don't predict JMP32 pointer vs zero comparisons (bsc#1284064).\n- CVE-2026-98086: ALSA: ump: do not touch legacy_rmidi before it exists (bsc#1283785).\n- CVE-2026-98264: ALSA: virtio: reset device before deleting virtqueues (bsc#1284363).\n- CVE-2026-98306: seg6: set IPSKB_L3SLAVE from IP6SKB_L3SLAVE on IPIP decapsulation (bsc#1284505).\n- CVE-2026-98368: esp: downgrade zerocopy managed frags before mutating skb frags (bsc#1284498).\n- CVE-2026-98374: tcp: fix use-after-free of retransmit_skb_hint in tcp_send_synack() (bsc#1284740).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n- CVE-2026-98471: KVM: SEV: Do cache maintenance on the source VM during intra-host migration (bsc#1286240).\n\nThe following non security issues were fixed:\n\n- accel/qaic: reject BO sizes that overflow page count (git-fixes).\n- ACPI: CPPC: Validate the _CPC package header (git-fixes).\n- ACPI: extlog: Validate elog record length before walking sections (git-fixes).\n- ACPI: PCI: pci_link: clear driver_data before free (git-fixes).\n- ACPI: pfr_update: zero-initialize capability query result (git-fixes).\n- ACPI: PM: Drop parent state update from acpi_device_get_power() (git-fixes).\n- ACPI: tables: handle failed initrd override mappings (git-fixes).\n- ACPI: TAD: Rearrange RT data validation checking (stable-fixes).\n- ACPI: video: Fix backlight unregistration ordering (git-fixes).\n- ACPICA: Fix memory leak in acpi_ds_create_field() (git-fixes).\n- ACPICA: Fix PCC OperationRegion command offsets (git-fixes).\n- ALSA: 6fire: take stream_mutex in the Digital Thru control (git-fixes).\n- ALSA: aloop: Keep the timer source alive until card release (git-fixes).\n- ALSA: caiaq: Allow zero-length packet handling for EP1 (git-fixes).\n- ALSA: caiaq: Fix races at MIDI URB and trigger accesses (git-fixes).\n- ALSA: caiaq: Fix the Kore controller key map (git-fixes).\n- ALSA: caiaq: Register card at the final step (git-fixes).\n- ALSA: caiaq: Serialize access to the EP1 command buffer (git-fixes).\n- ALSA: compress: add missing OPEN-state gate to SET_METADATA (git-fixes).\n- ALSA: compress: fix buffer leak on failed SET_PARAMS (git-fixes).\n- ALSA: compress: reject buffer geometry change on gapless next_track (git-fixes).\n- ALSA: control: Fix virtual master creation reference in kernel-doc (git-fixes).\n- ALSA: cs46xx: fix unit mismatch in DSP code area bounds check (git-fixes).\n- ALSA: hda/hdmi: clamp num_cvts against cvt_nids in hdmi_read_pin_conn (git-fixes).\n- ALSA: hda/hdmi: clamp sad_count in ELD proc write handler (git-fixes).\n- ALSA: hda: Add NULL check for the driver pointer at unsol event work (git-fixes).\n- ALSA: hda: Avoid non-operational GPU warning at regular device removal (git-fixes).\n- ALSA: hda: Fix potential UAF for gating jack (git-fixes).\n- ALSA: hda: intel: Cancel delayed work at shutdown, too (git-fixes).\n- ALSA: info: Fix memory leak at card removal (git-fixes).\n- ALSA: jack: Fix kctl free at error in snd_jack_kctl_new() (git-fixes).\n- ALSA: jack: Remove debugfs before freeing unregistered jacks (git-fixes).\n- ALSA: line6: Clear prev_fbuf on capture buffer release (git-fixes).\n- ALSA: line6: Fix potential OOB write in line6_capture_copy() (git-fixes).\n- ALSA: line6: Reject too small max packet sizes (git-fixes).\n- ALSA: line6: Use kzalloc() for PCM buffer allocation (git-fixes).\n- ALSA: pcm: Fix driver_tstamp value reporting (git-fixes).\n- ALSA: pcm: Protect channel-map reads against runtime detach (git-fixes).\n- ALSA: pcm: Protect delay DMA sync against concurrent HW_FREE (git-fixes).\n- ALSA: pcm: Protect delay DMA sync in forward and rewind, too (git-fixes).\n- ALSA: pcm: Protect the unregister notifier traversal (git-fixes).\n- ALSA: pcm: Remove channel-map controls before freeing substreams (git-fixes).\n- ALSA: pcm: Unlink substreams before releasing them (git-fixes).\n- ALSA: rawmidi: Drain input work before freeing the runtime (git-fixes).\n- ALSA: seq: Fix missing direction and ump_group handling in 32bit compat ioctl (git-fixes).\n- ALSA: seq: oss: Skip events until fully initialized (git-fixes).\n- ALSA: ump: Avoid dereference with max_src_size=0 (git-fixes).\n- ALSA: ump: Correct return size of fill_rpn() (git-fixes).\n- ALSA: usb-audio: Use fixed control index for us16x08 mixer elements (git-fixes).\n- ALSA: via82xx: use helper to activate DXS controls (git-fixes).\n- ALSA: vmaster: Protect follower lookup and setup (git-fixes).\n- ASoC: adau17x1: return cache sync errors from resume (git-fixes).\n- ASoC: ak4642: return cache sync errors from resume (git-fixes).\n- ASoC: amd: acp: Fix .close() being skipped on rollback (git-fixes).\n- ASoC: amd: ps: Fix acp63_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: ps: Fix acp63_sdw_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: raven: Fix acp3x_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: renoir: Fix acp_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: vangogh: Fix acp5x_dma_close() being skipped on rollback (git-fixes).\n- ASoC: amd: yc: Add DMI quirk for Acer Aspire Go 15 (AG15-21P) (stable-fixes).\n- ASoC: amd: yc: Fix acp6x_pdm_dma_close() being skipped on rollback (git-fixes).\n- ASoC: arizona-jack: Fix runtime PM imbalance in arizona_start_hpdet_acc_id() (git-fixes).\n- ASoC: atmel-i2s: fix MCK generator error handling (git-fixes).\n- ASoC: atmel-i2s: use optional API for gclk (git-fixes).\n- ASoC: atmel-i2s: use optional API for muxclk (git-fixes).\n- ASoC: atmel: atmel-pcm-pdc: Fix atmel_pcm_close() being skipped on rollback (git-fixes).\n- ASoC: codecs: da732x: Fix definition of ADC2 EQ Overall Volume control (git-fixes).\n- ASoC: codecs: lpass-wsa-macro: use v2.5 Compander1 addresses on v2.5+ (git-fixes).\n- ASoC: codecs: rt5659: propagate GPIO errors (git-fixes).\n- ASoC: codecs: rt5682s: disable jack detection work on shutdown (git-fixes).\n- ASoC: codecs: sta32x: Fix definition of Ch2 and Ch3 Volume Bypass controls (git-fixes).\n- ASoC: codecs: sta32x: Fix definition of limiter threshold controls (git-fixes).\n- ASoC: codecs: sta350: Fix definition of Ch2 and Ch3 Volume Bypass controls (git-fixes).\n- ASoC: codecs: sta350: Fix definition of limiter threshold controls (git-fixes).\n- ASoC: codecs: tlv320adc3xxx: Fix definition of AGC Target Level control (git-fixes).\n- ASoC: codecs: wcd9335: Fix SLIM interface device leak in wcd9335_slim_status() (git-fixes).\n- ASoC: codecs: wm5100: Fix definition of EQ3 Band 1 Volume control (git-fixes).\n- ASoC: codecs: wm8510: Fix definition of ADC Inversion Switch control (git-fixes).\n- ASoC: codecs: wm8737: Fix definition of zero cross switches (git-fixes).\n- ASoC: codecs: wm8750: Fix definition of ALC Capture NG Type control (git-fixes).\n- ASoC: codecs: wm8955: Fix definition of Treble Cutoff control (git-fixes).\n- ASoC: codecs: wm8983: Fix definition of ADC 128x Oversampling control (git-fixes).\n- ASoC: codecs: wm8985: Fix definition of ADC 128x Oversampling control (git-fixes).\n- ASoC: codecs: wm8990: Fix definition of LOMIX AINLMUX Bypass Volume control (git-fixes).\n- ASoC: codecs: wm8990: Fix definition of right input PGA controls (git-fixes).\n- ASoC: codecs: wm8991: Fix definition of LOMIX AINLMUX Bypass Volume control (git-fixes).\n- ASoC: codecs: wm8991: Fix definition of right input PGA controls (git-fixes).\n- ASoC: codecs: wm8994: Fix definition of WM8958 noise gate hold time controls (git-fixes).\n- ASoC: codecs: wm8994: Fix runtime PM leak in wm8994_mic_detect() (git-fixes).\n- ASoC: codecs: wm_hubs: Fix definition of MIXINR to MIXOUTR volume control (git-fixes).\n- ASoC: dwc: Use OF match data again for StarFive JH7110 (git-fixes).\n- ASoC: es8316: return cache sync errors from resume (git-fixes).\n- ASoC: es8326: report resume restore errors (git-fixes).\n- ASoC: fsl_asrc: check the second front-end DMA channel (git-fixes).\n- ASoC: fsl_asrc: use regmap_write_bits to update clock source registers (git-fixes).\n- ASoC: imx-pcm-rpmsg: Fix imx_rpmsg_pcm_close() being skipped on rollback (git-fixes).\n- ASoC: intel: atom: Fix .shutdown() being skipped on rollback (git-fixes).\n- ASoC: Intel: atom: Fix platform device leak on probe failure (git-fixes).\n- ASoC: Intel: avs: Prevent module info underflow (git-fixes).\n- ASoC: Intel: avs: Unprepare a stream when recovery occurs (git-fixes).\n- ASoC: mediatek: common: Handle constraint return value in FE startup (git-fixes).\n- ASoC: mediatek: common: Keep codec references until the card is bound (git-fixes).\n- ASoC: mediatek: mt6797: fix wrong unwind order and error code in enable_clock (git-fixes).\n- ASoC: mediatek: mt8183: Fix APLL enable error handling (git-fixes).\n- ASoC: mediatek: mt8183: Fix clock handling in mux disable path (git-fixes).\n- ASoC: mediatek: mt8183: Fix wrong clock cleanup on clk_set_parent() failure (git-fixes).\n- ASoC: mediatek: mt8186: Fix AFE clock error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix APLL enable error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix APLL mux setting error handling (git-fixes).\n- ASoC: mediatek: mt8186: Fix clock handling in mux disable path (git-fixes).\n- ASoC: mediatek: mt8186: Fix MCK error handling (git-fixes).\n- ASoC: mediatek: mt8188: Handle constraint return value in FE startup (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Handle clock enable errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Handle tuner clock enable errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-clk: Propagate regmap update errors (git-fixes).\n- ASoC: mediatek: mt8188: mt8188-afe-pcm: Handle runtime resume errors (git-fixes).\n- ASoC: mediatek: mt8192-mt6359: Fix error handling in MTKAIF calibration (git-fixes).\n- ASoC: mediatek: mt8192: check return values in mt8192_afe_gpio_init() (git-fixes).\n- ASoC: mediatek: mt8192: fix AFE clock error handling (git-fixes).\n- ASoC: mediatek: mt8192: fix APLL mux error handling (git-fixes).\n- ASoC: mediatek: mt8192: fix error handling in APLL enable functions (git-fixes).\n- ASoC: mediatek: mt8192: fix MCK clock error handling (git-fixes).\n- ASoC: mediatek: mt8192: Handle regcache_sync() failure in runtime resume (git-fixes).\n- ASoC: mediatek: mt8192: Propagate errors in I2S DAI DAPM event handlers (git-fixes).\n- ASoC: mediatek: mt8192: Propagate errors in TDM DAI DAPM event handlers (git-fixes).\n- ASoC: mediatek: mt8192: Propagate mt8192_afe_gpio_request() errors in ADDA DAI (git-fixes).\n- ASoC: mediatek: mt8192: switch to devm_clk_get_optional() (git-fixes).\n- ASoC: mediatek: mt8195: Check paired MEMIF clock enable in FE trigger (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM MCLK error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM probe error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix ETDM startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix FE startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix HDMI TX startup error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix main clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix paired memif clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix register access clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix runtime resume error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix timing system clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Fix tuner clock error handling (git-fixes).\n- ASoC: mediatek: mt8195: Propagate IRQ lookup errors (git-fixes).\n- ASoC: mt6359-accdet: manage private workqueues with devres (git-fixes).\n- ASoC: nau8540: return cache sync errors from resume (git-fixes).\n- ASoC: ops: Fix return value in snd_soc_limit_volume() (git-fixes).\n- ASoC: qcom: q6apm: clear g_apm on driver removal (git-fixes).\n- ASoC: qcom: q6apm: reset the hw pointer with the fragment queue (git-fixes).\n- ASoC: rockchip: rockchip_i2s: Handle runtime PM resume failures in set_fmt (git-fixes).\n- ASoC: rt711-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt711-sdw: always cancel jack work on remove (git-fixes).\n- ASoC: rt712-sdca-dmic: fix drvdata type in the gain controls (git-fixes).\n- ASoC: rt712-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt722-sdca: always cancel jack work on remove (git-fixes).\n- ASoC: rt1011: return cache sync errors from resume (git-fixes).\n- ASoC: rt1016: return cache sync errors from resume (git-fixes).\n- ASoC: rt1305: return cache sync errors from resume (git-fixes).\n- ASoC: rt1308: return cache sync errors from resume (git-fixes).\n- ASoC: rt5616: return cache sync errors from resume (git-fixes).\n- ASoC: rt5659: return cache sync errors from resume (git-fixes).\n- ASoC: rt5660: return cache sync errors from resume (git-fixes).\n- ASoC: rt5665: return cache sync errors from resume (git-fixes).\n- ASoC: rt5682-sdw: always cancel jack work on remove (git-fixes).\n- ASoC: soc-ac97: Fix error handling in snd_soc_new_ac97_component() (git-fixes).\n- ASoC: soc-component: Fix return type of snd_soc_pcm_component_pointer() (git-fixes).\n- ASoC: soc-topology-test: Check return value of kunit_device_register() (git-fixes).\n- ASoC: SOF: amd: fix amd_sof_acp_remove() teardown ordering (git-fixes).\n- ASoC: SOF: imx: Prevent stack OOB read in DSP panic dump (git-fixes).\n- ASoC: ti: davinci-mcasp: Fix runtime PM imbalance in __davinci_mcasp_set_clkdiv() (git-fixes).\n- ASoC: wcd9335: Fix device reference leak in wcd9335_slim_status() (git-fixes).\n- ASoC: wcd-mbhc-v2: Fix incorrect properties names and typos (git-fixes).\n- ASoC: wm8994: Fix runtime PM imbalance in wm8994_component_probe() (git-fixes).\n- asymmetric_keys: reject trust keys without IDs (git-fixes).\n- ata: libata-scsi: abort multi-sector pass-through commands when multi_count is 0 (git-fixes).\n- ata: libata-scsi: Fix ata_scsi_hotplug() reference in kernel-doc (git-fixes).\n- ata: pata_parport: fix parport attach idr_alloc for (git-fixes).\n- ata: pata_parport: Fix use-after-free in new_device_store (git-fixes).\n- ata: sata_fsl: Fix use-after-free of host_priv on probe() failure (git-fixes).\n- backlight: lm3630a: Cancel delayed work before destroying workqueue (git-fixes).\n- backlight: qcom-wled: Fix NULL pointer dereference in wled_remove() (git-fixes).\n- backlight: qcom-wled: Fix unbalanced OVP IRQ enable at probe (git-fixes).\n- backlight: qcom-wled: Fix WLED3 brightness register stride (git-fixes).\n- Bluetooth: 6lowpan: Drain RCU readers on registration failure (git-fixes).\n- Bluetooth: 6lowpan: Pin module for 6lowpan_control debugfs file (git-fixes).\n- Bluetooth: 6LoWPAN: Use RCU-safe device list removal (git-fixes).\n- Bluetooth: Add missing newline to bt_dev_{err,warn}_ratelimited() (git-fixes).\n- Bluetooth: btintel: fix buffer over-read in btintel_hw_error() (git-fixes).\n- Bluetooth: btintel: validate DDC record lengths (git-fixes).\n- Bluetooth: btmtk: fix skb double free on ISO padding failure (git-fixes).\n- Bluetooth: btqcomsmd: Convert to platform remove callback returning void (stable-fixes).\n- Bluetooth: btqcomsmd: destroy RPMsg endpoints before freeing hci_dev (git-fixes).\n- Bluetooth: btusb: Add IMC Networks QCA9377 to quirks table (stable-fixes).\n- Bluetooth: hci_conn: Lock parent access during enhanced SCO setup (git-fixes).\n- Bluetooth: hci_core: free the HCI ID if naming fails (git-fixes).\n- Bluetooth: hci_core: Keep RCU protection through LTK filtering (git-fixes).\n- Bluetooth: hci_debugfs: Pin module for debugfs file operations (git-fixes).\n- Bluetooth: hci_sync: don't drain cmd_sync backlog on unregister (git-fixes).\n- Bluetooth: hci_sync: Fix inquiry cache use-after-free (git-fixes).\n- Bluetooth: hci_sync: fix mesh adv timeout units (git-fixes).\n- Bluetooth: hci_sync: Protect IRK identity reads with RCU (git-fixes).\n- Bluetooth: hci_sync: Serialize devcoredump reset during device open (git-fixes).\n- Bluetooth: hci_vhci: Pin module for debugfs file operations (git-fixes).\n- Bluetooth: ISO: Hold the listener during disconnect notification (git-fixes).\n- Bluetooth: L2CAP: hold chan in l2cap_ecred_conn_rsp() (git-fixes).\n- Bluetooth: L2CAP: hold l2cap_conn::lock in l2cap_connect_cfm() (git-fixes).\n- Bluetooth: L2CAP: refuse __l2cap_chan_add if chan already has conn (git-fixes).\n- Bluetooth: L2CAP: Reject invalid TxWindow in configuration requests (git-fixes).\n- Bluetooth: L2CAP: Reject mode changes on connected channels (git-fixes).\n- Bluetooth: L2CAP: Use default TxWindow for zero socket option (git-fixes).\n- Bluetooth: MGMT: Fix leaking instance on Add Extended Advertising Parameters (git-fixes).\n- Bluetooth: MGMT: Fix pending state of instances added without HCI traffic (git-fixes).\n- Bluetooth: MGMT: Reject quality report requests during unregister (git-fixes).\n- Bluetooth: msft: Lock failed probe cleanup against feature readers (git-fixes).\n- Bluetooth: MSFT: Serialize handle map cleanup with event processing (git-fixes).\n- Bluetooth: RFCOMM: Fix initial port reference race (git-fixes).\n- Bluetooth: selftest: Pin module for selftest debugfs file operations (git-fixes).\n- bus: arm-cci: Drop cci-control-port node reference in __cci_ace_get_port() (git-fixes).\n- bus: arm-cci: Drop CPU node reference in cci_ace_init_ports() (git-fixes).\n- bus: fsl-mc: register the object drivers after misc_class exists (git-fixes).\n- char: scx200_gpio: check cdev_add() return value (git-fixes).\n- comedi: comedi_parport: validate the IRQ supplied by userspace (git-fixes).\n- comedi: dmm32at: validate the IRQ supplied by userspace (git-fixes).\n- comedi: dt2811: fix shift-out-of-bounds in IRQ check (git-fixes).\n- comedi: dt2814: validate the IRQ supplied by userspace (git-fixes).\n- comedi: ni_atmio16d: validate the IRQ supplied by userspace (git-fixes).\n- comedi: pcmmio: validate the IRQ supplied by userspace (git-fixes).\n- comedi: pcmuio: validate the IRQs supplied by userspace (git-fixes).\n- crypto: amlogic - Fix DMA memory leak in cipher error path (git-fixes).\n- crypto: amlogic - Fix IRQ handler return value and fallthrough logic (git-fixes).\n- crypto: asymmetric_keys - fix OOB read in pefile_parse_binary (git-fixes).\n- crypto: atmel - handle authenc requests without plaintext (git-fixes).\n- crypto: atmel-aes - fix AADLENR for standalone GHASH (git-fixes).\n- crypto: atmel-sha - reject initialization without a device (git-fixes).\n- crypto: atmel-tdes - sync output bounce buffer before DMA (git-fixes).\n- crypto: atmel-tdes - zero-initialize device state (git-fixes).\n- crypto: caam - fix double-free in caam_rsa_set_priv_key_form() (git-fixes).\n- crypto: ccp - kill v3 IRQ tasklet during teardown (git-fixes).\n- crypto: ccp - kill v5 IRQ tasklet during teardown (git-fixes).\n- crypto: hisilicon/hpre - fix ECDH destination DMA mapping (git-fixes).\n- crypto: hisilicon/hpre - fix GFP flags for dma_alloc_coherent (git-fixes).\n- crypto: hisilicon/hpre - fix pointer dereference before length check (git-fixes).\n- crypto: hisilicon/hpre - remove dma_free_coherent on NULL req-\u003edst in ECDH (git-fixes).\n- crypto: hisilicon/hpre - return -EOVERFLOW for small ECDH output buffer (git-fixes).\n- crypto: qat - avoid OOB read when stripping RSA leading zeros (git-fixes).\n- crypto: qat - fix active_devs leak on crypto alg registration failure (git-fixes).\n- crypto: qat - fix use of destroyed vf2pf_lock on VF restart (git-fixes).\n- crypto: qat - initialise state_lock on every path in adf_devmgr_add_dev() (git-fixes).\n- crypto: qat - release instance on DH fallback allocation failure (git-fixes).\n- crypto: qat - zero the VF migration state buffer on save (git-fixes).\n- crypto: tcrypt - Avoid reading req-\u003ebase after submission (git-fixes).\n- Documentation: rs485: Pull uart_get_rs485_mode() from serial_core.c (git-fixes).\n- Documentation: virt: Fix the struct snp_guest_request_ioctl name in sev-guest.rst (git-fixes).\n- drivers/base/node: fix UAF on device_register() failure (git-fixes).\n- Drivers: hv: vmbus: add VTL2 redirect connection ID (git-fixes).\n- drm/amd/display: assign missing trace entry in amdgpu_dm_dc_clocks_state (git-fixes).\n- drm/amd/display: disable replay when crc source is enabled (stable-fixes).\n- drm/amd/display: Fix direct scanout alpha on some DRM_FORMATs (stable-fixes).\n- drm/amd/display: fix vready offset assignment in dcn_optc_lock_unlock_state (git-fixes).\n- drm/amd/display: Force GAMCOR for subsampled surfaces with PQ/Gamma22/HLG (git-fixes).\n- drm/amd/display: remove duplicated prev_p_state_change_support assignment (git-fixes).\n- drm/amd/display: Use kcalloc() instead of kzalloc() (stable-fixes).\n- drm/amd/display: use right type for amdgpu_dc_performance event entries (git-fixes).\n- drm/amd/pm: bound SCLK FCW range entries to the table size (git-fixes).\n- drm/amdgpu/atombios: drop empty function (stable-fixes).\n- drm/amdgpu/gfx6: fix firmware leak on teardown (stable-fixes).\n- drm/amdgpu: Check for multiplication overflow in checkpoint stack (bsc#1276280).\n- drm/amdgpu: make Mac FB workaround generic (stable-fixes).\n- drm/amdgpu: Remove unused amdgpu_i2c functions (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro14,3 (stable-fixes).\n- drm/amdgpu: reset VI ASIC on MacBookPro15,1 (stable-fixes).\n- drm/amdgpu: rework i2c init and fini (stable-fixes).\n- drm/amdgpu: serialize vblank counter reads against GPU reset (stable-fixes).\n- drm/amdgpu: Update SRIOV Exchange Headers for RAS Telemetry Support (stable-fixes).\n- drm/amdgpu: Use dbg level for VBIOS check messages (stable-fixes).\n- drm/amdkfd: Fix checkpoint-restore on multi-xcc (bsc#1276280).\n- drm/amdkfd: Fix partial migrate issue (stable-fixes).\n- drm/bridge: analogix_dp: Restore mandatory samsung DP DT properties (git-fixes).\n- drm/exynos/fimd: fix register offset type in fimd_trigger() (git-fixes).\n- drm/i915/display: convert I915_STATE_WARN() to struct intel_display (stable-fixes).\n- drm/i915/gmbus: convert to struct intel_display (stable-fixes).\n- drm/i915/vga: Convert VGA code to intel_display (stable-fixes).\n- drm/i915: document range_overflows() and range_end_overflows() macros (stable-fixes).\n- drm/i915: rename range_overflows_end() to range_end_overflows() (stable-fixes).\n- drm/imx/lcdc: avoid duplicate clk_per enable (git-fixes).\n- drm/komeda: Fix bits parsing of GLB_CORE_ID (git-fixes).\n- drm/mali-dp: Fix runtime PM leak in malidp_crtc_atomic_enable() (git-fixes).\n- drm/msm/a6xx: Fix secondary rail vote in ARC votes (git-fixes).\n- drm/msm/a6xx: fix use-after-free of OPP in a6xx_pm_resume (git-fixes).\n- drm/msm/dp: don't report link training success after a reinit (git-fixes).\n- drm/msm/dpu: disable the slave encoder before the master (git-fixes).\n- drm/msm/hdmi_phy: Cleanup after msm_hdmi_phy_resource_enable() failure (git-fixes).\n- drm/msm/mdp5: drop cursor pipe for msm8x76 (git-fixes).\n- drm/msm: Properly handle msm_ioremap() without name (git-fixes).\n- drm/nouveau/svm: drain fault handler before freeing svmm (git-fixes).\n- drm/nouveau: cancel the DP IRQ work before freeing the connector (git-fixes).\n- drm/nouveau: disable the fence uevent work instead of just cancelling it (git-fixes).\n- drm/nouveau: don't dereference outp before checking it in nouveau_dp_irq (git-fixes).\n- drm/nouveau: reject zero-size notifier object allocation (git-fixes).\n- drm/omap: dsi: avoid sending bta sync all the time in writes (git-fixes).\n- drm/panel: ebbg-ft8719: Set prepare_prev_first (git-fixes).\n- drm/panfrost: Explicitly enable MMU interrupts at device init (git-fixes).\n- drm/panfrost: Prevent division by 0 (git-fixes).\n- drm/panthor: Fix TOCTOU race between GROUP_REGISTERED check and erase (git-fixes).\n- drm/panthor: Take reqs_lock in soft_reset for clearing pending_reqs (git-fixes).\n- drm/tegra: Don't pass an ERR_PTR to drm_syncobj_replace_fence() (git-fixes).\n- drm/tegra: Drop reference on postfence (git-fixes).\n- drm/tegra: Fix syncobj_in wait return value check (git-fixes).\n- drm/ttm: return an error when kmapping a BO without pages (git-fixes).\n- drm/vc4: Fix firmware reference leak in vc4_drm_bind() (git-fixes).\n- drm/vc4: Use video aperture helpers (stable-fixes).\n- drm/virtio: Add a helper to map and note the dma addrs and lengths (stable-fixes).\n- drm/virtio: Use drm_gem_plane_helper_prepare_fb() (stable-fixes).\n- drm/vmwgfx: Stop using dev_private to store driver data (stable-fixes).\n- drm: of: Fix drm_of_get_data_lanes_count_ep() return value documentation (git-fixes).\n- fbdev: atmel_lcdfb: Prevent FIFO work after removal (git-fixes).\n- fbdev: gxt4500: Release WC setup on probe failure (git-fixes).\n- fbdev: sh_mobile_lcdc: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: smscufx: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: ssd1307fb: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: udlfb: check for fb_deferred_io_init() error (git-fixes).\n- fbdev: udlfb: don't rebuild the mode list while the framebuffer is in use (git-fixes).\n- fbdev: xen-fbfront: check for fb_deferred_io_init() error (git-fixes).\n- firewire: cdev: Fix FW_CDEV_IOC_CREATE_ISO_CONTEXT references in kernel-doc (git-fixes).\n- firmware: cs_dsp: clear dsp-\u003erunning on the cs_dsp_run() error path (git-fixes).\n- firmware: imx: dsp: fix mailbox channel leak on kasprintf failure (git-fixes).\n- fpga: Fix of_fpga_mgr_get() reference in fpga_mgr_lock() docs (git-fixes).\n- gpio: crystalcove: add missing MODULE_ALIAS() (git-fixes).\n- gpio: davinci: Clear interrupt status in every bank on suspend (git-fixes).\n- gpio: pca953x: Preserve wakeup accounting on parent IRQ failure (git-fixes).\n- HID: alps: unregister DualPoint Stick input device on remove (git-fixes).\n- HID: amd_sfh: Remove unsupported motion-state field from accelerometer report (git-fixes).\n- HID: amd_sfh: Use report type from request node (git-fixes).\n- HID: core: Add reserved item tag for main items (stable-fixes).\n- HID: core: Fix out-of-bounds left shift by 32 in s32ton() (git-fixes).\n- HID: cougar: reject short special-key reports (git-fixes).\n- HID: cp2112: validate response report lengths (git-fixes).\n- HID: elo: reject short touchscreen reports (git-fixes).\n- HID: hid-alps: Use pm_ptr instead of #ifdef CONFIG_PM (stable-fixes).\n- HID: hid-steam: Make client_opened a counter (stable-fixes).\n- HID: logitech-dj: validate unnumbered keyboard reports (git-fixes).\n- HID: mcp2221: clear rxbuf after I2C/SMBus transfer completes (git-fixes).\n- HID: mcp2221: fix OOB write in mcp2221_raw_event() (stable-fixes).\n- HID: mcp2221: validate response report length (git-fixes).\n- HID: picoLCD: check for fb_deferred_io_init() error (git-fixes).\n- HID: pxrc: reject short input reports (git-fixes).\n- HID: rate-limit hid_warn to prevent log flooding (stable-fixes).\n- HID: roccat: isku: reject short button reports (git-fixes).\n- HID: roccat: koneplus: reject short button reports (git-fixes).\n- HID: roccat: konepure: reject short button reports (git-fixes).\n- HID: roccat: kovaplus: reject short button reports (git-fixes).\n- HID: roccat: pyra: reject short button reports (git-fixes).\n- HID: roccat: ryos: reject short special reports (git-fixes).\n- HID: roccat: savu: reject short special reports (git-fixes).\n- HID: wacom: fix wacom_intuos_irq NULL pen_input deref (git-fixes).\n- HID: zydacron: validate key report length (git-fixes).\n- hostfs: fix dev_t handling (git-fixes).\n- hwmon: (coretemp) Refresh the temperature on the first read (git-fixes).\n- hwmon: (corsair-cpro) Make wait_input_report_lock IRQ safe (git-fixes).\n- hwmon: (lm70) Fix rounding of negative temperatures (git-fixes).\n- hwmon: (lm95245) Fix negative temperature conversion (git-fixes).\n- hwmon: (sht3x) Return the consumed count for heater writes (git-fixes).\n- hwrng: amd - report partial reads in non-blocking mode (git-fixes).\n- hwrng: ba431 - fix reported byte count (git-fixes).\n- hwrng: cctrng - Fix runtime PM usage counter leak (git-fixes).\n- hwrng: core - reject unknown RNG names (git-fixes).\n- hwrng: intel - return -ENOMEM when ioremap() fails (git-fixes).\n- hwrng: intel - return -ENOMEM when kmalloc_obj() fails (git-fixes).\n- hwrng: starfive - propagate clock and reset errors (git-fixes).\n- i2c: acpi: Fix adapter reference leak in i2c_acpi_new_device_by_fwnode() (git-fixes).\n- i2c: at91: release DMA channels when probe defers (git-fixes).\n- i2c: designware: queue only one read command for block reads (git-fixes).\n- i2c: mt7621: fix copying uninitialized kernel stack with reduced page_len (git-fixes).\n- i2c: xiic: don't clobber msg-\u003elen to signal block-read completion (git-fixes).\n- i2c: xiic: Relocate xiic_i2c_runtime_suspend and xiic_i2c_runtime_resume to facilitate atomic mode (stable-fixes).\n- iio: accel: adis16201: fix channel order for buffer mode (git-fixes).\n- iio: accel: kionix-kx022a: Fix IPOL macro name (git-fixes).\n- iio: accel: kxcjk-1013: Disable autosuspend on remove (git-fixes).\n- iio: accel: mma9551: disable autosuspend on remove (git-fixes).\n- iio: accel: mma9553: disable autosuspend on remove (git-fixes).\n- iio: adc: aspeed: propagate reset deassert errors (git-fixes).\n- iio: adc: aspeed: Simplify with dev_err_probe (stable-fixes).\n- iio: adc: at91-sama5d2: disable autosuspend on remove (git-fixes).\n- iio: adc: stm32: fix minimum sampling time values (git-fixes).\n- iio: adc: ti-adc128s052: validate SPI match data (git-fixes).\n- iio: core: add accessors 'masklength' (stable-fixes).\n- iio: dac: ad5758: Fix alignment for DMA safety (git-fixes).\n- iio: dac: ad5758: Fix the offset calculation (git-fixes).\n- iio: dac: ad5758: Reject out-of-range raw values (git-fixes).\n- iio: humidity: hts221: report available values via read_avail() (git-fixes).\n- iio: imu: adis16400: Check return value of spi_setup() (git-fixes).\n- iio: light: ltrf216a: Return floating point values (stable-fixes).\n- iio: pressure: dps310: fix CFG_REG bit definitions (git-fixes).\n- iio: temperature: tmp117: fix calibbias cache update on I2C write failure (git-fixes).\n- Input: atkbd - skip deactivate for Lenovo IdeaPad Slim 3 15IWC11 (stable-fixes).\n- Input: da7280 - fix input device parent assignment (git-fixes).\n- Input: drv2665 - fix input device parent assignment (git-fixes).\n- Input: drv2667 - fix input device parent assignment (git-fixes).\n- Input: i8042 - add nomux quirk for Fujitsu LIFEBOOK U7410 (stable-fixes).\n- Input: lkkbd - disable pending work before freeing device (stable-fixes).\n- Input: maple_keyb - fix key press detection (git-fixes).\n- Input: maplecontrol - emit EV_SYN report after reporting events (git-fixes).\n- Input: matrix-keymap - reject keycodes above KEY_MAX (git-fixes).\n- Input: synaptics - add LEN205b entry to smbus_pnp_ids for ThinkPad T490 (stable-fixes).\n- Input: tps6507x-ts - fix input device parent assignment (git-fixes).\n- Input: xpad - add support for Corsair Novablade Pro (stable-fixes).\n- kobject: fix out-of-bounds access in kobject_action_type() (git-fixes).\n- kobject: Fix the kobj_set_name reference in kset_register() kernel-doc (git-fixes).\n- KVM: SEV: Do cache maintenance on the source VM *before* clearing SEV state (git-fixes).\n- landlock: Always allow signals between threads of the same process (git-fixes).\n- landlock: Fix cosmetic change (git-fixes).\n- landlock: Fix non-TCP sockets restriction (git-fixes).\n- landlock: Fix TCP handling of short AF_UNSPEC addresses (git-fixes).\n- landlock: Fix unmarked concurrent access to socket family (git-fixes).\n- leds: flash: Prevent using uninitialized variable in flash_fault_show() (git-fixes).\n- leds: lm3692x: Fix regulator/gpio leak and wrong enabled state on last write failure (git-fixes).\n- leds: lp8860: Fix device_node leak in lp8860_probe() (git-fixes).\n- leds: pca9532: Check i2c_smbus_read_byte_data() return value (git-fixes).\n- mac80211: tx: Use info-\u003eflags in ieee80211_tx_h_select_key() (git-fixes).\n- media: adv748x: Fix endpoint reference leaks on probe failure (git-fixes).\n- media: adv7180: Initialize mutex before ancillary clients (git-fixes).\n- media: adv7604: avoid negative array index in log_status when cp_read fails (git-fixes).\n- media: amphion: fix runtime PM imbalance on probe failure (git-fixes).\n- media: amphion: prevent unbind while video instances are open (git-fixes).\n- media: atmel-isi: release unregistered video device on remove (git-fixes).\n- media: au0828: Fix media device leak in au0828_usb_probe() (git-fixes).\n- media: au0828: fix use-after-free in bulk_timeout timer on disconnect (git-fixes).\n- media: au0828: Free URBs when starting DVB streaming fails (git-fixes).\n- media: cx18: Disable PCI device on probe failure (git-fixes).\n- media: cx88: Disable PCI device on MPEG initialization failure (git-fixes).\n- media: cx231xx-audio: drain wq_trigger before audio fini (git-fixes).\n- media: cx231xx: Fix cleanup path on failure (git-fixes).\n- media: cx23885: Fix use-after-free in cx23885_finidev due to race condition (git-fixes).\n- media: cx23885: unregister DVB bus when SP2 CI setup fails (git-fixes).\n- media: em28xx: fix double free in em28xx_alloc_urbs (git-fixes).\n- media: em28xx: reject audio endpoint with zero packet size (git-fixes).\n- media: exynos4-is: Fix a race between s_stream(0) and the interrupt handler (git-fixes).\n- media: go7007: bound EZ-USB I2C transfers to the usb_buf size (git-fixes).\n- media: go7007: unregister the I2C adapter on USB probe failure (git-fixes).\n- media: gspca: use vb2_video_unregister_device() on disconnect (git-fixes).\n- media: hackrf: fix use-after-free in hackrf_alloc_urbs() error path (git-fixes).\n- media: hantro: Disable multicore support (stable-fixes).\n- media: hantro: disable runtime PM before hardware teardown (git-fixes).\n- media: hantro: Harden MPEG-2 control access against NULL (git-fixes).\n- media: i2c: ar0521: remove duplicate media entity cleanup (git-fixes).\n- media: i2c: ov5648: Fix a data race on state-\u003estreaming (git-fixes).\n- media: i2c: ov8856: fix debug message to report actual CSI-2 lane count (git-fixes).\n- media: i2c: tc358743: add missing color-space strings (git-fixes).\n- media: imon: fix use-after-free in display_close via dev_dbg (git-fixes).\n- media: imx-jpeg: cancel timeout worker when streaming stops (git-fixes).\n- media: imx-jpeg: finish the job on device_run() error paths (git-fixes).\n- media: ir-hix5hd2: Ensure rdev is setup before interrupts are enabled (git-fixes).\n- media: ir_toy: Validate the maximum tx carrier (git-fixes).\n- media: m2m-deinterlace: fix default capture field (git-fixes).\n- media: marvell-cam: fix unmet dependency for VIDEO_MMP_CAMERA (git-fixes).\n- media: marvell: manage the MMP camera clock provider (git-fixes).\n- media: mediatek: jpeg: Avoid context access after job finish (git-fixes).\n- media: mediatek: jpeg: retry HW selection after successful wait (git-fixes).\n- media: mediatek: vpu: free IRQ before destroying watchdog workqueue (git-fixes).\n- media: mediatek: vpu: release reserved memory on remove (git-fixes).\n- media: meson-ir-tx: Ensure clock is disabled on unbind (git-fixes).\n- media: meson-ir-tx: Ensure probe error is propagated (git-fixes).\n- media: meson-ir-tx: Prevent divide by zero in meson_irtx_prepare_pulse() (git-fixes).\n- media: meson: vdec: size capture planes from the aligned canvas (git-fixes).\n- media: microchip-csi2dc: fix async notifier leak on probe error path (git-fixes).\n- media: microchip-isc: disable histogram and flush AWB work on teardown (git-fixes).\n- media: microchip-isc: do not touch WB registers when not streaming (git-fixes).\n- media: microchip-isc: fix PM runtime leak in AWB work handler (git-fixes).\n- media: microchip-isc: synchronize the IRQ before disabling clocks on stop (git-fixes).\n- media: mtk-jpeg: Fix runtime PM leak in mtk_jpegdec_worker() (git-fixes).\n- media: mtk-jpeg: Fix runtime PM leak in mtk_jpegenc_worker() (git-fixes).\n- media: platform: mtk-mdp3: Fix device reference leak in mdp_comp_init() (git-fixes).\n- media: pvrusb2: Fix USB parent device leak in class_dev_create() (git-fixes).\n- media: rc: fintek-cir: process a full RX buffer instead of overflowing it (git-fixes).\n- media: rc: mce_kbd: Fix inconsistent locking of keylock (git-fixes).\n- media: redrat3: Ensure all urbs are suspended (git-fixes).\n- media: redrat3: Ensure we don't read beyond the end of the packet (git-fixes).\n- media: redrat3: fix UAF in probe error path leaving rc device registered (git-fixes).\n- media: require two-byte Cypress type 04 records (git-fixes).\n- media: rtl28xxu: fix SDR platform device leak (git-fixes).\n- media: saa7146: Initialize interrupt lock before requesting IRQ (git-fixes).\n- media: streamzap: Add missing rc_unregister_device() (git-fixes).\n- media: stv090x: bound DiSEqC reply length to msg size (git-fixes).\n- media: stv0900: bound DiSEqC reply length to msg size (git-fixes).\n- media: tw68: balance PCI enable on cleanup (git-fixes).\n- media: tw686x: fix V4L2 device lifetime on probe failure (git-fixes).\n- media: uvcvideo: Fix NULL deref on events for uninitialized controls (git-fixes).\n- media: v4l2-common: Fix P010 format info (git-fixes).\n- media: v4l2-ctrls: do nothing if controls == NULL in cluster functions (git-fixes).\n- media: venus: Drop session events without an instance (git-fixes).\n- media: verisilicon: rockchip: Fix leaks in init (git-fixes).\n- media: vicodec: fix NULL deref on oversized frame (git-fixes).\n- media: vicodec: fix out-of-bounds write on under-rounded coded dimensions (git-fixes).\n- media: vicodec: make encoder CAPTURE dimensions read-only (git-fixes).\n- media: vicodec: zero-initialize stateful decoder heap buffers (git-fixes).\n- media: vidtv: fix frontend reference leak on unbind (git-fixes).\n- media: vidtv: fix uaf in vidtv_bridge_on_new_pkts_avail (git-fixes).\n- media: vim2m: keep transaction buffer count stable while streaming (git-fixes).\n- media: vivid: round the height down to the vertical subsampling factor (git-fixes).\n- media: vpif_display: Fix i2c adapter reference leak in vpif_probe() (git-fixes).\n- mei: vsc-tp: initialize IRQ state before requesting interrupt (git-fixes).\n- mei: vsc: Fix packet CRC computed over pointer size (git-fixes).\n- mfd: ab8500: Fix child device leaks on probe failure (git-fixes).\n- mfd: da9150: Balance IRQ wake on teardown (git-fixes).\n- mfd: intel_quark_i2c_gpio: Manage the fixed-rate clock (git-fixes).\n- mfd: tps65217: Check return value when masking interrupt sources (git-fixes).\n- mfd: tps65217: Fix NULL pointer dereference on IRQ init failure (git-fixes).\n- mfd: wcd934x: Fix NULL pointer dereference on IRQ probe deferral (git-fixes).\n- mfd: wcd934x: set DMA mask on parent to silence 'DMA mask not set' (git-fixes).\n- misc: enclosure: fix UAF on device_register() failure (git-fixes).\n- mm, vmscan: flush tlb before large folio is freed (bsc#1250656).\n- mm: introduce num_pages_contiguous() (bsc#1284243).\n- mtd: amd76xrom: Fix PCI device reference leak in amd76xrom_init_one() (git-fixes).\n- mtd: block: prevent reclaim I/O during request processing (git-fixes).\n- mtd: Call get_wunit() on the master partition (git-fixes).\n- mtd: cfi_cmdset_0002: cap the write-buffer chunk at 256 bytes on an x8 device (git-fixes).\n- mtd: maps: l440gx: Fix double put of the ISA bridge in init_l440gx() (git-fixes).\n- mtd: maps: l440gx: Fix double put of the PM device in init_l440gx() (git-fixes).\n- mtd: maps: pci: balance PCI enable on cleanup (git-fixes).\n- mtd: parsers: qcom: fix offset/size overflow on large partitions (git-fixes).\n- mtd: rawnand: atmel: Fix MCK clock leak in atmel_nand_controller_init() (git-fixes).\n- mtd: rawnand: pl353: fix clk reference leak in pl35x_nfc_setup_interface() (git-fixes).\n- mtd: rawnand: sunxi: reject ECC maximization on small pages (git-fixes).\n- mtd: spi-nor: sfdp: check the length of the SCCR map (git-fixes).\n- mtd: spi-nor: sfdp: check the length of the xSPI Profile 1.0 table (git-fixes).\n- mtd: spi-nor: Unprepare legacy controllers upon RWW wait interruption (git-fixes).\n- mtd: spinand: Fix spinand_manufacturer_ops kernel-doc (git-fixes).\n- net: usb: lan78xx: reject invalid EEPROM write requests (git-fixes).\n- net: usb: r8153_ecm: reject short register reads (git-fixes).\n- net: usb: sierra_net: reject short firmware attribute reads (git-fixes).\n- net: wwan: iosm: validate msg_head before indexing msg_ring (git-fixes).\n- PCI/AER: Fix memory leak in aer_recover_queue() on kfifo buffer overflow (git-fixes).\n- PCI/AER: Fix struct pci_dev reference leak in aer_process_err_devices() (git-fixes).\n- PCI/P2PDMA: Gate the host bridge whitelist warning on verbose (git-fixes).\n- PCI/P2PDMA: Safely terminate ACS redirect lists (git-fixes).\n- PCI/sysfs: Handle a malformed _DSM result in acpi_attr_is_visible() (git-fixes).\n- PCI/sysfs: Pass the device name length in UTF-16 code units (git-fixes).\n- PCI/sysfs: Stop reporting _DSM failures as -EPERM (git-fixes).\n- PCI: aardvark: Disable PHY on probe failures (git-fixes).\n- PCI: cadence: Preserve all error codes in cdns_plat_pcie_probe() (git-fixes).\n- PCI: Disable MSI for ULi M1575 EHCI controller (git-fixes).\n- PCI: dra7xx: Fix clock enable leak on probe failure (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Pass PF/VF number when BAR programming (git-fixes).\n- PCI: endpoint: pci-epf-vntb: Serialize virtual PCI bus scan (git-fixes).\n- PCI: Fix out-of-bounds MMIO read in nvme_disable_and_flr() (git-fixes).\n- PCI: qcom: Honor IOMMU provider's #iommu-cells in qcom_pcie_config_sid_1_9_0() (git-fixes).\n- PCI: rockchip-host: Do not attempt 5.0 GT/s retraining (git-fixes).\n- PCI: xgene: Use managed clock for PCIe controller (git-fixes).\n- peci: aspeed: Initialize state before requesting IRQ (git-fixes).\n- phy: core: Fix race-condition between _of_phy_get() and try_module_get() (git-fixes).\n- pinctrl: mediatek: mt7629: fix the 2.4 GHz Wi-Fi pin mode array (git-fixes).\n- pinctrl: sprd: free maps on DT map failure (git-fixes).\n- pinctrl: stm32: Fix fwnode reference leak in stm32_gpiolib_register_bank() (git-fixes).\n- platform/chrome: cros_ec_proto: Fix deferred response (git-fixes).\n- power: supply: charger-manager: Convert to platform remove callback returning void (stable-fixes).\n- power: supply: lp8788-charger: Convert to platform remove callback returning void (stable-fixes).\n- power: supply: lp8788-charger: fix use-after-free on remove (git-fixes).\n- power: supply: lp8788: Use devm_power_supply_register() helper (stable-fixes).\n- pwm: mtk-disp: Fix period readback (git-fixes).\n- RDMA/core: Add rdma_restrack_begin/abort/commit_del() operations (git-fixes).\n- regulator: ab8500: Fix AB8505 VANA voltage selectors (git-fixes).\n- regulator: ab8500: Handle AB8505 VINTCORE selector 7 (git-fixes).\n- regulator: ab8500: Propagate mode enable read errors (git-fixes).\n- regulator: ab8500: Test dedicated enable bits only (git-fixes).\n- regulator: ab8500: Treat cut 1.0 VAUX3 as fixed (git-fixes).\n- regulator: core: Fix c_rdev reference leak in regulator_resolve_coupling() (git-fixes).\n- regulator: core: Fix coupled regulators reference leak on removal (git-fixes).\n- regulator: core: Fix rdev reference leak in regulator_resolve_supply() (git-fixes).\n- regulator: mp886x: check get_voltage_sel() return value (git-fixes).\n- regulator: mp886x: fix pontential division by zero (git-fixes).\n- regulator: mp886x: fix vsel_mask (git-fixes).\n- regulator: rt6190: Fix runtime PM imbalance in rt6190_out_enable() (git-fixes).\n- Reinstate 'resource: avoid unnecessary lookups in find_next_iomem_res()' (bsc#1284243).\n- Revert 'wifi: mac80211: do not use old MBSSID elements' (git-fixes).\n- rtc: ac100: Assign .num before accessing .hws (git-fixes).\n- rtc: dev: zero-initialize struct rtc_wkalrm to prevent information leak (git-fixes).\n- rtc: mpfs: fix unchecked devm_clk_get() error pointer in probe() (git-fixes).\n- rtc: spear: initialize IRQ state before requesting alarm IRQ (git-fixes).\n- selftests/alsa: Do not take another control's event as our own (git-fixes).\n- selftests/landlock: Add a new test for setuid() (git-fixes).\n- selftests/landlock: Fix build with non-default pthread linking (git-fixes).\n- selftests/landlock: Fix screwed up pointers in the scoped_signal_test (git-fixes).\n- selftests/landlock: Skip scoped_signal subtest with MSG_OOB if not available (git-fixes).\n- selftests/landlock: Split signal_scoping_threads tests (git-fixes).\n- serial: 8250_lpss: do not touch uninitialized line in ehl_serial_exit() (git-fixes).\n- serial: core: shut down initialized port on removal (git-fixes).\n- serial: max310x: don't clobber the TX break bit in set_termios (git-fixes).\n- serial: pmac_zilog: push received data to the port that received it (git-fixes).\n- serial: pmac_zilog: report received breaks (git-fixes).\n- slimbus: messaging: fix leaked PM vote on tid allocation failure (git-fixes).\n- soc/tegra: flowctrl: Release OF node reference on error (git-fixes).\n- soc: fsl: cpm1: tsa: Fix clock leak in tsa_of_parse_tdms() (git-fixes).\n- soc: fsl: dpio: Fix cleanup on IRQ registration failure (git-fixes).\n- soc: fsl: dpio: Free the IRQ before releasing the I/O object (git-fixes).\n- soc: qcom: apr: clean up failed service registrations (git-fixes).\n- soc: ti: k3-ringacc: Correct ring API kernel-doc (git-fixes).\n- soc: ti: k3-ringacc: Fix DMA ring initialization kernel-doc (git-fixes).\n- spi: amd: fix len==0 underflow and FIFO overflow (git-fixes).\n- spi: bcm63xx-hsspi: Disable runtime PM on remove (git-fixes).\n- spi: Fix the return value in spi_new_ancillary_device() kernel-doc (git-fixes).\n- spi: jcore: fix divide-by-zero when speed_hz is zero (git-fixes).\n- spi: mtk-nor: fix runtime PM usage count leak in probe error path (git-fixes).\n- spi: mxic: fix ps_clk leak in runtime resume (git-fixes).\n- spi: npcm-fiu: limit UMA data_size to the 16-byte staging buffer (git-fixes).\n- spi: omap2-mcspi: Remove unbalanced pm_runtime_put_sync() calls (git-fixes).\n- spi: spi-sun4i: sun4i_spi_fill_fifo(): always apply A10 FIFO fill level workaround (git-fixes).\n- spi: spi-sun4i: sun4i_spi_transfer_one(): fix transfers for SUN4I_FIFO_DEPTH (git-fixes).\n- staging: iio: adc: ad7816: Fix DMA safety issues in SPI transfers (git-fixes).\n- staging: media: av7110: fix corrupted BER reporting in sp8870 (git-fixes).\n- staging: media: imx: csc-scaler: fix ipu_image_convert_run leak on queue error (git-fixes).\n- staging: rtl8723bs: clean up redundant \u0026 parentheses (stable-fixes).\n- Staging: rtl8723bs: Delete dead code from update_current_network() (stable-fixes).\n- staging: rtl8723bs: fix buffer over-read in rtw_update_protection (git-fixes).\n- staging: rtl8723bs: fix RX buffer OOB write from device-reported length (git-fixes).\n- Staging: rtl8723bs: Remove dead code from _rtw_free_network() (stable-fixes).\n- staging: sm750fb: free cmap on framebuffer release (git-fixes).\n- thermal/drivers/sprd: validate the sensor id from the device tree (git-fixes).\n- thermal: intel: int340x: Fix temperature selection around 0 C (git-fixes).\n- thermal: intel: powerclamp: Reject invalid window_size values (git-fixes).\n- thermal: ti-soc-thermal: Fix the return value in ti_bandgap_get_sensor_data() kernel-doc (git-fixes).\n- thunderbolt: Disable CL states for the Anker Prime TB5 dock (stable-fixes).\n- thunderbolt: Do not RPM complete unrelated subtrees on unplug (git-fixes).\n- tools/thermal/tmon: Fix string truncation warning in optarg copy (git-fixes).\n- tpm: fix zero-length read discarding the pending response (git-fixes).\n- tpm: tpm_nsc: fix NULL pointer dereference on init failure (git-fixes).\n- tpm: tpm_nsc: stop using the cleanup callback as dev.release (git-fixes).\n- tty: add break_wait kernel-doc (git-fixes).\n- tty: vcc: hold port lock when clearing tty pointer in vcc_cleanup (stable-fixes).\n- tty: vcc: zero-initialize control packet in vcc_send_ctl() (stable-fixes).\n- um: hostfs: avoid issues on inode number reuse by host (git-fixes).\n- usb-storage: alauda: check the return value of alauda_read_map() (git-fixes).\n- usb-storage: alauda: do not do DMA from the stack (git-fixes).\n- usb-storage: alauda: fix out-of-bounds zone index (git-fixes).\n- USB: cdc-acm: fix urb leak on disconnect (git-fixes).\n- usb: chipidea: udc: fix DMA and SG cleanup in _ep_nuke() (stable-fixes).\n- usb: dwc3: clear forceRM when issuing EndTransfer (git-fixes).\n- usb: dwc3: gadget: Fix use-after-free in dwc3_gadget_free_endpoints due to race condition (git-fixes).\n- usb: dwc3: gadget: Reinitiate stream for all host NoStream behavior (stable-fixes).\n- usb: fotg210: validate endpoint index in ep0 handlers (git-fixes).\n- usb: gadget: composite: avoid warning on aborted delayed status (git-fixes).\n- usb: gadget: dummy_hcd: fix SuperSpeed ep0 maxpacket (git-fixes).\n- usb: gadget: dummy_hcd: prevent unbind via sysfs (git-fixes).\n- usb: gadget: f_fs: Fix Use-After-Free in AIO error path (git-fixes).\n- usb: gadget: f_mass_storage: ignore class requests while inactive (git-fixes).\n- usb: gadget: f_midi: Annotate struct f_midi with __counted_by (stable-fixes).\n- usb: gadget: f_midi: initialize work in f_midi_alloc() (git-fixes).\n- USB: gadget: ffs: fix mm lifetime handling (stable-fixes).\n- usb: gadget: functionfs: Factorize wait-for-endpoint code (stable-fixes).\n- usb: image: microtek: stop SG processing after transfer errors (git-fixes).\n- usb: musb: da8xx: depopulate OF children on probe failure (git-fixes).\n- usb: musb: da8xx: depopulate OF children on remove (git-fixes).\n- usb: ohci-spear: disable controller wakeup on removal (git-fixes).\n- usb: ohci-spear: Remove unnecessary NULL check before clk_disable_unprepare() (stable-fixes).\n- USB: pci-quirks: Release EHCI device reference (git-fixes).\n- USB: serial: cp210x: add Corsair AX1500i Power Supply (stable-fixes).\n- USB: serial: option: add Compal EXC-T1 support (stable-fixes).\n- USB: serial: option: add Compal EXM-G1x support (stable-fixes).\n- USB: serial: option: add Quectel EG060W (stable-fixes).\n- USB: serial: option: add Quectel RG660QB (stable-fixes).\n- USB: serial: option: add support for SIMCom SIM8260C (stable-fixes).\n- USB: serial: sierra: fix urb leak on write completion (git-fixes).\n- USB: serial: usb_wwan: fix urb leak on disconnect (git-fixes).\n- usb: typec: ucsi_ccg: Add retry mechanism in ccg_read (git-fixes).\n- USB: usbmon: fix null-ptr-deref in mon_bus_remove() when mon_bus_init() fails (git-fixes).\n- usbnet: fix smp_processor_id() use in preemptible context (git-fixes).\n- vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote() (bsc#1284243).\n- vfio/type1: conditional rescheduling while pinning (bsc#1284243).\n- vfio/type1: introduce a new member has_rsvd for struct vfio_dma (bsc#1284243).\n- vfio/type1: optimize vfio_pin_pages_remote() (bsc#1284243).\n- vfio/type1: optimize vfio_unpin_pages_remote() (bsc#1284243).\n- vt: skip screen update for DEC alignment test on backgroup consoles (git-fixes).\n- watchdog: mediatek: Apply the driver's mode to a watchdog left running (git-fixes).\n- wifi: ath6kl: don't take RTNL in del_virtual_intf (git-fixes).\n- wifi: ath9k: delete channel-context timers on deinit (git-fixes).\n- wifi: ath10k: avoid IDR mutation during TX cleanup (git-fixes).\n- wifi: ath11k: avoid IDR mutation during pending mgmt TX cleanup (git-fixes).\n- wifi: ath11k: avoid IDR mutation during vif mgmt TX cleanup (git-fixes).\n- wifi: ath11k: disable interrupts during firmware crash recovery (git-fixes).\n- wifi: ath11k: fix locking problem in ath11k_dp_rx_tid_del_func() (git-fixes).\n- wifi: ath11k: fix NULL dereference in ahb remove when QMI init incomplete (git-fixes).\n- wifi: ath11k: Fix possible memory leak in ath11k_dp_srng_setup() (git-fixes).\n- wifi: ath11k: fix sporadic WLAN initialization failures (git-fixes).\n- wifi: ath11k: fix unbalanced IRQ enable/disable during suspend/resume (git-fixes).\n- wifi: ath11k: modify null check logic in ath11k_ce_rx_post_pipe() (git-fixes).\n- wifi: ath11k: reset ar-\u003enum_stations on hardware start (git-fixes).\n- wifi: ath11k: unregister PM notifier on QMI init failure path (git-fixes).\n- wifi: ath12k: avoid IDR mutation during vif mgmt TX cleanup (git-fixes).\n- wifi: ath12k: fix incorrect TID updation in DP monitor status path (stable-fixes).\n- wifi: ath12k: fix struct hal_rx_phyrx_rssi_legacy_info (stable-fixes).\n- wifi: ath12k: fix the fetching of combined rssi (git-fixes).\n- wifi: ath12k: Free allocated CE IRQs on request_irq() failure (git-fixes).\n- wifi: ath12k: Reserve space for a string terminator (git-fixes).\n- wifi: b43: don't pass unterminated string to sscanf() (git-fixes).\n- wifi: b43: fix use-after-free in b43_bcma_remove() (git-fixes).\n- wifi: b43legacy: debugfs: NUL terminate string in debugfs (git-fixes).\n- wifi: brcmsmac: Adjust txpwrindex value in nphy_ipa_rxcal_gaintbl_2GHz (git-fixes).\n- wifi: carl9170: NUL terminate string in debugfs (git-fixes).\n- wifi: cfg80211: allow zero HE OBSS PD offsets (git-fixes).\n- wifi: cfg80211: preserve hidden-group beacon IE ownership (git-fixes).\n- wifi: cfg80211: reject duplicate wiphy cipher suite entries (stable-fixes).\n- wifi: cfg80211: track SSID regardless of country data (git-fixes).\n- wifi: cw1200: fix TX padding OOB read leaking heap data to device (git-fixes).\n- wifi: iwlegacy: 3945: free EEPROM data on remove (git-fixes).\n- wifi: iwlwifi: dvm: pair transport op-mode enter/leave (stable-fixes).\n- wifi: iwlwifi: mvm: remove mvm prefix from iwl_mvm_tx_resp* (stable-fixes).\n- wifi: iwlwifi: mvm: validate TX_CMD response layout (stable-fixes).\n- wifi: iwlwifi: simplify nested if checks (stable-fixes).\n- wifi: mac80211: account proxy paths against the mesh path limit (git-fixes).\n- wifi: mac80211: Add 802.3 multicast encapsulation offload support (stable-fixes).\n- wifi: mac80211: Add multicast to unicast support for 802.3 path (stable-fixes).\n- wifi: mac80211: Add sta pointer sanity check in ieee80211_8023_xmit() (stable-fixes).\n- wifi: mac80211: clear fragment cache entry 'is_protected' (git-fixes).\n- wifi: mac80211: don't call ieee80211_handle_reconfig_failure when not needed (stable-fixes).\n- wifi: mac80211: don't reset the TXQ scheduling round number (git-fixes).\n- wifi: mac80211: don't send encap offload frames unencrypted (git-fixes).\n- wifi: mac80211: drain PS delivery work during station teardown (git-fixes).\n- wifi: mac80211: drop encap offload frames with a tainted key (git-fixes).\n- wifi: mac80211: Fix a race when expiring a mesh path (git-fixes).\n- wifi: mac80211: fix encryption tailroom (git-fixes).\n- wifi: mac80211: fix key selection for encap offload frames (git-fixes).\n- wifi: mac80211: fix mesh fast xmit path deletion UAF (git-fixes).\n- wifi: mac80211: fix missing RX bitrate update for mesh forwarding path (stable-fixes).\n- wifi: mac80211: fix swapped fq_overlimit/fq_overmemory in aqm debugfs (git-fixes).\n- wifi: mac80211: Fix the return value in mesh_path_add() kernel-doc (git-fixes).\n- wifi: mac80211: fix typo in HE MCS check (stable-fixes).\n- wifi: mac80211: fix unauthorised port check for encap offload (git-fixes).\n- wifi: mac80211: handle empty FILS association request payload (git-fixes).\n- wifi: mac80211: init radiotap iter after length checks (git-fixes).\n- wifi: mac80211: kill wake_txqs_tasklet on unregistration (git-fixes).\n- wifi: mac80211: limit injected HT/VHT MCSes (git-fixes).\n- wifi: mac80211: log link information in ieee80211_determine_chan_mode (stable-fixes).\n- wifi: mac80211: mesh: use hlist_add_head_rcu() (git-fixes).\n- wifi: mac80211: minstrel_ht: validate fixed rate index (git-fixes).\n- wifi: mac80211: prevent AP VLAN tx from other interfaces (git-fixes).\n- wifi: mac80211: refactor populating mesh related fields in sinfo (stable-fixes).\n- wifi: mac80211: release mesh path quota on failed additions (git-fixes).\n- wifi: mac80211: reserve MME tailroom for protected beacons (git-fixes).\n- wifi: mac80211: set info-\u003eband for 802.3 encap offload frames (git-fixes).\n- wifi: mac80211: use link address as TA for non-MLO 4-addr station on MLD AP (git-fixes).\n- wifi: mt76: feed the station RSSI average from the chain signals (git-fixes).\n- wifi: mt76: fix memory leak in USB TX path (git-fixes).\n- wifi: mt76: Fix of_node reference leak in mt76_get_rate_power_limits() (git-fixes).\n- wifi: mt76: fix unlocked wcid check in mt76_tx_status_skb_add() (git-fixes).\n- wifi: mt76: fix wcid-\u003epktid corruption in mt76_wcid_cleanup() (git-fixes).\n- wifi: mt76: mt76x02: validate RX padding before use (git-fixes).\n- wifi: mt76: mt76x02: validate TX-status rate index before mac80211 handoff (git-fixes).\n- wifi: mt76: mt792x: fix UAF in SDIO TX path when out of memory (git-fixes).\n- wifi: mt76: mt7603: don't drop short frames looped back on PS entry (git-fixes).\n- wifi: mt76: mt7615: cancel reset work during unregister (git-fixes).\n- wifi: mt76: mt7615: do not tear down BSS/STA state for monitor vifs (git-fixes).\n- wifi: mt76: mt7615: read MT7663 temperature from the correct offset (git-fixes).\n- wifi: mt76: mt7615: usb: fix source overread in mt7663u_copy (git-fixes).\n- wifi: mt76: mt7615: validate MCU response lengths (git-fixes).\n- wifi: mt76: mt7915: allocate vif wcid in the same range as stations (stable-fixes).\n- wifi: mt76: mt7915: bound the device EEPROM address before the EFUSE copy (git-fixes).\n- wifi: mt76: mt7915: check default EEPROM firmware size before copying (git-fixes).\n- wifi: mt76: mt7915: clear wcid mask under mutex after RCU pointer clear (git-fixes).\n- wifi: mt76: mt7915: Fix an error handling path in mt7915_add_interface() (git-fixes).\n- wifi: mt76: mt7915: guard firmware memory dump write on disabled memdump (git-fixes).\n- wifi: mt76: mt7915: set correct background radar capability (stable-fixes).\n- wifi: mt76: mt7915: unregister thermal cooling device on hwmon failure (git-fixes).\n- wifi: mt76: mt7921: check drv_pmctrl return in the PCIe reset path (git-fixes).\n- wifi: mt76: mt7921: fix lock inversion between dev-\u003emutex and iflist_mtx (git-fixes).\n- wifi: mt76: mt7921: fix the lock inversion in suspend and resume (git-fixes).\n- wifi: mt76: mt7925: check drv_pmctrl return in the PCIe reset path (git-fixes).\n- wifi: mt76: mt7925: fix lock inversion between dev-\u003emutex and iflist_mtx (git-fixes).\n- wifi: mt76: mt7925: fix the lock inversion in suspend and resume (git-fixes).\n- wifi: mt76: mt7925: honour mac80211's FIF_FCSFAIL instead of hardcoding drop_err (git-fixes).\n- wifi: mt76: mt7925: restore the reset state when fw_pmctrl fails (git-fixes).\n- wifi: mt76: mt7996: fix PLE free page and AC queue register offsets (git-fixes).\n- wifi: mt76: mt7996: validate firmware event lengths before parsing (git-fixes).\n- wifi: mt76: usb: fix source overread in mt76u_copy (git-fixes).\n- wifi: mwifiex: append hotfix number to firmware version string (git-fixes).\n- wifi: rtw88: debugfs: don't vzalloc(0) when rsvd_page is read unconfigured (git-fixes).\n- wifi: rtw88: debugfs: support multiple adapters debugging (stable-fixes).\n- wifi: rtw88: fix out-of-bounds CAM write when key table is full (git-fixes).\n- wifi: rtw88: sdio: zero the padding added to a TX transfer (git-fixes).\n- wifi: rtw89: 8851b: fix swapped DPK channel/bandwidth backup fields (git-fixes).\n- wifi: rtw89: cap firmware section_num before parsing (git-fixes).\n- wifi: wfx: fix possible device hang during init (git-fixes).\n- wifi: wfx: fix use-after-free of the cooling work on device removal (git-fixes).\n- wifi: wfx: validate MIB read length before copying to caller (git-fixes).\n- wwan: wwan_hwsim: Pin module for debugfs file operations (git-fixes).\n- x86/hyperv: Avoid using per-cpu output page in hv_apicid_to_vp_index() (git-fixes).\n- x86/PCI: Disable enhanced atomics on AMD NBIO 7.7 and 7.11 (git-fixes).\n- xhci: dbc: lock the minor IDR on registration failure (git-fixes).\n","status":"published","published":"2026-11-03T16:27:43Z","modified":"2026-11-04T14:15:08.544785478Z","updated_at":"2026-11-04T14:31:33.296313Z"},{"id":"SUSE-SU-2026:5121-1","title":"Security update for the Linux Kernel","description":"\nThe SUSE Linux Enterprise 12 SP5 kernel was updated to fix various security issues:\n\nThe following security issues were fixed:\n\n- CVE-2025-40100: btrfs: do not assert we found block group item when creating free space tree (bsc#1252918).\n- CVE-2025-68741: scsi: qla2xxx: Fix improper freeing of purex item (bsc#1255703 bsc#1275737).\n- CVE-2026-23059: scsi: qla2xxx: Sanitize payload size to prevent member overflow (bsc#1257737 bsc#1275737).\n- CVE-2026-46195: smb: client: validate dacloffset before building DACL pointers (bsc#1266860).\n- CVE-2026-64370: posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path (bsc#1273805).\n- CVE-2026-64379: smb: client: mask server-provided mode to 07777 in modefromsid (bsc#1273029).\n- CVE-2026-64413: netfilter: ebtables: zero chainstack array (bsc#1274082).\n- CVE-2026-64435: audit: Fix data races of skb_queue_len() readers on audit_queue (bsc#1274080).\n- CVE-2026-64539: Bluetooth: eir: Fix stack OOB write when prepending the Flags AD (bsc#1273338).\n- CVE-2026-64546: drm/edid: fix OOB read in drm_parse_tiled_block() (bsc#1273334).\n- CVE-2026-64549: Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() (bsc#1273341).\n- CVE-2026-72250: netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag (bsc#1277663).\n- CVE-2026-72310: smb: client: fix overflow in passthrough ioctl bounds check (bsc#1277750).\n- CVE-2026-72416: netfilter: nft_compat: ebtables emulation must reject non-bridge targets (bsc#1278041).\n- CVE-2026-72428: bpf: Fix stack slot index in nospec checks (bsc#1278050).\n- CVE-2026-74620: net/sched: act_gact, act_police: range check the fallback control action (bsc#1277044).\n- CVE-2026-74683: Input: evdev - sanitize event type index when fetching event masks (bsc#1277387).\n- CVE-2026-74720: bpf: Preserve pointer state for commuted arithmetic (bsc#1276574).\n- CVE-2026-74748: netfilter: ipset: fix refcount race between list:set GC and swap (bsc#1277578).\n- CVE-2026-80572: Input: byd - synchronize timer deletion before freeing private data (bsc#1277338).\n- CVE-2026-80579: fbdev: clear fb_info-\u003emode before deleting a videomode (bsc#1277260).\n- CVE-2026-80637: netfilter: synproxy: fix unaligned memory access in timestamp adjustment (bsc#1278343).\n- CVE-2026-80704: drm/amd/display: use proper context for logging (bsc#1278431).\n- CVE-2026-80717: sctp: validate Adaptation Indication parameter length (bsc#1277836).\n- CVE-2026-80764: Bluetooth: hci_event: fix LE list UAF on reset (bsc#1279493).\n- CVE-2026-80808: ext4: stop retrying saturated xattr cache entries (bsc#1279795).\n- CVE-2026-80809: ocfs2: fix missing metadata reservation for large xattrs (bsc#1279606).\n- CVE-2026-80879: ocfs2: fix circular locking dependency in ocfs2_dio_end_io_write (bsc#1279494).\n- CVE-2026-80881: ocfs2: fix buffer head management in ocfs2_read_blocks() (bsc#1279496).\n- CVE-2026-80888: drm/vmwgfx: drop dma_buf reference on foreign-fd prime import (bsc#1279455).\n- CVE-2026-80978: net: cap advertised IP tunnel headroom (bsc#1280253).\n- CVE-2026-80989: net: thunderbolt: Mark the connection down when bringing it up fails (bsc#1280305).\n- CVE-2026-89494: ocfs2: validate lengths in dlm_mig_lockres_handler (bsc#1280520).\n- CVE-2026-89495: ocfs2: bound namelen in dlm_migrate_request_handler (bsc#1280569).\n- CVE-2026-89537: SUNRPC: Reject short RFC 4121 MIC tokens in gss_krb5_verify_mic_v2 (bsc#1280713).\n- CVE-2026-89559: libnvdimm/labels: Prevent integer overflow in __nd_label_validate() (bsc#1280554).\n- CVE-2026-89606: ecryptfs: reject too-small tag 70 packets (bsc#1280469).\n- CVE-2026-89607: ecryptfs: reject oversized encrypted_key_size in parse_tag_3_packet (bsc#1281792).\n- CVE-2026-89608: ecryptfs: pass packet set buffer size to parser (bsc#1280826).\n- CVE-2026-89631: smb: client: reject a tree connect response whose byte count is too small (bsc#1280496).\n- CVE-2026-89636: smb: client: clear ce-\u003etgthint in free_tgts() (bsc#1281042).\n- CVE-2026-89638: smb: client: clear setuid/setgid bit on write with cifsacl/modefromsid/posix extensions (bsc#1281046).\n- CVE-2026-89640: cifs: fix loff_t underflow in cifs_remap_file_range() when len == 0 (bsc#1280950).\n- CVE-2026-89642: cifs: call pagecache_isize_extended() in cifs_setsize() when extending (bsc#1280970).\n- CVE-2026-89656: libceph: reject buckets with mismatched CRUSH ids (bsc#1280563).\n- CVE-2026-89821: drm/amd/display: avoid divide-by-zero in __is_lut_linear() (bsc#1280996).\n- CVE-2026-89842: scsi: qla2xxx: Skip NVMe LS reject IOCB when FW not started (bsc#1275737 bsc#1281189).\n- CVE-2026-89843: scsi: qla2xxx: Zero-init bsg stack buffers to avoid info leak (bsc#1275737 bsc#1280984).\n- CVE-2026-89844: scsi: qla2xxx: Hold vport_slock for host map update in report ID acquisition (bsc#1275737\n  bsc#1281183).\n- CVE-2026-89845: scsi: qla2xxx: Avoid req_q_map double-read in qla2x00_error_entry() (bsc#1275737 bsc#1281001).\n- CVE-2026-89846: scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read (bsc#1275737 bsc#1281184).\n- CVE-2026-89847: scsi: qla2xxx: Avoid double completion in async IOCB timeout (bsc#1275737 bsc#1281185).\n- CVE-2026-89848: scsi: qla2xxx: Quiesce response IRQ before freeing request queue (bsc#1275737 bsc#1281179).\n- CVE-2026-89849: scsi: qla2xxx: Reject non-SCSI SRB on status IOCB fast path (bsc#1275737 bsc#1281180).\n- CVE-2026-89850: scsi: qla2xxx: Don't query firmware state while chip is down (bsc#1275737 bsc#1281181).\n- CVE-2026-89851: scsi: qla2xxx: Fix FCE trace enable parsing in debugfs (bsc#1275737 bsc#1281175).\n- CVE-2026-89852: scsi: qla2xxx: Zero mailbox struct in qla2x00_get_firmware_state() (bsc#1275737 bsc#1281174).\n- CVE-2026-89853: scsi: qla2xxx: Fix FCE trace use-after-free during firmware dump (bsc#1275737 bsc#1281173).\n- CVE-2026-89854: scsi: qla2xxx: Fix cs84xx use-after-free on host teardown (bsc#1275737 bsc#1281165).\n- CVE-2026-89855: scsi: qla2xxx: Serialize flash version read in reset handler (bsc#1275737 bsc#1281164).\n- CVE-2026-89857: scsi: qla2xxx: Hold qpair lock when sending NVMe LS reject (bsc#1275737 bsc#1281211).\n- CVE-2026-89858: scsi: qla2xxx: Bound image count in qla2x00_update_fru_versions() (bsc#1275737 bsc#1281334).\n- CVE-2026-89859: scsi: qla2xxx: Zero dport diagnostics buffer to avoid info leak (bsc#1275737 bsc#1281333).\n- CVE-2026-89860: scsi: qla2xxx: Initialize NVMe abort_work once at submission (bsc#1275737 bsc#1281357).\n- CVE-2026-89861: scsi: qla2xxx: Hold vport reference in qla24xx_report_id_acquisition() (bsc#1275737 bsc#1281353).\n- CVE-2026-89862: scsi: qla2xxx: Fix BSG job leak on validate flash image error path (bsc#1275737 bsc#1281214).\n- CVE-2026-89863: scsi: qla2xxx: edif: Fix NULL pointer deref in RX SA delete check (bsc#1275737 bsc#1281251).\n- CVE-2026-89864: scsi: qla2xxx: Bound i2c-\u003elength in I2C bsg handlers (bsc#1275737 bsc#1281253).\n- CVE-2026-89865: scsi: qla2xxx: Zero SFP DMA buffer in FRU/I2C bsg handlers (bsc#1275737 bsc#1281254).\n- CVE-2026-90015: xhci: fix lost bounce buffers on TDs spanning several ring segments (bsc#1281080).\n- CVE-2026-90057: slip: remove slip_hangup() to fix use-after-free in slip_receive_buf() (bsc#1281650).\n- CVE-2026-90081: net/rds: use wq_has_sleeper() in rds_cong_map_updated() (bsc#1281490).\n- CVE-2026-90103: NFSv4.2: fix LAYOUTSTATS send buffer exhaustion (bsc#1281538).\n- CVE-2026-90125: smb: client: fix request buffer leak in smb2_new_read_req() (bsc#1281580).\n- CVE-2026-90138: vsock: don't check the listener's sk_err in vsock_accept() (bsc#1281535).\n- CVE-2026-90227: nvme: fine-granular CAP_SYS_ADMIN for nvme io commands (bsc#1281705).\n- CVE-2026-90434: isofs: release zisofs block pointer buffer head (bsc#1281993).\n- CVE-2026-93210: smb: client: harden DFS cache against invalid target hints (bsc#1282737).\n- CVE-2026-93231: lockd: fix swapped arguments in nlmsvc_match_ip() (bsc#1282778).\n- CVE-2026-93242: scsi: qla2xxx: Fix response queue over-consumption in __qla_consume_iocb() (bsc#1275737 bsc#1282684).\n- CVE-2026-93262: md/raid5-ppl: fix use-after-free in ppl_do_flush() (bsc#1283004).\n- CVE-2026-93269: ext4: fix circular lock dependency in ext4_ext_migrate (bsc#1282810).\n- CVE-2026-93785: cifs: validate idmap key payload length (bsc#1282869).\n- CVE-2026-93787: smb: client: bound dirent name against end of SMB response in cifs_filldir (bsc#1282932).\n- CVE-2026-93817: perf: Fix addr_filter_ranges lifetime (bsc#1283017).\n- CVE-2026-97527: scsi: qla2xxx: Serialize NVMe unsol ctx list with a per-fcport lock (bsc#1275737 bsc#1283343).\n- CVE-2026-97528: scsi: qla2xxx: Unlink NVMe unsol ctx before freeing on LS reject error (bsc#1275737 bsc#1283360).\n- CVE-2026-97530: scsi: qla2xxx: Fix soft lockup polling continuation IOCB signature (bsc#1275737 bsc#1283159).\n- CVE-2026-97531: scsi: qla2xxx: Skip vport under deletion in report ID acquisition (bsc#1275737 bsc#1283834).\n- CVE-2026-97535: scsi: qla2xxx: Bound VP index against VP_CTRL IOCB bitmap size (bsc#1275737 bsc#1283837).\n- CVE-2026-97537: scsi: qla2xxx: Fix queue teardown NULL dma_free and bitmap locking (bsc#1275737 bsc#1283453).\n- CVE-2026-97612: net: mpls: clear inner_protocol when the last label is popped (bsc#1283967).\n- CVE-2026-97926: ufs: validate cylinder group metadata before caching it (bsc#1283887).\n- CVE-2026-97954: net/rds: fix tcp stream corruption with large pages (bsc#1283113).\n- CVE-2026-97965: vxlan: initialize _md in vxlan_xmit_one() (bsc#1282963).\n- CVE-2026-98014: net/mlx5: E-Switch, prevent mc_list repopulation during vport disable (bsc#1283668).\n- CVE-2026-98022: net: cap tx_queue_len at S16_MAX to prevent oversized ring allocations (bsc#1283810).\n- CVE-2026-98071: net/rds: clear cp_flags bits individually in rds_conn_path_reset() (bsc#1283842).\n- CVE-2026-98072: net/rds: use wq_has_sleeper() in release_in_xmit() (bsc#1283846).\n- CVE-2026-98074: bonding: do not clear curr_active_slave prematurely when releasing all slaves (bsc#1283871).\n- CVE-2026-98078: ipvs: fix reversed sequence option serialization (bsc#1284150).\n- CVE-2026-98095: af_packet: Don't cast tpacket_hdr.tp_len to int in tpacket_parse_header() (bsc#1283921).\n- CVE-2026-98116: ALSA: pcm: Serialize PCM mmap with buffer reallocation to fix page UAF (bsc#1283878).\n- CVE-2026-98158: ppp_async: drop the errored frame instead of resetting its headroom (bsc#1283933).\n- CVE-2026-98257: rds: ib: use rds_conn_drop() on protocol version mismatch (bsc#1284346).\n- CVE-2026-98282: powerpc/iommu: Fix the overflow validation in iommu_tce_check_ioba (bsc#1284360).\n- CVE-2026-98386: scsi: qla2xxx: Use memset_io() to clear QLAFX00 request ring slot (bsc#1275737 bsc#1285668).\n- CVE-2026-98432: ipv4: free inet_opt and ireq_opt after an RCU grace period (bsc#1285685).\n\nThe following non security issues were fixed:\n\n- net/rds: use clear_bit_unlock() in release_refill() (git-fixes).\n- nvmet-tcp: do not continue for invalid icreq (git-fixes).\n- ocfs2: reserve xattr value tree metadata only once (git-fixes).\n- rds: add missing barrier to release_refill (git-fixes).\n- Revert 'mkspec: Exclude rt flavor from kernel-syms dependencies' (bsc#1244337).\n\t  - Revert 'rpm/mkspec: Fix missing kernel-syms-rt creation' (bsc#1244337).\n","status":"published","published":"2026-11-05T12:54:31Z","modified":"2026-11-06T12:30:03.505139994Z","updated_at":"2026-11-06T12:43:06.926783Z"},{"id":"USN-8278-1","title":"linux, linux-aws, linux-aws-fips, linux-gcp, linux-gcp-fips, linux-gke, linux-gkeop, linux-ibm, linux-ibm-6.8, linux-lowlatency, linux-lowlatency-hwe-6.8, linux-raspi, linux-raspi-realtime, linux-realtime, linux-realtime-6.8 vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-19T22:33:02Z","modified":"2026-11-05T19:04:28.160890429Z","updated_at":"2026-11-05T19:27:14.534654Z"},{"id":"USN-8278-2","title":"linux-azure vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-43033, CVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-26T19:00:47Z","modified":"2026-11-05T19:01:25.946958298Z","updated_at":"2026-11-05T19:27:36.688147Z"},{"id":"USN-8289-1","title":"linux-nvidia, linux-nvidia-lowlatency vulnerabilities","description":"\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23204, CVE-2026-23205, CVE-2026-23206,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23254, CVE-2026-23256, CVE-2026-23257,\nCVE-2026-23258, CVE-2026-23260, CVE-2026-23261, CVE-2026-23262,\nCVE-2026-23264, CVE-2026-23274, CVE-2026-23351, CVE-2026-23394,\nCVE-2026-31419, CVE-2026-31504, CVE-2026-31533, CVE-2026-43033,\nCVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-20T23:06:37Z","modified":"2026-11-05T19:03:53.913181128Z","updated_at":"2026-11-05T19:27:26.236035Z"},{"id":"USN-8289-2","title":"linux-nvidia-6.8 vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23204, CVE-2026-23205, CVE-2026-23206,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23254, CVE-2026-23256, CVE-2026-23257,\nCVE-2026-23258, CVE-2026-23260, CVE-2026-23261, CVE-2026-23262,\nCVE-2026-23264, CVE-2026-23274, CVE-2026-23351, CVE-2026-23394,\nCVE-2026-31419, CVE-2026-31504, CVE-2026-31533, CVE-2026-43033,\nCVE-2026-43077, CVE-2026-43078)\n","status":"published","published":"2026-05-25T17:48:27Z","modified":"2026-11-05T19:03:51.918692229Z","updated_at":"2026-11-05T19:27:26.236035Z"},{"id":"USN-8296-1","title":"linux-fips vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394)\n","status":"published","published":"2026-05-22T13:39:49Z","modified":"2026-11-04T20:02:47.669069853Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8296-2","title":"linux-nvidia-tegra vulnerabilities","description":"Several security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394)\n","status":"published","published":"2026-05-25T16:46:50Z","modified":"2026-11-04T20:02:40.473452713Z","updated_at":"2026-11-04T20:16:32.566315Z"},{"id":"USN-8393-1","title":"linux-azure-fips vulnerabilities","description":"\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - x86 architecture;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - Drivers core;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TCM subsystem;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - HFS+ file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NTFS3 file system;\n  - SMB network file system;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40039, CVE-2025-40082,\nCVE-2025-40149, CVE-2025-68351, CVE-2025-68358, CVE-2025-68365,\nCVE-2025-68725, CVE-2025-68749, CVE-2025-68803, CVE-2025-68823,\nCVE-2025-71160, CVE-2025-71162, CVE-2025-71163, CVE-2025-71180,\nCVE-2025-71182, CVE-2025-71183, CVE-2025-71184, CVE-2025-71185,\nCVE-2025-71186, CVE-2025-71188, CVE-2025-71189, CVE-2025-71190,\nCVE-2025-71191, CVE-2025-71192, CVE-2025-71193, CVE-2025-71194,\nCVE-2025-71195, CVE-2025-71196, CVE-2025-71197, CVE-2025-71198,\nCVE-2025-71199, CVE-2025-71200, CVE-2025-71220, CVE-2025-71222,\nCVE-2025-71224, CVE-2025-71225, CVE-2025-71268, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23105, CVE-2026-23107,\nCVE-2026-23108, CVE-2026-23110, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23200, CVE-2026-23202, CVE-2026-23204, CVE-2026-23205,\nCVE-2026-23206, CVE-2026-23212, CVE-2026-23213, CVE-2026-23214,\nCVE-2026-23215, CVE-2026-23216, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31676, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,\nCVE-2026-43494, CVE-2026-46028)\n","status":"published","published":"2026-06-04T22:10:25Z","modified":"2026-11-07T01:45:07.221179684Z","updated_at":"2026-11-07T01:57:16.198641Z"},{"id":"USN-8440-1","title":"linux-azure-6.8 vulnerabilities","description":"Josh Eads, Kristoffer Janke, Eduardo Vela Nava, Tavis Ormandy, and Matteo\nRizzo discovered that some AMD Zen processors did not properly verify the\nsignature of CPU microcode. This flaw is known as EntrySign. A privileged\nattacker could possibly use this issue to cause load malicious CPU\nmicrocode causing loss of integrity and confidentiality. (CVE-2024-36347)\n\nIt was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Compute Acceleration Framework;\n  - ACPI drivers;\n  - Drivers core;\n  - Network block device driver;\n  - Null block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Data acquisition framework and drivers;\n  - Counter interface drivers;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - Input Device core drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Macintosh device drivers;\n  - Multiple devices driver;\n  - Media drivers;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - STMicroelectronics network drivers;\n  - Ethernet team driver;\n  - MediaTek network drivers;\n  - NVME drivers;\n  - PA-RISC drivers;\n  - PHY drivers;\n  - Chrome hardware platform drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Voltage and Current Regulator drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - Media Oriented Systems Transport (MOST) driver;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - USB Host Controller drivers;\n  - USB Type-C Connector System Software Interface driver;\n  - Backlight driver;\n  - W1 Dallas's 1-wire bus driver;\n  - Watchdog drivers;\n  - Xen hypervisor drivers;\n  - BFS file system;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FUSE (File system in Userspace);\n  - HFS+ file system;\n  - File systems infrastructure;\n  - Journaling layer for block devices (JBD2);\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - File system notification infrastructure;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - SMB network file system;\n  - BPF subsystem;\n  - Ethernet bridge;\n  - Scheduler infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - Perf events;\n  - Locking primitives;\n  - Shadow Call Stack mechanism;\n  - Floating proportions library;\n  - Memory management;\n  - Bluetooth subsystem;\n  - CAIF protocol;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - Ethtool driver;\n  - Handshake API;\n  - HSR network protocol;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Open vSwitch;\n  - Packet sockets;\n  - RDS protocol;\n  - Rose network layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - Network sockets;\n  - Sun RPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - Integrity Measurement Architecture(IMA) framework;\n  - Key management;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - FireWire sound drivers;\n  - HD-audio driver;\n  - Turtle Beach Wavefront ALSA driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - STMicroelectronics SoC drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-57795, CVE-2024-58096, CVE-2024-58097,\nCVE-2025-22022, CVE-2025-22111, CVE-2025-37926, CVE-2025-38022,\nCVE-2025-38201, CVE-2025-38234, CVE-2025-38591, CVE-2025-40039,\nCVE-2025-40082, CVE-2025-40149, CVE-2025-40164, CVE-2025-40325,\nCVE-2025-68206, CVE-2025-68254, CVE-2025-68255, CVE-2025-68256,\nCVE-2025-68257, CVE-2025-68258, CVE-2025-68259, CVE-2025-68261,\nCVE-2025-68263, CVE-2025-68264, CVE-2025-68265, CVE-2025-68266,\nCVE-2025-68291, CVE-2025-68325, CVE-2025-68332, CVE-2025-68335,\nCVE-2025-68336, CVE-2025-68337, CVE-2025-68344, CVE-2025-68345,\nCVE-2025-68346, CVE-2025-68347, CVE-2025-68349, CVE-2025-68351,\nCVE-2025-68354, CVE-2025-68358, CVE-2025-68362, CVE-2025-68363,\nCVE-2025-68364, CVE-2025-68365, CVE-2025-68366, CVE-2025-68367,\nCVE-2025-68369, CVE-2025-68371, CVE-2025-68372, CVE-2025-68374,\nCVE-2025-68378, CVE-2025-68379, CVE-2025-68380, CVE-2025-68724,\nCVE-2025-68725, CVE-2025-68727, CVE-2025-68728, CVE-2025-68732,\nCVE-2025-68733, CVE-2025-68740, CVE-2025-68741, CVE-2025-68742,\nCVE-2025-68744, CVE-2025-68746, CVE-2025-68749, CVE-2025-68753,\nCVE-2025-68755, CVE-2025-68756, CVE-2025-68757, CVE-2025-68758,\nCVE-2025-68759, CVE-2025-68763, CVE-2025-68764, CVE-2025-68765,\nCVE-2025-68766, CVE-2025-68767, CVE-2025-68769, CVE-2025-68770,\nCVE-2025-68771, CVE-2025-68772, CVE-2025-68773, CVE-2025-68774,\nCVE-2025-68775, CVE-2025-68776, CVE-2025-68777, CVE-2025-68778,\nCVE-2025-68780, CVE-2025-68782, CVE-2025-68783, CVE-2025-68785,\nCVE-2025-68786, CVE-2025-68787, CVE-2025-68788, CVE-2025-68794,\nCVE-2025-68795, CVE-2025-68796, CVE-2025-68797, CVE-2025-68798,\nCVE-2025-68799, CVE-2025-68800, CVE-2025-68801, CVE-2025-68803,\nCVE-2025-68804, CVE-2025-68806, CVE-2025-68808, CVE-2025-68809,\nCVE-2025-68810, CVE-2025-68811, CVE-2025-68813, CVE-2025-68814,\nCVE-2025-68815, CVE-2025-68816, CVE-2025-68817, CVE-2025-68818,\nCVE-2025-68819, CVE-2025-68820, CVE-2025-68821, CVE-2025-68823,\nCVE-2025-71064, CVE-2025-71065, CVE-2025-71066, CVE-2025-71067,\nCVE-2025-71068, CVE-2025-71069, CVE-2025-71071, CVE-2025-71072,\nCVE-2025-71075, CVE-2025-71077, CVE-2025-71078, CVE-2025-71079,\nCVE-2025-71081, CVE-2025-71082, CVE-2025-71083, CVE-2025-71084,\nCVE-2025-71085, CVE-2025-71086, CVE-2025-71087, CVE-2025-71088,\nCVE-2025-71089, CVE-2025-71091, CVE-2025-71093, CVE-2025-71094,\nCVE-2025-71095, CVE-2025-71096, CVE-2025-71097, CVE-2025-71098,\nCVE-2025-71101, CVE-2025-71102, CVE-2025-71104, CVE-2025-71105,\nCVE-2025-71107, CVE-2025-71108, CVE-2025-71109, CVE-2025-71111,\nCVE-2025-71112, CVE-2025-71113, CVE-2025-71114, CVE-2025-71116,\nCVE-2025-71118, CVE-2025-71119, CVE-2025-71120, CVE-2025-71121,\nCVE-2025-71122, CVE-2025-71123, CVE-2025-71125, CVE-2025-71126,\nCVE-2025-71127, CVE-2025-71130, CVE-2025-71131, CVE-2025-71132,\nCVE-2025-71133, CVE-2025-71135, CVE-2025-71136, CVE-2025-71137,\nCVE-2025-71138, CVE-2025-71140, CVE-2025-71141, CVE-2025-71143,\nCVE-2025-71144, CVE-2025-71147, CVE-2025-71148, CVE-2025-71150,\nCVE-2025-71151, CVE-2025-71153, CVE-2025-71154, CVE-2025-71160,\nCVE-2025-71162, CVE-2025-71163, CVE-2025-71180, CVE-2025-71182,\nCVE-2025-71183, CVE-2025-71184, CVE-2025-71185, CVE-2025-71186,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71220, CVE-2025-71222, CVE-2025-71224,\nCVE-2025-71225, CVE-2025-71268, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22982,\nCVE-2026-22984, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22994, CVE-2026-22996, CVE-2026-22997, CVE-2026-22998,\nCVE-2026-22999, CVE-2026-23000, CVE-2026-23001, CVE-2026-23003,\nCVE-2026-23005, CVE-2026-23006, CVE-2026-23010, CVE-2026-23011,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23025,\nCVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032,\nCVE-2026-23033, CVE-2026-23035, CVE-2026-23037, CVE-2026-23038,\nCVE-2026-23047, CVE-2026-23049, CVE-2026-23050, CVE-2026-23053,\nCVE-2026-23054, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23068, CVE-2026-23069,\nCVE-2026-23071, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23078, CVE-2026-23080, CVE-2026-23083, CVE-2026-23084,\nCVE-2026-23085, CVE-2026-23086, CVE-2026-23087, CVE-2026-23088,\nCVE-2026-23089, CVE-2026-23090, CVE-2026-23091, CVE-2026-23093,\nCVE-2026-23094, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23105, CVE-2026-23107, CVE-2026-23108,\nCVE-2026-23110, CVE-2026-23112, CVE-2026-23113, CVE-2026-23116,\nCVE-2026-23119, CVE-2026-23120, CVE-2026-23121, CVE-2026-23123,\nCVE-2026-23124, CVE-2026-23125, CVE-2026-23126, CVE-2026-23128,\nCVE-2026-23129, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23139, CVE-2026-23140, CVE-2026-23141,\nCVE-2026-23142, CVE-2026-23144, CVE-2026-23145, CVE-2026-23146,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23156,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23163, CVE-2026-23164,\nCVE-2026-23166, CVE-2026-23167, CVE-2026-23168, CVE-2026-23170,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23176, CVE-2026-23178,\nCVE-2026-23179, CVE-2026-23180, CVE-2026-23182, CVE-2026-23187,\nCVE-2026-23190, CVE-2026-23191, CVE-2026-23193, CVE-2026-23198,\nCVE-2026-23204, CVE-2026-23205, CVE-2026-23206, CVE-2026-23209,\nCVE-2026-23212, CVE-2026-23213, CVE-2026-23214, CVE-2026-23215,\nCVE-2026-23216, CVE-2026-23231, CVE-2026-23254, CVE-2026-23256,\nCVE-2026-23257, CVE-2026-23258, CVE-2026-23260, CVE-2026-23261,\nCVE-2026-23262, CVE-2026-23264, CVE-2026-23274, CVE-2026-23351,\nCVE-2026-23394, CVE-2026-31419, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31676, CVE-2026-43033, CVE-2026-43077, CVE-2026-43078,\nCVE-2026-43362, CVE-2026-43494, CVE-2026-46028, CVE-2026-46323)\n","status":"published","published":"2026-06-16T22:30:05Z","modified":"2026-11-07T01:45:16.546246471Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8499-1","title":"linux-xilinx vulnerabilities","description":"It was discovered that the Linux kernel algif_aead module did not properly\nhandle in-place cryptographic operations. This flaw is known as Copy Fail.\nA local attacker could use this to escalate privileges, or possibly escape\na container. (CVE-2026-31431)\n\nIt was discovered that the Linux kernel did not properly handle shared page\nfragments during socket buffer operations, collectively known as Dirty\nFrag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the\nRxRPC networking subsystem when processing paged fragments. A local\nattacker could use this to escalate privileges, or possibly escape a\ncontainer. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000)\n\nIt was discovered that a logic flaw existed in the XFRM ESP-in-TCP\nsubsystem in the Linux kernel when handling socket buffer fragments. This\nflaw is known as Fragnesia. A local attacker could use this to escalate\nprivileges, or possibly escape a container. (CVE-2026-43503,\nCVE-2026-46300)\n\nQualys discovered that a race condition existed in the ptrace subsystem of\nthe Linux kernel when privileged processes are exiting. An unprivileged\nlocal attacker could use this issue to expose sensitive information.\n(CVE-2026-46333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a memory leak when handling AppArmor notifications. A local\nattacker could use this to cause resource exhaustion. (CVE-2026-47326)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontain a NULL pointer dereference when handling AppArmor notifications. A\nlocal attacker could use this to cause a kernel oops. (CVE-2026-47327)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an invalid free when handling AppArmor notifications. A local\nattacker could use this to corrupt kernel memory. (CVE-2026-47328)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained insufficient validation of AppArmor notification responses. A\nlocal attacker could use this to allow crafted responses to be processed.\n(CVE-2026-47329)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used\nan uninitialized variable when handling AppArmor notifications. A local\nattacker could use this to cause incorrect caching of data.\n(CVE-2026-47330)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a use-\nafter-free (UAF) bug. A local attacker could use this to cause memory\ncorruption and, theoretically, arbitrary code execution. (CVE-2026-47331)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained an out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause information disclosure of kernel\nmemory. (CVE-2026-47332)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained a out-of-bounds (OOB) read when handling AppArmor notifications.\nA local attacker could use this to cause kernel memory corruption and,\ntheoretically, influence processing of AppArmor policies. (CVE-2026-47333)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0\ncontained incorrect holding of locks when handling AppArmor notifications.\nA local attacker could use this to cause a kernel panic or deadlock.\n(CVE-2026-47334)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 contained a NULL\npointer dereference when handling AppArmor notifications. A local attacker\ncould use this to cause a kernel panic. (CVE-2026-47335)\n\nTristan Madani discovered that Ubuntu Linux kernel 6.8 used an\nuninitialized variable when handling AppArmor AF_INET/AF_INET6 socket\nmediation. A local attacker could use this to influence processing of fine-\ngrained network socket mediation. (CVE-2026-47336)\n\nTristan Madani and Trevor Lawrence have each independently discovered that\nUbuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference\nwhen handling AppArmor network socket mediation. A local attacker could use\nthis to cause a kernel oops. (CVE-2026-47337)\n\nSeveral security issues were discovered in the Linux kernel.\nAn attacker could possibly use these to compromise the system.\nThis update corrects flaws in the following subsystems:\n  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - MIPS architecture;\n  - PowerPC architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Intel NPU Driver;\n  - ACPI drivers;\n  - ATM drivers;\n  - Drivers core;\n  - Null block device driver;\n  - RNBD block device driver;\n  - Ublk userspace block driver;\n  - Bluetooth drivers;\n  - Bus devices;\n  - Character device driver;\n  - TPM device driver;\n  - Clock framework and drivers;\n  - Clocksource drivers;\n  - Counter interface drivers;\n  - CPU idle management framework;\n  - Hardware crypto device drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - EFI core;\n  - GPIO subsystem;\n  - GPU drivers;\n  - HID subsystem;\n  - Hardware monitoring drivers;\n  - Intel Trace Hub HW tracing drivers;\n  - IIO subsystem;\n  - IIO ADC drivers;\n  - InfiniBand drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - Multifunction device drivers;\n  - Broadcom VK accelerator driver;\n  - UACCE accelerator framework;\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  - NTB driver;\n  - NVME drivers;\n  - PCI subsystem;\n  - Performance monitor drivers;\n  - PHY drivers;\n  - Pin controllers subsystem;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - Power supply drivers;\n  - RapidIO drivers;\n  - RAS (Reliability, Availability, Serviceability) subsystem;\n  - Remote Processor subsystem;\n  - RPMSG subsystem;\n  - S/390 drivers;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - MediaTek SoC drivers;\n  - Texas Instruments SoC drivers;\n  - SPI subsystem;\n  - Greybus lights staging drivers;\n  - Realtek RTL8723BS SDIO drivers;\n  - TCM subsystem;\n  - UFS subsystem;\n  - ChipIdea USB driver;\n  - DesignWare USB3 driver;\n  - USB over IP driver;\n  - vDPA drivers;\n  - Virtio Host (VHOST) subsystem;\n  - Framebuffer layer;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - Ceph distributed file system;\n  - EFI Variable file system;\n  - exFAT file system;\n  - Ext4 file system;\n  - F2FS file system;\n  - FAT file system;\n  - GFS2 file system;\n  - HFS+ file system;\n  - JFS file system;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - NILFS2 file system;\n  - NTFS3 file system;\n  - OCFS2 file system;\n  - Proc file system;\n  - Pstore file system;\n  - Diskquota system;\n  - SMB network file system;\n  - XFS file system;\n  - Audit subsystem;\n  - Memory Management;\n  - Scheduler infrastructure;\n  - IPv6 networking;\n  - Netfilter;\n  - NFC subsystem;\n  - Tracing infrastructure;\n  - io_uring subsystem;\n  - BPF subsystem;\n  - Perf events;\n  - Kernel kexec() syscall;\n  - RCU subsystem;\n  - Floating proportions library;\n  - Scatterlist API;\n  - Memory management;\n  - 9P file system network protocol;\n  - Asynchronous Transfer Mode (ATM) subsystem;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - KCM (Kernel Connection Multiplexor) sockets driver;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - Packet sockets;\n  - RDS protocol;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - Sun RPC protocol;\n  - TLS protocol;\n  - Unix domain sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - XFRM subsystem;\n  - AppArmor security module;\n  - Simplified Mandatory Access Control Kernel framework;\n  - ALSA AC97 driver;\n  - Generic PCM loopback sound driver;\n  - Creative Sound Blaster X-Fi driver;\n  - AMD SoC Alsa drivers;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - SOF drivers;\n  - USB sound devices;\n  - KVM subsystem;\n(CVE-2024-50004, CVE-2024-58096, CVE-2024-58097, CVE-2025-37926,\nCVE-2025-38201, CVE-2025-38591, CVE-2025-40005, CVE-2025-40039,\nCVE-2025-40082, CVE-2025-40149, CVE-2025-68351, CVE-2025-68358,\nCVE-2025-68365, CVE-2025-68725, CVE-2025-68749, CVE-2025-68803,\nCVE-2025-68823, CVE-2025-71160, CVE-2025-71162, CVE-2025-71163,\nCVE-2025-71180, CVE-2025-71182, CVE-2025-71183, CVE-2025-71184,\nCVE-2025-71185, CVE-2025-71186, CVE-2025-71188, CVE-2025-71189,\nCVE-2025-71190, CVE-2025-71191, CVE-2025-71192, CVE-2025-71193,\nCVE-2025-71194, CVE-2025-71195, CVE-2025-71196, CVE-2025-71197,\nCVE-2025-71198, CVE-2025-71199, CVE-2025-71200, CVE-2025-71220,\nCVE-2025-71222, CVE-2025-71224, CVE-2025-71225, CVE-2025-71229,\nCVE-2025-71231, CVE-2025-71232, CVE-2025-71233, CVE-2025-71235,\nCVE-2025-71236, CVE-2025-71237, CVE-2025-71238, CVE-2025-71239,\nCVE-2025-71265, CVE-2025-71266, CVE-2025-71267, CVE-2025-71268,\nCVE-2025-71272, CVE-2025-71273, CVE-2025-71274, CVE-2025-71286,\nCVE-2025-71291, CVE-2025-71292, CVE-2025-71294, CVE-2025-71295,\nCVE-2025-71297, CVE-2025-71304, CVE-2025-71305, CVE-2026-22976,\nCVE-2026-22977, CVE-2026-22978, CVE-2026-22979, CVE-2026-22980,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23003, CVE-2026-23005, CVE-2026-23006, CVE-2026-23010,\nCVE-2026-23011, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23025, CVE-2026-23026, CVE-2026-23030, CVE-2026-23031,\nCVE-2026-23032, CVE-2026-23033, CVE-2026-23035, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23053, CVE-2026-23054, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23068,\nCVE-2026-23069, CVE-2026-23071, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23078, CVE-2026-23080, CVE-2026-23083,\nCVE-2026-23084, CVE-2026-23085, CVE-2026-23086, CVE-2026-23087,\nCVE-2026-23088, CVE-2026-23089, CVE-2026-23090, CVE-2026-23091,\nCVE-2026-23093, CVE-2026-23094, CVE-2026-23095, CVE-2026-23096,\nCVE-2026-23097, CVE-2026-23098, CVE-2026-23099, CVE-2026-23100,\nCVE-2026-23101, CVE-2026-23102, CVE-2026-23103, CVE-2026-23105,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23110, CVE-2026-23113,\nCVE-2026-23116, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23123, CVE-2026-23124, CVE-2026-23125, CVE-2026-23126,\nCVE-2026-23128, CVE-2026-23129, CVE-2026-23131, CVE-2026-23133,\nCVE-2026-23135, CVE-2026-23136, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23144, CVE-2026-23145,\nCVE-2026-23146, CVE-2026-23148, CVE-2026-23150, CVE-2026-23151,\nCVE-2026-23156, CVE-2026-23159, CVE-2026-23160, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23166, CVE-2026-23167, CVE-2026-23168,\nCVE-2026-23169, CVE-2026-23170, CVE-2026-23172, CVE-2026-23173,\nCVE-2026-23176, CVE-2026-23178, CVE-2026-23179, CVE-2026-23180,\nCVE-2026-23182, CVE-2026-23187, CVE-2026-23190, CVE-2026-23191,\nCVE-2026-23193, CVE-2026-23198, CVE-2026-23200, CVE-2026-23202,\nCVE-2026-23204, CVE-2026-23205, CVE-2026-23206, CVE-2026-23212,\nCVE-2026-23213, CVE-2026-23214, CVE-2026-23215, CVE-2026-23216,\nCVE-2026-23220, CVE-2026-23221, CVE-2026-23222, CVE-2026-23228,\nCVE-2026-23229, CVE-2026-23230, CVE-2026-23233, CVE-2026-23234,\nCVE-2026-23235, CVE-2026-23236, CVE-2026-23237, CVE-2026-23238,\nCVE-2026-23241, CVE-2026-23242, CVE-2026-23243, CVE-2026-23249,\nCVE-2026-23254, CVE-2026-23256, CVE-2026-23257, CVE-2026-23258,\nCVE-2026-23260, CVE-2026-23261, CVE-2026-23262, CVE-2026-23264,\nCVE-2026-23266, CVE-2026-23267, CVE-2026-23272, CVE-2026-23274,\nCVE-2026-23278, CVE-2026-23351, CVE-2026-23392, CVE-2026-23394,\nCVE-2026-23428, CVE-2026-23450, CVE-2026-23455, CVE-2026-31402,\nCVE-2026-31411, CVE-2026-31418, CVE-2026-31419, CVE-2026-31436,\nCVE-2026-31448, CVE-2026-31478, CVE-2026-31504, CVE-2026-31533,\nCVE-2026-31607, CVE-2026-31637, CVE-2026-31649, CVE-2026-31657,\nCVE-2026-31659, CVE-2026-31668, CVE-2026-31669, CVE-2026-31676,\nCVE-2026-31682, CVE-2026-31685, CVE-2026-31687, CVE-2026-31693,\nCVE-2026-43011, CVE-2026-43033, CVE-2026-43037, CVE-2026-43038,\nCVE-2026-43071, CVE-2026-43077, CVE-2026-43078, CVE-2026-43114,\nCVE-2026-43117, CVE-2026-43123, CVE-2026-43124, CVE-2026-43128,\nCVE-2026-43130, CVE-2026-43132, CVE-2026-43133, CVE-2026-43134,\nCVE-2026-43135, CVE-2026-43136, CVE-2026-43137, CVE-2026-43139,\nCVE-2026-43140, CVE-2026-43141, CVE-2026-43143, CVE-2026-43145,\nCVE-2026-43147, CVE-2026-43148, CVE-2026-43149, CVE-2026-43150,\nCVE-2026-43152, CVE-2026-43153, CVE-2026-43156, CVE-2026-43157,\nCVE-2026-43158, CVE-2026-43159, CVE-2026-43163, CVE-2026-43167,\nCVE-2026-43168, CVE-2026-43169, CVE-2026-43170, CVE-2026-43171,\nCVE-2026-43173, CVE-2026-43175, CVE-2026-43180, CVE-2026-43182,\nCVE-2026-43183, CVE-2026-43184, CVE-2026-43186, CVE-2026-43187,\nCVE-2026-43189, CVE-2026-43190, CVE-2026-43194, CVE-2026-43196,\nCVE-2026-43199, CVE-2026-43200, CVE-2026-43201, CVE-2026-43202,\nCVE-2026-43203, CVE-2026-43205, CVE-2026-43206, CVE-2026-43207,\nCVE-2026-43209, CVE-2026-43211, CVE-2026-43212, CVE-2026-43214,\nCVE-2026-43215, CVE-2026-43218, CVE-2026-43221, CVE-2026-43222,\nCVE-2026-43223, CVE-2026-43225, CVE-2026-43226, CVE-2026-43227,\nCVE-2026-43230, CVE-2026-43231, CVE-2026-43232, CVE-2026-43233,\nCVE-2026-43236, CVE-2026-43238, CVE-2026-43239, CVE-2026-43241,\nCVE-2026-43242, CVE-2026-43244, CVE-2026-43246, CVE-2026-43248,\nCVE-2026-43249, CVE-2026-43250, CVE-2026-43251, CVE-2026-43253,\nCVE-2026-43255, CVE-2026-43256, CVE-2026-43257, CVE-2026-43258,\nCVE-2026-43261, CVE-2026-43262, CVE-2026-43264, CVE-2026-43266,\nCVE-2026-43268, CVE-2026-43269, CVE-2026-43270, CVE-2026-43271,\nCVE-2026-43273, CVE-2026-43275, CVE-2026-43277, CVE-2026-43278,\nCVE-2026-43279, CVE-2026-43283, CVE-2026-43287, CVE-2026-43288,\nCVE-2026-43289, CVE-2026-43291, CVE-2026-43295, CVE-2026-43296,\nCVE-2026-43297, CVE-2026-43300, CVE-2026-43302, CVE-2026-43304,\nCVE-2026-43312, CVE-2026-43313, CVE-2026-43314, CVE-2026-43315,\nCVE-2026-43316, CVE-2026-43317, CVE-2026-43318, CVE-2026-43319,\nCVE-2026-43320, CVE-2026-43341, CVE-2026-43378, CVE-2026-43383,\nCVE-2026-43384, CVE-2026-43406, CVE-2026-43407, CVE-2026-43414,\nCVE-2026-43493, CVE-2026-43494, CVE-2026-43501, CVE-2026-45847,\nCVE-2026-45848, CVE-2026-45849, CVE-2026-45851, CVE-2026-45852,\nCVE-2026-45856, CVE-2026-45857, CVE-2026-45859, CVE-2026-45860,\nCVE-2026-45861, CVE-2026-45862, CVE-2026-45864, CVE-2026-45865,\nCVE-2026-45866, CVE-2026-45867, CVE-2026-45868, CVE-2026-45869,\nCVE-2026-45870, CVE-2026-45871, CVE-2026-45872, CVE-2026-45873,\nCVE-2026-45875, CVE-2026-45877, CVE-2026-45878, CVE-2026-45879,\nCVE-2026-45880, CVE-2026-45881, CVE-2026-45882, CVE-2026-45883,\nCVE-2026-45884, CVE-2026-45885, CVE-2026-45886, CVE-2026-45890,\nCVE-2026-45891, CVE-2026-45893, CVE-2026-45895, CVE-2026-45902,\nCVE-2026-45904, CVE-2026-45905, CVE-2026-45910, CVE-2026-45912,\nCVE-2026-45913, CVE-2026-45914, CVE-2026-45915, CVE-2026-45916,\nCVE-2026-45917, CVE-2026-45919, CVE-2026-45921, CVE-2026-45923,\nCVE-2026-45928, CVE-2026-45935, CVE-2026-45936, CVE-2026-45938,\nCVE-2026-45941, CVE-2026-45946, CVE-2026-45947, CVE-2026-45948,\nCVE-2026-45954, CVE-2026-45957, CVE-2026-45960, CVE-2026-45962,\nCVE-2026-45964, CVE-2026-45965, CVE-2026-45968, CVE-2026-45969,\nCVE-2026-45970, CVE-2026-45973, CVE-2026-45974, CVE-2026-45976,\nCVE-2026-45978, CVE-2026-45981, CVE-2026-45982, CVE-2026-45983,\nCVE-2026-45984, CVE-2026-45988, CVE-2026-46028, CVE-2026-46043,\nCVE-2026-46115, CVE-2026-46119, CVE-2026-46135, CVE-2026-46185,\nCVE-2026-46195, CVE-2026-46243, CVE-2026-46244, CVE-2026-46246,\nCVE-2026-46247, CVE-2026-46249, CVE-2026-46250, CVE-2026-46251,\nCVE-2026-46253, CVE-2026-46254, CVE-2026-46255, CVE-2026-46259,\nCVE-2026-46261, CVE-2026-46265, CVE-2026-46266, CVE-2026-46267,\nCVE-2026-46270, CVE-2026-46289, CVE-2026-46323, CVE-2026-46328)\n","status":"published","published":"2026-07-02T15:56:51Z","modified":"2026-11-07T01:45:08.338519599Z","updated_at":"2026-11-07T01:57:16.198641Z"},{"id":"USN-8570-1","title":"linux-gcp-6.17, linux-realtime-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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - File systems infrastructure;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987,\nCVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005,\nCVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009,\nCVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013,\nCVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022,\nCVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026,\nCVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033,\nCVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045,\nCVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054,\nCVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067,\nCVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071,\nCVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23077, CVE-2026-23078, CVE-2026-23079, CVE-2026-23080,\nCVE-2026-23081, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23086, CVE-2026-23087, CVE-2026-23088, CVE-2026-23089,\nCVE-2026-23090, CVE-2026-23092, CVE-2026-23093, CVE-2026-23094,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23100, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23104, CVE-2026-23105, CVE-2026-23106,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23109, CVE-2026-23110,\nCVE-2026-23113, CVE-2026-23114, CVE-2026-23115, CVE-2026-23116,\nCVE-2026-23118, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23122, CVE-2026-23123, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23126, CVE-2026-23128, CVE-2026-23129, CVE-2026-23130,\nCVE-2026-23131, CVE-2026-23133, CVE-2026-23135, CVE-2026-23136,\nCVE-2026-23137, CVE-2026-23138, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23143, CVE-2026-23144,\nCVE-2026-23145, CVE-2026-23146, CVE-2026-23147, CVE-2026-23148,\nCVE-2026-23150, CVE-2026-23151, CVE-2026-23152, CVE-2026-23154,\nCVE-2026-23156, CVE-2026-23157, CVE-2026-23158, CVE-2026-23159,\nCVE-2026-23160, CVE-2026-23161, CVE-2026-23162, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23165, CVE-2026-23166, CVE-2026-23167,\nCVE-2026-23168, CVE-2026-23169, CVE-2026-23170, CVE-2026-23171,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23212, CVE-2026-31444,\nCVE-2026-46290, CVE-2026-46317, CVE-2026-53277)\n","status":"published","published":"2026-07-20T15:55:42Z","modified":"2026-11-06T13:48:59.725228621Z","updated_at":"2026-11-06T14:26:45.553207Z"},{"id":"USN-8570-2","title":"linux-oracle-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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - File systems infrastructure;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987,\nCVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005,\nCVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009,\nCVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013,\nCVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022,\nCVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026,\nCVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033,\nCVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045,\nCVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054,\nCVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067,\nCVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071,\nCVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23077, CVE-2026-23078, CVE-2026-23079, CVE-2026-23080,\nCVE-2026-23081, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23086, CVE-2026-23087, CVE-2026-23088, CVE-2026-23089,\nCVE-2026-23090, CVE-2026-23092, CVE-2026-23093, CVE-2026-23094,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23100, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23104, CVE-2026-23105, CVE-2026-23106,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23109, CVE-2026-23110,\nCVE-2026-23113, CVE-2026-23114, CVE-2026-23115, CVE-2026-23116,\nCVE-2026-23118, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23122, CVE-2026-23123, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23126, CVE-2026-23128, CVE-2026-23129, CVE-2026-23130,\nCVE-2026-23131, CVE-2026-23133, CVE-2026-23135, CVE-2026-23136,\nCVE-2026-23137, CVE-2026-23138, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23143, CVE-2026-23144,\nCVE-2026-23145, CVE-2026-23146, CVE-2026-23147, CVE-2026-23148,\nCVE-2026-23150, CVE-2026-23151, CVE-2026-23152, CVE-2026-23154,\nCVE-2026-23156, CVE-2026-23157, CVE-2026-23158, CVE-2026-23159,\nCVE-2026-23160, CVE-2026-23161, CVE-2026-23162, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23165, CVE-2026-23166, CVE-2026-23167,\nCVE-2026-23168, CVE-2026-23169, CVE-2026-23170, CVE-2026-23171,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23212, CVE-2026-31444,\nCVE-2026-46290, CVE-2026-46317, CVE-2026-53277)\n","status":"published","published":"2026-07-28T07:19:37Z","modified":"2026-11-06T13:48:59.380704637Z","updated_at":"2026-11-06T14:26:45.553207Z"},{"id":"USN-8594-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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - File systems infrastructure;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987,\nCVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005,\nCVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009,\nCVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013,\nCVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022,\nCVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026,\nCVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033,\nCVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045,\nCVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054,\nCVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067,\nCVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071,\nCVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23077, CVE-2026-23078, CVE-2026-23079, CVE-2026-23080,\nCVE-2026-23081, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23086, CVE-2026-23087, CVE-2026-23088, CVE-2026-23089,\nCVE-2026-23090, CVE-2026-23092, CVE-2026-23093, CVE-2026-23094,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23100, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23104, CVE-2026-23105, CVE-2026-23106,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23109, CVE-2026-23110,\nCVE-2026-23113, CVE-2026-23114, CVE-2026-23115, CVE-2026-23116,\nCVE-2026-23118, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23122, CVE-2026-23123, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23126, CVE-2026-23128, CVE-2026-23129, CVE-2026-23130,\nCVE-2026-23131, CVE-2026-23133, CVE-2026-23135, CVE-2026-23136,\nCVE-2026-23137, CVE-2026-23138, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23143, CVE-2026-23144,\nCVE-2026-23145, CVE-2026-23146, CVE-2026-23147, CVE-2026-23148,\nCVE-2026-23150, CVE-2026-23151, CVE-2026-23152, CVE-2026-23154,\nCVE-2026-23156, CVE-2026-23157, CVE-2026-23158, CVE-2026-23159,\nCVE-2026-23160, CVE-2026-23161, CVE-2026-23162, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23165, CVE-2026-23166, CVE-2026-23167,\nCVE-2026-23168, CVE-2026-23169, CVE-2026-23170, CVE-2026-23171,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23212, CVE-2026-31444,\nCVE-2026-43318, CVE-2026-46317, CVE-2026-53277)\n","status":"published","published":"2026-07-23T07:42:15Z","modified":"2026-11-06T13:48:41.115427249Z","updated_at":"2026-11-06T14:26:45.553207Z"},{"id":"USN-8604-1","title":"linux-azure-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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - USB over IP driver;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Kernel thread helper (kthread);\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - IPv6 networking;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Scatterlist API;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22985, CVE-2026-22986,\nCVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996,\nCVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000,\nCVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004,\nCVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008,\nCVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012,\nCVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017,\nCVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025,\nCVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032,\nCVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036,\nCVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044,\nCVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049,\nCVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053,\nCVE-2026-23054, CVE-2026-23055, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23066,\nCVE-2026-23067, CVE-2026-23068, CVE-2026-23069, CVE-2026-23070,\nCVE-2026-23071, CVE-2026-23072, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23077, CVE-2026-23078, CVE-2026-23079,\nCVE-2026-23080, CVE-2026-23081, CVE-2026-23083, CVE-2026-23084,\nCVE-2026-23085, CVE-2026-23086, CVE-2026-23087, CVE-2026-23088,\nCVE-2026-23089, CVE-2026-23090, CVE-2026-23092, CVE-2026-23093,\nCVE-2026-23094, CVE-2026-23095, CVE-2026-23096, CVE-2026-23097,\nCVE-2026-23098, CVE-2026-23099, CVE-2026-23100, CVE-2026-23101,\nCVE-2026-23102, CVE-2026-23103, CVE-2026-23104, CVE-2026-23105,\nCVE-2026-23106, CVE-2026-23107, CVE-2026-23108, CVE-2026-23109,\nCVE-2026-23110, CVE-2026-23113, CVE-2026-23114, CVE-2026-23115,\nCVE-2026-23116, CVE-2026-23118, CVE-2026-23119, CVE-2026-23120,\nCVE-2026-23121, CVE-2026-23122, CVE-2026-23123, CVE-2026-23124,\nCVE-2026-23125, CVE-2026-23126, CVE-2026-23128, CVE-2026-23129,\nCVE-2026-23130, CVE-2026-23131, CVE-2026-23133, CVE-2026-23135,\nCVE-2026-23136, CVE-2026-23137, CVE-2026-23138, CVE-2026-23139,\nCVE-2026-23140, CVE-2026-23141, CVE-2026-23142, CVE-2026-23143,\nCVE-2026-23144, CVE-2026-23145, CVE-2026-23146, CVE-2026-23147,\nCVE-2026-23148, CVE-2026-23150, CVE-2026-23151, CVE-2026-23152,\nCVE-2026-23154, CVE-2026-23156, CVE-2026-23157, CVE-2026-23158,\nCVE-2026-23159, CVE-2026-23160, CVE-2026-23161, CVE-2026-23162,\nCVE-2026-23163, CVE-2026-23164, CVE-2026-23165, CVE-2026-23166,\nCVE-2026-23167, CVE-2026-23168, CVE-2026-23169, CVE-2026-23170,\nCVE-2026-23171, CVE-2026-23172, CVE-2026-23173, CVE-2026-23212,\nCVE-2026-23272, CVE-2026-23278, CVE-2026-23392, CVE-2026-23427,\nCVE-2026-23428, CVE-2026-23450, CVE-2026-23455, CVE-2026-31402,\nCVE-2026-31418, CVE-2026-31436, CVE-2026-31448, CVE-2026-31478,\nCVE-2026-31607, CVE-2026-31635, CVE-2026-31637, CVE-2026-31649,\nCVE-2026-31657, CVE-2026-31659, CVE-2026-31668, CVE-2026-31669,\nCVE-2026-31682, CVE-2026-31685, CVE-2026-31718, CVE-2026-43011,\nCVE-2026-43037, CVE-2026-43038, CVE-2026-43071, CVE-2026-43083,\nCVE-2026-43114, CVE-2026-43117, CVE-2026-43125, CVE-2026-43185,\nCVE-2026-43186, CVE-2026-43197, CVE-2026-43304, CVE-2026-43341,\nCVE-2026-43376, CVE-2026-43378, CVE-2026-43383, CVE-2026-43384,\nCVE-2026-43402, CVE-2026-43406, CVE-2026-43407, CVE-2026-43414,\nCVE-2026-43493, CVE-2026-43501, CVE-2026-45898, CVE-2026-45988,\nCVE-2026-46039, CVE-2026-46043, CVE-2026-46084, CVE-2026-46115,\nCVE-2026-46119, CVE-2026-46135, CVE-2026-46185, CVE-2026-46195,\nCVE-2026-46243, CVE-2026-46244, CVE-2026-46266, CVE-2026-46289,\nCVE-2026-46290, CVE-2026-46316, CVE-2026-46317, CVE-2026-46325,\nCVE-2026-53277, CVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:07:12Z","modified":"2026-11-07T01:45:21.579104128Z","updated_at":"2026-11-07T01:57:06.567161Z"},{"id":"USN-8605-1","title":"linux-azure-fde-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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Cryptographic API;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Microsoft Azure Network Adapter (MANA) driver;\n  - STMicroelectronics network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - USB over IP driver;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - File systems infrastructure;\n  - EFI Variable file system;\n  - Ext4 file system;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Kernel thread helper (kthread);\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - IPv6 networking;\n  - Netfilter;\n  - NFC subsystem;\n  - io_uring subsystem;\n  - Perf events;\n  - Kernel exit() syscall;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Scatterlist API;\n  - B.A.T.M.A.N. meshing protocol;\n  - Bluetooth subsystem;\n  - Ethernet bridge;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv4 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - Network traffic control;\n  - SCTP protocol;\n  - SMC sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - X.25 network layer;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22984, CVE-2026-22985, CVE-2026-22986,\nCVE-2026-22987, CVE-2026-22989, CVE-2026-22990, CVE-2026-22991,\nCVE-2026-22992, CVE-2026-22993, CVE-2026-22994, CVE-2026-22996,\nCVE-2026-22997, CVE-2026-22998, CVE-2026-22999, CVE-2026-23000,\nCVE-2026-23001, CVE-2026-23002, CVE-2026-23003, CVE-2026-23004,\nCVE-2026-23005, CVE-2026-23006, CVE-2026-23007, CVE-2026-23008,\nCVE-2026-23009, CVE-2026-23010, CVE-2026-23011, CVE-2026-23012,\nCVE-2026-23013, CVE-2026-23014, CVE-2026-23015, CVE-2026-23017,\nCVE-2026-23018, CVE-2026-23019, CVE-2026-23020, CVE-2026-23021,\nCVE-2026-23022, CVE-2026-23023, CVE-2026-23024, CVE-2026-23025,\nCVE-2026-23026, CVE-2026-23030, CVE-2026-23031, CVE-2026-23032,\nCVE-2026-23033, CVE-2026-23034, CVE-2026-23035, CVE-2026-23036,\nCVE-2026-23037, CVE-2026-23038, CVE-2026-23042, CVE-2026-23044,\nCVE-2026-23045, CVE-2026-23046, CVE-2026-23047, CVE-2026-23049,\nCVE-2026-23050, CVE-2026-23051, CVE-2026-23052, CVE-2026-23053,\nCVE-2026-23054, CVE-2026-23055, CVE-2026-23056, CVE-2026-23057,\nCVE-2026-23058, CVE-2026-23059, CVE-2026-23061, CVE-2026-23062,\nCVE-2026-23063, CVE-2026-23064, CVE-2026-23065, CVE-2026-23066,\nCVE-2026-23067, CVE-2026-23068, CVE-2026-23069, CVE-2026-23070,\nCVE-2026-23071, CVE-2026-23072, CVE-2026-23073, CVE-2026-23075,\nCVE-2026-23076, CVE-2026-23077, CVE-2026-23078, CVE-2026-23080,\nCVE-2026-23081, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23086, CVE-2026-23087, CVE-2026-23088, CVE-2026-23089,\nCVE-2026-23090, CVE-2026-23092, CVE-2026-23093, CVE-2026-23094,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23100, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23104, CVE-2026-23105, CVE-2026-23106,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23109, CVE-2026-23110,\nCVE-2026-23113, CVE-2026-23114, CVE-2026-23115, CVE-2026-23116,\nCVE-2026-23118, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23122, CVE-2026-23123, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23126, CVE-2026-23128, CVE-2026-23129, CVE-2026-23130,\nCVE-2026-23131, CVE-2026-23133, CVE-2026-23135, CVE-2026-23136,\nCVE-2026-23137, CVE-2026-23138, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23143, CVE-2026-23144,\nCVE-2026-23145, CVE-2026-23146, CVE-2026-23147, CVE-2026-23148,\nCVE-2026-23150, CVE-2026-23151, CVE-2026-23152, CVE-2026-23154,\nCVE-2026-23156, CVE-2026-23157, CVE-2026-23158, CVE-2026-23159,\nCVE-2026-23160, CVE-2026-23161, CVE-2026-23162, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23165, CVE-2026-23166, CVE-2026-23167,\nCVE-2026-23168, CVE-2026-23169, CVE-2026-23170, CVE-2026-23171,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23212, CVE-2026-23272,\nCVE-2026-23278, CVE-2026-23392, CVE-2026-23427, CVE-2026-23428,\nCVE-2026-23450, CVE-2026-23455, CVE-2026-31402, CVE-2026-31418,\nCVE-2026-31436, CVE-2026-31448, CVE-2026-31478, CVE-2026-31607,\nCVE-2026-31635, CVE-2026-31637, CVE-2026-31649, CVE-2026-31657,\nCVE-2026-31659, CVE-2026-31668, CVE-2026-31669, CVE-2026-31682,\nCVE-2026-31685, CVE-2026-31718, CVE-2026-43011, CVE-2026-43037,\nCVE-2026-43038, CVE-2026-43071, CVE-2026-43083, CVE-2026-43114,\nCVE-2026-43117, CVE-2026-43125, CVE-2026-43185, CVE-2026-43186,\nCVE-2026-43197, CVE-2026-43304, CVE-2026-43341, CVE-2026-43376,\nCVE-2026-43378, CVE-2026-43383, CVE-2026-43384, CVE-2026-43402,\nCVE-2026-43406, CVE-2026-43407, CVE-2026-43414, CVE-2026-43493,\nCVE-2026-43501, CVE-2026-45898, CVE-2026-45988, CVE-2026-46039,\nCVE-2026-46043, CVE-2026-46084, CVE-2026-46115, CVE-2026-46119,\nCVE-2026-46135, CVE-2026-46185, CVE-2026-46195, CVE-2026-46243,\nCVE-2026-46244, CVE-2026-46266, CVE-2026-46289, CVE-2026-46290,\nCVE-2026-46316, CVE-2026-46317, CVE-2026-46325, CVE-2026-53277,\nCVE-2026-64018, CVE-2026-64034)\n","status":"published","published":"2026-07-24T10:11:06Z","modified":"2026-10-17T12:55:29.574386436Z","updated_at":"2026-11-02T16:58:25.103481Z"},{"id":"USN-8669-1","title":"linux-nvidia-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  - Foo-over-UDP (FOU);\n  - ARM64 architecture;\n  - x86 architecture;\n  - Block layer subsystem;\n  - Drivers core;\n  - Null block device driver;\n  - Bluetooth drivers;\n  - Counter interface drivers;\n  - DMA engine subsystem;\n  - DPLL subsystem;\n  - GPIO subsystem;\n  - GPU drivers;\n  - I2C subsystem;\n  - IIO ADC drivers;\n  - IIO subsystem;\n  - InfiniBand drivers;\n  - On-Chip Interconnect management framework;\n  - IOMMU subsystem;\n  - IRQ chip drivers;\n  - Modular ISDN driver;\n  - LED subsystem;\n  - Multiple devices driver;\n  - Media drivers;\n  - UACCE accelerator framework;\n  - MMC subsystem;\n  - Ethernet bonding driver;\n  - Network drivers;\n  - Mellanox network drivers;\n  - Texas Instruments network drivers;\n  - NVME drivers;\n  - Device tree and open firmware driver;\n  - PHY drivers;\n  - x86 platform drivers;\n  - i.MX PM domains;\n  - SCSI subsystem;\n  - SLIMbus drivers;\n  - SPI subsystem;\n  - TTY drivers;\n  - USB Host Controller drivers;\n  - W1 Dallas's 1-wire bus driver;\n  - Xen hypervisor drivers;\n  - BTRFS file system;\n  - EFI Variable file system;\n  - File systems infrastructure;\n  - Ext4 file system;\n  - FUSE (File system in Userspace);\n  - Network file systems library;\n  - Network file system (NFS) client;\n  - Network file system (NFS) server daemon;\n  - SMB network file system;\n  - Memory Management;\n  - Memory management;\n  - Scheduler infrastructure;\n  - Tracing infrastructure;\n  - IPv4 networking;\n  - Netfilter;\n  - NFC subsystem;\n  - Network traffic control;\n  - TCP network protocol;\n  - io_uring subsystem;\n  - Perf events;\n  - Locking primitives;\n  - Hibernation control;\n  - Timer subsystem;\n  - BPF subsystem;\n  - Floating proportions library;\n  - Bluetooth subsystem;\n  - CAN network layer;\n  - Ceph Core library;\n  - Networking core;\n  - IPv6 networking;\n  - L2TP protocol;\n  - MAC80211 subsystem;\n  - Multipath TCP;\n  - NET/ROM layer;\n  - RxRPC session sockets;\n  - SCTP protocol;\n  - SMC sockets;\n  - VMware vSockets driver;\n  - Wireless networking;\n  - ALSA AC97 driver;\n  - Creative Sound Blaster X-Fi driver;\n  - Texas InstrumentS Audio (ASoC/HDA) drivers;\n  - USB sound devices;\n(CVE-2025-71158, CVE-2025-71160, CVE-2025-71161, CVE-2025-71162,\nCVE-2025-71163, CVE-2025-71180, CVE-2025-71182, CVE-2025-71183,\nCVE-2025-71184, CVE-2025-71185, CVE-2025-71186, CVE-2025-71187,\nCVE-2025-71188, CVE-2025-71189, CVE-2025-71190, CVE-2025-71191,\nCVE-2025-71192, CVE-2025-71193, CVE-2025-71194, CVE-2025-71195,\nCVE-2025-71196, CVE-2025-71197, CVE-2025-71198, CVE-2025-71199,\nCVE-2025-71200, CVE-2025-71201, CVE-2026-22976, CVE-2026-22977,\nCVE-2026-22978, CVE-2026-22979, CVE-2026-22980, CVE-2026-22981,\nCVE-2026-22982, CVE-2026-22985, CVE-2026-22986, CVE-2026-22987,\nCVE-2026-22989, CVE-2026-22990, CVE-2026-22991, CVE-2026-22992,\nCVE-2026-22993, CVE-2026-22994, CVE-2026-22996, CVE-2026-22997,\nCVE-2026-22998, CVE-2026-22999, CVE-2026-23000, CVE-2026-23001,\nCVE-2026-23002, CVE-2026-23003, CVE-2026-23004, CVE-2026-23005,\nCVE-2026-23006, CVE-2026-23007, CVE-2026-23008, CVE-2026-23009,\nCVE-2026-23010, CVE-2026-23011, CVE-2026-23012, CVE-2026-23013,\nCVE-2026-23014, CVE-2026-23015, CVE-2026-23017, CVE-2026-23018,\nCVE-2026-23019, CVE-2026-23020, CVE-2026-23021, CVE-2026-23022,\nCVE-2026-23023, CVE-2026-23024, CVE-2026-23025, CVE-2026-23026,\nCVE-2026-23030, CVE-2026-23031, CVE-2026-23032, CVE-2026-23033,\nCVE-2026-23034, CVE-2026-23035, CVE-2026-23036, CVE-2026-23037,\nCVE-2026-23038, CVE-2026-23042, CVE-2026-23044, CVE-2026-23045,\nCVE-2026-23046, CVE-2026-23047, CVE-2026-23049, CVE-2026-23050,\nCVE-2026-23051, CVE-2026-23052, CVE-2026-23053, CVE-2026-23054,\nCVE-2026-23055, CVE-2026-23056, CVE-2026-23057, CVE-2026-23058,\nCVE-2026-23059, CVE-2026-23061, CVE-2026-23062, CVE-2026-23063,\nCVE-2026-23064, CVE-2026-23065, CVE-2026-23066, CVE-2026-23067,\nCVE-2026-23068, CVE-2026-23069, CVE-2026-23070, CVE-2026-23071,\nCVE-2026-23072, CVE-2026-23073, CVE-2026-23075, CVE-2026-23076,\nCVE-2026-23077, CVE-2026-23078, CVE-2026-23079, CVE-2026-23080,\nCVE-2026-23081, CVE-2026-23083, CVE-2026-23084, CVE-2026-23085,\nCVE-2026-23086, CVE-2026-23087, CVE-2026-23088, CVE-2026-23089,\nCVE-2026-23090, CVE-2026-23092, CVE-2026-23093, CVE-2026-23094,\nCVE-2026-23095, CVE-2026-23096, CVE-2026-23097, CVE-2026-23098,\nCVE-2026-23099, CVE-2026-23100, CVE-2026-23101, CVE-2026-23102,\nCVE-2026-23103, CVE-2026-23104, CVE-2026-23105, CVE-2026-23106,\nCVE-2026-23107, CVE-2026-23108, CVE-2026-23109, CVE-2026-23110,\nCVE-2026-23113, CVE-2026-23114, CVE-2026-23115, CVE-2026-23116,\nCVE-2026-23118, CVE-2026-23119, CVE-2026-23120, CVE-2026-23121,\nCVE-2026-23122, CVE-2026-23123, CVE-2026-23124, CVE-2026-23125,\nCVE-2026-23126, CVE-2026-23128, CVE-2026-23129, CVE-2026-23130,\nCVE-2026-23131, CVE-2026-23133, CVE-2026-23135, CVE-2026-23136,\nCVE-2026-23137, CVE-2026-23138, CVE-2026-23139, CVE-2026-23140,\nCVE-2026-23141, CVE-2026-23142, CVE-2026-23143, CVE-2026-23144,\nCVE-2026-23145, CVE-2026-23146, CVE-2026-23147, CVE-2026-23148,\nCVE-2026-23150, CVE-2026-23151, CVE-2026-23152, CVE-2026-23154,\nCVE-2026-23156, CVE-2026-23157, CVE-2026-23158, CVE-2026-23159,\nCVE-2026-23160, CVE-2026-23161, CVE-2026-23162, CVE-2026-23163,\nCVE-2026-23164, CVE-2026-23165, CVE-2026-23166, CVE-2026-23167,\nCVE-2026-23168, CVE-2026-23169, CVE-2026-23170, CVE-2026-23171,\nCVE-2026-23172, CVE-2026-23173, CVE-2026-23212, CVE-2026-31405,\nCVE-2026-31414, CVE-2026-31444, CVE-2026-31501, CVE-2026-31589,\nCVE-2026-31633, CVE-2026-31636, CVE-2026-31705, CVE-2026-43198,\nCVE-2026-43379, CVE-2026-43465, CVE-2026-43499, CVE-2026-46113,\nCVE-2026-46137, CVE-2026-46242, CVE-2026-46290, CVE-2026-46317,\nCVE-2026-46331, CVE-2026-52924, CVE-2026-52989, CVE-2026-53086,\nCVE-2026-53131, CVE-2026-53176, CVE-2026-53212, CVE-2026-53225,\nCVE-2026-53228, CVE-2026-53277, CVE-2026-53359)\n","status":"published","published":"2026-08-21T19:59:28Z","modified":"2026-11-06T13:49:11.551849356Z","updated_at":"2026-11-06T14:26:46.957794Z"}]}}